JStolle

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Bootloader Tutorial – build failed #25037
    JStolle
    Participant

    Hi,

    I checked, but step 19  had been done. Build dependencies are looking good and the build itself is going well – first bootloader, then application, but at the linking at the end of both builds, the bootloader.bin is missing:

     

    ….

    1>stm32f4xx_ll_utils.c
    1>Linking ../VisualGDB/Debug/Bootloader…
    1>——————- Memory utilization report ——————-
    1>Used FLASH: 2676 bytes out of 1024KB (0%)
    1>Used SRAM: 44 bytes out of 128KB (0%)
    1>Used CCMRAM: 0 bytes out of 64KB (0%)
    2>—— Neues Erstellen gestartet: Projekt: MainApplication, Konfiguration: Debug VisualGDB ——
    2>LEDBlink.cpp

    ….

    2>stm32f4xx_ll_utils.c
    2>C:\SysGCC\arm-eabi\bin\arm-eabi-ld.exe: cannot find C:/Users/jan.stolle/source/repos/BootloaderDemo/VisualGDB/Debug/Bootloader.bin: No such file or directory
    2>C:\Users\jan.stolle\source\repos\BootloaderDemo\MainApplication\bootloader.props(4,2): error : Build failed: arm-eabi-ld.exe exited with code 1

    As written before, that program has been cloned directly from the git-hub repository. It is working if built separate, but not if done using the rebuild-function on the main-application. I can live with that, but it is a bit bothersome.

     

    Regarding the entry point, it was my mistake. I misread the tutorial and changed the stackpointer of the bootloader instead of the main-application. That part has been fixed and is working.

    • This reply was modified 5 years, 5 months ago by JStolle.
    in reply to: Bootloader Tutorial – build failed #25011
    JStolle
    Participant

    As I do not have the hardware to debug the original tutorial program this is the result of the debugging of my own program (based on the tutorial) with the same problem:

    If I build the two programs (bootloader, main app) separately I do not get an error. But when debugging it does start at disassembly (Starting point seems to be the reset-vector of the main application) and gets stuck at some point, therefore returning to the reset vector. I am however not able to get to a breakpoint either in the bootloader or the main app.

    (Reset Target after programming is set).

    When debugging the bootloader as standalone the _app_start address and the _estack seem correct in the debugger.

    Also in the Embedded Memory Explorer of the main application I can see the .bootldr section with the correct range, but it says “Other” inside with the indication that the space has been lost due to padding between symbols. Is there another way to see the memory of the combined programs?

    Greetings

    Jan

    <hr />

    I rebuild the whole program using gnu make and the bootloader makefile tutorial. This seems to work without a problem.

    • This reply was modified 5 years, 6 months ago by JStolle.
    in reply to: Bootloader Tutorial – build failed #25010
    JStolle
    Participant

    Hi,

    it seems the Bootloader.bin file is missing, when building the two projects separately it gets generated. With rebuild however it gets deleted and is not regenerated(or deleted immideately after generation – hard to see), although the compilation itself happens for both projects.

    So is there some general setting ( like only-delete-bin-files-at-first-rebuild? ) I am missing?

    Greetings

    Jan

Viewing 3 posts - 1 through 3 (of 3 total)