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.

CCS/TMS320F28035: C2000Ware - device_support vs driverlib

Part Number: TMS320F28035
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

I noticed that in C2000Ware there are two sets of "drivers" available: device_support and driverlib.

The "device_support" is based on bit-level access to configuration registers and have defines for all peripheral (module) registers.

The "driverlib" does not have configuration register definitions, but has more configuration functions with a lot of macro constants and enums.

Which one is recommended to be used in new projects? In other words, which of the two will receive support in the future?

Moreover, it seems that "driverlib" is not available for F2803x in the latest C2000Ware release. Is there a plan to provide "driverlib" for F2803x in the future, or we have no other option but to use "device_support" in that case?

  • Marko,

    TI recommends to use DriverLib based system for new design and new devices. Bitfield based sdk will not be maintained. However, for F28035, there is no plan to bring support for DriverLib. It will continue to be supported in bitfield based sdk.