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.

How to transplant code from TMS320F28377S to TMS320F28379D

Other Parts Discussed in Thread: TMS320F28377S, TMS320F28377D, TMS320F28379D

Hi,

How can I transplant code from TMS320F28377S to TMS320F28377D. F28377S is single core, the F28379D is dual-cord. What is the difference between them in source code. Can I just modify the header file for this transplant or I need to do more work for it. Thanks.

Regards,

John

  • Hi John,

    You can directly port the code to the "D" part. Just that you'll be using the single core instead of dual. You'll have to do some initialization to enable core 2 and communicate with it. Refer example codes for the same.

    Regards,
    Gautam
  • John,

    Gautam is right that you should be able to port the code from single code to dual-core device.

    Couple of things to note on this -

    • If you are using 1MB part for single core and using sectors which are beyond 512KB then you need to partition the code between CPU1 and CPU2 so that code size does not go beyond 512KB on each CPU because on TMS320F28379D device both CPU have 512KB of flash. You need to use dual core linker cmd file to recompile the code.
    • All the device initialization including GPIO initialization and  peripheral selection is done by CPU1 only hence based on the code partition you may need to include some handshake between CPU using IPC.
    • Based on the code partition, if CPU2 needs more RAMs then some of the GSx RAMs need to be assigned to CPU2 (again done by CPU1 only).

    Regards,

    Vivek Singh

  • Thank you very much for help from you guys. Thanks.

  • You're Welcome!

    Goodluck & Regards,
    Gautam