• State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 73 subscribers
  • Views 1966 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 293344
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

JLink CDC UART Port visible but no working properly on Windows 11

fabocode

Hey guys, I was looking for a similar issue, however, I haven't found something like this (maybe I am searching for a case similar to this in a wrong way) 

But essentially, I have a nRF52840 DK board (and also have a nRF52 DK board) both on this computer are capable of  flash and debugging applications, however, the JLink CDC UART Port is not working properly and I can't see the logs in any example/code in nRF5 SDK  (or nRF Connect SDK) that uses the UART Port of the development kits that I have. 

I have another laptop where I do not have this problem, but I really would like to solve this problem on this computer without needing to go to my other workstation. 


I uninstalled nRF Command Line Tools and reinstalled and also uninstalled JLink and reinstall it again, my Jlink version is V7.66 and my computer is 64bit Windows 11 Operation system. 


Any tips and suggestions will be welcome, thank you so much for reading this and let me know if you need any other information from me to work on this. 

  • 0

    Hi there,

    Does your other computer run Windows 11? Can you check if you're able to reproduce it with the same DK on a computer running Windows 10? That would confirm whether the issue is related to your DK or the OS version. 

    regards

    Jared 

  • 0 in reply to Jared

    Hi, thank you so much for your reply! 

    My other computer doesn't run Windows 11, it's running Windows 10 and it's currently working without problems so I will not be able to reproduce the same problem there. Do you think I should downgrade my OS to be able to solve this issue or is something else? 

    Thanks

    Fabian

  • +1 in reply to fabocode

    Fabian,

    Ok, so I guess we can assume that the issue is somehow related to your computer and not your DKs. 

    Looking at your device list, it looks like there is a possible conflict on COM4? I see that there is two devices that are listed on that virtual com port, there is the nRF52 DK(Jlink CDC UART Port) and Standard Serial over Bluetooth link. Can you try to disable the latter?

    regards

    Jared 

  • 0 in reply to Jared

    Jared,

    After disable the Standard Serial over Bluetooth link it appears that the conflict was solved. I tested the peripheral/cli example in nRF5 SDK v17.1.0 and it's working properly, I can access to COM4 and view the logs using putty 

  • 0 in reply to fabocode

    Great Fabian,

    I'm happy that it worked!

    best regards

    Jared

Related
Terms of service