• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 206 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.

CC1310: CC1310 & CC1352 code portability

Corey H
Intellectual 260 points
Part Number: CC1310

I am developing some high level I2C functionality that be used for a cc1310 & cc1352. The SDKs for these devices are dramatically different, for example simplelink_cc13x0_sdk_4_20_02_07 SDK the "I2C_Transaction" Struct in the cc13x0 I2C.h does not contain a "status", while "I2C_Transaction" in I2C.h file in simplelink_cc13xx_cc26xx_sdk_6_40_00_13 does contain that member. What is the best way to deal with code portability between the code between these types of devices. 

  • 0
    TI__Guru* 81501 points

    From an application point of view, I do not think there are much differences, if any, and you should be able to use the same application code for the I2C on both devices.

    However, there are several differences between the SDKs, and the CC13x2 SDK have for example the UART2 driver and the GPIO++ driver.

    My recommendation is that since you would need to use two SDKs anyway, you should on the CC13x2 use the new drivers, and improved features etc. that are available for CC13x2, and not focus too much on keeping the code identical, since you cannot use the same SDK for both devices anyway.

    Siri