SOLVED: Unable to program or upgrade STLink on Nucleo-32 L432KC

[PCamp.2]

I got a new Nucleo-32 L432KC board today.

It powers on the demo runs, the ST-Link connects, but it isn't supported under CubeIDE and an upgrade is required.

On running the upgrade tool for LINK-009 it detects the ST-Link, when I click "Open in Update mode" however, the ST-Link LED goes RED, the PC makes a disconnect sound and... the STLink is dead until I power cycle it.

I've tried un plugging and plugging it back in while the upgrader is open, but it just says it's not in update mode.

So I can't program with it because it needs to be upgraded, and I can't upgrade it because it doesn't survive a reset in update mode.

I tried to download an older version of the firmware, to maybe bridge a version gap, but it keeps taking me back to 009.

Google surprisingly didn't come up with much related. Either my google foo is rusty or these is something wrong, maybe an older version of the programmer firmware in place? That or it's a fake board, but I doubt that.

[Tesla DeLorean]

Generally you have to just reset the board.

But in the other mode it still has to load new drivers, and Win 7 this can take a lot of time the first go around, so make sure it's completed the driver install before pushing forward.

Use high quality USB cables, not charging cables, avoid hubs and docking stations.

Machines locking out USB MSC device may also be a challenge.

[PCamp.2]

Thanks. I'll put my question on hold. Because my VM just ran out of disk space. Which could be a cause, or cause by.

While I have used the STLinks connected to a VMs. I'm not convinced I have upgrade the STLink in a VM. So if fixing disc space and restoring my STMCube Repo doesn't fix it, I'll look there.

[PCamp.2]

Turns out this was the VM causing the issue. When you use a USB device on a VM you have to add it to a list of devices (or the host takes it). When the STLink upgrade tool resets the device into "stlink bootloader" it will appear as a different device to the USB selector, so the VM never seen the STLink bootloader as it never got assigned to the VM.

It's fixable, but it was just as easy to do the firmware upgrade on a physical machine.