Is there an version of OpenOCD with support for the STM32F413
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-04-04 5:50 AM
Hi,
I tried to connect to the STM32F413 with OpenOCD, but I get the following error:
Info : device id = 0x10006463
Warn : Cannot identify target as a STM32 family.Error: auto_probe failedI searched the source code of OpenOCD 0.10.0 and it seems as if the F413 is not yet supported. Does anyone has a patched version of OpenOCD with support for the STM32F413?
Best regards,
Stefan
#openocd #stm32f413Solved! Go to Solution.
- Labels:
-
STM32F4 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-04-04 7:32 AM
You know they have a mailing list?
https://sourceforge.net/p/openocd/mailman/message/33251369/
The patch would be pretty trivial, at least to get basic functionality, ie recognize the 0x463 Device ID and set memory sizes. Try it, it shouldn't be that hard.
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-04-04 7:32 AM
You know they have a mailing list?
https://sourceforge.net/p/openocd/mailman/message/33251369/
The patch would be pretty trivial, at least to get basic functionality, ie recognize the 0x463 Device ID and set memory sizes. Try it, it shouldn't be that hard.
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-04-05 2:06 AM
Hi,
that's right. Adding the device id to OpenOCD was not very hard. It was much harder to compile OpenOCD for Windows, but I finally could compile a basic version with at least support for the st-link.
Another issue was to update the ST Link Adapter's firmware. With the old firmware there was a cryptic error message about address wrapping.
Now I can start porting my application to the STM32F413.
