AnsweredAssumed Answered

Cannot mass erase K64 by Mcuxpresso and LPC-link2

Question asked by HAIZHOU LI on Apr 25, 2018
Latest reply on Apr 27, 2018 by HAIZHOU LI

I use the exact same PCB that can be mass erased when using KDS + P&Emicro.

 

Now I switched the debug setup to mcuxpresso + LPC-link2, while, I cannot mass erase the MCU.

 

Here is what I did.

1.  I went to startup_mk64f12.c and changed the flash_config 

From

Flash_Config = {0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFE};

to

Flash_Config = {0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFB};

 

2.  Program the new compile axf into the MCU. 

 

3. I clicked the "Linkserver GUI flash programmer" icon on the menu bar and chose the LPC-LINK2

 

4. I chose the following setup

 

5, When I chose OK, it showed an error msg:

 

the next page after clicking the "OK" is

 

the full msg log is:

 

Ns: MCUXpresso RedlinkMulti Driver v10.0 (Jun 22 2017 23:34:07 - crt_emu_cm_redlink build 272)
Pc: ( 0) Reading remote configuration
Wc(03). No cache support.
Pc: ( 5) Remote configuration complete
Nc: Reconnected to existing redlink server (PID 4294967295)
Nc: Connecting to probe 1 core 0 (server PID unknown) gave 'Ee(36). Could not connect to core.'
Nc: Connecting to probe 1 core 0 (server PID unknown) gave 'Ee(36). Could not connect to core.'
Nc: Connecting to probe 1 core 0 (server PID unknown) gave 'Ee(36). Could not connect to core.'
Nc: Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(36). Could not connect to core.
Ed:02: Failed on connect: Ee(36). Could not connect to core.
Et:31: No connection to chip's debug port
Pc: (100) Target Connection Failed
Nc: error closing down debug session - Em(02). MEM-AP is not selected

 

------------------------------------------------

 

In the step 4, there is a warning msg:  image file '' not found 

I dont know what "the image file" here means. Then even I tried to load an axf file, it still shows such msg. 

 

Thanks in advance!

Outcomes