• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 419 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.

how to change elf entry_point by xdctool

descent sung
Intellectual 270 points

Other Parts Discussed in Thread: OMAPL138

Dear all,

I already build messageq_single.xe674.

Current I want to change  elf entry_point and memory layout.

When I wirte bare-metal dsp (c67) program, I have a link script like this:

-stack 0x1000
-heap 0x1000

/* =========================================================================*
 *                                              Specify the System Memory Map                                           *
 * =========================================================================*/
MEMORY
{
    entry_point:                o = 0x11800000          l = 0x00000080
        L2:             o = 0x11800080          l = 0x0003FF80
        L1P:    o = 0x11E00000          l = 0x00008000
        L1D:    o = 0x11F00000          l = 0x00008000
        DDR:    o = 0xC7800000          l = 0x00100000
}

But in ipc 3.x directory, I find no the files.

My developing platform is debian and don't use ccs, I only use command line.

I do all test on omapl138.

Is any suggestion?

  • 0
    TI__Genius 12865 points

    Hi descent,

    When using IPC 3.x, a better starting point than the messageq_single test is the ex02_messageq example (<IPC_installation_directory>/examples/OMAPL138_linux_elf/ex02_messageq.zip). If you look at this example, it uses the configuro tool from XDCTOOLS to generate the linker command file in ex02_messageq/dsp/bin/debug/configuro/linker.cmd at build-time. The information used by the configuro tool for the memory map is located in the platform instance defined in the file ex02_messageq/dsp/config.bld. The platform instance is used to 'override' the default platform definition for your platform.

    For more information on XDCTOOLS memory management, how to control the generated linker command file, and platform instances, here are a couple of resources:

    http://rtsc.eclipse.org/docs-tip/Memory_Management
    http://rtsc.eclipse.org/cdoc-tip/xdc/bld/BuildEnvironment.html#platform.Table

    Best regards,

    Vincent