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


STLink Downloading Issue[SOLVED]

Hello,

I cant download compiled binary file to stm32 without Error using “External Tools Configurations -> Program” interface.
Here is the configuration:
DownloadConfig


ST-Link Output is::


STM32 ST-LINK CLI v2.4.0
STM32 ST-LINK Command Line Interface

ST-LINK SN : 49FF72064983515114290987
ST-LINK Firmware version : V2J23S0
Connected via SWD.
SWD Frequency = 4000K.
Target voltage = 2.9 V.
Connection mode : Normal.
Device ID:0x422
Device flash Size : 256 Kbytes
Device family :-STM32F302xB-xC/F303xB-xC/F358xx

Loading file...
Flash Programming:
File : E:\workspace_ll\NT7538_Test\Release\NT7538_Test.bin
Address : 0x00000000
Memory programming...
±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±± 0%
0%
Memory programming...
ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ 100%
Internal command error
Error occured during program operation!
Programming Complete.

MCU Reset.


My opinion is ST-LINK_CLI.exe isn’t proper for .bin file downloading? If it is true how can I build .hex file?

Tunisia

Hello,

have you tried to connect under reset (-c SWD UR)

-c SWD UR -P ${workspace_loc}${config_name:{project_name}}\${project_name}.bin 0x08000000 -Rst


>> My opinion is ST-LINK_CLI.exe isn’t proper for .bin file downloading? If it is true how can I build .hex file?
ST-Link_CLI is proper for .bin & .hex loading
If you are looking to generate .hex file, this is possible through :
Project Properties > C/C++ Build > Settings > Build Steps (TAB) > Post-build steps :
replace this command:

arm-none-eabi-objcopy -O binary "${BuildArtifactFileBaseName}.elf" "${BuildArtifactFileBaseName}.bin"

by the following command:

arm-none-eabi-objcopy -O ihex "${BuildArtifactFileBaseName}.elf" "${BuildArtifactFileBaseName}.hex"


Edit :
You can also program you chip using SystemWorkbench (without debug)
in Project Explorer view > right click in your project > contextual menu > Target > Program chip

Regards,
Tarek


Thanks for extra informations. The last option is working well.I’ll continue with that :-)

-c SWD UR -P ${workspace_loc}${config_name:{project_name}}\${project_name}.bin 0x08000000 -Rst this command also isn’t worked for me. I cant figure out why that method isn’t worked. While I was using ARM-GNU plugn-in I was downloading like that.

Best regards,
Nazım