The following describes the software, hardware, procedures we use for working with the C6748 SOM.
Hardware
C6748 SOM and EVM kit from Logic PD
XDS100v2 from Spectrum Digital (the EVM kit has one built in, but you will need this to bring up your own hardware)
Software
CCS 4.2.2, includes bios 5.41.10.36, and bios 5.41.10.36
NDK 2.20.03.24
NSP 1.00.00.09
PSP Drivers 1.30.01 (for BIOS 5)
PSP Drivers 2.10.01 (for BIOS 6)
EDMA3_LLD 1.11.02.05 (for BIOS 5)
EDMA3_LLD 2.11.01.02 (for BIOS 6)
GEL file from Logic PD (or suitable substitute)
Read the CCS4 documentation (such as it is) and watch the video.
Read the user guides for the software you are installing, they contain installation instructions and some require that environment variables be set in your desktop operating system. (the user guide i think does not say how to do this, you can search for it on the microsoft web site).
Also, read the BIOS (and NDK, NSP) user guides to understand how to work with CCS, what is going on in the examples, and for some important information about how to design your application.
Create a target configuration for the C6748, and add the gel file. To run the examples, do not go straight to "debug target". Instead, launch the configuration, connect to the target, reset the cpu, load the program, and then debug. See http://e2e.ti.com/support/embedded/f/355/p/103739/365536.aspx#365536
Some really neat networking examples are in the NSP. Both the BIOS 6 and the BIOS 5 versions of the examples compile and run. It's very cool, try it.
The UPP driver is only in the PSP for BIOS 5. This is an important feature on the C6748 chip, it really should be supported in BIOS 6. You should be able to import the examples as legacy CCSv3 projects, but to build them you have to patch up some file search paths. See http://e2e.ti.com/support/embedded/f/355/p/104061/366679.aspx#366679
The instructions from Logic PD would have the user install the BSL and run the test programs. This is probably NOT what you want to use as a starting point for production code. According to Logic PD the BSL and test programs are "not mean to be incorporated in a production device". Maybe i missed this in their documentation. Before it arrived in my email, our contractor had already spent about 6 weeks trying to patch the BSL to do more than loopback. He still cannot get interrupts working.
For comparison, getting to the starting point for writing our application as described above with TI API's and with examples that are relevant and useful, took a little over 1 week with copious help from the E2E forum. Without the E2E forums, it would be something like a scavenger hunt for information diffused and scattered into a half meter high stack of paper. Hopefully this posting provides something of a crude map to what i hope will be a reasobable starting point.
