• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 1837 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.

.cmd File for OMAP L138

Majid Kazemitbaar
Prodigy 80 points
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Hello

I have a board with an OMAP-L138 Processor on it.

I need to run SYS/BIOS on the processor, but I have errors linking the .cmd file with it.

Errors:

=> Where do these "range overlaps" come from??

These are the contents of my .cmd file:

-stack 0x00000800

-heap 0x00000800

MEMORY

{

dsp_l2_ram: ORIGIN = 0x11800000 LENGTH = 0x00040000

shared_ram: ORIGIN = 0x80000000 LENGTH = 0x00020000

external_ram: ORIGIN = 0xC0000000 LENGTH = 0x08000000

arm_local_ram: ORIGIN = 0xFFFF0000 LENGTH = 0x00002000

}

SECTIONS

{

.far > shared_ram

.text > arm_local_ram

.stack > arm_local_ram

.bss > arm_local_ram

.data > arm_local_ram

.const > arm_local_ram

.switch > arm_local_ram

.sysmem > arm_local_ram

.cinit > arm_local_ram

.cio > arm_local_ram

}

What's wrong with this .cmd file? How can I fix it?

  • 0
    TI__Mastermind 37985 points

    Majid,
    which platform are you using? You can find out that at Project->Properties->CCS General->RTSC->Platform. Some platform generate their own linker command file linker.cmd in Debug/configPkg, and that file also defines the memory layout, as well as section allocations. You can disable parts of that file if needed, but you can also try disabling your linker command file, and check if the layout produced by the generated file works for you.

  • 0 in reply to Sasha Slijepcevic
    Prodigy 80 points

    Sasha,

    This is my platform:     ti.platforms.evmOMAPL138

    But it doesn't automatically generate the Memory layout :-|

    I'm watching the 1.5Day workshop on OMAPL138 ... but it is for a standard board! My board is created from a standard board, I don't know is there any difference in the memory mapping?! [There is a DDR memory connected to the OMAP and we have successfully connected to that Module. ] I am totally confused with the mapping! :D

    I'd be glad if you share any document that could help me with this problem

    Tnx for the reply, Sasha ;)

  • 0 in reply to Majid Kazemitbaar
    TI__Mastermind 37985 points

    How did you find out that the platform doesn't generate the memory layout? Is the file Debug/configPkg/linker.cmd empty or there is no such file?

    Can you also try the following:
    Right-click on your linker command file, Resource Configurations->Exclude from build, and then try rebuilding the project.

    I am not sure yet what the problem is, but here is the document about memory configuration in RTSC: http://rtsc.eclipse.org/docs-tip/Memory_Management.

  • 0 in reply to Sasha Slijepcevic
    Prodigy 80 points

    Sorry, I didn't clarify you at first...

    The board, is a Custom board, created by ourselves... 

    For running Sys/Bios on the OMAP, using the documentation you gave, I found that I need to create a custom platform using "New RTSC Platform" and add it to the Sys/Bios Project later.
    but before that I need to configure a DDR Ram on the board. because the Sys/Bios project needs a lot of memory.
    we wrote the code for the Dsp side, but the problem is that we need to initialize the DDR ram in a .gel file and attach it in the "Target Configuration File" -> "Advanced Setup" -> "Initialization Script"

    Now my question is how should I write this Gel file? I have the code for configuring the DDR, i just  don't know where to add it.

    Thank you so much for all the help :)
    Regards,
    Majeed 

  • 0 in reply to Majid Kazemitbaar
    TI__Mastermind 37985 points

    Your initial problem was that you couldn't build because the memory objects were overlapping. I guess you solved that issue, right?
    Now, what's your exact problem with the Gel file? You need to write a file and attach it in the text box that you mentioned in your post. Are you asking where on your hard drive to create that file? Your project directory is as good place as any.