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.

TMS320F280049: F280049 development – Device Support vs. DriverLib

Part Number: TMS320F280049
Other Parts Discussed in Thread: C2000WARE

Tool/software:

I have experience using C2000 MCUs such as F28335 and F28069. For those devices, I relied heavily on the device support files (e.g., InitSysCtrl, InitEPwm1Gpio, InitAdc) provided in C2000Ware, which made development easier.
I could check the TRM for registers and configure peripherals directly while using those support functions.

Now, I’m starting development with the F280049, but I noticed that many of those device support files are not available. Instead, TI provides DriverLib for this device family.

My questions are:

1. Is DriverLib the only recommended way to develop on F280049?

2. Can I still mix approaches – for example, use the traditional style (InitSysCtrl for clocks, GPIO setup, etc.) together with DriverLib for modules like CAN?

3. What is generally considered the best practice? Should I fully switch to DriverLib for all modules, or is a mixed approach acceptable?

4. Will the device support style (like InitSysCtrl, InitEPwm1Gpio) no longer be provided for newer devices such as F28004x?


Honestly, I feel a bit worried since I haven’t used DriverLib before, and I found the device support style easier.
It would have been nice if F280049 also had device support like the older devices.

Any guidance or recommendations from TI engineers would be greatly appreciated.

Thank you!

  • Hi,

    Sorry for the delayed response.

    1. The recommended way is to use driverlib for the Gen3 devices. F28335 and F28069 are referred as Gen 2 devices whereas F2807x onwards are referred as Gen 3 devices.  Bitfields headers are still provided for F280049 but the recommended approach is to use driverlib. 

    2. You can still use both the approaches. 

    3. DriverLib is the preferred model of accessing peripherals for the new generation MCUs.

    Pls refer the following page  Drivers — C2000Tm Software Guide for details about driverlib and bitfields.

    Best Regards

    Siddharth