Why is there no DVSDK source for the WEC 7 release like there is for the A8 CE 6?
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.
Why is there no DVSDK source for the WEC 7 release like there is for the A8 CE 6?
As posted on the download page, DVSDK on WEC7 is not aTI supported product.
1Note: Please note that this SDK does not contain any DVSDK sources. DVSDK binaries that are supplied with BSP package were built using WinCE 6.0 DVSDK (found here) by making the changes highlighted in this porting guide. Currently, DVSDK on WEC 7 is not a TI supported product but customers are free to take older DVSDK package and make any necessary modifications.
-Madhvi
If TI does not support it then who does?
There are several issues with binary only. If you are only giving the built binaries then why are you coping the .map and .pdb files into the BSP FILES directory? They seem to be useless baggage if we have no source to debug. Also they are copied from the DVSDK obj folder in the 3rdparty folder, the obj folder gets nuked on a clean rebuild. good luck if you have not saved off a copy somewhere. ... yea they should still be in the FILES directory of your OMAP3530 BSP but what if you are building for multiple BSP's like I do?
My custom BSP has certain restrictions on memory layout and I can not follow the exact same archaic layout the EVM uses. There seem to be several hardcoded memory boundries in the DVSDK code that need to be modified to align with the BSP's config.bib
DavidVescovi said:Also they are copied from the DVSDK obj folder in the 3rdparty folder, the obj folder gets nuked on a clean rebuild. good luck if you have not saved off a copy somewhere. ...
Thanks for reporting this - we will investigate further. Here is the link for the defect:
DavidVescovi said:My custom BSP has certain restrictions on memory layout and I can not follow the exact same archaic layout the EVM uses. There seem to be several hardcoded memory boundries in the DVSDK code that need to be modified to align with the BSP's config.bib
As mentioned before, you can use the CE6 DVSDK source project customized for your BSP and do the necessary changes as mentioned in DVSDK porting guide and you will have the WEC7 DVSDK source project.