Programming MPC56xx for dual core operation

[raghurajappa]

The intention is to develop two models, in Simulink, that will run independently on core0 and core1 of the MPC56xx controller. I am using MCT-Toolbox for this and flashing the controller using serial interface (SCI) using RappID bootloader.

1. I know how to program on one core and run the model. But I do not know how to program two cores and flash the two cores through SCI, from Simulink environemnt. 

2. Should I generate two .mot files or one? I think answering question might also cover this question but I am not sure. 

Any information/material that would help me (understand) programming two cores from Simulink, would be greatly appreciated. Thank you. 

[Daniel_Popa]

Hi Raghu,

Our toolbox can handle only single core programs that are design to operate under lock step mode.

For decoupled operation there are multiple things you need to change:

- bootup

- startup files

- linker command files

All there needs to be done in the toolbox files and might not be a trivial task.

For more information about decoupled mode you can check this: https://www.nxp.com/docs/en/application-note/AN4034.pdf 

Hope this helps!

Daniel

[raghurajappa]

Hi Daniel,

Thank you for your reply.

I have indeed already looked at the application you have shared (AN4034). I do understand bootcode, startup files and linker command files in plain C programming but I do not know where they exist in Simulink's NXP toolbox. 

Is there an application note which describes how to modify the toolbox or any other related information? 

[Daniel_Popa]

Hi Raghu, 

There is no such app note for the toolbox. Anyhow - all these files are copied from the toolbox folders into the generated folder once you click on build button.

The simplest approach you could easily try is to modify the crt0.s, MPC564xL_Flash.lcf and the rest of the files that are in the *_rtw folder and run in command line the *.bat file to rebuild the executable. Once you have the elf you could try to load it on the second core.

If that works - then i can teach you how to modify the toolbox to generate new project based on these modifications by default by replacing the appropriate files \rappid564xl\src\ so that at each rebuild they could be copied automatically in the *_rtw generated folder.

Best regards,

Daniel

[raghurajappa]

Thank you :smileyhappy: I shall try what you mention and get back, in a few weeks, to you when I succeed. 

[Daniel_Popa]

Hope to have you back sooner in case you have issues or resolved it :-)