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 two short videos (registration required) highlighting:

System Workbench for STM32


Some (beginners) problems with OpenSTM32

Ok, debugging works so far...thanks a lot!

Now there is one problem left, when i try to program the chip: (target->prorgramm chip)

05:06:02 **** Programing project test1 on chip ****
/home/harry/.eclipse/org.eclipse.platform_4.5.2_1473617060_linux_gtk_x86_64/plugins/fr.ac6.mcu.externaltools.openocd.linux64_1.8.0.201603291120/tools/openocd/bin/openocd -f test1.cfg -s /home/harry/workspace/ARM/test1/SW4STM32/test1 -s /opt/eclipse/../../home/harry/.eclipse/org.eclipse.platform_4.5.2_1473617060_linux_gtk_x86_64/plugins/fr.ac6.mcu.debug_1.8.0.201603291114/resources/openocd/scripts -c “program Debug/test1.elf verify exit”
Open On-Chip Debugger 0.10.0-dev-00265-g12ff60f (2016-03-11-12:04)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
srst_only separate srst_nogate srst_open_drain connect_assert_srst
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
in procedure ‘program’
in procedure ‘init’ called at file “embedded:startup.tcl”, line 473
in procedure ‘ocd_bouncer’

    • OpenOCD init failed **

shutdown command invoked

I’ve used the board-definition i created when initialy launched openocd.

What’s going wrong?
I think, it has to do with the reset-handling....any idea?

Harry