Unable to save flash image from target board with MCULink probe W10, Linkserver 26.9.130, MCULink FW 3.174: I want to save a flash image from a LPC804 board using SWD. I have the MCULink probe, I installed the Linkserver package which includes the LinkFlash tool. With this I was able to update the MCULink FW to the latest. Using the LinkFlash GUI I am not able to save the flash image from my target board due to a "Failed on Connect (Ee42)". No probe jumpers are placed (SWD). I have selected "LPC804:" as a device, but I noticed in other examples a more complete part# and an IDE is usually named. Do I need to create a configuration file or install an IDE such as Expresso to get past this, or is it more likely to be cabling and target connection issue? Ns: LinkServer RedlinkMulti Driver v26.9 (Sep 18 2026 19:34:33 - crt_emu_cm_redlink.exe build 1382) Pc: ( 0) Reading remote configuration Wc(03). No cache support. Nc: Found generic directory XML file in C:\Users\T\AppData\Local\Temp\tmps4ueywdg\crt_directory.xml Pc: ( 5) Remote configuration complete Nc: Reconnected to existing LinkServer process. Nc: Connecting to probe 1 core 0 (using server started externally) reports: 'Ee(42). Could not connect to core.' Nc: Retrying... Nc: Reconnected to existing LinkServer process. Nc: Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core. Ed:02: Failed on connect: Ee(42). Could not connect to core. Et:31: No connection to chip's debug port Pc: (100) Target Operation Failed Re: Unable to save flash image from target board with MCULink probe I also tried the CL instead of the GUI but it made no difference. Comparing with your output I seem to get stuck on: Nc: Connecting to probe 1 core 0 (using server started externally) reports: 'Ee(42). Could not connect to core.' This seems to be complaining about the probe, not the target. Re: Unable to save flash image from target board with MCULink probe I think you might have a connection (physical cable?) issue. Using it on Ubuntu, but same would apply to Win10: /usr/local/LinkServer_26.9.130/LinkServer flash --probe 4FIQSNVD2MICA LPC804: dump 0x00000000 0x00001000 /tmp/memory.bin
INFO: Exact match for LPC804: found
INFO: Selected device LPC804:LPCXpresso804
INFO: Selected probe #1 4FIQSNVD2MICA (MCU-LINK Pro (r1CF) CMSIS-DAP V3.174)
INFO: MCU-Link firmware update `check`: Probe ([4FIQSNVD2MICA] [MCU-LINK Pro (r1CF) CMSIS-DAP V3.174]) is already running the same firmware version as the included firmware version [3.174]
Firmware update `check`: not required - forced update can be performed using: `./LinkServer probe #1 update forced`
Ns: LinkServer RedlinkMulti Driver v26.9 (Sep 18 2026 19:46:03 - crt_emu_cm_redlink build 1382)
Pc: ( 0) Reading remote configuration
Wc(03). No cache support.
Nc: Found generic directory XML file in /tmp/tmpuhtfp3bl/crt_directory.xml
Pc: ( 5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Nc: Probe Firmware: MCU-LINK Pro (r1CF) CMSIS-DAP V3.174 (NXP Semiconductors)
Nc: Serial Number: 4FIQSNVD2MICA
Nc: VID:PID: 1FC9:0143
Nc: USB Path: 0005:0013:00
Nc: Using memory from core 0 after searching for a good core
Pc: ( 30) Emulator Connected
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: debug interface type = CoreSight DP (DAP DP ID 0BC11477) over SWD TAP 0
Nc: processor type = Cortex-M0+ (CPU ID 00000C60) on DAP AP 0
Nc: number of h/w breakpoints = 4
Nc: number of flash patches = 0
Nc: number of h/w watchpoints = 2
Nc: Probe(0): Connected&Reset. DpID: 0BC11477. CpuID: 00000C60. Info:
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE E00FF000: CID B105100D PID 04000BB4C0 ROM (type 0x1)
Nc: ROM 1 E000E000: CID B105E00D PID 04000BB008 Gen SCS (type 0x0)
Nc: ROM 1 E0001000: CID B105E00D PID 04000BB00A Gen DWT (type 0x0)
Nc: ROM 1 E0002000: CID B105E00D PID 04000BB00B Gen FPB (type 0x0)
Nc: NXP: LPC804
Nc: DAP stride is 1024 bytes (256 words)
Nc: Inspected v.2 On-chip Flash Memory LPC80x_32.cfx
Nc: Image 'LPC80x (32K) Sep 18 2026 18:35:07'
Pc: ( 65) Chip Setup Complete
Pc: ( 70) License Check Complete
Nt: Dumping 'memory.bin' Binary section 0 at 0x00000000 len 0x1000
Nc: Opening flash driver LPC80x_32.cfx
Nc: VECTRESET requested, but not supported on ARMv6-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash device supported (32KB = 32*1K at 0x0)
Ps: ( 0) at 00000000: 0 bytes - 0/4096
Ps: (100) at 00000000: 4096 bytes - 4096/4096
Nc: Closing flash driver LPC80x_32.cfx
Nt: Dumped 0x1000 bytes in 17ms (about 240kB/s) With the GUI: I hope this help, Erich Re: Unable to save flash image from target board with MCULink probe My diy tc2030 cable did not have the GNDdetect connected. I fixed that and I am now able to read and write flash using either the command line or GUI. Re: Unable to save flash image from target board with MCULink probe Yes, I see the MCULink kit only had a 10cm cortex cable and adding a tc2030 cable onto that would more than double that length. BTW, the LPC804 UM mentions that pin0.12 has some ability to recover from a problem state. Is there any further description of how and when to use this feature? Re: Unable to save flash image from target board with MCULink probe Update: It worked fine for an hour but now it is very unreliable. Sometimes I can dump the flash contents but not erase. Sometimes I can dump and erase but not program. Trying to dump, erase, program and verify only worked that one time and never again. I have tried two different tc2030 cables, various wire speeds, and both the CLI and GUI. Even when FlashLink says it succeeded, I usually find when I dump flash that some bytes were not erased or written. I think a very short cable may be needed. Re: Unable to save flash image from target board with MCULink probe How long is your cable? It should not exceed ~10 cm. Additionally, what board are you using? Your own/custom one? In that case you might have a connector/trace problem on your board. I hope this helps, Erich Re: Unable to save flash image from target board with MCULink probe A shorter 8cm cable made no difference. When I erase all 0x7F80 bytes and it reports success, I dump all 0x7F80 bytes expecting all 0xFF. Instead the dump is almost all 0x00, so either Flashlink is wrong about the status it reports or there is a HW issue like a partially shorted SWD signal preventing a proper dump of the flash.
記事全体を表示