Original question:
Do you expect to add SYS/BIOS support for the TMS320F28002x devices?
Is there a reason this would not be worthwhile?
Is there any timeline?
Okay, thanks for your patience. I confirmed that there are currently no plans to update SYS/BIOS with F28002x support, but I did experiment a bit with using the F28004x support on F28002x and was successful. There are a few incompatibilities in the Boot module, but they're easily disabled and replaced with driverlib calls. I can walk you through what I did.
In CCS go to File -> New -> CCS Project, pick one of the F28004x parts, and grab whatever example you want to start with from the templates and examples box. I picked TMS320F280049C and the "pie" example.
When the example is created, go into the project properties and correct the device variant in the general settings Project tab to your F28002x part and switch the output format from COFF to EABI. On the Products tab however, change the XDStools platform back to the F28004x since BIOS won't recognize the F28002x.
You'll need to get a linker cmd file for your project. I grabbed a generic flash one for F28002x from C2000Ware.
If you try building at this point, you'll see a few linker errors related to the default "flashfuncs" settings using memory names that don't exist in your .cmd file. Correct these settings in the .cfg file to use ones that actually exist.
While you're editing the Boot module, also disable "Configure PLL and CPU clock dividers" and "Configure Flash controller". This is the one place where I believe there is some incompatibility between the F28004x SYS/BIOS implementation and the F28002x. You can just call driverlib's SysClk_setClock() and Flash_initModule() functions instead either in main() or earlier if you use one of the SYS/BIOS reset function hooks.
You may need to make some other minor adjustments to your cmd files to get the application to fit (I needed to give .const some more room and add .binit), but that should give you a way to use SYS/BIOS on F28002x.
Whitney
