Need advice: Can't flash and debug with LPCXpresso.

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

Need advice: Can't flash and debug with LPCXpresso.

2,445 Views
herusetiawan
Contributor II

Today, I just get error when flashing (use Program Flash) and debugging. below is the error message:

I use: LPC812 Max Board, LPCXpresso v8.2.2 [Build 650] [2016-09-09] Software.

LPCXpresso RedlinkMulti Driver v8.2 (Sep  5 2016 10:12:38 - crt_emu_cm_redlink build 725)
Failed on connect: Ee(36). Could not connect to core.
No connection to emulator device.

Any advice? Last week ago, I have successfully debug or flash, I have try to change another usb port, change cable, restart pc, reinstall lpcxpresso. but sadly the problem still have.

Thanks.

Labels (2)
0 Kudos
3 Replies

1,839 Views
herusetiawan
Contributor II

Problem is solved.

Thanks for your support

0 Kudos

1,839 Views
lpcxpresso_supp
NXP Employee
NXP Employee

In the first place, try powering your board up in ISP mode before trying to start your debug connection:

Regards,

LPCXpresso Support

0 Kudos

1,839 Views
herusetiawan
Contributor II

Thanks for your advice,

But the problem still not solved.

1. I have try install with another pc, but still fail

2. untick Window > Preferences > LPCXpresso > Redlink Options > Pull ISP on reset (on LPC-Link 2), but still fail

3. Add the script "ISPResetConnect.scp" to the "CMSIS-DAP Options - Connect Script" box within the dialog, but still fail

4. use lpc link2, jumper jip1 on lpc812 max, connect j7 (lpc link2) to p3(lpc812 max), but still fail

5. connect p0_1 (lpc max) to ground, reset, disconnect p0_1, but still fail

Any other step that I missed? or my lpc812 max is damage? hopefully not....

Pls see debug log:

Ns: MCUXpresso RedlinkMulti Driver v10.1 (Nov  9 2017 16:45:39 - crt_emu_cm_redlink.exe build 360)
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.

0 Kudos