This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP-L138: Bootloader Sections overwrite in GNU GCC Toolchain

Part Number: OMAP-L138


Hi there,

we recently changed from using Keil ARM Toolchain to GNU gcc Toolchain v7.1 to build our application for OMAP-L138. I am booting my OMAP from SPI-Flash.

We use AISgen to generate our bootloader binary with the neccessary startup code from elf File. This worked perfectly for me when using Keil ARM Toolchain.

Now after switching to gcc Toolchain, it seems that some sections are overwritten somewhere in the build process. I am pretty sure, that I didn´t make a mistake in the new Linker command file.

Is it possible that AISgen gets confused with the changed elf structure provided by gcc toolchain, or did yet someone else report errors in using AISgen with gcc Toolchain?

The Startup code Aisgen added works well, I already checked this, the neccessary initializations are done properly, but some sections seem to contain rubbish, according to this fact, omap gets stuck.

All support is appreciated.

Best regards,

Chris

  • Hi there,

    I found a solution which may be helpful for other OMAP-Developers:

    AISgen does not seem to parse GNU-based ELF-files correctly. Some sections are omitted.

    I solved the problem just like this:

    - Use objcpy.exe to put the relevant sections in binary files - one for each dedicated memory region.

    - Give all these binaries with their load addresses to AISgen (AISgen manual tells you how)

    - Define the application entry point manually in AISgen

    Now you should be able to generate working GNU-GCC based Startup-Binaries.

    Best regards,

    Chris