• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 454 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.

TMS320F28377D: Combination of the .hex or .out files in a dual core application.

Jochen Lindenmaier
Prodigy 100 points
Part Number: TMS320F28377D

We start with the first steps in developing a DualCore application. Two separate projects are created for core 1 and core 2. Now a few basic questions:

The software should later be able to be loaded onto the processor as one file. Is it possible to combine the two .out files and .hex files into a single file?
Do two projects always have to be created separately for core 1 and core 2 in the CCS?

Many thanks for your help.

Translated with www.DeepL.com/Translator (free version)

  • 0
    TI__Guru 50531 points

    Hi,

    It is better to create two separate projects and add CPU1 / CPU2 predefined symbol for projects and generate two separate binaries for two cores. It is possible to reuse the code based on these predefined build symbols.

    If you want to keep single project, then you can create two separate build configurations for two cores.

  • 0 in reply to Santosh Jha
    Prodigy 100 points

    Hello

    That is not what I meant. We have our own bootloader in the later application. It would be nice if the build process could create a common HEX file for both cores. Then each core does not have to be loaded separately.

    Greetings

    Jochen

  • +1 in reply to Jochen Lindenmaier
    TI__Guru 50531 points

    We cannot have common hex file for both cores. The linker command file for both cores are different which is statically linked to the project.