I’m posting this to the community in hopes that someone else has experienced what I’m seeing here and can assist with a potential work around or reconfiguration.
I’m trying to setup my new ST-LINK/V2 dongle and ST-LINK UTILITY software. I’ve installed all the latest everything (except the ST-LINK-SERVER) and upgraded the dongle firmware. When I launch the utility and do an “about” operation, here’s what I get:
So far, so good. My ST-LINK/V2 dongle is plugged in and Windows device manager recognizes the dongle. The LED on the dongle is solid red at this stage.
If I go to configure the ST-LINK settings, I get this dialog:
Everything looks good to this point, but this is about all the operational functionality I have. Attempting to change any of my target settings per the Particle Guide suggestions eventually nets an communication error, and a subsequent launch into settings again nets this result:
I’m running an effective up-to-date Win10 laptop. There’s no apparent “COM” or LED indication during any operations, and my only recourse to get any operational function back is to reset the ST-LINK dongle with a connection cycle.
Is the server required? Based on description this provides arbitration for multiple apps which I’m currently not running. Any assistance or suggestions appreciated.
EDIT
I forgot to post the dongle firmware version… the upgrader firmware version in the Utility IDE got deprecated by the ST-LINK firmware upgrade version:
I had a similar experience to what you’re describing and it turned out to be the pinout from the ST-Link to the PCB was not what was I thought it was. I’d suggest having a very close look at the pinning through if your wires from the ST-Link to your board.
What sort of cabling setup do you have?
What type of connector is in your board?
Make sure you connect VCC on the ST-LINK/V2 to 3V3 on the device. It’s a voltage sensing pin, and if you don’t connect it, it won’t work.
And make sure the device is in DFU mode (blinking yellow). If you’re booting into normal operating mode with regular system and user firmware you won’t be able to connect using SWD/JTAG. DFU mode has it enabled, as well as debugging firmware that has JTAG/SWD mode enabled. JTAG/SWD also works when there’s no bootloader (dim D7).
I want to clarify that all my angst with the Utility app and the dongle is independent of trying to connect to or flash a Particle device.
I should be able to tweak on the dongle settings independent of a target device connection and not have things crash, right?
That’s the issue I’m currently having. These suggestions are great, but I can’t reliably configure my dongle through the app. The dongle crashes and requires reconnection. The Setup dialog runs “once” as I’ve posted above, and with any follow up invocation of Setting the dongle goes tharn… I can’t even click OK in the Settings dialog. The dongle crashes on throws a comm error in the status console.
EDIT: Wiped the trace file and created the crash from a clean start. The trace capture is the same from a session that was directly connected to a v1.0 programmer shield with the 20-pin IDC cable or with the dongle disconnected.
Should the programmer shield be a direct-connect proposition? I’m going to attempt the P1 connection shown in the guide on a RedBoard since it appears there’s some invocation of “target”.
In an attempt to eliminate target dependency in regard to my woes, I connected in a red board. There’s no difference in behavior at all. I even powered up the P1 and placed it into DFU mode to no avail, and likewise with an unpowered P1 device, no difference in the dongle behavior.
