1. I recently posted a similar topic to this thread on the TI E2E forum at http://e2e.ti.com/support/embedded/bios/f/355/t/277108.aspx. Basically, I am trying to find out if there are plans for higher-level Mware style driver library APIs (part of TI-RTOS perhaps) for either F28027 or F28069 Piccolo in the works. The reply I got from Todd Mullanix was that completion of support for F28x drivers (particularly for TI-RTOS) is lower priority than driver library code for ARM, TIVA and Concerto.
But now that I have searched the ControlSuite documentation a bit more, I see that there is an existing a set of driver APIs for the Launchpad F2802x Peripheral Driver Library which is not yet present or ported to the F2806x Piccolo. The F28069 Mware library for F28069 only supports PIE, Systick, UART and USB drivers currently. I think that the F28069 Piccolo driver library support needs improvement. I think it is important to have a complete driver library supported on all the F28x chip platforms and available regardless of whether some developer wants to adopt the TI-RTOS or not (in my case I am using the Quantum Leaps QP platform for development). My point is that the driver code is useful even if an alternate kernel solution is used. I see that some of your drivers for the F2802x Launchpad Peripheral Driver Library are more formal driver API abstractions (rather than just sample code such as provided in the ControlSuite example code and header files.
2. Like Anguel, I also would like to see the availability of tested I2C driver code and a revision to the F2802x Peripheral Driver Library documentation to include this I2C driver API. I'm also somewhat surprised that many of the C2000 ControlSuite user guides and manuals are not unbundled and available online as separate SPRxxxx PDF files (i.e. the developer has to download the entire ControlSuite to get the documentation). For TivaWare, StellarisWare and the CC2538 families, the Peripheral driver library guides are available as separate downloads from ControlSuite.
3. Are there any suggestions you may have if I attempt to port any of the F2802x drivers you have developed to the F28069 Piccolo ControlStick or ControlCard? Which ones would have to be changed for compatibility with F28069 on-chip peripherals? I assume that PWM and eCAP drivers might probably have to change because the F28069 uses the newer ePWM and eCAP modules instead of the older 281x Event Manager based-design. In addition, I assume that there may be driver changes to support the SOC (start of capture) based ADC instead of the older sequencer-based design. There may be other changes (memory map?) of which I am unaware. Please let me know if you have any other porting suggestions.
4. Also, are there F2802x examples which use the new driver-style APIs rather than the older header files, or do all the examples still use the older headers.
i.e. I am looking for complete examples which use something like the following ...
//Perform basic system initialization
//Select the internal oscillator as the clock source
//Setup the PLL for x10/2 which will yield 50Mhz=10Mhz or10/ 2
//Disable the PIE and all interrupts
rather than the older header version - e.g.
// Step 1. Initialize System Control using example function is found in the F2806x_SysCtrl.c file.
// Step 2. Initalize GPIO using example found in the F2806x_Gpio.c file
// Step 3. Clear all interrupts
// Initialize PIE control registers to their default state as found in the F2806x_PieCtrl.c file.
// Disable CPU interrupts and clear all CPU interrupt flags:
IER = 0x0000;
IFR = 0x0000;
5. Since you are a TI developer who has developed some of the F2802x family drivers, I thought that you should be made aware of my interest in ongoing C2000 Piccolo driver library support and improvements. Please let me know if there are further releases of driver code planned or in the works!