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.

Still working on creating codec server on WindowsXP



((This thread has been split off from http://e2e.ti.com/support/embedded/f/355/p/87850/306834.aspx#306834))

Chris,

Fixing a bunch of paths and editing the makefile in CCSv4 project for mycompany.mygroup.servers.serverscom, I get the following error still:

js: "C:/ti-tools/xdctools_3_16_02_32/packages/xdc/cfg/Main.xs", line 40: 

XDC runtime error: can't find the library 'export/BIN/DspBios/DAVINCI/DM6446GEM_0/RELEASE/dsplink.lib' 

specified by package dsplink.dsp. It wasn't found along the path 
'C:/ti-tools/xdctools_3_16_02_32/packages;
C:/ti-tools/codec_engine_2_26_02_11/packages;
C:/ti-tools/bios_5_41_02_14/packages;
C:/ti-tools/dsplink_linux_1_64;
C:/ti-tools/xdais_6_25_01_08/packages;
C:/ti-tools/codec_engine_2_26_02_11/cetools/packages;
P:/Doc/MTEQ/Skin/Codecs/packages;
C:/ti-tools/xdctools_3_16_02_32/packages;
C:/ti-tools/codec_engine_2_26_02_11/packages;
C:/ti-tools/codec_engine_2_26_02_11/cetools/packages;
C:/ti-tools/xdais_6_25_01_08/examples;
C:/ti-tools/codec_engine_2_26_02_11/examples;
C:/ti-tools/xdais_6_25_01_08/packages;
C:/ti-tools/xdctools_3_16_02_32/packages;
../../../..;'.

 

Meanwhile, I do indeed have a file at "C:\ti-tools\dsplink_linux_1_64\dsplink\dsp\export\BIN\DspBios\DAVINCIHD\DM6467GEM_0\RELEASE".  This error picks up at the "export" point, and the error refers to a path ending at the "dsplink_linux_1_64" point.  This leaves a gap of "\dsplink\dsp\", which SHOULD correspond to the "dsplink.dsp" package being processed.  So I think I should be fine and not get the error, but i do.

My package.xdc file (at C:\ti-tools\dsplink_linux_1_64\dsplink\dsp\package.xdc) seems to do nothing, containing only comments plus package "dsplink.dsp [1,4,0] {    module Global; }" (on three lines, combined to one to type here).  I don't see it "specifying" anything directly at least, as the error message suggests to me.

So, please help me yet again in trying to connect the dots!

Thanks very much,

Helmut

 

  • On GenServer's first page, did you pick the ti.platforms.evmDM6467?

    It's subtle, but the in the error msg, the library that can't be found is for the DM6446 (not the DM6467 I think you want - and built DSP Link for).  If you select the DM6467 platform in GenServer, it should look for the DM6467 library - which your now-built DSP Link should have.

    Chris

  • Chris,

    Thanks for noticing 6446 vs 6467.  I know I changed that correctly in the past, but also know I omitted change recently.  I've been retyping all my parameters.  Finally got smart and tried File/Open.  Lo and behold, I could pull in the .wiz I've been saving every time.  Won't have to type stuff in again from scratch, and won't miss this 6446 vs 6467 change.

    BUILD WORKED.  Ends with message "making relase file mycompany_mygroup_servers_servercom.zip".

    Thanks very much for your help on this, Chris.  It is genuinely appreciated.

    What's next? I believe I know at least a couple upcoming steps.  Per Robert's first reply at http://e2e.ti.com/support/embedded/f/354/p/88023/305777.aspx#305777, I'm going to copy strictly my servercom.x64P file my newly compiled server to the actual hard disk on my EVM (it still can't boot to NFS as root, but can connect to NFS as auxiliary fs that's beneath root).  I'll then recompile the encodedecode demo to refer to _____________, where this blank refers to my codec server and/or codec.

    If you don't mind, Chris, please check back on this thread for [links to a new thread containing] questions about that next step!!!!  When I'm totally finished, I'll send you a gift [of no financial value, of course].

    -Helmut

  • Chris,

    Send me your [work] mailing address to receive your gift [of no financial value, of course] !!!  Call 678-919-1093 or email temp2010@forren.org

    I've finally gotten me-modifed video out to my monitor.  A simple top/bottom frame half swap, but that lets me know it' MY code running.  Lots of cleanup and other stuff to do, but generally speaking, this brings me to the baseline I'm supposed to be at for (re-) developing our codec.

    Thanks very much for all your help,

    Helmut