Hi all,
As I am getting up to speed with regards to the latest developments in processor and SW technologies from TI, I want to solicit input from the e2e community on the following questions:
1. Is it correct that the ViCP libraries for the DM6446 are included as binaries in DVSDK2.x but not accessible from DVSDK1.x?
- Did TI ever make the source code for the ViCP libraries available?
2. What options exist for accessing the ViCP from a DM6446 system running ver. 1.30 of the DSP-BIOS?
- I see from
http://www.ti.com/lit/ug/sprugj3e/sprugj3e.pdf
that the VICP library was built using code gen tools v6.1.8 and were tested in applications using DSP/BIOS v5.33 and version 1_05_00_01 of the EDMA libraries.
- Did TI ever release a version of the ViCP intended to run with ver. 1.30 of the DSP-BIOS?
3. How much did the MontaVista Linux change between DVSDK 1.x and DVSDK2.x? What did the primary modifications consist of?
4. How much did the DSP BIOS change between DVSDK1.x and DVSDK2.x? Again, which modules were changed in particular?
5. Were the API calls needed to access the ViCP for the DM6446 ever included in SDK1?
- Would a full upgrade to the DVSDK2 be unavoidable in order to be able to access the ViCP of the DM6446?
6. Is it correct that the video and image processing modules in VLIB 2.0, available for the DM6446 (?), are taking advantage of the ViCP?
- Hence, by calling these modules, one could take an indirect route to harnessing the the ViCP.
Best regards,
Baldur