Forum Replies Created
-
AuthorPosts
-
carneytom1981Participant
Hi, thanks for your reply.
Sorry, I should have specified in my original post, I have already wrapped all relevant header and source files with
#ifdef __cplusplus
extern "C" {
#endif
// code#ifdef __cplusplus
}
#endif
Unfortunately, the Undefined Reference problem persists.
carneytom1981ParticipantI seem to have fixed this particular problem. I used Zadig to switch USB driver over to libusb-win32 and it now appears as ST-Link Debug in the device manager.
carneytom1981ParticipantThanks for your reply, I really appreciate your help with this.
I tried what you suggested. I pointed the driver installation GUI to
\\STMicroelectronics\STM32 ST-LINK Utility\ST-LINK_USB_V2_1_Driver
which contains the files ‘stlink_dbg_winusb.inf’ and ‘stlink_VCP.inf’.
As soon as I click ‘OK’ in the driver installation GUI I get an error message as follows
Select Device
The folder you specified doesn’t contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems
I have also attempted the same process, using a driver package downloaded from the ST website – en.stsw-link009.zip. But the result is the same.
carneytom1981ParticipantHi, Thanks for the response.
Thanks for the response. The ST-Link debug driver does not appear as shown, but rather, as shown in the attachment, as a single ‘STM32’ nested under a ‘USB Mass Storage Device’.
I have attempted uninstalling these devices through the device manager and reinstalling with the drivers I downloaded from the ST website but this results in the exact same situation.
You state that “the drivers are located inside the ST-Link Tool directory” – where exactly is the ST-Link Tool directory?
- This reply was modified 4 years, 5 months ago by carneytom1981.
Attachments:
You must be logged in to view attached files. -
AuthorPosts