This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I'm a bit confused about which tool versions I can and/or should be using!
We are developing a device that includes both an OMAPL-137 and a C6455.
We don't have any existing investment in TI software and therefore if feels like a bad idea to start using old tools i.e. CCSv3 and DSP/BIOS V5, but AFAICT it's not that simple!
Is it correct to think that we shouldn't start using the new tools for these devices?
There appears to be an OMAPL-137 PSP for BIOS V5 but not V6. DSP LINK appears to only support BIOS V5 on the OMAPL-137.
Although there's no PSP for C6455 there are other tools i.e. NDK or RapidIO MSGQ that we might want to use.
I think it makes sense to use the same tools on both platforms.
Matt,
CCSv4 actually includes two versions of DSP/BIOS. 5.40 which is binary compatible with the BIOS 5.33 that the OMAPL137 PSP is built for and BIOS 6 which is a brand new version of BIOS. The easiest thing for you to do will likely be to use CCSv4 + BIOS 5.40. If you import projects from the OMAPL137 kit it should automatically convert them to BIOS 5.40.
Regards,
John
Hi John,
Sorry, I did know that CCSv4 & BIOS 5.4 was an option and (without knocking CCSv3 too much) it is probably better than CCSv3 & BIOS 5.3.
But, just to be clear, BIOS *6* is *not* an option for OMAPL-137(?).
I feeling a little disappointed because I read the stuff about BIOS 6 and thought it looked much better (I was particularly interested in the native execution).
Thanks,
Matt
Matt,
CCSv4 + BIOS 5.40 is the easiest option. BIOS6 definitely has some nice features (native execution, better support in debug displays...) however by default it uses a new API so you would need to run it in backward compatibility mode to attempt to use PSP. We have done some migration exercises in moving OMAPL137 projects to CCSv4/BIOS5.40 and it is pretty smooth. Moving to BIOS6 would be a lot more involved. I don't have much experience with doing that.
Regards,
John