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.

Changing SRAM Base Address does not work in non-debug environment

Other Parts Discussed in Thread: CC3200

Hi Experts,

I would like to change Base Address for my application and it works fine from debugger. It does not work when I flash it as mcuimg.bin and change SOP jumper to boot directly.

Following gcc linker configuration works fine for blinky example

SRAM (rwx) : ORIGIN = 0x20004000, LENGTH = 0x00030000

and following doesn't work though it works from debugger.

SRAM (rwx) : ORIGIN = 0x20005000, LENGTH = 0x0002F000

The reason I believe that gdb/ccs knows where to jump after loading image in SRAM but TI bootloader seems to expect image to be present only at 0x20004000. Is this a hard limit or there is any way around to tell TI bootloader where to find image.

  • Hi Vipin,

    You  are right, CC3200 bootloader expects the application image to start from 0x20004000 with first two locations as Stack Pointer(SP) and Entry Point (PC)  respectively for the application. This can't be changed.

    Thanks and Regards,

    Praveen

  • Hi Praveen,

    Thanks for the confirmation. I believe hardcoding the address is not a good choice. When generating a bin file you could add base address (4 bytes say at the start). Then bootloader could read it (as it reads entrypoint to jump) and load the image at the base address present in bin file itself. I believe that could give lots of flexibility to the developers. I don't think that approach is any different than finding entry point for the jump.

    Though you have correctly answered the query and confirmed the limitation, however I have not marked the answer as verified so that some TI person can take a note of this and provide flexibility in bootloader (hopefully in production chips at least)

  • Hi Vipin,

    Appreciate your suggestion!

    I am closing this thread as it explains the current status of operation.

    Best regards,

    Naveen