• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 328 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 new design arm926 problem

Chen Li
Prodigy 70 points
Other Parts Discussed in Thread: OMAP-L137

Hi all,

I designed a omap-l137 based board that referenced the DA830  EVM board.

When I use CCS3.3  to connect the two processors, only the DSP could be reached. Then I try to connect the ARM926 manually, and it can successfully connect the ARM926.

But when I download the armubl, download process fail at 0x8000 0050 (which is a shared ram in the chip)becsuse of data vierify failed.

Even the nandwriter which will run in the external SDRAM could not download to the target memory.

On the contrary, at DSP side all things are OK.

After I burn the all pre-compiled image  to the nand flash at DSP side, I get nothing from the uart console at host side.

Does anybody meet the same strange problem or provide any suggestion?

Thanks!

  • 0
    Prodigy 70 points

    The omap-l137's sillicon version is 1.1.

  • 0
    TI__Mastermind 27585 points

    The DSP must wake the arm up in order to connect to it in CCS. The GEL file you have on the DSP does this for you when you connect.

    I suggest connecting to the ARM and trying to write to the memory location that is failing to make sure it is accessible.

    Also, is your baud rate 115200 on your uart console?

    Jeff

  • 0 in reply to jc-ti
    Prodigy 70 points

    Jeff;

    Thanks for your reply.

    I connect CCS to the arm core, and try to download the armubl(bin file from TI) to 0x8000 0000. CCS pop a dialog and says: data verify error at 0x8000 0050.

    So I edit the linker.cmd and relaocate the code to 0x8000 0100. CCS also pop a dialog and says: data verify error at 0x8000 0150.

    The address start from 0x8000 000 is internal ram, and the DSP can accesss it, why could not the ARM core?

    Is there any special pin should be configured or others?

    This problem almost drive me mad!!! 

  • 0 in reply to Chen Li
    TI__Guru* 83745 points

    Hi Chen Li

    Since you said it is a custom board that you designed, can you please confirm that pin number H6 and H12 (device internal RAM supplies) are connected to 1.2V?

    Regards

    Mukul

  • 0 in reply to Chen Li
    TI__Mastermind 27585 points

    Did you try poking at 0x80000050 in the memory window from the ARM side? Was it able to read/write correctly?

    Jeff

  • 0 in reply to jc-ti
    Prodigy 70 points

    Jeff, Mukul and those who care about this post:

    We finally find this is a power on reset problem. Because we have not bought the glue logic for the reset circuit, and only a pull up resistor is connected to the reset pin. After we tie the reset pin to the output of the power monitor chip, it works! 

    It seems that omap-l137 need a external power on reset, or it will not run.

    Is it right?

    Or where could i find any useful thing about the power on reset constraints?

    Thanks a lot!

    Best regards.

    Chen Li