TMS320F28P650DK: Workspace migration from F280039C to TMS320F28P650DK

Hi Saurabh,

Sorry for the delay in our response.  Unfortunately, migrating workspaces from different family of devices is not supported.  Each family of device, like f28003x and f28p65x have their drivers in C2000Ware (driverlib).  Driverlib is device dependent as the register locations and offsets or some registers may be present on one device but not the other especially if the module is only unique to one device family.  Basic function names are the same for all device families though, for instance setting the clock regardless of the device is accomplished through driverlib function SysCtl_setClock() but the device dependencies, such as the file headers will be device specific.

There is actually a useful tool in C2000 Academy called C2000 Migration that would be helpful in what you are trying to acheive.  You can use this link: https://dev.ti.com/tirex/explore/node?node=A__ADgjfumqfm-rQYjFAdfTPA__c2000ware_software_package__gYkahfz__LATEST

How to use the tool: Choose Device 1 (you can choose the latest driverlib for f28003x) and Device 2 (you can choose the latest driverlib for f28p65x) then hit the Generate button.  This will first provide a general table that marks which module (or IP) does not exist in the corresponding device which you really do not need for migration.  The other columns would be important to note as these would highlight which IPs have functional and register changes between devices.  These are the critical IPs to note as implementing the functions may not be starightforward,  The proceeding tables highlight register differences (if any) and function implementation differences in driverlib.  ADC IP would be highlighted first as these are different modules between these 2 devices (f28003x has 12-bit only ADC while f28p65x supports both 12-bit and 16-bit modes and ADC trigger selections and options have also changed in f28p65x).  Some other modules have differences like EPWM as there are more features added to the f28p65x family but rest of the features and functions are backward compatible.

Next step would be to create a project in C2000Ware for f28p65x target device.  It would be best to start from an example code as this would create the needed dependencies and header files for f28p65x, then start adding the functions found in the f28003x application.  If the module/function does not come out as different based on the C2000 Migration link, then functions in f28003x can be used as they are in the f28p65x project, otherwise you will need to modify based on the IP/function differences as highlighted by the C2000 Migration tool.

Hope this would provide you some starting point.

Best regards,

Joseph