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

TMS320F28379D: Only one core works - linker issue? flash settings?

Stefan Leucht
Prodigy 20 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE

Hey,

i am working with a F28379D Dual-Core. My codes for both cores are working.

If i flash first CPU1 and after CPU2, only the code from CPU2 is working. Other way around is the same problem, if i flash CPU2 first and then CPU1, only the code on CPU1 is working.

Which settings i have to use, that the codes on both cores are working?

I am using the default command file from MATLAB, Embedded Coder Support Package c28377D.cmd.

I selected the CPU2 in Debug -> Flash settings.

I am not sure, if these flags for the C2000 compiler and the c2000 linker are correct. Because there is CPU1 mentioned.

thanks in advance

regards

Stefan

  • 0
    TI__Guru 50611 points

    Stefan,

    C2000Ware sdk provides a small example showing how to flash for CPU1 and CPU2 and then how to run it in standalone mode. The example is located at:

    C:/ti/c2000/C2000Ware_4_00_00_00/driverlib/f2837xd/examples/dual/led

    When you import the project, it will have two projects one for cpu1, and another for cpu2. For cpu1, please select the configuration CPU1_FLASH_STANDALONE and for cpu2, select CPU2_FLASH configuration. It should flash for both cores. The key point in CPU1_FLASH_STANDALONE is that it boot CPU2 from Flash. Please take a look at the code.

    Once you are comfortable with the setup, please review the linker command file in MathWorks project. You may need to post the question in MathWorks forum directly to get faster response.

  • +1
    Prodigy 20 points

    You're right.

    It seems that it was a bug in MATLAB Embedded Coder.

    Despite the core selection CPU2 in the hardware settings, the code generation does not seem to take care of this. (As the flags in the screenshot above shows)

    I copied my complete Simulink model in the c28379D blink example and now it works.