• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 789 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.

How to build a new cs.x64p

you lee
Prodigy 50 points

Other Parts Discussed in Thread: CCSTUDIO

I modified the server.cfg of cs1omap3530_1_01_00 in the WINCE DVSDK , So how to build a new cs.x64p ?

  • 0
    TI__Intellectual 2525 points

    You Lee,

    Please refer to release notes distributed under the codec server folder of the dvsdk installation - example location would be

    C:\ti\dvsdk_wince\dvsdk_wince_1_00_00_05\cs1omap3530_1_00_01

    The build procedure is part of the release notes.

    You have modified the server.cfg - in case you have to double-check anything with that part, here is a link which would help you

    http://processors.wiki.ti.com/index.php/How_do_I_Integrate_new_codecs_into_DVSDK

    regards,

    Aparna

  • 0 in reply to Aparna Balasubramanian
    Prodigy 50 points

    thanks Aparna

    To build the codec server, I do

    • Open up Visual Studio
    • Open up OS design in Visual Studio
    • Select "Build->Open Release Directory in Build window" and open up a build window
    • Then run the following commands in the build window
    • %DVSDK_INSTALL_DIR%\setpaths.bat
    • cd %CODEC_INSTALL_DIR%
    • gmake clean
    • gmake

    but the result:

    C:\WINCE600\3rdparty\dvsdk_wince_01_11_00_02\src\cs1omap3530_1_01_00>gmake
    Makefile:68: Your BIOS needs to be patched for SDSCM00004525!
    Makefile:68: *** Please copy C:\Program Files\Texas Instruments\bios_5_41_00_06/
    packages/ti/rtdx/package_export.xdc to C:\Program.  Stop.

     my questions are:

    1. BIOS_INSTALL_DIR=C:\Program Files\Texas Instruments\bios_5_41_00_06, and the version meets the requirement according to releasenote. where and how should I get that patch, SDSCM00004525?

    2. I don't find any file named package_export.xdc in C:\Program Files\Texas Instruments\bios_5_41_00_06/packages/ti/rtdx/? so why this error happens?

    here is my setpaths.bat

  • 0 in reply to you lee
    TI__Genius 9185 points

    I think the problem may be related to the fact that the XDC and (maybe) the BIOS are installed in directories that have space in the path name "Program Files/Texas Instruments". We have had issues with paths that have spaces in them for XDC and Codegen tools. Please refer to the DVSDK wiki that lists the steps for sw tools installation and caveats. 

    http://processors.wiki.ti.com/index.php/GSG:_DVSDK_for_Windows_CE_Software_Setup

    The wiki lists XDC, Codegen to be installed in dirs that have no space. Even though it does not list BIOS as having issues with space I would recommend that you install it in a directory that does not have space in its path name (the default dir is c:\ccstudio_v3.3\bios_5_41_00_06) and that is what must have been used for testing.

    Our recommendation is that you install all the tools, dvsdk etc as recommended in the wiki above and try a build (in your case just the codec server) without making any  changes (other than updating the tools path in the setpaths.bat file). Make sure that works before you make any modifications in the server cfg files etc.

     

  • 0 in reply to Jatin Jain
    Prodigy 50 points

    Jatin Jain

    Thanks for your help,that I solved the problem.

    But there is a new problem of the WINCE DVSDK, when I use the app capturetest to encode some videos(h264 or mpeg4),the wince system auto reboot immediately.

    And when I use ceplayer.exe to decode videos,the system also auto reboot immediately. I have not modified the server cfg files.

    what's the problem, and why?

  • 0 in reply to you lee
    TI__Intellectual 2525 points

    you lee,

    Which release are you using and have you tried using the demo builds which are shipped with that release? Are there any changes you have made to the DVSDK or BSP source code?

    Thanks,

    Aparna

  • 0 in reply to Aparna Balasubramanian
    Prodigy 50 points

    Aparna

    I am using  BSP_WINCE_ARM_A8_01_01_00_Source and dvsdk_wince_01_11_00_02.

    Because my evm is sbc3530, not TI' evm. I have only Modified the definition of blacklight GPIO.

    Thanks,

    you lee