• State Verified Answer
  • Replies 8 replies
  • Subscribers 87 subscribers
  • Views 1826 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 259800
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

52805 programmer problem

??

Dear sir ,

      Get the customer's board, I can find the device at the nRF Connect for the first time, then program hex, but fail,  and then I can't find the device again. I try two customer's board,but the same problem was happened. and The same operation is OK on the nRF52 DK.

      nRF5_SDK_17.0.2_d674dde

      s112_nrf52_7.2.0_softdevice.hex

      nRF Connect 3.6.0

      nRF-Command-Line-Tools_10_11_1_Installer.exe

log:

2020-11-14T01:15:57.487Z INFO Segger version: J-Link V9 compiled Dec 13 2019 11:14:50
2020-11-14T01:15:57.494Z INFO Core probed: 69611139.
2020-11-14T01:15:57.494Z INFO Core RAM: 24KiB.
2020-11-14T01:15:57.494Z INFO Core ROM: 192KiB in pages of 4KiB.
2020-11-14T01:15:57.654Z INFO Model: NRF52805_xxAA_REV1.
2020-11-14T01:15:58.404Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2020-11-14T01:15:58.458Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2020-11-14T01:15:58.630Z INFO SoftDevice detected, id 0x103 (S112 v7.2.0)
2020-11-14T01:15:58.658Z INFO Writing procedure starts for core0
2020-11-14T01:16:07.316Z ERROR HighLevel_probe_init
2020-11-14T01:16:07.317Z ERROR . HighLevel_get_connected_probes
2020-11-14T01:16:07.317Z ERROR . . nRFXX_enum_emu_snr
2020-11-14T01:16:07.318Z ERROR . . . Segger_enum_emu_snr
2020-11-14T01:16:07.318Z ERROR . . . . Segger_enum_emu_snr
2020-11-14T01:16:07.318Z ERROR . . . . . Segger_get_num_emus
2020-11-14T01:16:07.318Z ERROR HighLevel_probe_init: jlink_path parameter is NULL, using default JLINKARM DLL path given with or obtained in NRFJPROG_dll_open() function.
2020-11-14T01:16:07.319Z ERROR
2020-11-14T01:16:07.319Z ERROR HighLevel_probe_init: Using JLINKARM DLL at "C:\\Program Files (x86)\\SEGGER\\JLink\\JLinkARM.dll".
2020-11-14T01:16:07.319Z ERROR
2020-11-14T01:16:07.319Z ERROR HighLevel_probe_init: Creating new probe
2020-11-14T01:16:07.320Z ERROR
2020-11-14T01:16:07.320Z ERROR Debug_Probe-69611139_logger_open
2020-11-14T01:16:07.320Z ERROR Debug_Probe-69611139_logger_open: nRFJProg logger opened to callback at address 0X5E7E2080
2020-11-14T01:16:07.320Z ERROR HighLevel_probe_init: Initialize new probe.
2020-11-14T01:16:07.321Z ERROR
2020-11-14T01:16:07.321Z ERROR Debug_Probe-69611139_initialize
2020-11-14T01:16:07.321Z ERROR . Debug_Probe-69611139_base_debug_probe_initialize
2020-11-14T01:16:07.321Z ERROR . Debug_Probe-69611139_base_debug_probe_initialize: Copying Segger dll to temporary folder to allow a new probe connection.
2020-11-14T01:16:07.321Z ERROR
2020-11-14T01:16:07.322Z ERROR . Debug_Probe-69611139_base_debug_probe_initialize: Copy "C:\\Program Files (x86)\\SEGGER\\JLink\\JLinkARM.dll"->"C:\\Users\\king\\AppData\\Local\\Temp\\nrfjprogdll\\highlevel\\debug\\69611139\\jlinkarm\\s3lk.1j"
2020-11-14T01:16:07.322Z ERROR
2020-11-14T01:16:07.322Z ERROR . Debug_Probe-69611139_base_debug_probe_initialize: Using Segger dll at "C:\\Users\\king\\AppData\\Local\\Temp\\nrfjprogdll\\highlevel\\debug\\69611139\\jlinkarm\\s3lk.1j".
2020-11-14T01:16:07.322Z ERROR
2020-11-14T01:16:07.323Z ERROR . Debug_Probe-69611139_base_debug_probe_initialize: Copied from "C:\\Program Files (x86)\\SEGGER\\JLink\\JLinkARM.dll".
2020-11-14T01:16:07.323Z ERROR
2020-11-14T01:16:07.323Z ERROR . Debug_Probe-69611139_base_debug_probe_initialize: Copy "C:\\Users\\king\\AppData\\Local\\Programs\\nrfconnect\\resources\\app.asar.unpacked\\node_modules\\pc-nrfjprog-js\\build\\Release\\jlinkarm_unknown_nrfjprog.dll"->"C:\\Users\\king\\AppData\\Local\\Temp\\nrfjprogdll\\highlevel\\debug\\69611139\\s3lk.1k"
2020-11-14T01:16:07.323Z ERROR
2020-11-14T01:16:07.323Z ERROR . Debug_Probe-69611139_base_debug_probe_initialize: Load library at "C:\\Users\\king\\AppData\\Local\\Temp\\nrfjprogdll\\highlevel\\debug\\69611139\\s3lk.1k".
2020-11-14T01:16:07.324Z ERROR
2020-11-14T01:16:07.324Z ERROR . Debug_Probe-69611139_base_debug_probe_initialize: Read the device's family.
2020-11-14T01:16:07.324Z ERROR

......

2020-11-14T04:05:08.642Z INFO Application data folder: C:\Users\king\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2020-11-14T04:05:08.867Z DEBUG App pc-nrfconnect-programmer v1.4.7 official
2020-11-14T04:05:08.868Z DEBUG App path: C:\Users\king\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2020-11-14T04:05:08.868Z DEBUG nRFConnect 3.6.0 is supported by the app (^3.6.0)
2020-11-14T04:05:08.868Z DEBUG nRFConnect path: C:\Users\king\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-11-14T04:05:08.868Z DEBUG HomeDir: C:\Users\king
2020-11-14T04:05:08.868Z DEBUG TmpDir: C:\Users\king\AppData\Local\Temp
2020-11-14T04:05:08.908Z INFO Using nrfjprog library 10.9.0, pc-nrfjprog-js 1.7.3
2020-11-14T04:05:21.162Z INFO Using nrfjprog to communicate with target
2020-11-14T04:05:22.246Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: CANNOT_CONNECT (fffffff5)

Parents Reply Children
  • 0 in reply to Jared

    Dear Jared,

    FYI,  press K1 before burning and at all the time while burning.

  • 0 in reply to ??

    ps:

    I use the JLINK on the development board, and there is no problem burning other boards. The connection is as follows:

    VTG -> VCC of the board

    SWDIO

    SWDCLK

    GND

    The board is self powered。



  • 0 in reply to ??

    Hi,

    Are you using the nRF Connect Programmer app? Are you using v1.4.7, if not can you update it and see if the issue is persistent?

    Could you try to recover the unresponsive device with:

    nrfjprog --recover

    Could you try to measure the VDD_nRF voltage while you try to program the board? Use a oscilloscope and take a trace of the voltage. Is the voltage stable? Could you upload the trace?

    Alternatively try to omit the button switch stage by supplying the board directly with VDD from a bench supply while you try to program the board.

  • 0 in reply to Jared

    Dear Jared,

    1.yes. use nRF Connect Programmer app. 1.4.7, but maybe this is the latest version.

    2. still fail

    3. I've tried it. got nothing.

    I first check whether this board has problems, so I am looking for someone else's good board to verify.

    thanks

  • 0 in reply to ??

    Hi,

    I've tried programming a nRF52805 with nrfjprog and did not experience any issues.

    What kind of debugger are you using? J-link? Which model?

    Could you upload the log from nrfjprog?:

    nrfjprog --recover --log

    Note sure if you answered my previous question regarding VDD or not: 

     

    Jared said:

    Could you try to measure the VDD_nRF voltage while you try to program the board? Use a oscilloscope and take a trace of the voltage. Is the voltage stable? Could you upload the trace?

    Alternatively try to omit the button switch stage by supplying the board directly with VDD from a bench supply while you try to program the board.

Related
Terms of service