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


Unable to run CubeMX created code on STM32F4-DISCOVERY

Hi!
I am absolutly new to all this arm programming stuff and currently kind of frustrated.
After I tried out this tutorial to printf logs for debugging i can’t run any code on my chip EXCEPT of debugging?!

I do no understand what is going on and it would be really awesome if I can get any help of you guys!

Here are the logs I get from SWSTM32.

By the way great work for this awesome toolsuite!

Open On-Chip Debugger 0.10.0-dev-00007-g58350bc-dirty (2018-01-12-12:21)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter_nsrst_delay: 100
adapter speed: 1800 kHz
Info : clock speed 1800 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : STLINK v2.1 JTAG v30 API v2 M19 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 2.899586
Info : Stlink adapter speed set to 1800 kHz
Info : STM32F407VGTx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : Stlink adapter speed set to 1800 kHz
adapter speed: 1800 kHz
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08002a54 msp: 0x20020000
configuring PLL
Info : Stlink adapter speed set to 4000 kHz
adapter speed: 4000 kHz

    • Programming Started **

auto erase enabled
Info : device id = 0x10076413
Info : flash size = 1024kbytes
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x20000046 msp: 0x20020000
wrote 16384 bytes from file Debug/HID_TEST1.elf in 0.978830s (16.346 KiB/s)

    • Programming Finished **
    • Verify Started **

target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000002e msp: 0x20020000
verified 11132 bytes in 0.795881s (13.659 KiB/s)

    • Verified OK **
    • Resetting Target **

Info : Stlink adapter speed set to 1800 kHz
adapter speed: 1800 kHz
shutdown command invoked

Hi,

I only see an error from Libusb but it is maybe because you’re using Win10 or USB3.1 port ?
But anyway, this error is not blocking and you can see in the log that you have correctly programmed and verified an reseted your target.

So, i don’t understand your question, you can’t debug your program ?
Can you try to use the menu “Debug As” => “AC6 stm32 C/C++ appli...”.
It should Program your appli and Stop on Main.

Rgds,
Laurent

Debugging is absolutly possible.

I can’t run the programm on the chip. Just by clicking run it doesn’t work. Only in debug mode. But this “deployment” doesn’t stay on the chip. After closing the debug connection the chips resets to some undefined state.
I expected that run just flashes the compiled code to the chip. Is that correct?

Hi,

“Run” will indeed erase and flash and verify and optionally reset the target.

Maybe the stlink stay in debug swd mode.
It shouldn’t as the shutdown command is invoked at the end and we exit swd mode normally.

Or maybe your “Debug” config is letting something different than in “Release” config.
Can you try to set “Release” config and “Run” again to see if any difference ?

Rgds,
Laurent