**** Advance Notice ****

This site will be closed on 31 December 2015,

Important Information for users of NXP LPCXpresso

This site is for users of Code Red branded products.

NXP LPCXpresso users should visit the LPCXpresso FAQ's for up-to-date information relevant to that product.

LPC8xx Flash programming fails after using MTB instruction trace

In Code Red IDE v5.1.2 and earlier, there is an issue with the MTB not being disabled correctly when a debug session where instruction trace has been carried out is terminated. This may lead to flash programming problems the next time you try to start a new debug connection to the board, with an error message such as:

Flash driver "EraseSector" return code: 0x3
15: Target error from Commit Flash write: Ef(38). Flash operation has returned an error (see log).

or

Flash driver "EraseSector" timeout (3000 ms)  PC: FFFFFFFE
15: Target error from Commit Flash write: Ef(31). Timed-out erasing flash.

or

Flash driver "EraseSector" return code: 0xFFFFFFFD
Flash driver "UnInit" return code: 0xFFFFFFFE
15: Target error from Commit Flash write: Ef(38). Flash operation has returned an error (see log).

The simplest way to avoid this is either by doing a full reset of the board before connecting again, or else setting the "vector catch" option to "true" in the launch configuration.

NOTE - In Code Red IDE v5.2.2 and later, the launch configuration for LPC800 targets will default to having the "vector catch" option set to "true", such that this problem should not be seen.

LPC8xxFlashFailMTB (last edited 2013-04-19 23:52:30 by CrSupportAb)