• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 514 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.

AM2434: using ARM Fusa compiler on M4F

Benjamin Scheufele
Intellectual 360 points
Part Number: AM2434

Tool/software:

Hello there,

we're using cmake as buildsystem and can generate an ELF file for the safety core M4F with the ARM Fusa V6.16 compiler.
We can load and run the ELF output file via CCS. It seems everything is working within CCS.
We can set breakpoints and also have debug output over shared memory log messages or dedicated UART on M4F.

For the last step, we need a flashable RPRC image, which can be loaded by the SBL. This is currently not working.
It seems that the stripped binary from the out2rprc is a little bit different from the stripped ARM V6.16 binary.
Can the tool "out2rprc" process all ELF files regardless of the type of ARM compiler, or are there limitations?
 
kind regards,

Benjamin

  • 0
    TI__Mastermind 48958 points

    Hi Benjamin,

    Thanks for your query.

    Can you please tell what is the format of binary generated by the ARM Fusa V6.16 compiler? Is it *.elf or something else?

    The out2rprc tool is only validated with ti-arm compilers. We have not validated it with other compilers.

    Can you please also tell is there a specific reason to use different compiler?

    The MCU+SDK is validated to work with TI-ARM-CLANG compilers. Please refer INSTALL_TIARMCLANG 

    Can you please share the binary created with ARM Fusa V6.16 compiler? 

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Intellectual 360 points

    Hi Tushar,

    our output format of the ARM Fusa compiler is *.elf.

    In our project, we also use a safety companion core for the second safety channel. On this side, we have the ARM Fusa compiler in use. So it would be a great benefit for us to use the same compiler on both cores.  By the way, the ARM Fusa compiler is certified - and we don't need the certification process of the ticlang compiler, which guarantees that we are on the safe path.

    We can create the rprc file - but the sbl could not load the binary into the m4f memory.  Please check the rprc content - for me it looks good. Entry point and sizes are right...

    I will share the binary by private message!

    Regards,
    Benjamin

  • 0 in reply to Benjamin Scheufele
    TI__Mastermind 48958 points

    Hello Benjamin,

    Thanks for the above details.

    I have an another thread which might help you. Please try the steps suggested here.

    Regards,

    Tushar

  • +1 in reply to Tushar Thakur
    TI__Mastermind 48958 points

    Hello Benjamin,

    I have checked the *.elf file shared earlier. After parsing the *.elf file it seems that you are using ipc_vring section at memory address 0x70014000 which is reserved for SBL usage. User application should not use this region.

    Please refer below screenshot.

    Please refer MEMORY_MAP for details.

    Hope the above information helps.

    Regards,

    Tushar