This question is open to TI employees and customers. I am interested in both perspectives.
I am developing a power electronics controller that must support a lot of features. I started the project with a TMS320F28335 and had gotten to a point where all the peripheral devices woked in CCS3 with DSP/BIOS (internal ADCs synchronized with the ePWMs). The DSP/BIOS debugging/scheduling features was what originally attracted me to the framework. Do practicing digital control engineers ever use the BIOS? The framework seems targeted to video/audio applications and not control. All TI's MCU examples are written without a BIOS and it was very painful to translate the non-BIOS code to BIOS supported code.
I put the project on hold for a few months since CCS4 was about to come out. The major overhaul ( the largest IDE change in TI history?) seemed to warrant the wait. Also, I switched to a TMS320C28346 with external ADCs, since I ran out of them on the TMS320F28335. So now I am back at ground zero--new processor, new IDE, and now a new BIOS (v6).
I understand CCS4 is new, but I have already hit some pretty nasty errors trying to create a CCS4 RTSC project for the TMS320C28346. This has caused me to question if the debugging/scheduling features in the BIOS justify the added headaches and performance hits.
So here is the open question:
Do you use DSP/BIOS in your Control Projects? If so, in what ways has it helped you?
Thanks for the input.
Grant