I am supporting a legacy program that utilizes 3rd party drivers that were developed using CCS3.1 for the 6713. These libraries are not compatible with SYSBIOS and CCS5.5 but I have been able to migrate (sort of) to CCS 5.5 so I can at least work in Eclipse and Windows 7. The migration involved using the CCS3.1 libraries and the .c, .h and .s62 files generated by the CCS 3.1 configuration editor but using the CCS 5.5 compiler/linker and IDE. Thus SYSBIOS is not being used. I can now build my code and link successfully though the new target libraries are not used. I understand that I can not change the configuration in CCS5.5 but that is OK. We plan to migrate away from these legacy 3rd party drivers when we migrate to a new set of HW but for now, that is not an option. My question has to do with replicating this environment at a customer site. I had CCS 3.1 on my PC already so the DSP/BIOS libraries were already available, but my customer does not have that and needs to get access to them. My question is whether it is acceptable to TI for me to provide the CCS 3.1 libraries to my customer (as a zip file for example). They need the C6000 bios, cgtools, csl and rtdx include folders. The CCS 3.1 IDE and compiler/linker are not required.