• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 142 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM2634: TMDSCNCD263

Abdelrhman Afifi
Intellectual 415 points
Part Number: AM2634

What is the difference between loading the elf directly into the RAM and SBL loading the app image into the RAM?

I have an application when I load it to the RAM it is working fine, when I convert it to an appimage and flash it with the eQSBI SBL the SBL is started but the application is not working as expected.

Is there something special that happens while copying the application to the RAM? Is there any header added to the code itself or any extra checking that is not fulfilled by the application?

Best regards,

  • 0
    TI__Mastermind 26145 points

    Hi Abdelrhman Afifi,

    Abdelrhman Afifi said:
    What is the difference between loading the elf directly into the RAM and SBL loading the app image into the RAM?

    By loading directly into the RAM do you mean loading via debugger ? If yes, then CCS or for that matter any debugger supports ELF loading into the RAM memory only. Once the power on reset or warm reset is asserted, the data is cleared.

    Well in case of flashing the image into the QSPI, will help you load the image on every power cycle as flash has non-volatile memory. App Image is a custom format defined by TI to load the images into respective memories.

    Abdelrhman Afifi said:
    I have an application when I load it to the RAM it is working fine, when I convert it to an appimage and flash it with the eQSBI SBL the SBL is started but the application is not working as expected.

    Currently the SBL does not handle the Load/Run Address and the copy table behavior. Also the sections in the linker must be 8 bytes aligned. Check SDK's example of hello_world.

    Abdelrhman Afifi said:
    Is there something special that happens while copying the application to the RAM? Is there any header added to the code itself or any extra checking that is not fulfilled by the application?

    The application is simply copied to RAM. There is no header etc. appended nor there is any check of that sort apart from the restrictions mentioned.

    Hope it helps.

    Best Regards,
    Aakash