AM2434: Multi-core Project Management and Motor Control SDK (MCU+SDK) version Upgrades

Tsunoda-san

Mari Tsunoda said:

However, if my customer has an already existing MCU+SDK project that they have worked on, how can they migrate smoothly to Motor Control SDK project most easily?

1. I was looking at the migration guide provided in the Motor Control SDK documentation but could not understand the highlighted line... Does it mean to copy the folders in the Motor Control SDK to the MCU+SDK folder locations listed? Or the other way from MCU+SDK to Motor Control SDK? If it is the latter, I am not sure how to do this because there is no Motor Control example or source that comes pre-included in the MCU+SDK

No manual folder movement is needed. Is this question same as (+) AM2434: Add Motor Control SDK Features to MCU+ SDK Project - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums ?

Mari Tsunoda said:

If they are using a higher version of MCU+SDK currently than what is included in the Motor Control SDK, is it possible to upgrade the version of MCU+SDK included? If so, how can they do this?

MCU+ SDK can be updated by replacing mcu_plus_sdk folder within installed Motor Control SDK. But this would be an untested version of Motor Control SDK - as MCU+ SDK will change. Are you looking for any specific MCU+ SDK version?

Mari Tsunoda said:

1. If they want to copy a project for one core (ie. R5_0_0) to another core (ie. R5_0_1) how can they do this?

If customer wants starting point for projects on different core, they can check empty example in MCU+ SDK. What do you mean by copy here? If there is no core level code change needed, then we can just load the binary to appropriate core.

Regards

Dhaval

Hi Dhaval,

Thanks for the reply. I can close up the other thread and continue on here.

Since they need to start with a Motor Control SDK project to get all the features in sysconfig, if they want to make a system project but change the default empty project to the Motor Control SDK project, how can they do this? Do they change the makefile_system_ccs_bootimage_gen? Would they need to change other project settings for the linker? 

Regarding the project copy from one core to another, since most projects in the Motor Control SDK are only provided for the r5fss0-0 core, I was wondering if they needed to change anything else for a multi-core project if they want to port the project to the r5fss1-0 core for example.

Dhaval Khandla said:

MCU+ SDK can be updated by replacing mcu_plus_sdk folder within installed Motor Control SDK. But this would be an untested version of Motor Control SDK - as MCU+ SDK will change. Are you looking for any specific MCU+ SDK version?

They want to upgrade to v.10.1 because of the system project bug listed here:

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1467956/am2434-configuring-mpu-settings-but-instance-limit-has-been-reached/5641932#5641932

It seems like there is a couple bugs with the system project, not just the MPU region setting. I think it would be easiest to just upgrade the SDK version within the Motor Control SDK than to patch all the bugs in v.9.02

Best regards,

Mari Tsunoda

Tsunoda-san

We plan to make MCU+ SDK 10.01 based Motor Control SDK release in April.

Regards

Dhaval

Hi Dhaval,

Thanks for the response.

I don’t think they will be able to wait until April unfortunately.

best regards,

Mari

Hi Dhaval,

So they are moving forward with Motor control SDK 9.2. They still want to know how to port a project for r5f0-0 to r5f1-1. Do they have to build it from an empty project for r5f1-1 and copy all pin settings and files to this empty project? Is there an easier way to port to a different core? The linker and memory settings also have to be different right?

Best regards,

Mari