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


Listing of generated code

Is there a way to get a listing of code generated by eclipse, source lines and assembly?
Thx, Martin.

Tunisia

Blindly, I could tell you to add ‘-S’ to compiler command (Project Properties > C/C++ Build > Settings > Tool Settings (TAB) > MCU GCC Compiler > Miscellaneous > Other flags)

http://www.delorie.com/djgpp/v2faq/faq8_20.html


Unfortunately this won’t work for you (I have tested it) :/

After some digging I found something (-Wa,-adhlns=xxx.lst) but the problem is how to put it in (eclipse) gcc compiler options ....

The twisted way I found, is to add this
-Wa,-adhlns="$(@:%.o=%.lst)"
in Project Properties > C/C++ Build > Settings > Tool Settings (TAB) > MCU GCC Compiler > Miscellaneous > Other flags


Update: this command will generate lst file for each c file
To generate listing for the hole application, you can use objdump
To add the call to objdump after build you have to add it in post-build steps (Project Properties > C/C++ Build > Settings > Build Steps (TAB))

arm-none-eabi-objdump -D "${BuildArtifactFileBaseName}.elf" > "${BuildArtifactFileBaseName}.lst"

As you can see the Command field of pot build steps is not empty, to conserve old post build steps add &&
eg.

arm-none-eabi-objdump -D "${BuildArtifactFileBaseName}.elf" > "${BuildArtifactFileBaseName}.lst" && arm-none-eabi-objcopy -O binary "${BuildArtifactFileBaseName}.elf" "${BuildArtifactFileBaseName}.bin" && arm-none-eabi-size "${BuildArtifactFileName}"
Thanks for your effort! Will try that.