cancel
Showing results for 
Search instead for 
Did you mean: 

Is there an version of OpenOCD with support for the STM32F413

Stefan W
Associate II
Posted on April 04, 2017 at 14:50

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 failed

I 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 #stm32f413
1 ACCEPTED SOLUTION

Accepted Solutions
Posted on April 04, 2017 at 16:32

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.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

View solution in original post

2 REPLIES 2
Posted on April 04, 2017 at 16:32

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.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
Stefan W
Associate II
Posted on April 05, 2017 at 11:06

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.