• State Verified Answer
  • Replies 2 replies
  • Subscribers 87 subscribers
  • Views 642 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 349602
Options

Custom board is not responsive even after successfully flushing with nRF5340DK with SWD

frogrammer

Hi team,

I am using ncs2.6.1 ( github - install from VS Code ) , toolchain 3.0.2 ( previously used 2.6.1), My DK works great standalone also here is the view from nrf-connect-desktop-programmer

------------------------------------------------------------------------------------------------------------

Now moving onto my issues with Custom board:

I have two custom boards consisting nRF5340 modules from uBlox. I have been flashing these boards for past 2-3 months using my usual setup:

nRF5340DK Pin header 20 , swo - reset - swclk-swdio- (VTG+nRF_VDD) - GND to my custom board 6pin tag connect.

Few days ago, i had some installation issues with other zephyrs and my ncs 2.6.1 , so i deleted all, and installed fresh new. I also had to re touch the SWD tag connect cable woth soldering, but since then i am facing issues that my DK can not detect the board. I have been back and forth with the cable , it is working fine ( I have flashed STM32 with it ), I have chnaged jlink driver and recovered the board, changed firmware of the dk jlink using JLINK software. Still, my board wasn't detecting realiably , maybe once in a while it would show.

After that, i made a completely new setup in Linux, after that, my boards were reliably shown in VS code connected devices, It would flash into my custom boards as well, but the customs boards doesnt do anything. 1. simply blink , and 2. RTT Viewer. Here is the screenshots:

As it says it has uploaded the code, i went to check it with nrf-connect-desktop-programmer app, i get these window and messages, i clicked all, like reset, read memory.

Here is the log file:

2025-08-07T09:09:05.192Z INFO Initialising the bundled nrfutil device
2025-08-07T09:09:05.218Z DEBUG Application data folder: /home/xxxx/.config/nrfconnect/pc-nrfconnect-programmer
2025-08-07T09:09:05.268Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:09:05.268Z DEBUG App pc-nrfconnect-programmer v4.6.2 (official)
2025-08-07T09:09:05.268Z DEBUG App path: /home/xxxx/.nrfconnect-apps/node_modules/pc-nrfconnect-programmer
2025-08-07T09:09:05.268Z DEBUG nRFConnect 5.2.0, required by the app is (>=5.2.0)
2025-08-07T09:09:05.269Z DEBUG nRFConnect path: /tmp/.mount_nrfconixYf2c/resources/app.asar
2025-08-07T09:09:05.269Z DEBUG HomeDir: /home/xxxx
2025-08-07T09:09:05.269Z DEBUG TmpDir: /tmp
2025-08-07T09:09:05.364Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:09:05.364Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:09:05.369Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:09:05.389Z INFO Using the bundled core version for nrfutil device: 8.0.0
2025-08-07T09:09:05.465Z INFO Using nrfutil-device version: 2.12.3
2025-08-07T09:09:05.466Z INFO Using nrf-device-lib version: 0.17.81
2025-08-07T09:09:05.466Z INFO Using nrf-probe version: 0.40.1
2025-08-07T09:09:05.466Z INFO Using JLink version: JLink_V8.58
2025-08-07T09:09:05.468Z INFO Your version of SEGGER J-Link (8.58) is newer than the one this app was tested with (8.18). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.
2025-08-07T09:09:16.819Z INFO Getting serial port options from the persistent store for 001050018045.pc-nrfconnect-programmer
2025-08-07T09:09:16.820Z INFO Device connected with the serial number 001050018045
2025-08-07T09:09:16.822Z DEBUG Sending event "programmer: device connected"
2025-08-07T09:09:16.871Z INFO Getting serial port options from the persistent store for 001050018045.pc-nrfconnect-programmer
2025-08-07T09:09:16.873Z DEBUG Sending event "programmer: device connected"
2025-08-07T09:20:01.287Z INFO Selecting device with the serial number 001050018045
2025-08-07T09:20:01.331Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:01.536Z INFO Selected device with the serial number 001050018045
2025-08-07T09:20:01.537Z INFO Using nrfutil device to communicate with target via JLink
2025-08-07T09:20:01.538Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Jul  8 2025 10:15:34
2025-08-07T09:20:01.538Z INFO Device family NRF53_FAMILY
2025-08-07T09:20:01.538Z INFO Device version NRF5340_xxAA_REV1
2025-08-07T09:20:01.538Z INFO Board version PCA10095
2025-08-07T09:20:01.562Z DEBUG Sending event "programmer: device selected"
2025-08-07T09:20:01.563Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:01.564Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:01.683Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:01.823Z INFO Reading readback protection status for Application core
2025-08-07T09:20:01.824Z INFO Reading readback protection status for Application core 0%
2025-08-07T09:20:01.826Z INFO Reading readback protection status for Application core 100%
2025-08-07T09:20:01.826Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2025-08-07T09:20:01.826Z INFO Reading readback protection status for Application core completed
2025-08-07T09:20:01.826Z INFO Reading readback protection status for Network core
2025-08-07T09:20:01.827Z INFO Reading readback protection status for Network core 0%
2025-08-07T09:20:01.931Z INFO Reading readback protection status for Network core 100%
2025-08-07T09:20:01.931Z INFO Network core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2025-08-07T09:20:01.932Z INFO Reading readback protection status for Network core completed
2025-08-07T09:20:02.013Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:02.014Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:02.132Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:02.282Z INFO Loading core information for Application core
2025-08-07T09:20:02.283Z INFO Loading core information for Application core 0%
2025-08-07T09:20:02.286Z INFO Loading core information for Application core 100%
2025-08-07T09:20:02.287Z INFO Loading core information for Application core completed
2025-08-07T09:20:02.287Z INFO Loading core information for Network core
2025-08-07T09:20:02.287Z INFO Loading core information for Network core 0%
2025-08-07T09:20:02.287Z INFO Loading core information for Network core 100%
2025-08-07T09:20:02.288Z INFO Loading core information for Network core completed
2025-08-07T09:20:02.376Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:02.377Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:02.378Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:02.499Z DEBUG Sending event "programmer: running nrfutil device"
2025-08-07T09:20:02.638Z INFO Reading memory for Application core
2025-08-07T09:20:02.639Z INFO Reading memory for Application core 0%
2025-08-07T09:20:05.314Z ERROR Error: Failed with exit code 1.
One or more batch tasks failed:

One or more batch tasks failed:
 * 1050018045: Device error: Failed to read from memory address 0x50003100: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic)


Message: Batch task memory-read failed, Device error: Failed to read from memory address 0x50003100: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1).
2025-08-07T09:20:05.315Z ERROR Error: Failed with exit code 1.
One or more batch tasks failed:
 * 1050018045: Device error: Failed to read from memory address 0x50003100: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic)


Message: Batch task memory-read failed, Device error: Failed to read from memory address 0x50003100: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1).

I did repeat the process with these commands , i though would be useful i seen in another community post:

I can not figure it out whether if its cable fault? because only thing i did was re-solder all the connections, checked with continuity, no shorts between connections. Even if, it was cable fault would it simply say programmed the device? or just show no devices? or simply there has be another setup in the software?

note: i would be checking the cable and check with another DK

Parents
  • +1

    Hi,

    A cable fault does not look likely as from the VS Code screenshot I see that programming the device was successfull. When you write that it does not work, did you do any debugging to see the state of the device (by observing logs or starting a debug session and inspecting the state)?

    Is it so that you had the application working on the custom board on the old setup? And do you still get it to run on a DK on your new setup? A typical reason for problesm when going to custom boards, is if that does not have the 32.768 kHz crystal or DCDC inducors, and any of these are enabled in firmware.

  • 0 in reply to Einar Thorsrud

    Yes, before i had these two lines, now i have added them again, it works.

    CONFIG_CLOCK_CONTROL_NRF_K32RC_RC=y

    CONFIG_CLOCK_CONTROL_NRF_K32RC_XTAL=n 

    although, it threw me off when VS Code could not detect my board, and nrf Connect desktop programmer spewed out errors beyond my knowledge, and couldn’t show memory layout. 

Reply Children
No Data
Related
Terms of service