FAQs
English (US) 日本語 | Japanese 中文 | Chinese (Simplified)

MPC5606B update app. via bootloader leads to MCU lock

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MPC5606B update app. via bootloader leads to MCU lock

‎01-08-2019 06:15 AM
521 Views
dannydeng
Contributor III

Dears,

We found some MPC5606B  chip locked which means I cannot connect via U-Multilink and update app. again, while I update app. failure. Can you help to advice?

BRs,

Ray Deng

0 Kudos
Reply
2 Replies

‎01-13-2019 06:30 AM
359 Views
dannydeng
Contributor III

Thanks, Lukas.

0 Kudos
Reply

‎01-09-2019 11:49 PM
359 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

there’s only one thing which can cause such troubles - have you modified shadow flash memory during app update? Shadow flash contains censorship information. If the shadow flash is erased, it is necessary to program the censorship control words appropriately (before next reset) otherwise the chip will be locked forever. And there’s no way to recover in this case.

The only way to recover is to have some code already loaded to MCU which checks the censorship information and which restores it if necessary (that means with no JTAG debugger intervention). But such code must be loaded to flash BEFORE(!) the chip is locked.

We have two examples here on community:

https://community.nxp.com/docs/DOC-102582

https://community.nxp.com/docs/DOC-332307

It shows how to erase the shadow flash and how to program censorship information back to shadow flash. There’s also shown how to unlock the chip using a debugger and known password.

Regards,

Lukas

Reply