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

F28M36P63C2: Programming C28 from M3

Regis_W
Expert 1170 points
Part Number: F28M36P63C2

After reviewing forums for information I have come up with an idea on how to configure the C28 from my M3 bootloader.

I would like to know if there are any issues I am not aware of.

I have a linux host application on uart0 that communicates with M3. This will pass code to the M3 which will eventually pass code to C28.

After M3 is taken care of I would  like to use shared RAM to setup the C28.

The M3  would place code in share RAM for the C28. It would include flashAPI and code to set the C28 into serloop.

Once C28 is running.. when C28 gets data over serloop it would program its own flash.

ToDo:

Figure out how to program shared RAM from M3.

Figure out how make the C28 run from shared RAM (controlled by M3).

Any info into problems with this approach and suggestions are greatly appreciated.

Thanks! 

  • 0
    TI__Guru** 113875 points
    Hi,

    The flow you mentioned should work. Instead of using the shared RAM, why not pass the data from M3 to C28x via MSG RAM and let C28x write that data to shared RAM. In that case you don't have to worry about the two "ToDo" points.

    Regards,

    Vivek Singh
  • 0 in reply to Vivek Singh
    Expert 1170 points
    Thank you for the advice, can you elaborate on the differences in implementation between MSG RAM and shared RAM.
    Would I be able to boot the C28 from code in MSG RAM?
  • 0 in reply to Regis_W
    TI__Guru** 113875 points
    No Regis, code can not be executed from MSG RAMs. C28x need to copy the code from MSG RAM to Shared RAM or it's local RAM and then execute it from there. This will just avoid the ownership change of shared RAM otherwise shared RAM method will be simpler.