![]() ![]() The OpenOCD binaries were downloaded from Freddie Chopin’s site. The version of OpenOCD that I’ll be using is 0.8.0 and my test system will be Windows 7 圆4 using Cygwin. hex binaries and do interactive debugging using Eclipse. Once you’ve got a live OpenOCD connection you can flash your. In the rest of this article I’ll take each board that I’ve got and explain how to connect and use it with OpenOCD using the ST-Link v2 programmer. There are still some places offering the older ‘v1’ version. If you’re buying elsewhere then make sure that you’re getting the ‘v2’ device. At the time of writing it’s only £18.68 plus VAT at Farnell. Not only is it the most compatible of all the programmers and debuggers, it’s also probably the cheapest. Times have changed since those early days and now since the release of version 0.7.0 of OpenOCD the support for ST-Link is completely stable and there’s no reason why you can’t use ST-Link v2 for all your STM32 programming and debugging needs. It’s fast, reliable and it costs double what you should be paying for an ST-Link v2. This is a JTAG-based programmer that is compatible with ARM devices from many manufacturers. Because of the lack of support in OpenOCD for ST-Link v2 I was forced to go down the third party route and use the Olimex ARM-USB-TINY-H for all my F1 programming and debugging. The situation with the commonly available third party F1 boards was always less clear because up until a year or so ago the ST-Link interface was not fully operational in the popular and free OpenOCD debugger. I suppose that when you are the manufacturer of these MCUs it’s cheaper to do it this way than to manufacture a custom ST-Link IC just for this purpose ![]() The embedded ST-Link debugger on the discovery boards is implemented inside ST’s own STMF32F103C8T6 MCU in a 48 pin QFP package with an external 8MHz clock. We’ve been lucky with the official ST discovery boards because they all come with an ST-Link included on the PCB so you don’t need to buy anything else at all to get a complete C++ development and visual debugging environment up and running. Third party boards dominate my collection for the F1 series whilst I have official ST discovery boards for the F0, F4 and F1 Value Line. Present in the original source code during compiling the utility.Over the last few years I’ve amassed quite a collection of STM32 development boards. The directory/line numbers “C:\Users\User\Downloads\stlink\src\sg.c” seems to refer to the assertions T11:14:26 ERROR C:\Users\User\Downloads\stlink\src\sg.c: Could not open stlink device However, when I manually invoke st-util forcing ST-LINK/V1 mode (st-util.exe -1), I see: T11:14:26 WARN C:\Users\User\Downloads\stlink\src\sg.c: Failed to find an stlink v1 by VID:PID = Took 38.89 seconds =įrom above, the USB VID:PID seems to be 001:006 T11:08:57 WARN C:\Users\User\Downloads\stlink\src\usb.c: Error -12 (No error) opening ST-Link/V2 device 001:006 pioenvs\disco_f100rb\firmware.elfīuilding. pioenvs\disco_f100rb\FrameworkMbed-TARGET_STM-611d4\stm_spi_api.oĬompiling. Verbose mode can be enabled via `-v, -verbose` optionĬompiling. Ĭommand: platformio.exe run -e disco_f100rb -target upload Processing disco_f100rb (platform: ststm32, board: disco_f100rb, framework: mbed) Ideally, I would like to upload using platformio and get gdb up over ST-Link/V1. I have the STMicro “official” GUI “ST-LINK Utility” program v4.0.0.0, I am able to connect to my board and upload the binary built by platformio and can get my blinky program to work.ġ9:39:04 : ST-LINK Firmware version : V1J13S0ġ9:39:04 : Debug in Low Power mode enabled. ![]() T20:55:57 ERROR C:\Users\User\Downloads\stlink\src\sg.c: Could not open stlink device T20:55:57 WARN C:\Users\User\Downloads\stlink\src\sg.c: Failed to find an stlink v1 by VID:PID When I try to use the st-util to connect (forcing ST-Link/V1), I see The STM32VLDISCOVERY uses the ST-Link/V1 protocol (mounts the board as a USB storage device), but seems platformio is trying to upload using the ST-Link/V2 protocol instead. T20:03:24 WARN C:\Users\User\Downloads\stlink\src\usb.c: Error -12 (No error) opening ST-Link/V2 device 001:004 I can build the binary, but see this issue while uploading. I am learning mbed on a 5-year old STM32 VL DISCOVERY board that was lying around (platform: ststm32, board: disco_f100rb, framework: mbed). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |