• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 347 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.

Binary file from CCS

Tobias Knutsson
Prodigy 150 points
Other Parts Discussed in Thread: OMAP-L137

Hello,

I'm using the OMAP-L137 EVM Kit to run a GNU/Linux system and that is working fine. Now I would like to load a DSP-application into RAM and have the DSP execute it. My question is, is there a simple way of compiling a raw binary that I can place in RAM and execute? In essence, what I want to do is to capture the data that "File->Load Program" stores in RAM on the target, into a file that i can load into RAM from the Linux system running on the ARM CPU.

  • 0
    TI__Mastermind 41665 points

    I believe you could do this with the hex conversion utility (hex6x.exe) with the -b option, though I am not sure this is well documented in SPRU186, I have seen it used with the UBL conversion to binary, the UBL build may make make a good reference for this sort of thing.

    Tobias Knutsson said:
    In essence, what I want to do is to capture the data that "File->Load Program" stores in RAM on the target, into a file that i can load into RAM from the Linux system running on the ARM CPU.

    This would be a different approach that may also work, you can save and load raw data on the target with the File -> Data... menu of CCS, I suppose if you knew where everything was being loaded by the .out file and it was all relatively contiguous that you could make a dump of the loaded image and restore it later, however I have not tried this.

  • 0 in reply to Bernie Thompson TI
    Prodigy 150 points

    Thank you, after examining ubl2bin.cmd from the ubl project I managed to create a compatible binary. Now my problem is how to release the DSP from reset. I have tried to power up power domain 1 by writing 1 to the NEXT field in PDCTL1 and writing 0x00000103 (Enable state and de-assert local reset) to MDCTL15 and then written a 2 to PTCMD but reading from MDSTAT15 reveals the DSP to remain in reset. However, looking in CCS the DSP is reported to have both power and clock on and not in reset. What am I missing?

  • 0 in reply to Mariana
    Prodigy 150 points

    The thing is that I do not want to have a custom application in the DSP ROM. There must be some way to release the DSP from reset, right?

    Other then transitioning from SwRstDisable state to Enable state and de-asserting local reset, what are the steps required to release the DSP from reset?  

  • 0 in reply to Tobias Knutsson
    Prodigy 150 points

    Ok, problem fixed.

    It turns out that you do not have to do anything else. You do however need to enable for example the gpio module if your test application is the led test program. I was trying my code in u-boot, at which point these modules had not been initialized yet. If I booted Linux first, it all worked fine. The thing that confused me was that connecting to CCS and then disconnecting again apparently enables all modules.