• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 305 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.

OMAP-L137 DSP NOR boot

Erik Svensson
Prodigy 60 points

Hello,

I have successfully booted the DSP with images up to 32kb from NOR. But we need to be able to boot bigger images so I have been looking into loading images and starting from a first bootloader. My problem is that I don't know how to start the second program.

I have this program that should write a message on UART1 which is the second DSP program. I'm linking this into SDRAM (0xC3C00000). and generate a bin-file using hex6x. This program is successfully uploaded to NOR (0x60001000). Then I start my first bootloader which loads the image from NOR (0x60001000) into SDRAM (0xC3C00000). This is where I haven't gotten a clear answer on what to do. I have tried to move PC to _c_int00 (0xc3c00ee0) and _main (0xc3c000c8) indicated by the map file and execute from there with no result.

All programs are written using c and linked against rts64plus.lib (No BIOS), except the NOR uploader program written for the ARM and linked against rts32e.lib.

What do I need to know to boot my second DSP c program loaded from NOR?

 

  • 0
    TI__Mastermind 24340 points

    Hi Erik,

    It seems that you are on the right track. Here are some Debug suggestions that come to my mind:

    1) Check if your GPIO controlling of the higher addresses of the NOr flash is correct.

    2) Check if you are copying it correctly. You could try copying a simple file into SDRAM using your program and see it is correct.

    3) Try connecting to CCS and looking at the memory.

    4) Make sure that the c_int00 symbol is indeed in that address, every time you compile it can change.

    5) You can Load Symbols only and see where is your program.

     

     

  • 0 in reply to Mariana
    Prodigy 60 points

    Hello Mariana,

    Thank you for your reply.

    I've solved my problem. I used an old program file that overwrote itselfe in memory. I also started using the "-boot" option in hex6x. This means that I can extract the entry point from the image header. See http://e2e.ti.com/forums/p/3958/16992.aspx#16992 for reference.