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.

TMS320F28031: F28335 vs F28031 code compatibility functionality wise

Part Number: TMS320F28031

Hi,

I have my project in F28335 and i want to migrate it to f28031 . I want to know how much compatible the code will be?.

To make it  more clear suppose I have code for  I2C written for F28335 and if I change the necessary register mapping according to F28031 , functionality wise will there be any difference in  I2C for two devices  and same goes for other modules like ADC, SCI ,CAN etc.

Just want to know if I correctly map the register between the two controller, and use the f28031 library in place of f28335 , can i use the f28335  code for f28031.?

If not can u suggest what else needs to be changed apart form register mapping between between the two?

Thanks,

Romi Srivastava

  • Hi Romi,

    Romi Srivastava said:
    Just want to know if I correctly map the register between the two controller, and use the f28031 library in place of f28335 , can i use the f28335  code for f28031.?

    It should be easy enough as I2C register set is pretty similar for both the devices. Simply compare the I2C user guides of both the devices to observe the similarities. 

    I'd once migrated a very complex code from F28335 to F28027. Hardly any efforts were required apart from the obvious timing constraints.

    Regards,

    Gautam

  • Romi,

    Please consult the C2000 Peripheral Selection Guide. (SPRU566) It provides a comprehensive list of all of the peripherals used in C2000 MCUs. As the F2803x is a more recent device than the F2833x, there will be some differences and improvements. A good portion of your peripheral code should work with minimal modification. You will obviously need to make some changes to System Control and Clocking configurations, but otherwise your changes should be relatively minor.

    Thanks,
    Mark