LPC Flash Target marked as not debuggable LPC1833

[jverscheure]

Hello,

I am having trouble to flash my LPC 1833JET.

Due to chip availability, I had to use NXP1833 instead of NXP1837. My producer send me a test with new chip to test and this was working without changing anything.

I now received a new batch and I got following error

Program flash

crt_emu_cm_redlink -flash-load-exec "S:\RnD\ELEKTRONICA\#SYX\UIFE\FW\UIFE V3.xx\UIFEV3-72r.axf" -g -2 -vendor=NXP -
pLPC1837 -ConnectScript=LPC12XXConnect.scp -reset=vectreset -flash-driver=LPC18x7_43x7_2x512_BootA.cfx

Detailed info

Ni: LPCXpresso RedlinkMulti Driver v8.2 (Sep 5 2016 10:12:38 - crt_emu_cm_redlink.exe build 725)
Pc: ( 0) Reading remote configuration
Pc: ( 5) Remote configuration complete
Wc: ============= SCRIPT: LPC12XXConnect.scp =============
Wc: LPC12XX Connect Script
Wc: DpID = 2BA01477
Wc: APID = 0x24770011
Wc: Status fail
Wc: ============= END SCRIPT =============================
Xe:
Nc: Probe Firmware: LPC-LINK2 CMSIS-DAP V5.182 (NXP Semiconductors)
Nc: Serial Number: JXBUN1AU
Nc: VID:PID: 1FC9:0090
Nc: USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&2a0728ba&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Nc: CM3/4 debug bus (DP 0x2BA01477 MemAP[0] 0x04770011) SWD connection failed - 'Em(01). Cannot find selected MEM-AP (check targ¼Ho÷Ð"
Nc: connection failed - Ep(01). Target marked as not debuggable. - retrying
Nc: CM3/4 debug bus (DP 0x2BA01477 MemAP[0] 0x04770011) SWD connection failed - 'Em(01). Cannot find selected MEM-AP (check targ¬Ho÷À"
Wc: Vector catch on VECTRESET signal
Nc: Debug bus check after stop (MemAP 0x4770011) FAILS - Em(02). MEM-AP is not selected.
Ed:02: Failed on connect: Ep(01). Target marked as not debuggable.
Et: Emu(0): Connected&Reset. Was: NotConnected. DpID: 00000000. CpuID: 00000000. Info: <None>
Nc: Last stub error 0: OK
Nc: Last sticky error: 0x0 AIndex: 0
Nc: No debug bus (MemAp) selected
Nc: DAP Speed test unexecuted or failed
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Pc: (100) Target Connection Failed

is there something I can do about this?

[jverscheure]

hello,

I did made a new project to flash. Same problems. the reason for LPC12XX in my logfile is becasue of a connect script.

I am using following script in it. Should that be different for the LPC 1833? Again, I had no problems using LPC 1837 and suddenly, it worked after a lot of retry. But when I take a new board, same issue appaers.

Script I am using :

10 rem ---------------------------------
20 print "LPC12XX Connect Script"
30 rem ---------------------------------
40 rem probelist
50 p% = probefirstfound
60 rem probeopenbyindex p%
70 wireswdconnect p%
80 selectprobecore p% 0
90 cminitapdp this
100 cmhalt this
110 cmwatchset this 0 0x40048000 W
120 cmresetvectorcatchclear this
130 cmsysresetreq this
140 qpoke32 this 0x40004000 0x00
150 qpoke32 this 0x40004008 0xAA
160 qpoke32 this 0x40004008 0x55
170 qstarttransfers this 0
180 rem ---------------------------------
190 rem Watchdog MOD Register
200 rem ---------------------------------
210 rem m% = peek32 this 0x40004000
220 rem print "MOD = "; ~m%
230 cmwatchclear this 0
240 rem cmresetvectorcatchset this
250 rem ---------------------------------
260 end

When using debug I got following error :

Error in final launch sequence
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=51939 -g -mi -4 -pLPC1833 -vendor=NXP -ResetScript=LPC18LPC43InternalFLASHBootResetscript.scp -reset=VECTRESET -ProbeHandle=1 -CoreIndex=0 -flash-driver=LPC18x3_43x3_2x256_BootA.cfx
Error message from debugger back end:
Remote communication error. Target disconnected.: No error.
Remote communication error. Target disconnected.: No error.

where can I change the used resetscript? Maybe that's an issue because I use now LPC 133 instead of LPC 1837 (more memory, but I do not need it)

[ZhangJennie]

Do you use MCUXpresso IDE? Which version?

This error is on a new created project setting without any modification?

Could you please record a screen video of how to reproduce your problem?

Thanks,

Jun Zhang

[ZhangJennie]

Hi jverscheure 

You use LPC1833 board. But I see LPC12XXin your log file.

Please create a new workspace to avoid old associations. then follow attached video to create a new LPC1833 project to test the connection again.

Have a nice day,

Jun Zhang