LPC55S16-EVK can't flash and debug firmware directly from the MCUXpressoIDE

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

LPC55S16-EVK can't flash and debug firmware directly from the MCUXpressoIDE

Jump to solution
576 Views
evgreen
Contributor I

Hi.

I am looking for help to be able to flash and debug firmware directly from the MCUXpressoIDE.

I am trying to flash and debug the led_blink example from the SDK. Previously on this board, I flashed a firmware with secure boot keys and that process works, I can flash the led_blink example firmware using the manufacturing_package.zip:

evgreen_0-1709830527068.png

To be able to flash and debug using the MCUXpressoIDE, I disabled the secureboot on CMPA as also I keep the swd debug enable:

evgreen_2-1709830782435.png

However, on MCUXpressoIDE, when I try to debug, seems that the firmware is flashed but the process fails right after - here the output:

evgreen_3-1709830908933.png

evgreen_4-1709831058251.png


I also verified I can debug if I select the "attach to a running target", but this way I am forced to build and flash a manufacturing_package.zip each time I change the firmware...

evgreen_5-1709832300236.png

0 Kudos
Reply
1 Solution
415 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @evgreen 

"I disabled the secureboot on CMPA as also I keep the swd debug enable:"

->> Please read back the CMPA value, compare it with default CMPA.

 

BR

Alice

View solution in original post

0 Kudos
Reply
2 Replies
416 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @evgreen 

"I disabled the secureboot on CMPA as also I keep the swd debug enable:"

->> Please read back the CMPA value, compare it with default CMPA.

 

BR

Alice

0 Kudos
Reply
383 Views
evgreen
Contributor I

Hi Alice.

After writing, when I click on the Read button, it always shows as disabled as expected (as seen on the image). But then I tested to restart again this process and verified that in fact it is locked again....

Anyway, the debug now works!! I did a few power resets and the debug always work -- problem solved, thank you.


Screenshot from 2024-03-21 11-04-08.png

0 Kudos
Reply