Multiple ST-link Debuggers

Posted on December 23, 2014 at 14:48

The correct way to do this is to have JTAG pods with unique serial numbers, or can identify multiple CPU in the scan chain, and drivers/dll's supporting said. How to do it with ST-LINK's is a whole other matter. You can't daisy chain via SWD.

The ST-LINK really isn't a commercial solutions, there's no one paying for such niche solutions.

Perhaps a bunch of Virtual Boxes?

Posted on December 26, 2014 at 18:53

If you have multiple instances of STLink connected to PC, then you can select which will be connected where in your Keil projects.

Keil allows you to select STLink Serial number (picture below).

Now, you can detach all stlinks, connect first and set it for your project, then remove first and insert another and set for another project.

I've tested this using F429-Disco and F401-Nucleo, works great.

Another way to get all connected STLinks is to open ST-Link Utility and under ''Target'' -> ''Settings...'' you have available STLinks probes.

Posted on January 08, 2015 at 01:41

Thnx for answering!

I'm using a couple of Nucleo-F072RB and the Debug Target Driver for the onboard ST-LINK/V2 reports Ser. Number ''N/A''. HW Version is ''V2'' as in your picture, Firmware Version is ''V2J23S6''.

I've tried to ''cheat'' (manipulating the driver's ''inf'' files) in an attempt to force Windows install the same driver under a different name, but this gets nasty -  the ST-LINK appears as a Virtual COM Port, a USB Mass Storage, a Portable Device and as a USB device as well.

The ST-Link Utility works, but debugging with it is far from comfortable!

So far my solution is a bunch of “actual�? boxes!