FAILED! Cannot enter Test Mode of PSoC6 device: CPU stopped at wrong address

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

cross mob
UrPl_1236626
Level 4
Level 4
10 likes given First solution authored 50 replies posted

Hi,

on one board with the CY8C6247BZI-D34 we face a strange error report from MiniProg3:

| FAILED! Cannot enter Test Mode of PSoC6 device: CPU stopped at wrong address (0x100001AA).

                                                                   | Please, check the following items:

                                                                   |  - the connection between the programmer and the PSoC;

                                                                   |  - the correct programming protocol is selected;

                                                                   |  - the correct connector option is selected.

The only thing it happened meanwhile is that USB - UART was connected to the same pins, if that possibly damaged the device; but if there is no connection to the device then the error is typically different to the one above.

BR Uros

0 Likes
1 Solution

Hi UrPl_1236626,

As you have mentioned the device might have been damaged or the memory might also be corrupted due to ESD. If fluctuations in power supply or ESD occurs during a memory access operation, it might also corrupt the memory and thus cannot be accessed to enter Test Mode.

Please refer to the PSoC 6 datasheet and ensure that the ESD is within the ratings provided and ESD protection is provided to your device.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B

View solution in original post

0 Likes
5 Replies
Rakshith
Moderator
Moderator
Moderator
250 likes received 1000 replies posted 750 replies posted

Hi UrPl_1236626​,

There might be many reasons that you are getting this error including issue with the hardware schematic/layout design issue. Can you please verify the hardware schematic with the design guidelines in the PSoC 6 MCU Hardware Design Considerations?

Also please ensure that you are using a very short SWD connector between MiniProg3 and the device (ideally 5cm).

The only thing it happened meanwhile is that USB - UART was connected to the same pins, if that possibly damaged the device;

Can you please provide more information regarding this? Were you able to program the device anytime before? Was a supply greater than 3.6V connected to any pin of the device?

if there is no connection to the device then the error is typically different to the one above.

Yes, you should be getting the error -  'Failed to acquire the device'.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B
0 Likes

Hi Rakshith,

It is about the board which is was working and then single core was replaced with dual core as currently you do not support bootloader on single core devices.

Now we again replaced the device and looks like it was a kind of partly damaged by the ESD, as now it works. So it would be good to understand what is behind this "error message"

BR Uros

0 Likes

Hi UrPl_1236626​,

The error message says that the device could not enter Test mode (programming mode). Test mode prevents the execution of the firmware in the device. You can find more information regarding Test mode in Section 5.3,  Step 1.A – Acquire PSoC 6 MC, page 30, in the following document - PSoC® 6 MCU Programming Specifications.

Also, please ensure that your hardware design matches with the guidelines in the hardware design considerations. We have seen that this error is displayed generally when there is an issue with the custom board design.

Can you also let me know the programming frequency that you are using?

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B
0 Likes

Hi Rakshith,

We have tried all frequencies even down to 1.5 MHz but it didn't work.

So to sum up:

  • single core chip was always OK
  • replaced single chip with dual core, was OK
  • then UART TTL was connected to the same pins, (we didn't provide extra ESD protection on the JTAG port, it's for sure our mistake)
  • after it didn't work,
  • replaced dual core chip again, is still OK

So this points out a possible ESD event, but still it's interesting that error message is so "strange".

Best regards,
Uros

0 Likes

Hi UrPl_1236626,

As you have mentioned the device might have been damaged or the memory might also be corrupted due to ESD. If fluctuations in power supply or ESD occurs during a memory access operation, it might also corrupt the memory and thus cannot be accessed to enter Test Mode.

Please refer to the PSoC 6 datasheet and ensure that the ESD is within the ratings provided and ESD protection is provided to your device.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B
0 Likes