• State Verified Answer
  • Replies 3 replies
  • Subscribers 92 subscribers
  • Views 1201 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 317343
Options

Issue with nRF7002DK Board - LED 5 Fast Flashing Post-Azure IoT Hub Example

Actif

Dear Nordic Support Team,

I am reaching out for assistance with an issue I’ve encountered on my new nRF7002DK board. After successfully flashing the Azure IoT Hub example with Device Provisioning Service (DPS) enabled, I am experiencing unexpected behaviour upon resetting the board.

Problem Description: Post-flashing, every reset of the board results in LED 5 blinking at an unusually high rate. My system recognizes the board as it appears in the connected devices list, but it seems stuck in a loop, perpetually attempting to establish a connection.

System and Tools:

  • Operating System: Windows 11 Pro
  • Nordic SDK: nRF Connect SDK (NCS) version 2.5.0
  • Programming/Debugging Tool: nRF Command Line Tools

Steps Already Taken:

  1. Attempted to recover the board using the nrfjprog tool with the following command: nrfjprog.exe --recover --log.
  2. I reviewed the log for apparent errors but couldn't find a clear cause.

Request: I would appreciate guidance on how to troubleshoot this issue further. Is there a known issue with the Azure IoT Hub example in NCS 2.5.0 that could cause this behaviour? Additionally, if there are any specific logs or details you require to assist me better, please let me know.

Thank you for your time and assistance.
Looking forward to your response.

[2023-Nov-07 14:59:13] [debug] --------------------------------------------------------------------------------
[2023-Nov-07 14:59:13] [debug] C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.exe --recover --log . 
[2023-Nov-07 14:59:13] [debug] nrfjprog version 10.23.2 external
[2023-Nov-07 14:59:13] [debug] --------------------------------------------------------------------------------
[2023-Nov-07 14:59:13] [ info] Load library at C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.dll.
[2023-Nov-07 14:59:13] [ info] Library loaded, loading member functions.
[2023-Nov-07 14:59:13] [ info] Member functions succesfully loaded.
[2023-Nov-07 14:59:13] [debug] [ Client] - open
[2023-Nov-07 14:59:13] [debug] [ Client] - start
[2023-Nov-07 14:59:13] [ info] [ Client] - stdout: Jlinkarm nRF Worker ready. Handling sequence d0881295-8880-4214-8240-8bc449420a40.

[2023-Nov-07 14:59:13] [trace] [ Client] - Command open executed for 47 milliseconds with result 0
[2023-Nov-07 14:59:13] [debug] [ Client] - config
[2023-Nov-07 14:59:13] [trace] [ Client] - Command config executed for 15 milliseconds with result 0
[2023-Nov-07 14:59:13] [debug] [ Client] - enum_emu_snr
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - Logger sink registered in Segger backend logger
[2023-Nov-07 14:59:13] [debug] [  JLink] - Logger sink registered in JLink logger
[2023-Nov-07 14:59:13] [debug] [  nRFXX] - open
[2023-Nov-07 14:59:13] [debug] [  nRFXX] - just_check_family
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - open_dll
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - No J-Link DLL path was provided. Attempting to auto detect.
[2023-Nov-07 14:59:13] [ info] [SeggerBackend] - Load library at C:\Program Files\SEGGER\JLink\JLink_x64.dll.
[2023-Nov-07 14:59:13] [ info] [SeggerBackend] - Library loaded, loading member functions.
[2023-Nov-07 14:59:13] [ info] [SeggerBackend] - Member functions succesfully loaded.
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - Set batch mode
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - dll_version
[2023-Nov-07 14:59:13] [ info] [SeggerBackend] - Segger dll version 7.88.j loaded.
[2023-Nov-07 14:59:13] [trace] [ Worker] - Command open executed for 3 milliseconds with result 0
[2023-Nov-07 14:59:13] [debug] [  nRFXX] - config
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - enum_emu_snr
[2023-Nov-07 14:59:13] [trace] [ Worker] - Command config executed for 2 milliseconds with result 0
[2023-Nov-07 14:59:13] [trace] [ Client] - Command enum_emu_con_info executed for 15 milliseconds with result 0
[2023-Nov-07 14:59:13] [debug] [ Client] - connect_to_emu_with_snr
[2023-Nov-07 14:59:13] [debug] [  nRFXX] - enum_emu_con_info
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - is_connected_to_emu
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - enum_emu_con_info
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - is_connected_to_emu
[2023-Nov-07 14:59:13] [trace] [ Worker] - Command enum_emu_con_info executed for 2 milliseconds with result 0
[2023-Nov-07 14:59:13] [debug] [  nRFXX] - connect_to_emu_with_snr
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - is_connected_to_emu
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - connect_to_emu_with_snr
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - is_connected_to_emu
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - ---just_enum_emu_snr
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - ---just_get_num_emus
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - ---just_connect_to_emu_with_snr
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - ---just_connect_to_emu_without_snr
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - Segger logging enabled.
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] -    ***** Error: 
[2023-Nov-07 14:59:13] [trace] [  JLink] - Cannot connect to J-Link
[2023-Nov-07 14:59:13] [trace] [  JLink] - - 1.563ms returns "Cannot connect to J-Link"  
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_HasError()  
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_OpenEx(...)  
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] -    ***** Error: 
[2023-Nov-07 14:59:13] [trace] [  JLink] - Cannot connect to J-Link
[2023-Nov-07 14:59:13] [trace] [  JLink] - - 0.924ms returns "Cannot connect to J-Link"  
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_HasError()  
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_OpenEx(...)  
[2023-Nov-07 14:59:13] [error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 31 milliseconds with result -102
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] - Out of sync , resynchronizing...
[2023-Nov-07 14:59:13] [trace] [  JLink] -    ***** Error: 
[2023-Nov-07 14:59:13] [trace] [  JLink] - Cannot connect to J-Link
[2023-Nov-07 14:59:13] [trace] [  JLink] - - 0.951ms returns "Cannot connect to J-Link"  
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_HasError()  
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - is_connected_to_emu
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_IsOpen()  
[2023-Nov-07 14:59:13] [trace] [  JLink] - - 0.005ms returns 0x00  
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_HasError()  
[2023-Nov-07 14:59:13] [error] [ Worker] - JLinkARM.dll Open returned error 'Cannot connect to J-Link'
[2023-Nov-07 14:59:13] [trace] [ Worker] - Command connect_to_emu_with_snr executed for 16 milliseconds with result -102
[2023-Nov-07 14:59:13] [debug] [  nRFXX] - close
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - is_connected_to_emu
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_IsOpen()  
[2023-Nov-07 14:59:13] [trace] [  JLink] - - 0.015ms returns 0x00  
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_HasError()  
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - close
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - disconnect_from_emu
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - is_connected_to_emu
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_IsOpen()  
[2023-Nov-07 14:59:13] [trace] [  JLink] - - 0.029ms returns 0x00  
[2023-Nov-07 14:59:13] [trace] [  JLink] - JLINK_HasError()  
[2023-Nov-07 14:59:13] [debug] [SeggerBackend] - Segger Backend closed.
[2023-Nov-07 14:59:13] [debug] [  nRFXX] - nRF family DLL closed
[2023-Nov-07 14:59:13] [trace] [ Client] - Command close executed for 45 milliseconds with result 0
[2023-Nov-07 14:59:13] [debug] [ Client] - terminate
[2023-Nov-07 14:59:13] [trace] [ Client] - Command terminate executed for 0 milliseconds with result 0
[2023-Nov-07 14:59:13] [trace] [ Worker] - Command close executed for 30 milliseconds with result 0
[2023-Nov-07 14:59:13] [trace] [ Worker] - Command terminate executed for 0 milliseconds with result 0
[2023-Nov-07 14:59:13] [trace] [ Worker] - Executed 6 commands for 53 milliseconds
[2023-Nov-07 14:59:13] [debug] [ Client] - Worker process exited with code: 0
[2023-Nov-07 14:59:13] [debug] [ Client] - Worker process exited with code: 0
[2023-Nov-07 14:59:13] [debug] [ Client] - Child process terminated with result 0
[2023-Nov-07 14:59:13] [trace] [ Client] - Executed 6 commands for 153 milliseconds
[2023-Nov-07 14:59:13] [debug] [ Client] - terminate

  • 0

    Hello Vincent,

    Request: I would appreciate guidance on how to troubleshoot this issue further. Is there a known issue with the Azure IoT Hub example in NCS 2.5.0 that could cause this behaviour? Additionally, if there are any specific logs or details you require to assist me better, please let me know.

    None that should stay there when you've even recover the board. 

    Have you updated to the newest version of nRF Commandline tools? Is there anything shorted or cut on the board? Could you check if all the switches are in the default position?

    What version of the board do you have?

    Regards,

    Håkon

  • +1 in reply to Elfving

    Thank you for the answer.
    Everything was updated, and nothing was shorting the board.

    We went with a new board.


    Regards,
    Actif

  • 0

    I had a similar thing happen today, except I had made no changes to the nRF7002DK other than unplugging it for a day and then plugging it back in.  The LED5 was flashing fast, and there were no communications.  And a different nRF7002 board acted the same way.  The J-Link device wasn't showing up on the USB Device Tree (MacBook) either, so I rebooted the laptop and everything returned to normal.

Related
Terms of service