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 ]  

Launching SW4STM32 debug fails

Posted by MaximeCh on 2017-10-02 22:02

Hello hopefully my last topic before starting learning from code for good,

I have my Eclipse-SW4STM32 project built, I can use the binary to fly the drone : the software looks working without major issue.
I have managed to launch a Texane/STLink GDB server by command line, with a STLink probe to connect to my custom F4 board : I can reach main breakpoint without issue.
Although, when I launch a debug session via Eclipse, it crashes during loading :

- here is the console output : https://pastebin.com/Y2wNER8b.Question

- here is the warning message “Error in final launch sequence
Failed to execute MI command:
load /home/maxzor/eclipse/workspace-pixracer/pixracer/obj/main/inav_PIXRACER.elf

Error message from debugger back end:
Error erasing flash with vFlashErase packet
Error erasing flash with vFlashErase packet”

-here is the content of .cfg script

  1. This is an Pixracer board with a single STM32F427VITx chip
  3. Generated by System Workbench for STM32
  4. Take care that such file, as generated, may be overridden without any early notice. Please have a look to debug launch configuration setup(s)


source find interface/stlink.cfg

set WORKAREASIZE 0x8000

transport select “hla_swd”

set CHIPNAME STM32F427VITx

  1. Enable debug when in low power modes

set ENABLE_LOW_POWER 1

  1. Stop Watchdog counters when halt

set STOP_WATCHDOG 1

  1. STlink Debug clock frequency

set CLOCK_FREQ 4000

  1. use hardware reset, connect under reset
  2. connect_assert_srst needed if low power mode application running (WFI...)

reset_config srst_only srst_nogate connect_assert_srst
set CONNECT_UNDER_RESET 1

source find target/stm32f4x.cfg


Any ideas?
Best regards

Reads: 8382
Link
Posted by LaurentL on 2017-10-03 10:20

Hello,

The error message in log is that it couldn’t halt the core and afterwards, the flash erase fails because the mcu is not halted.

I suspect the reset line is not connected on your target (from stlink).
Can you try to connect it and retry ?
If not possible to connect the reset, you must NOT use the default option “connect under reset” and you should use the “software reset” option (in debug configuration, in debugger tab, you can choose the stlink freq and connection mode).
In that case, you might not be able to reconnect if the mcu has a program running in low power...

The voltage is also measured at 0V so you didn’t connect the VDD of the mcu to the stlink input.
This is not mandatory to work but better for voltage adapter.

Rgds,
Laurent

Link
Posted by MaximeCh on 2017-10-03 11:39

Thank you,
Board does not have reset line, I think Ill get away since code might not have low power mode.
Also got 3.3 VDD input on stlink.
I can finally dig into code,
Best regards.

Link