SATA support for TMS320C6748

Matt,

Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages. Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics.

To find an answer and to offer a vision of the Wiki, I went to the TI Wiki Pages and searched for "PSP C6748" (no quotes, no caps). The first link looked obvious, but was too old. Looking down the list, the one about CSL now being in the BIOS PSP looked promising, in an indirect way. It was. On that page was a link to find the BIOSPSP where the CSL lives, here, and it has a newer BIOSPSP 03.00.01.00 for SYS/BIOS.

See if this has what you are looking for and please let us know, either way.

Three popular misconceptions about SYS/BIOS:

1. It adds too much size overhead to my system.

SYS/BIOS starts tiny and increases efficiently as you select only the modules you need. The size has been improved over DSP/BIOS, which started big and required you to go in and reduce it.

2. It adds too much performance overhead to my system.

SYS/BIOS will stay out of your way when you do not need its scheduling features, and it adds benchmarking features almost for free (you can control how much of that you get). If you will have interrupts in your system, SYS/BIOS' Hwi system takes care of context save/restore and allows you to just write a C function that does what you need without having to worry about special interrupt-handling. But if you want to do your own context save/restore or use the C Compiler's "interrupt" keyword, you can do that and SYS/BIOS leaves you alone. If you have several different independent functions to be performing, SYS/BIOS provides a convenient was to keep them separated by running them as Tasks with their own stacks and their own assigned priority; SYS/BIOS enforces that priority for you and provides Semaphore objects for you to use to control switching between the different threads. If you have something that needs to be higher priority than your tasks and needs to run to completion before going back to those independent Tasks, the Swi software interrupts start when you tell them to and finish when they are done - with priority levels for more important Swi's and they will always be interrupted by Hwi's.

3. It will slow down my development process to use SYS/BIOS.

Maybe you have to spend some time learning SYS/BIOS, but it is not very tough to start with the basics. We have a "1.5 Day SYS/BIOS" workshop on the Wiki - try searching for it - that has code examples with the solutions and shows you what it is all about. You can do it faster on your own, since you do not get the extra value of the live instructor, and we might have some recorded training sessions for this or other workshops. Let me know if you find one, I have not searched for them but I heard they were being recorded or posted for some workshops. It will save you a lot of time to have basic system things taken care of, especially for something like the SATA interface, if you can just pickup the SYS/BIOS & PSP version and just start writing your application instead of having to also develop new driver code just to be OS-free. OS-free is not free, but we do not charge for SYS/BIOS (mixed metaphor but I like it). If you end up having questions about SATA registers, we may point you to the PSP to see how they did it there - all those problems have been worked out and debugged by someone already.

Regards,
RandyP

Matt

Currently there are no plans to upgrade Starterware and SYSBIOS offering to include SATA driver. Can you please elaborate further on your SATA use-case?

Regards

Mukul