System Workbench for STM32

> Ok, v1.10.0 is the latest version.
great.
> Driver is ok and since you can use STLink utility, it is ok on this side.
great
> I said to not let an STLink connection active on another software (like Stlink utility) or another ide like co-ide because > > you can only have 1 STLink connection active.
> Reboot the disco (and the PC) and try again.
Rebooted and still get the same problems....... 😑

> Win 7, 64 or 32 bits ?
64bit

> The error message "open failed", you get it when no stlink board is connected.
> And if i let a STLink utility connected, i have the libusb error access added on the message:
> Info : clock speed 1800 kHz
> Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
> Error: open failed
> in procedure 'init'
> in procedure 'ocd_bouncer'

I assume this is when doing a target-erase or similar, rather than debug? In which case that is similar but not the same. I get no mention of libusb_open()
I just disconnected my nucleo board (so no st link present) and get exactly the same errors as I posted above. Not sure what that tells me though....

EDIT: I just re-read your last post. So
"Error: open failed" on its own means no stlink is not connected.
and "Error: libusb_open() failed with LIBUSB_ERROR_ACCESS. Error: open failed" means stlink util is still connected?

So my errors are saying it cannot find any connected stlink? Correct?

Thanks
Toby