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


STM32F072RBT6 not properly modeled in OPENOCD? 64K instead of 128K

Hi,

Maybe will help to activate debug level 3 (-d3) for OpenOCD.
(Here you can find how to do this http://www.openstm32.org/tiki-view_forum_thread.php?comments_parentId=977Question)

It is possible that OpenOCD creates a configuration that is not for STM32F0 MCU ?
My understanding is that OpenOCD creates the configuration at the beginning of the execution, but I don’t know what are the inputs. Probably the variables above are initialized at this time.


Something that can be useful is this:
12.1 Flash Configuration CommandsQuestion
http://openocd.org/doc/html/Flash-Commands.html#flashdriverlistQuestion
“Flash Driver: stm32f1x
Note that some devices have been found that have a flash size register that contains an invalid value, to workaround this issue you can override the probed value used by the flash driver.

flash bank $_FLASHNAME stm32f1x 0 0x20000 0 0 $_TARGETNAME”
(I think this will specify 128k)

Maybe you can ckeck if STM32 ST-LINK Utility reports the correct flash size.

I suppose you don’t use on-board ST-LINK debugger. Conform with ST NUCLEO-F072RB has a V2.1 debugger but from your log there is a V2.0

Hope this help somehow.