Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32

Forum List Topic List

[ prev topic ]  

AC6 OpenOCD and stm32wb [SOLVED]

Posted by Lefix on 2019-04-04 11:11

Hi,
With my team we’re currently prototyping a device on a newly stm32wb.
We’re working under Linux so all our project are based on Makefile.
I’ve noticed that openocd plugin for AC6 differ from last dev version of official openocd repository...

First, stm32wb55x.cfg don’t exist in “official” version.
Then stm32wb55x.cfg make call to `flash erase_padded_zone 0` that is unknown in “official” version.

So my question is: Does AC6 provide somewhere its version of OpenOCD which can be built and launched as a standalone tool?

Here are versions given by both OpenOCD:
Local install based on last dev revision:
Open On-Chip Debugger 0.10.0+dev-00763-g5202d82a (2019-04-04-10:54)

Eclipse plugin:
Open On-Chip Debugger 0.10.0-dev-00019-g5352c55 (2019-02-14-15:31)

PS: I read somewhere that Eclipse use gnu-openocd but this version seems to be behind AC6 version too:
https://github.com/gnu-mcu-eclipse/openocd/releasesQuestion

Reads: 3847
Link
Posted by Lefix on 2019-04-05 13:49

Here is my progress,

I’ve found ac6 repository for openocd at git://git.ac6.fr/openocd.Question
Last tag on st branch “st_2.8.0” matches the git hash 5352c55 of installed openocd used by eclipse.
- The fact is that this version doesn’t seem to compile because of calls to JIM old API...
- Once compiled, stm32l4x.cfg tcl file isn’t enough to connect to target because of bad DEVICEID
- Finally, with a custom stm32wbx.cfg openocd connect, then freeze when trying to flash with command openocd -d3 -c “program binFile.bin verify reset exit 0x8000000” or openocd -d3 -c “program elfFile.elf verify reset exit”

Thank’s for your attention, if someone has information about this I’ll be pleased to hear of.

PS: I’ve attached my modifications patch to this message
PPS: Same error is reproductible with a stm32l4 (Nucleo board in my case)

st_2.8.0_fix.patch (7.79 Kb)
Link

Posted by Lefix on 2019-04-05 15:36

Finally i managed to get it working

Using official repo https://git.code.sf.net/p/openocd/codeQuestion
Then applying to patch corresponding to these commits:
- https://sourceforge.net/p/openocd/code/ci/2e8b2c4e516c5eef4790688840c2f2fb956bc46a/Question
- https://sourceforge.net/p/openocd/code/ci/0018081ed3cb1200e74d9911e66f1edf72e75579/Question
Finally including tcl script in the cfg file:
source find interface/stlink-v2-1.cfg
source find target/stm32wbx.cfg

I put commits patch as attachement

g2e8b2c.patch (27.25 Kb)
Link