I am trying to develop a Globalstar ST150M The project board is a Nordic Semiconductor nRF 52840 DK running an Arm Cortex M4 CPU.

[Mark O]

I'm using a Windows 11 IBM computer. I have gone thru the Dev Academy exercise 1. I installed the software's, nRf for Desktop, nRF Connect SDK, its toolchain, VS Code IDE as well as the Segger J-Link 7.94e application .I then created  and built the project, as per the Dev Academy tutorial, named Blinki_Tutorial

The nRF52480DK board is not found in the VS Code app.

I can communicate with the board through Putty and other terminal applications, so I know the is a serial connection between the board and computer, however I cannot get the SDK/IDE to recognize the board.

Please advise

[khelmutlord]

Hello Mark,

I believe this issue is caused by an incorrect JLink USB driver install. 

Begin by downloading JLink from this link: https://www.segger.com/downloads/jlink/

During installation, select "Install legacy USB Driver for J-Link" and "Update existing installation."

Close VScode and open it again after this installation and you should be able to program the devkit.

Thanks,

Helmut Lord

[Mark O]

Helmul, than you for your response.  I tried installing the current version Segger JLink 7.94e, driver, and following the instructions you provided, setting it up for legacy USB Driver, and updating the current instillation. I still could not see the board in the "connected devices" fiel in Visual Studio code. I then tried completly uninstalling the JLink application from the computer and re ran the instillition., making sure I selected run as administrator. I stll can't see the board.

Additionally, I now can't terminal into the board with Putty, or a terminal session in Visual Studio, as I could before. I moved the board to another computer, that doesn't have any of the Nordic, Segger, or Visual Studio app's and I could terminal into the board as before.

I take it that the Segger JLink app is the serial access from the SDK/IDE Application to the board. 

This is a screen shot from nRF Connect Desktop - Terminal..  I'm installing the Segger JLink usb driver V 7.94e, is this perhaps the wrong one? 

Thank you

[Kenneth]

Can you also try to install nRF Command line tools and then run 'nrfjprog --version' in a command line window?

Kenneth

[Mark O]

Thank you Kenneth. I have nRF command line Tools and will try this. At this time on my developnment computer, I am no longer able to connect to the board with any terminal program (previously, I could connect to the board with Putty). The original com port, nor any other I choose in "Putty" are avaliable.

Can you tell me what version of 'nfrjprog" I shoud load?

Thank you

Ok, I got back to the shop, figured out what the terminal connection problem was, now I'm trying to get the 'nrfjprog' version, but keep getting an invlad command error

What is the proper snytex for that commnd?

Ok here it is

[Kenneth]

Type 'cmd' in Windows to open a command line window.

Kenneth

[Mark O]

Ok here it is

[Kenneth]

Looks good, does running 'nrfjprog --recover' work?

Edit: If that works, then I would try to go back to VS code and check.

Kenneth

[Mark O]

Kenneth

I ran nrfjprog --recover and I still can't see the board in VS code 

[Kenneth]

The only thing I can think of is some kind of driver issue, is there any unknown devices in device manager? Here is how it looks at my place using Windows 11 also:

[Mark O]

Kenneth

I can't get a good shot of my Device manager right now.

The Seeger SMD drive is not showing up, nor the Jlnk Portable device and certianly not the com ports.

Sompthind is missing.

Am I supposed to have an actual Seegar Debugger installed? I didn't see it in the Nordic Acamedy instructions.

[Kenneth]

Gan you send me a picture of your DK, with USB cable plugged in and tell me which leds are on, blinking, or off?

Kenneth