sys/bios for Picccolo

Depends upon what you are trying to do... If you have a simple control program that loops and waits on interrupts to run, probably not.  If you need more complex thread handling, semaphores, mailboxes, queues, etc., then maybe so. 

I just got done porting my 28335 code over to CCSv4 and SYS/BIOS 6.21 (not really called SYS/BIOS, yet) and it has been a trying few weeks of effort, but I'm pretty close to something quite robust. 

The hard part is getting used to RTSC, particularly if you were/are already familiar with DSP/BIOS 5.x.  Much of the RTSC content is weakly documented since it is so new, and it is all done with JavaScript (and some Java) which adds to the learning curve if you don't already know either - I did not (and probably still do not).  There are bugs and/or "features" that make its implementation frustrating at times.  C28x support was only recently added making the documentation issue even more noticeable.  PIE interrupts are a key example of that (though not difficult to figure out).

Beyond that, the BIOS adds quite a bit of code (relative to your available RAM) which makes mapping your memory sections a little more difficult and may necessitate running out of FLASH and copying only critical sections to RAM, rather than all of your code/data, for faster execution.  The process for doing this is not straightforward though there are posts here and over at the Eclipse forum that outline a working method (from me and others).

Once it is "working," the BIOS is quite slick.  I traded many hours (days) of figuring out how to implement something through the configuration script for very little time writing code to do deal with it directly.  Interrupt handling, thread scheduling, timers, and other tasks are automatic once the BIOS is up and running.  It does not seem to be intrusive to the code I have running, either.  Also, with CCSv4, SYS/BIOS 6.x is the only way to get RTA to work that I know of (still buggy, however, as it shuts down frequently).

Over all, if I had to gripe about anything, it would be the poor performance of CCSv4 once it is attached to an emulator, not the BIOS.  It is very buggy and has a HUGE memory leak.  Telling users to increase their Java heap size to increase the time between crashes/erratic behavior is not a fix.

Mark

Mark,

Yes I can say I am doing the simple control of  a power supply so I do not need the fancy sys/bios etc.

Some more Issues....

28035 has much less of the RAM (20KB Vs 68KB of 28335) that can be a deterrent to using bios. 28035 has a co processor (CLA) that I do not know how the sys/bios handles.

I want to do something better than taking project from one to the next power supply design and change it completely. In the true sense I am not "reusing" what is already built.

sunil

Hi, I'm trying to understand the SYS/BIOS in CCSV4.  I tried to create an example from the wizard, but it does not link.  Do you have any links to "how toos"
 for the c2000 family? Thanks.

Tom

Tom,

I have an example posted on a wiki article for setting up a HWI (Hardware Interrupt) with SYSBIOS on a F28335.  Unfortunately, it is not targeting the device you are (ie. the F28035), but is an example you can reference.

SYSBIOS HWI example for C2000

Hi Tom --

Which version of CCS, BIOS and XDC are you using?   We did some significant work in BIOS 6.32 to simplify the use of 28x.  

If you are using CCS 4.2.2 or later, you should update to 6.32.01 or 6.32.02.   You will also need to update XDCtools using link on the download page below.

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/index.html

Regards,
-Karl-

I'm using 6.21.0.13.  I'll update and see if things are improved.

Thanks!