cannot program board, but can connect to it

[douglas.malnati]

Windows 11, NCS v2.3.0, VSCode

Hi,

I have a custom board that I am trying to flash, but I am failing.

The error in VSCode is this:

 *  Executing task: nRF Connect: Flash: Traquito/build_traquito_1.1.0 (active) 

Flashing build_traquito_1.1.0 to 683684592
west flash -d c:\Users\dougl\git\nRF52\app\Traquito\build_traquito_1.1.0 --skip-rebuild -r jlink --dev-id 683684592 --erase

-- west flash: using runner jlink
-- runners.jlink: mass erase requested
-- runners.jlink: JLink version: 7.86e
-- runners.jlink: Flashing file: c:\Users\dougl\git\nRF52\app\Traquito\build_traquito_1.1.0\zephyr\zephyr.hex
FATAL ERROR: command exited with status 1: 'C:\Program Files\SEGGER\JLink\JLink.exe' -USB 683684592 -nogui 1 -if swd -speed 4000 -device nRF52840_xxAA -CommanderScript 'C:\Users\dougl\AppData\Local\Temp\tmp22fv2yg8jlink\runner.jlink' -nogui 1

I tried manually flashing using a jlink script, but it also failed:

si 1
speed 4000
device NRF52840_XXAA
connect
loadfile ../../app/Traquito/build_traquito_1.1.0/zephyr/zephyr.hex 0x0
reset
go
exit

C:\Users\dougl\git\nRF52\utl\jlink>jlink.exe -CommandFile jlink.jls -nogui 1
SEGGER J-Link Commander V7.86e (Compiled Mar 22 2023 16:29:05)
DLL version V7.86e, compiled Mar 22 2023 16:27:41


J-Link Command File read successfully.
Processing script file...
J-Link>si 1
J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Nov  7 2022 16:21:57
Hardware version: V1.00
J-Link uptime (since boot): 6d 04h 15m 28s
S/N: 683684592
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
USB speed mode: High speed (480 MBit/s)
VTref=3.300V
Selecting SWD as current target interface.
J-Link>speed 4000
Selecting 4000 kHz as target interface speed
J-Link>device NRF52840_XXAA
J-Link>connect
Device "NRF52840_XXAA" selected.


Connecting to target via SWD
InitTarget() start
InitTarget() end - Took 4.43ms
Found SW-DP with ID 0x2BA01477
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
Memory zones:
  Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>loadfile ../../app/Traquito/build_traquito_1.1.0/zephyr/zephyr.hex 0x0
'loadfile': Performing implicit reset & halt of MCU.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading file [../../app/Traquito/build_traquito_1.1.0/zephyr/zephyr.hex]...
Comparing flash   [100%] Done.
Erasing flash     [100%] Done.
Programming flash [100%] Done.
Error while programming flash: Programming failed.
J-Link>reset
Reset delay: 0 ms
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
J-Link>go
J-Link>exit

I see that the jlink is able to connect to the device via SWD, but for whatever reason the flash upload doesn't work.  I don't see an error message explaining the issue.

How can I diagnose the issue and flash this device?

This is one device among several in a batch, the others flash ok, this one doesn't.

I understand that sometimes manufacturing doesn't work out or whatever, but I'm very unclear on what could be specifically wrong here that SWD comms work, but flashing doesn't.

I don't want to give up on this device since it's lost money.  Can you please help me look into this and solve the issue?

Thanks.

Doug