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

AM2634: AM2634-CC How to build cascade appimage for booting from QSPI Flash

ngrkus
Expert 1020 points
Part Number: AM2634

Hi,

I am trying to find out the mechanism within TI-CCS to combine two programs for the Cortex_R5_0 and the ICSSM_PRU_0 (a.out files or RPRC files) into an appimage file. This combined appimage file would be downloaded using the python procedure described within the SDK. While I am able to manually create the RPRC files from the 'a.out' I do fail to combine them using the "Multi-core Image Gen" tool.

Q: Is the SBL capable of loading the application for a Cortex and the PRU core and then releasing the cores in order to start execution of both programs? Or do I need to write a custom function to do so?

Q: Is there a way to configure the 'post build' process that let me automate the creation steps described in the "Booting Tools" section of the AM263x+SDK documentation in order to get the appimage file with the two programs mentioned?

Q: The concept of signing. Is this mandatory? I am able to download one single app for the Cortex_R5_0 into the QSPI flash and boot from it. However I did not manually sign anything.

Thank's

br

Markus

  • +1
    TI__Guru 54905 points

    Hi Marcus,

    The SBL is capable to load and run application code on multiple cores (R5F, M4F etc.) from one single appImage. However to load and run the PRU core is different. It is not via SBL. It is done in the R5F code. Take endat_diagnostic_am243x-evm_r5fss0-0_freertos_ti-arm-clang as example. Loading the PRU code for this example is done in endat_pruss_load_run_fw(): PRUICSS_writeMemory, PRUICSS_resetCore and PRUICSS_enableCore. The binary code for PRU is at EnDatFirmware which is part of the R5F_0_0 application code.

    The "post build" is done in the makefile_ccs_bootimage_gen of each project. You can certainly change it as you wish.

    The signing is not mandatory for GP device, but it is mandatory for HS device

    Best regards,

    Ming