• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 101 subscribers
  • Views 894 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.

RTOS/AM5718: How to convert .out to .xem4 file

WTMEC_Will Hsu
Expert 2620 points
Part Number: AM5718

Tool/software: TI-RTOS


Hi TI team,
I've rebuilt "GPIO_LedBlink_idkAM571x_m4TestProject" of pdk_am57xx_1_0_6.
I can load "GPIO_LedBlink_idkAM571x_m4TestProject.out" to AM5718-IDK using CCS7, and it's is working fine.
if I want to load ".xem4" to IPU via remoteproc of Linux.
How to conver "xxx.out" to "xxx.xem4" ?

Reference:

http://processors.wiki.ti.com/index.php/Rebuilding_The_PDK#Steps_to_run_example_and.2For_unit_test_projects_on_C66x.2FA15_Target

From Will Hsu

  • 0
    TI__Guru* 96960 points
    I've moved your thread to the device forum.

    Todd
  • 0
    TI__Guru** 116020 points
    You can rename your GPIO_LedBlink_idkAM571x_m4TestProject.out file to GPIO_LedBlink_idkAM571x_m4TestProject.xem4 and place it in your target filesystem's /lib/firmware directory.

    As an alternative, you can configure the CCS project to create the output executable with an extension different than .out. You can use the --output_file=<filename> linker option to specify a different output name.

    To be loaded by remoteproc, your executable must contain the resource table and be linked to the correct memory locations as reflected by that resource table. The Ipc product examples do this, so they should be used as a starting point. Refer to the IPC Linux examples under the folder
    ipc_3_44_01_01\examples\DRA7XX_linux_elf\ex12_mmrpc

    Executables built with CCS have '.out' as their default file extension. Executables built using a RTSC native build flow under a Linux or DOS command line are tagged with an extension unique to the RTSC target used to build the application. In this case, '.xem4' is the file extension associated with executables built using the RTSC native build flow (most likely under Linux) with the 'ti.targets.arm.elf.M4' RTSC target.

    In terms of executable file structure, there is no difference between a 'app.out' file and a 'app.xem4' file.