Why does ST-Link Server not start properly?

[PHirs.1]

Hi!

I recently tried to put my Nucleo G071RB board back in use.

Sadly it refused to work.

I´m using Cube IDE, Windows 10 (64).

After some research I found out, that Cube IDE is using ST-Link Server software to connect to the board, of which I installed the recent version.

I could not find the associated process in my task manager.

Even starting it manually could not do the trick.

Console pops up and disappear again, no task!

So I suspect ST-Link Server software.

Board is updated to the latest firmware, using Cube Programmer and I also re-installed Cube IDE.

Any suggestion?

[Imen.D]

Hello @PHirs.1​,

Welcome to the Community :)

Check the jumper of the board, boot pins and configuration.

Imen

[Sarra.S]

Hello @PHirs.1​ ,

It sounds like you have done the necessary steps to get your board working,

so it may be worth checking your computer's firewall settings to check If the ST-Link Server software is blocked! it may be preventing the board from connecting properly.

You can also try uninstalling the ST-Link Server software and reinstalling it again to see if this helps

[PHirs.1]

Hi,

thank you both for your quick response!

All jumpers are in their default state.

JP4, JP5, JP3 and CN4 (both) are set.

JP2 is set to "STLK".

No other jumpers are set.

ST-Link Server is now no longer blocked by windows firewall, if it ever was...

No change, software is still not starting up properly.

Interestingly the board is accessible via Cube Programmer software, which did make me wonder.

Don't Cube Programmer use ST-Link server to connect to the board?

I actually tried uninstall and reinstall ST-Link, as well as Cube IDE, but it did not work either.

Kind regards!

[Sarra.S]

@PHirs.1​ ,

So correct me if am wrong, you are able to connect to the board using STM32CubeProgrammer but not with STM32CubeIDE..

So I suspect ST-Link Server software >> I think the ST-Link server is not the problem here!

Have a look at this thread that suggests a solution that seems to work for several people.

Hope that helps!

[PHirs.1 · Accepted solution]

Thank you, problem solved! :smiling_face_with_smiling_eyes:

Indeed, libusb caused the trouble.

As mentioned in the thread, a change of libusb-1.0.dll is necessary and it in fact made things working again.

Kind regards!