Another debug launch and target program/erase failure......
> Did you update the software: menu Help => Check for update
Yes.So should be fully up to date.
>The nucleo F401re has a Stlink V2-1, not V2.
> So, use the default script that is inside the software (nucleo_f401re.cfg).
Thanks, but it made no difference whether I used default (nucleo_f401re.cfg) or manual Stlink V2-1.
Although I have found there are 4 copies (and two versions) of nucleo_f401re.cfg installed.
Paths are:
C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.debug_1.10.0.201607251855\resources\openocd\scripts\st_board
C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.debug_1.10.0.201607251855\resources\openocd\scripts\board
C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.debug_1.8.0.201603291114\resources\openocd\scripts\st_board
C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.debug_1.8.0.201603291114\resources\openocd\scripts\board
I am not sure which one it will pick up as the default?
> The error you get is “open failed” at the begining so i suspect a libusb issue.
> Either you have another session not terminated, either the driver is not installed correctly ? admin rights ?
> Or you didn’t close the STlink connection on another software ?
Would these things cause both the debug error as well as the target-erase... error?
I have checked the task manager, there are no st link apps or processes running. I am running something else at the moment but as soon as it is done I will do a reboot to double check but I doubt this is it.
I am using an admin account so again, this should not be a problem?
The stlink is shown as “StMicroelectronics STLink dongle” under “universal serial bus devices”. Driver used is “c:\windows\system32\DRIVERS\winusb.sys” version 6.1.7601.17514.
Any problems there?
Thanks for your help so far!
Toby