Skip to content
Snippets Groups Projects
  • Tom Rini's avatar
    320d9746
    am33xx: Correct NON_SECURE_SRAM_START/END · 320d9746
    Tom Rini authored
    
    Prior to Sricharan's cleanup of the boot parameter saving code, we
    did not make use of NON_SECURE_SRAM_START on am33xx, so it wasn't a
    problem that the address was pointing to the middle of our running SPL.
    Correct to point to the base location of the download image area.
    Increase CONFIG_SPL_TEXT_BASE to account for this scratch area being
    used.  As part of correcting these tests, make use of the fact that
    we've always been placing our stack outside of the download image area
    (which is fine, once the downloaded image is run, ROM is gone) so
    correct the max size test to be the ROM defined top of the download area
    to where we link/load at.
    
    Signed-off-by: default avatarTom Rini <trini@ti.com>
    
    ---
    Changes in v2:
    - Fix typo noted by Peter Korsgaard
    320d9746
    History
    am33xx: Correct NON_SECURE_SRAM_START/END
    Tom Rini authored
    
    Prior to Sricharan's cleanup of the boot parameter saving code, we
    did not make use of NON_SECURE_SRAM_START on am33xx, so it wasn't a
    problem that the address was pointing to the middle of our running SPL.
    Correct to point to the base location of the download image area.
    Increase CONFIG_SPL_TEXT_BASE to account for this scratch area being
    used.  As part of correcting these tests, make use of the fact that
    we've always been placing our stack outside of the download image area
    (which is fine, once the downloaded image is run, ROM is gone) so
    correct the max size test to be the ROM defined top of the download area
    to where we link/load at.
    
    Signed-off-by: default avatarTom Rini <trini@ti.com>
    
    ---
    Changes in v2:
    - Fix typo noted by Peter Korsgaard