Unable to Flash or Debug

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unable to Flash or Debug

Jump to solution
1,014 Views
Kolibri
Contributor III

Hello i´m working with the FRDM-K32L3A6 Freedom Development Board,

i just wanted to use some GPIO Pins but i´ve inadverently programmed J7[6] and J7[4] as GPIO Input/Outputs, now i´m unable to flash the board again. I´ve set everything back like it was before, tried to flash the hello world example, tried to use the gui flash tool, made an mass erase, activate sysresreq. Nothing helps there´s always this error message:

Executing flash operation 'Resurrect locked Kinetis device' (Resurrect locked Kinetis device) - Mon Jun 20 16:40:38 CEST 2022
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.5 (Dec 16 2021 12:38:31 - crt_emu_cm_redlink.exe build 2)
( 0) Reading remote configuration
Wc(03). No cache support.

 

MCUXpresso IDE RedlinkMulti Driver v11.5 (Dec 16 2021 12:38:31 - crt_emu_cm_redlink build 2)
Found chip XML file in C:/MCUXpresso_Workspace/frdmk32l3a6_hello_world_demo_cm4/Debug\K32L3A60xxx.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
Connecting to probe 1 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
Reconnected to existing LinkServer process.
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
============= SCRIPT: K32L3Aconnect.scp =============
K32L3A M4 Connect Script
Connecting to Probe Index = 1
Error: Probe not connected
Error: Wire Ack Fault - target connected?
Assert NRESET
Reset pin state: 00
Error: Wire not connected
Power up Debug
Error: Wire not connected
Error: Wire not connected
No Debug Power
============= END SCRIPT ============================
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port

 

What can i do to reset the board and to flash it again. I think theres a problem because these pins are something for SWD.

Thanks for you´re help.

0 Kudos
1 Solution
999 Views
diego_charles
NXP TechSupport
NXP TechSupport

Hi @Kolibri 

I hope you are doing great. 

Please try to :

1 disconnect your board.

2 Press (and maintain pressed) SW2.

3 Connect board.

4 Release SW2.

5 Attempt to debug or program.

SW2 is connected to the default BOOT_pin of the MCU. If during boot process the BOOT_pin is sampled low the  ROM bootloader will be executed by default, instead your application. Thus we have the chance to regain debug access.

Please let me know your results.

All the best, 

Diego.

View solution in original post

0 Kudos
2 Replies
1,000 Views
diego_charles
NXP TechSupport
NXP TechSupport

Hi @Kolibri 

I hope you are doing great. 

Please try to :

1 disconnect your board.

2 Press (and maintain pressed) SW2.

3 Connect board.

4 Release SW2.

5 Attempt to debug or program.

SW2 is connected to the default BOOT_pin of the MCU. If during boot process the BOOT_pin is sampled low the  ROM bootloader will be executed by default, instead your application. Thus we have the chance to regain debug access.

Please let me know your results.

All the best, 

Diego.

0 Kudos
994 Views
Kolibri
Contributor III

Hi diego_charles,

Thanks for the quick reply, it worked! I am able to flash and debug it again.