Loading...
 
Skip to main content

System Workbench for STM32

Forum List Topic List

Forums » System Workbench for STM32 » Listing of generated code » Listing of generated code
You are viewing a reply to Listing of generated code
 
Thread actions
Print this page
  • Print all pages

    • Listing of generated code

    Posted by tarek bouchkati on 2016-02-21 14:39 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
    Copy to clipboard
    -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))

    Copy to clipboard
    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.

    Copy to clipboard
    arm-none-eabi-objdump -D "${BuildArtifactFileBaseName}.elf" > "${BuildArtifactFileBaseName}.lst" && arm-none-eabi-objcopy -O binary "${BuildArtifactFileBaseName}.elf" "${BuildArtifactFileBaseName}.bin" && arm-none-eabi-size "${BuildArtifactFileName}"
    Reads: 2652