• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 101 subscribers
  • Views 708 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

omapl138e boot problem

nick24
Prodigy 100 points
Other Parts Discussed in Thread: OMAPL138

Hello!

I am using OMAPL138E processor with CCS 5.2.1.

Booting omapl138E from spi flash i found that spi flash read process simply stopped and program not started, jtag unfortunately inaccessible. But some commands from AIS were done.

Program itself, loaded by debugger, works well.

Interesting, that the same program slightly reduced in size successfully booted.

May be someone can help to understand what is wrong, and how to solve the problem?

Nick.

  • 0
    TI__Guru** 116100 points
    Hi,

    Interesting, that the same program slightly reduced in size successfully booted.

    How did you reduce the size of that binary ?

    Is that ARM or DSP code ?


    Booting omapl138E from spi flash i found that spi flash read process simply stopped and program not started, jtag unfortunately inaccessible. But some commands from AIS were done.

    You meant that you are able to boot the code via debugger but not with SPI flash boot and able to SPI boot with less size binary ?
  • 0 in reply to Titusrathinaraj Stalin
    Prodigy 100 points

    Hello!

    This is program for DSP.

    Actualy, I were reduced size of program itself, by comment some portions of code. Consequently size of binary reduced too.

    I can load and run program via debugger, but when I load binary file of that program into the flash, processor can't boot.

    Yes, I use the same program compiled with less code. And binary of that program boots processor from spi flash memory ok.

    Sorry, for my English.

    Thanks.

    Nick.

  • 0 in reply to nick24
    TI__Guru** 116100 points
    Hi Nick,
    Please make sure that you have not used big size binary more than SPI has.
    What about size of those binaries (working and not-working) ?
    Are you using bootloader to run DSP app since you are using OMAPL138 (ARM boot master) ?
    Which package are you using ?
    Your own code or from starterware ?


    I can load and run program via debugger, but when I load binary file of that program into the flash, processor can't boot.

    Able to get any output from ARM bootloader and not able to boot/get print from DSP ?
  • 0 in reply to Titusrathinaraj Stalin
    Prodigy 100 points

    Hello.

    Now I can explain my problem more clearly.

    I have program working via debugger. And this program not working when processor booted from spi flash (boot successful !!! and program not works).

    Program stalled trying communicate through I2C channel. Only 1 address byte sended. Jtag is opened, and I can connect to processor.

    I have only one idea, that interrupt vector (i2c) was wrong.

    I am using OMAPL138BZCED4E processor (DSP master). Code generaly from Starterware.

    From the other hand, I have another one slightly different program that work welI via debugger and from spi flash.

    Thanks.

    Nick.

  • 0 in reply to nick24
    Prodigy 100 points
    Sorry, it was my mistake, Secure version of DSP has protected regions in L2 memory during boot load process.
    No problems. Every thing ok, up to this moment. Thanks for your replies.
    Nick.
  • 0 in reply to nick24
    TI__Guru** 116100 points
    Sounds good Nick.
    Thanks for your update.