chip programming error

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
eeEn_4618901
Level 4
Level 4
5 likes given First like received First like given

Hi, I am trying to load the chip into a new circuit with miniprog3. It gives the following errors. EraseAll Finished at 00:16:08                              |                                                             | FAILED! EraseAll operation failed!                                                             | Timeout of SPC polling. Lost communication with chip (Status = 0x22) Program Finished at 00:09:30                                |                                                             | FAILED! Timeout of SPC polling. Lost communication with chip (Status = 0x82)                                                             | Programming of Flash Starting...                                                             | Erase Succeeded Device set to CY8C5888LTI-LP097 at 00:09:26                | 262144  FLASH bytes Device Family set to CY8C5xxxLP at 00:09:26                |                                                         | Automatically Detected Device: CY8C5888LTI-LP097                                                             | JtagID: 2E 16 10 69 Program Requested at 00:09:25                              | Successfully Connected to MiniProg3/1343DD00057F at 00:09:16 | MiniProg3 version 2.05 [3.11/2.10] Opening Port at 00:09:16                                    | Memory Types Load from HEX Finished at 00:09:16            | Device set to CY8C5888LTI-LP097 at 00:09:15                | 262144  FLASH bytes Device Family set to CY8C5xxxLP at 00:09:15                | Memory Types Load from HEX Requested at 00:09:15            |

0 Likes
1 Solution
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Dear eeEn-san,

So those two were all I could find.

And as you stated, one is working and the other is not, means

I'm afraid that the "not working one" could be damaged.

As I might have written, there is also a chance that some solder bridge etc

is laying under the device where you can not see.

But anyway, IMHO, I would try replace the deivce.

Best Regards,

1-May-2020

Motoo Tanaka

View solution in original post

0 Likes
10 Replies
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Hi,

It seems that the first "Erase All" failed.

Off my head this can be

(1) The board is not powered up or not stable by some reason(s)

(2) The connection between MiniProg3 and the board is not stable

(3) The device is protected

Please double check the power and other settings of the board

and the connection between the board and MiniProg3.

moto

0 Likes

Hi, The programmer detects and finds the chip. Then it gives an error. I wonder if I sold the chip too much while soldering? "(2) The connection between MiniProg3 and the board is not stable" I think the connection is OK. How can I fix this "(3) The device is protected"? Best Regards

0 Likes
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Hi,

> The programmer detects and finds the chip.

This is the good news.

> Then it gives an error.

And this is the bad news.

So assuming the connection is OK, I could imagine

(1) Device is write protected

(2) Device is damaged

If (2) is the case, the only option would be replacing the device.

But before trying it, I would try to erase the device using the PSoC Programmer.

Meantime, please use a magnifying glass to double check if there is/are any solder bridges around the device.

Please download PSoC Programmer from the following URL and try.

(I'd recommend you to use the newest one)

https://www.cypress.com/documentation/software-and-drivers/psoc-programmer-archive

And if even PSoC Programmer can not erase/program the device,

may be you need to consider the case that device is damaged somehow.

Best Regards,

28-Apr-2020

Motoo Tanaka

Rakshith
Moderator
Moderator
Moderator
250 likes received 1000 replies posted 750 replies posted

Hi eeEn_4618901​,

Adding to MoTa_728816​ response, please also confirm that your hardware schematic and layout design meets all the guidelines mentioned in the PSoC 5 Hardware Design Considerations. document. We have observed this error in certain cases where SWD communication does not meet the timing constraints. The best way to detect any issue with the PCB is by doing a swap test as suggested in the previous comment.

Please let us know your observations.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B

Hi Moto-san,

What can I do when the device protects itself?

Ekran Alıntısı.JPG

Best Regards.

0 Likes
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Hi,

Can you check the Flash Security in the Design Wide Resources of PSoC Creator?

You may have accidentally protected the flash.

000-FlashSecurity.JPG

moto

0 Likes

Hi,

Ekran Alıntısı.JPG

0 Likes
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Hi,

So there is no protected area in the flash?

And still you get the error about protection?

I have just found "Enable Device Protection" in the DWR > System, could you check it, too?

001-EnableDeviceProtection.JPG

moto

0 Likes

Hi, DWR is not selected. there are 2 of the same circuit. 1 of them is working 1 of them is not working. Could there be a problem with the chip? I actually used a temperature-controlled soldering iron to solder the chip. Should I replace the chip? Best Regards.

0 Likes
MotooTanaka
Level 9
Level 9
Distributor - Marubun (Japan)
First comment on blog Beta tester First comment on KBA

Dear eeEn-san,

So those two were all I could find.

And as you stated, one is working and the other is not, means

I'm afraid that the "not working one" could be damaged.

As I might have written, there is also a chance that some solder bridge etc

is laying under the device where you can not see.

But anyway, IMHO, I would try replace the deivce.

Best Regards,

1-May-2020

Motoo Tanaka

0 Likes