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


Release target

Hi,

While trying to upload a release I’m having this error:
-------

Warn : Could not determine executable path, using configured BINDIR.
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: 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : vid/pid are not identical: 0x0483/0x374B 0x0483/0x3748
Info : using stlink api v2
Info : Target voltage: 3.227913
Info : STM32F103C8Tx.cpu: hardware has 6 breakpoints, 4 watchpoints
adapter speed: 950 kHz
Error: timed out while waiting for target halted
TARGET: STM32F103C8Tx.cpu - Not halted
in procedure ‘program’
in procedure ‘reset’ called at file “embedded:startup.tcl”, line 490
in procedure ‘ocd_bouncer’

    • Unable to reset target **

shutdown command invoked

------

Debug tagret is uploading without trouble. I’d be grateful for any hint. I suspect my ignorance, most of all. Is there a good instruction on target configuration for Eclipse/SW4STM32?

Hi,

I suppose you didn’t connect Reset line from STLink to your mcu reset pin ?

I recommend also to update the STLink firmware to a newer version JTAG v17 is old.

For the reset, if you don’t want to connect it, you can use the “Software system Reset” reset config in debugger tab of debug configuration.

Rgds,
Laurent

I use Software System Reset. Debug is OK, Release is not. My hardware is STLink dongle and the Blue Pill, all the 4 lines in use.

>> I recommend also to update the STLink firmware to a newer version JTAG v17 is old.

I did the upgrade, with impunity. Nothing broken :-) . How am I supposed to check the version? stutils does not seem to have an option for checking stlink version.

Hi,

STutils, i don’t know but “STlink Utility” for windows or “STM32 Cube Programmer” for all OSes, yes, the STLink fw upgrade is integrated and you can check the version.

Rgds,
Laurent


Strange, i see in log: srst_only separate srst_nogate srst_open_drain connect_assert_srst
connect_assert_srst means “connect under reset”

I did the test on a nucleo_F4 in Release, i got “reset_config none” for software system reset so i suggest you review your Release debug configuration.

What do you call “Release debug configuration”? I’ve got “Run > Debug Configurations...” and “Run > Run Configurations...” int the main menu. They are one and the same thing, which I can’t understand. Both have “Software system reset” on Debugger tab, quite naturally.

There are Build Settings in Project Properties, which are obviously important and poorly understood by me :-) . They have nothing to do with reset mode, it seems.

Finally, there is “Target > Program chip...”. There is “reset after program” checkbox there, which I use. It works with project/Debug/project.elf and does not work with project/Release/project.elf.

That’s all. I am not at all sure about how I am supposed to use all these tools properly. There are also *.bin files, which must be there for a reason. What am I supposed to do with them? I don’t really understand the big picture, and have not yet found a good introduction.