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!