• Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 358 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SDK 01.01.00 install issue

DavidVescovi
Genius 5470 points
Other Parts Discussed in Thread: OMAP3530

I noticed if you install the WINCE_GFX_SGX_01_01_00_setup.exe it resets the DVSDK_INSTALL_DIR enviroment variable to the "C:\TI\...." path. This causes the default EVM_OMAP3530 OSDesign to fail when it looks for the dvsdk files.

Reseting the DVSDK_INSTALL_DIR enviroment variable back to "C:\WINCE600\3rdParty\dvsdk_wince_01_11_00_02"  or removing the enviroment variable alltogether fixes the problem.  See the prelink.bat file in the DVSDK subproject for info on how this variable is processed.

 

DV

  • TI__Genius 10960 points

    David, thanks for the information.

  • TI__Expert 5320 points

    David

    I think you mean dvsdk_01_11_00_02_setup.exe and not WINCE_GFX_SGX_01_01_00_setup.exe.

    It is intentional that dvsdk_01_11_00_02_setup.exe resets the DVSDK_INSTALL_DIR because when you install the SRC package of DVSDK (dvsdk_01_11_00_02_setup.exe), it is assumed that you will be using this source package for your development and not the binary package that is shipped as a part of BSP. Now the default installation of dvsdk_01_11_00_02_setup.exe is C:\WINCE600. This is designed in such a way that when you install dvsdk_01_11_00_02_setup.exe to the default location (WINCEROOT), it will overwrite the binary package that BSP provides and hence integration with the default BSP OS-design is seamless - since BSP OS design looks for the DVSDK subproject under WINCEROOT\3rdParty. There is no way to use the DVSDK_INSTALL_DIR variable inside the pbxml file to look for subproject.

    Now if the user decides to install the DVSDK source package in the non-default location, then there is some onus on the user to either

     (a) change his/her OS-design to point to this new location and copy the CATALOG folder to WINCEROOT\3rdParty\<dvsdk>\CATALOG, if he plans to use the source package with the BSP

    OR


    (b)  change the DVSDK_INSTALL_DIR variable to point to the old BSP's binary package.

     

    Let me know if something is not clear. In the meantime, I will check our wiki pages to make sure this information is captured somewhere.

     

     

     

  • in reply to Madhvi
    Genius 5470 points

    Not really... at least in my installation. I installed dvsdk_01_11_00-02_setup.exe and the DVSDK_INSTALL_DIR enviroment variable was ok (under the c:\WINCE600\3rdParty...) It was only after I installed the WINCE_GFX_SGX_01_01_00_setup.exe that the enviroment variable got reset to the "c:\TI\wince_gfx_sgx... which kills the build.