NRF5340 Dk jlink CDC UART Connection issue.

[Mr.NCK]

HI,

I want help to fix the nrf5340 Dk. I have worked fine with the DK for a long time. But, Suddenly  I can't be able to connect the DK with my PC. I can able to connect PDK and another DK also. 

I have to attach one Video for your reference. Kindly, Check and help me to fix this issue.

Thanks & Regards

Navin.

[Jared]

Hi,

1. What is SW9, SW10 and SW6 set to?
2. Have you modified any of the solder bridges?
3. What error code do you get if you try to flash the board with the blinky example?

regards

Jared 

[Mr.NCK]

Hi jared

Jared said:

What is SW9, SW10 and SW6 set to?

SW9 is ON

SW10 is OFF

SW6 has its default position

Jared said:

Have you modified any of the solder bridges?

No, I didn't modify any solder bridge

Jared said:

What error code do you get if you try to flash the board with the blinky example?

I have already flashed BLE peripheral UART Sample. That is working fine. I can't be able to flash any other code because the device is not even connected.

Thanks & Regards

Navin

[Jared]

Hi,

Can you go through the steps listed here and confirm whether it fixed your issue or not, step 4 and 6 does not apply for the nRF53 so you can omit them.

regards
Jared 

[Mr.NCK]

HI,

I have Tested the listed 7 tests

1) failed

2) failed

3) failed

5) I don't know how to check supply voltage on DK.

7) I have got the below result

Thanks & Regards,

Navin 

[Jared]

Mr.NCK said:

5) I don't know how to check supply voltage on DK.

You can use the VDD header on the DK and measure the voltage directly on it. 

Mr.NCK said:

7) I have got the below result

Could you use nRF Command Line tools instead, and  add the log option:

nrfjprog --ids --log

Can you upload the log. 

regards

Jared 

[Mr.NCK]

Hi Jarad,

Jared said:

ou can use the VDD header on the DK and measure the voltage directly on it. 

3.02V is comming

Jared said:

Could you use nRF Command Line tools instead, and  add the log option:

I have attached the log file below for your reference.

Fullscreen 4670.log.log Download

[2022-Jul-22 11:04:52] [ info] --------------------------------------------------------------------------------
[2022-Jul-22 11:04:52] [ info] nrfjprog --ids --log 
[2022-Jul-22 11:04:52] [ info] nrfjprog version 10.16.0 external
[2022-Jul-22 11:04:52] [ info] --------------------------------------------------------------------------------
[2022-Jul-22 11:04:52] [ info] Load library at C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.dll.
[2022-Jul-22 11:04:52] [ info] Library loaded, loading member functions.
[2022-Jul-22 11:04:52] [ info] Member functions succesfully loaded.
[2022-Jul-22 11:04:52] [debug] [ Client] - open
[2022-Jul-22 11:04:52] [debug] [ Client] - start
[2022-Jul-22 11:04:52] [ info] [ Client] - stdout: Jlinkarm nRF Worker ready. Handling sequence 0c281330-1767-40c2-a484-55e0cbb15d29.

[2022-Jul-22 11:04:52] [trace] [ Client] - Command open executed for 104 milliseconds with result 0
[2022-Jul-22 11:04:52] [debug] [ Client] - enum_emu_snr
[2022-Jul-22 11:04:52] [trace] [ Client] - Command enum_emu_con_info executed for 15 milliseconds with result 0
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - Logger sink registered in Segger backend logger
[2022-Jul-22 11:04:52] [debug] [  JLink] - Logger sink registered in JLink logger
[2022-Jul-22 11:04:52] [debug] [  nRFXX] - open
[2022-Jul-22 11:04:52] [debug] [  nRFXX] - just_check_family
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - open_dll
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - No J-Link DLL path was provided. Attempting to auto detect.
[2022-Jul-22 11:04:52] [ info] [SeggerBackend] - Load library at C:\Program Files\SEGGER\JLink\JLink_x64.dll.
[2022-Jul-22 11:04:52] [ info] [SeggerBackend] - Library loaded, loading member functions.
[2022-Jul-22 11:04:52] [ info] [SeggerBackend] - Member functions succesfully loaded.
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - dll_version
[2022-Jul-22 11:04:52] [ info] [SeggerBackend] - Segger dll version 7.68.  loaded.
[2022-Jul-22 11:04:52] [trace] [ Worker] - Command open executed for 14 milliseconds with result 0
[2022-Jul-22 11:04:52] [debug] [  nRFXX] - enum_emu_con_info
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - enum_emu_con_info
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jul-22 11:04:52] [trace] [ Worker] - Command enum_emu_con_info executed for 4 milliseconds with result 0
[2022-Jul-22 11:04:52] [trace] [ Client] - Command close executed for 32 milliseconds with result 0
[2022-Jul-22 11:04:52] [debug] [ Client] - terminate
[2022-Jul-22 11:04:52] [trace] [ Client] - Command terminate executed for 0 milliseconds with result 0
[2022-Jul-22 11:04:52] [debug] [  nRFXX] - close
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - close
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - disconnect_from_emu
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jul-22 11:04:52] [debug] [SeggerBackend] - Segger Backend closed.
[2022-Jul-22 11:04:52] [debug] [  nRFXX] - nRF family DLL closed
[2022-Jul-22 11:04:52] [trace] [ Worker] - Command close executed for 30 milliseconds with result 0
[2022-Jul-22 11:04:52] [trace] [ Worker] - Command terminate executed for 0 milliseconds with result 0
[2022-Jul-22 11:04:52] [trace] [ Worker] - Executed 4 commands for 48 milliseconds
[2022-Jul-22 11:04:52] [debug] [ Client] - Worker process exited with code: 0
[2022-Jul-22 11:04:52] [debug] [ Client] - Worker process exited with code: 0
[2022-Jul-22 11:04:52] [debug] [ Client] - Child process terminated with result 0
[2022-Jul-22 11:04:52] [trace] [ Client] - Executed 4 commands for 151 milliseconds
[2022-Jul-22 11:04:52] [debug] [ Client] - terminate

Thanks & Regards,

Navin