Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

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


 

Newest Forum Posts

  1. reservation car service Seattle by Jamesprede, 2025-05-01 10:06
  2. Last day: drone bonus by Danielrug, 2025-04-19 16:55
  3. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-25 07:37
  4. SPI on Nucleo_STMH533RE by royjamil, 2025-03-23 11:31
  5. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-23 09:33
  6. Configuring DMA for ADC in SW? by sam.hodgson, 2025-03-04 12:58
  7. Insightful Perspectives on This Subject by davidsycle, 2025-03-04 05:45
  8. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  9. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  10. Build a project in "release" mode by tang, 2025-02-20 10:36

Last-Modified Blogs