Unable to flash/debug LPC55S69 E1

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to flash/debug LPC55S69 E1

456 Views
blarg1
Contributor I

Following this guide

I load up the lpcxpresso55S69 exampled called led_blinky.

When clicking "Debug" on the Quickstart panel, the following errors show up:

blarg1_1-1664833395846.png

blarg1_2-1664833420596.png

blarg1_4-1664833444527.png

blarg1_5-1664833455676.png

Here's the console output:

blarg1_6-1664833517133.png

MCUXpresso version:

blarg1_7-1664833552637.png

This is the installed SDK:

blarg1_8-1664833608174.png

I have already reinstalled MCUXpresso and the SDK, tried several different ports on my PC, different USB cables, and had no luck. I tested with another PC and I was able to flash and debug successfully so it is not the board.

0 Kudos
11 Replies

367 Views
danielholala
Senior Contributor I

I tested with another PC and I was able to flash and debug successfully so it is not the board.

So obviously it's your PC. And you are not alone.

What is different with your PC compared to the other PC where the probe works (windows version)? Was the installation process performed differently (e.g, did you install all drivers, did you "grant access" that was requested)?

I suggest to try again with the recently released MCUXpresso IDE V11.6.1.

Further, you could switch PCs. 🤷‍

If nothing works, I'd suggest to switch to a Segger J-Link debug probe.

0 Kudos

344 Views
blarg1
Contributor I

Working PC:

Company PC, Windows 10

Not Working PC:

Personal PC, Windows 11 

The installation process was the same, same version, I allowed all drivers to be installed, and installation was performed on admin accounts.

Yesterday I tried with the newer version of the IDE and had the exact same issues.

Yeah, at least I got it working on one PC and if all else fails I'll use that in the meantime, I just hoped there was a solution to this but oh well.

Thanks!

0 Kudos

436 Views
Pavel_Hernandez
NXP Employee
NXP Employee

Hello, 

I test on my side, but I could not replay your issue, could you try to erase the flash?  

Pavel_Hernandez_0-1665007517043.png

Are you using the USB port with the label Debugger? Is the LED turned on when you put the USB cable? Did you do some modifications to the code? Do you have any connection in the pins of the board?

Best regards,
Pavel

0 Kudos

429 Views
blarg1
Contributor I

could you try to erase the flash?

It doesn't work, posting screenshots:

blarg1_0-1665092071385.pngblarg1_1-1665092107910.pngblarg1_2-1665092122383.png

 

Are you using the USB port with the label Debugger? 

Yes, I'm using the DEBUG USB port.

Is the LED turned on when you put the USB cable?

Yes the Power LED is on when plugged in.

Did you do some modifications to the code?

No, the code is as is when following the guide, I'm attaching the project 

Do you have any connection in the pins of the board?

No, I only have the USB cable connected to the board, no other cables is connected or mounted on the board.

0 Kudos

416 Views
Pavel_Hernandez
NXP Employee
NXP Employee

Hello, 

Ok, maybe the MCU is in the brick state, for getting out of that state needs to enter ISP mode and do a mass erase of the flash.

Pavel_Hernandez_2-1665158261037.png

Without any USB cable please push down the button of ISP SW03 (PIO0_5), then connect the USB cable in Debug+Power, then when the device is powered release the button ISP.

Then in the IDE again try to do a mass erase.

Pavel_Hernandez_3-1665158418183.png

Best regards,
Pavel

 

 

0 Kudos

403 Views
blarg1
Contributor I

I still have errors:

blarg1_0-1665180715799.pngblarg1_1-1665180735867.pngblarg1_2-1665180754985.png

 

0 Kudos

356 Views
Pavel_Hernandez
NXP Employee
NXP Employee

Hello,

Sorry, I forgot 1 step could you review again the last response, and do it?

Best regards,
Pavel

0 Kudos

345 Views
blarg1
Contributor I

Hello, 

I tried with the updated instructions and still had no luck, I got the same errors.

As other poster suggested, I installed the newer version and I still got the same issue.

0 Kudos

202 Views
brendonslade
NXP TechSupport
NXP TechSupport

Hi,

There is some confusion on this thread because it references both the lpcxpresso55s69 (the standard NXP EVK) and in the subject and in some other places it refers to the OKdo LPC55S69 E1 board. I'm guessing you are using the E1.

The E1 board has the LPC11u35 based debug probe, so isn't supported by LPCScrypt (which is for the LPC-Link2 type debug probe.) I dont have an E1, but what I describe below should work.

First step is to check if MCUXpresso IDE detects the debug probe when it starts a debug session. This is called "probe discovery" ... you should see a dialog appear showing the probes that the system can see, which should be an LPC11U35 probe in this case. If you see that, then the problem is probably down to the system not being able to get debug control of the target LPC55S69 device. Skip this next part in blue if probe discovery shows the LPC11U35 probe. Looking at the errors, it seems the IDE did already find a probe and you dont need to mess with the firmware, but I'm going to leave the info below for the benefit of others who read this thread

OKdo use (basically) the same firmware as NXP's LPC11u35, which we use on our LPC800 series boards. It is a basic DAP-Link implementation by Arm, with a VCOM (UART); note that it is not OpenSDA based. A few steps to try if MCUXpresso IDE doesn't see your probe:

  • Open Windows Device Manager then plug in the board and see if a VCOM port appears. If it does then its likely that the firmware is up and running, so skip the next part (debug firmware update)
  • Debug firmware update:
    Open a file manager window. Unplug your board, then hold down the reset button on the E1 while reconnecting. This should place the LPC11U35 into firmware update mode, and your should see a drive appear with the name CRP_DISABLED appear in the file manager. Go to that drive and delete the file there, then drag and drop the firmware.bin file into the CRP_DISABLD drive to update the firmware, then power cycle. You could use the firmware we use for LPC800 boards with the same debugger - but I cannot guarantee this will work (as I cant test it): https://cache.nxp.com/downloads/en/emulators-probes/LPC11Uxx-Debug-Probe-VCOM.zip

The LPC55S69 boot ROM is intended to be secure, its possible that an application can boot and prevent debug from attaching. It can also happen if the code is in a very tight loop. The best way to recover from this is to put the part into ISP mode by holding down then ISP button while pressing and releasing the reset button. After doing that try the debug session again. If this doesn't work try holding down ISP while power cycling the board, then retry your debug session (this is because a pin level reset wont reset absolutely everything in the device - details are in the device manual). When you place the LPC55S69 in ISP mode it is sitting in a loop waiting for an in-system programming operation to start, and will respond to a debug request. You can also try using the mass erase feature in the Quickstart panel to remove any troublesome code, preferably after doing the power-cycle type ISP mode entry.

 

Hope that helps.

0 Kudos

191 Views
blarg1
Contributor I

Hi Brendon, thanks for the reply,

Actually, I can see the probe: 

blarg1_0-1666821653023.png

And as you mentioned, it also shows up on Device Manager:

blarg1_1-1666821736785.png

But it shows the same errors, even on ISP mode, I flashed the blinky app on another PC and I can see that on ISP mode the LED is not blinking, but I can't seem to flash or erase it.

0 Kudos

328 Views
Pavel_Hernandez
NXP Employee
NXP Employee

Hello,

It seems like the LPC11[debugger] is in brick mode. You need to update the firmware with another debugger using LPCscrypt. 

LPCScrypt v2.1.2 | NXP Semiconductors 
LPCXpresso55s69 update to OpenSDA - NXP Community

Best regards,
Pavel

0 Kudos