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.

TMS320F280040-Q1: TMS320F280040-Q1

Part Number: TMS320F280040-Q1

Hello folks,

Personally, I like the Bitfield approach, however, apparently, there are more support examples for the Driverlib approach. As you guys said (and there is at least one appnote about it)  it's possible to merge both approaches at the same project.

My point here is to try to understand where TI is planning to provide better development support in the future (next 5 to 8 yrs). Is there any recommendation for new projects regarding this matter? 

Do you guys know which approach is recommended for new projects? I'm starting a new one, recoding many classes, because I'm migrating from another uC family and any information would be very welcome.

Cheers,

Luciano

  • Hi Luciano, 

    TI is planning to focus more on the driverlib approach which is a more readable and portable approach than performing direct register accesses using bit fields. 

    More driverlib examples will be added in future releases and bitfield examples will only be ported to newer devices.

    If you are starting a new project, the recommendation is to go with the driverlib approach. 

    Best Regards

    Siddharth