Re: Regarding Support from TI
Thank you for reply. I posted my problem on E2E but no reply. May be my info might not be clear for them to comment on that. So What I want is solution/advice, I can provide my code for simulating. Can I provide my code for simulation to TI for help? If its paid, please let me know. Many Thanks, Sandeep.Yedire From: Nori, Sekhar nsek...@ti.com To: Sandeep YEDIRE sandee...@yahoo.co.in; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Cc: bmi...@acmet.com bmi...@acmet.com; Sandeep Yedire sande...@acmet.com Sent: Thursday, 17 September, 2009 11:35:07 AM Subject: RE: Regarding Support from TI On Thu, Sep 17, 2009 at 10:17:37, Sandeep YEDIRE wrote: Hi, What is the procedure for avialing Help on certain issue from TI? Please let me know process. I can describe my problem and provide code for simulation. Hi Sandeep, You can visit support.ti.com, there is support available via E2E forums. There is email support available as well. Thanks, Sekhar Try the new Yahoo! India Homepage. Click here. http://in.yahoo.com/trynew___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Regarding Support from TI
Hi, What is the procedure for avialing Help on certain issue from TI? Please let me know process. I can describe my problem and provide code for simulation. Many Thanks, Sandeep.Yedire Yahoo! India has a new look. Take a sneak peek http://in.yahoo.com/trynew___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Regarding printf usage in Codec algorithm -Dm6446
Hello all, I might not sure about this problem I come across on DM6446. The codec stack i estimated on DM6446 is 1.5KB. I have used memtab for allocation and now my data (structures) on Heap is 210KB. I confirm thru CE_DEBUG=2 and DSKT2.trace=true. This heap data is allocated. Now my doubt and my problem, even when codec stack requirement is low 2KB, why does DM6446 halts ? I simulated same problem with having a huge array of 80-90K in local(in-side func). 1. Is it like using printf's or File * can cause this? 2. Does stack size vary on DM6446 wehn compared to CCS v3.1? 3. Is it like, I am not following xDAIS? There are no malloc in my codec algo. I have taken arrays and allocated and initialized. Please suggest some advice on this. Many Thanks, Sandeep.Yedire Love Cricket? Check out live scores, photos, video highlights and more. Click here http://cricket.yahoo.com___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Regarding allocation of constant data (tables) in .const segment of Dm6446.
Hello all, I am currently working with my codec algorithm. I want to allocate constant data like VLC tables into .const segment of DM6446. I tried to use prefix const int array1[]; but this did not allocate on .const segment. Can you please provide any link or info on this? Where as in simulator CCS v3.1 with prefix const, it updated into .const segment for 6416 target. Many Thanks, Sandeep.Yedire See the Web#39;s breaking stories, chosen by people like you. Check out Yahoo! Buzz. http://in.buzz.yahoo.com/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Regarding allocation of constant data (tables) in .const segment of Dm6446.
I have used const prefix and #pragma directive to put the arrays into .const section. Thanks for help. Many Thanks, Sandeep.Yedire From: Albert Burbea alber...@gmail.com To: Sandeep YEDIRE sandee...@yahoo.co.in Sent: Tuesday, 1 September, 2009 3:34:35 PM Subject: Re: Regarding allocation of constant data (tables) in .const segment of Dm6446. Hi Sandeep I guess you have to actually initialize the arrays. Otherwise, use a #pragma command to instruct the compiler to put the arrays in the .const section Albert On Tue, Sep 1, 2009 at 10:56 AM, Sandeep YEDIRE sandee...@yahoo.co.in wrote: Hello all, I am currently working with my codec algorithm. I want to allocate constant data like VLC tables into .const segment of DM6446. I tried to use prefix const int array1[]; but this did not allocate on .const segment. Can you please provide any link or info on this? Where as in simulator CCS v3.1 with prefix const, it updated into .const segment for 6416 target. Many Thanks, Sandeep.Yedire See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- Albert Burbea Harishonim 8 Ramat Gan 52502, Israel Tel/Fax + 972-3-7526016 Mobile: +972-52-3541842 Love Cricket? Check out live scores, photos, video highlights and more. Click here http://cricket.yahoo.com___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Regarding dynamic memory allocation on DSP side of DM6446.
Hello, Can we allocate Dynamic memory on DSP side of DM6446? Many Thanks, Sandeep.Yedire See the Web#39;s breaking stories, chosen by people like you. Check out Yahoo! Buzz. http://in.buzz.yahoo..com/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Regarding increase in Sever Thread stack size
Thanks for your reply. I am looking for the same. Is there any max limit for
this segment?
Many Thanks,
Sandeep.Yedire
From: Tivy, Robert rt...@ti.com
To: Sandeep YEDIRE sandee...@yahoo.co.in;
davinci-linux-open-source@linux.davincidsp.com
davinci-linux-open-source@linux.davincidsp.com
Cc: Sandeep Yedire sande...@acmet.com
Sent: Saturday, 15 August, 2009 5:09:38 AM
Subject: RE: Regarding increase in Sever Thread stack size
Is this what you're looking
for?:
var Server =
xdc.useModule('ti.sdo.ce.Server');
Server.algs =
[
{name: viddec_copy, mod: VIDDEC_COPY, threadAttrs:
{
stackSize: 0x4096, stackMemId: 0, priority: Server.MINPRI + 2}, groupId
:
0,
},
{name: videnc_copy, mod:
VIDENC_COPY, threadAttrs: {
stackMemId: 0, priority: Server.MINPRI + 2}, groupId : 0,
}
];
The max limit is dictated by your available memory for BIOS
TSK stacks.
- Rob
From: davinci-linux-open-source-boun...@linux.davincidsp.com
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf
Of Sandeep YEDIRE
Sent: Tuesday, August 11, 2009 10:34
PM
To: davinci-linux-open-source@linux.davincidsp.com
Cc: Sandeep Yedire
Subject: Regarding increase in Sever Thread stack
size
Hello all,
is there anyway to increase server thread stack size for one
particular codec? What is max limit ?
Many
Thanks,
Sandeep.Yedire
See the Web's breaking stories, chosen by people like you. Check out Yahoo!
Buzz.
Yahoo! recommends that you upgrade to the new and safer Internet Explorer
8. http://downloads.yahoo.com/in/internetexplorer/___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Regarding increase in Sever Thread stack size
Hello all, is there anyway to increase server thread stack size for one particular codec? What is max limit ? Many Thanks, Sandeep.Yedire Looking for local information? Find it on Yahoo! Local http://in.local.yahoo.com/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Stack-size on evmDM6446
Hello there,
I am working on evmDM6446 with my application.
What is maximum stack size limit I can set on h/w?
Please provide any document regarding this, it will be appreciated.
Stackseg is assigned to DDR2 which is 4MB, according to .tcf file.
Can it take upto 4MB?
My application needs stack size of 192K from CCS v3.1 simulator.
when I set this accordingly in my .cfg file, I still get same error. H/w hatls
at VIDDEC_process().
Is this stack size issue?
From .tcf file.
/*
* Copyright 2007
* Texas Instruments Incorporated
*
* All rights reserved. Property of Texas Instruments Incorporated
* Restricted rights to use, duplicate or disclose this code are
* granted through contract.
*
*/
var platform = environment[config.platform];
print(platform = + platform);
/*
* Setup platform-specific memory map:
*/
var mem_ext = [
{
comment:DDRALGHEAP: off-chip memory for dynamic algmem allocation,
name: DDRALGHEAP,
base: 0x8800, // 128MB
len:0x07A0, // 122MB
space: code/data
},
{
comment:L1DSRAM: memory for dynamic algmem allocation,
name: L1DSRAM,
base: 0x11F04000, //
len:0x1, // 64k
space: data
},
{
comment:DDR2: off-chip memory for application code and data,
name: DDR2,
base: 0x8FA0, // 250MB
//len:0x003C,
len:0x0040, // 4MB
space: code/data
},
{
comment:DSPLINK: off-chip memory reserved for DSPLINK code and data,
name: DSPLINKMEM,
base: 0x8FE0, // 254MB
len:0x0010, // 1MB
space: code/data
},
{
comment:RESET_VECTOR: off-chip memory for the reset vector table,
name: RESET_VECTOR,
base: 0x8FF0,
len:0x0080,
space: code/data
},
];
/*
* Internal memory partitioning for DM6446
*
* On the left in the diagram below is the layout of internal memory
* available on DM6446 for data caching and as RAM; on the right is the
* diagram showing how this configuration file partitions the available
* 64k+80k of memory. (The 32K for program cache is not affected by this
* configuration, and not shown below.) Please find more specifics on how
* the configuration is done further below.
*
*
* Physical internal memory on DM6446 Default partitioning in this .tcf
*
* |//| |//|
* 0x1180 +--+ 0x1180 +--+
* | L2Cache | | |
* | and/or | 64k | L2 Cache | 64k
* | IRAM| | |
* | | | |
* 0x1181 +--+ 0x1181 +--+
* |//| |//|
* : : : :
* |//| |//|
* 0x11F04000 +--+ 0x11F04000 +--+
* | | | |
* | L1DSRAM | 48k | L1DSRAM |
* | | | | 64k
* 0x11F1 +- - - - - + | |
* |L1Cache or| 32k +- - - - - +
* |more L1DSR| 0x11F14000 | L1 cache | 16k
* 0x11F18000 +--+ 0x11F18000 +--+
* |//| |//|
*/
/*
* Specify the L2 CACHE memory setting. This value indicates how the physical
* internal memory of size 64K starting at 0x1180 will be split between
* L2 cache and a general-purpose internal memory segment IRAM. The options
* are:
* l2Mode: 0k -- IRAM is 64K long, starts at 0x1180; no L2 cache
* l2Mode: 32k -- IRAM is 32K long, starts at 0x1180; L2 cache is
* 32K long, starts at 0x11808000
* l2Mode: 64k -- no IRAM; L2 cache is 64k long, starts at 0x1180
*/
var device_regs = {
l2Mode: 64k
};
var params = {
clockRate: 594,
catalogName: ti.catalog.c6000,
deviceName: DM6446,
regs: device_regs,
mem: mem_ext
};
/*
* Now customize the generic platform with parameters specified above.
*/
utils.loadPlatform(ti.platforms.generic, params);
/* ===
* Enable heaps and tasks
* ===
*/
bios.enableMemoryHeaps(prog);
bios.enableTskManager(prog);
/* ===
* Configure L1 cache and L1DSRAM
How to generate .map file when creating server.
Hi all, Can you please suggest me How to generate .map file when creating server ? I dont have ccs v3.3. Many Thanks, Sandeep.Yedire Looking for local information? Find it on Yahoo! Local http://in.local.yahoo.com/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: How to generate .map file when creating server.
Many Thanks, Sandeep.Yedire From: Ring, Chris cr...@ti.com To: Sandeep YEDIRE sandee...@yahoo.co.in; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Sent: Thursday, 9 July, 2009 7:32:16 PM Subject: RE: How to generate .map file when creating server. Depending on how you build your server, there may be one auto-generated already - search for a *.map file in your package/cfg/... directory tree. As a concrete example, the CE all_codecs example has a .map file in ti/sdo/ce/examples/servers/all_codecs/package/cfg/bin/platname/all.xext.map Chris From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Sandeep YEDIRE Sent: Thursday, July 09, 2009 3:43 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: How to generate .map file when creating server. Hi all, Can you please suggest me How to generate .map file when creating server ? I dont have ccs v3.3. Many Thanks, Sandeep.Yedire See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. Love Cricket? Check out live scores, photos, video highlights and more. Click here http://cricket.yahoo.com___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: How to generate .map file when creating server.
Yes I did notice that its auto-generated in all_codecs folder, but its not generated in video_copy folder. I am currently working on video_copy folder. The execution flow by using CE_DEBUG =2 is not just halts after I modified (added my call to decoder) viddec_copy example. I want to check the .map generated file if any help. Please let me know what difference in extra command that actaully made all_codecs generate .map and that did not in video_copy. Many Thanks, Sandeep.Yedire From: Ring, Chris cr...@ti.com To: Sandeep YEDIRE sandee...@yahoo.co.in; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Sent: Thursday, 9 July, 2009 7:32:16 PM Subject: RE: How to generate .map file when creating server. Depending on how you build your server, there may be one auto-generated already - search for a *.map file in your package/cfg/... directory tree. As a concrete example, the CE all_codecs example has a .map file in ti/sdo/ce/examples/servers/all_codecs/package/cfg/bin/platname/all.xext.map Chris From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Sandeep YEDIRE Sent: Thursday, July 09, 2009 3:43 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: How to generate .map file when creating server. Hi all, Can you please suggest me How to generate .map file when creating server ? I dont have ccs v3.3. Many Thanks, Sandeep.Yedire See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. Yahoo! recommends that you upgrade to the new and safer Internet Explorer 8. http://downloads.yahoo.com/in/internetexplorer/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: How to generate .map file when creating server.
Thank you for your help. Many Thanks, Sandeep.Yedire From: Ring, Chris cr...@ti.com To: Sandeep YEDIRE sandee...@yahoo.co.in; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Cc: Sandeep Yedire sande...@acmet.com; bmi...@acmet.com bmi...@acmet.com Sent: Thursday, 9 July, 2009 9:05:10 PM Subject: RE: How to generate .map file when creating server. Ah. The video_copy example shows how to build a Server with a GNU makefile, so many of the freebies you get from a package.bld-based build (like generating a .map file) aren't there. You should see an explicit '$(LINK)' command in the makefile you'll have to modify. The TI tools generate a .map file with the -m option. Run 'lnk64P --help' for the options. Chris From: Sandeep YEDIRE [mailto:sandee...@yahoo.co.in] Sent: Thursday, July 09, 2009 7:59 AM To: Ring, Chris; davinci-linux-open-source@linux.davincidsp.com Cc: Sandeep Yedire; bmi...@acmet.com Subject: Re: How to generate .map file when creating server. Yes I did notice that its auto-generated in all_codecs folder, but its not generated in video_copy folder. I am currently working on video_copy folder. The execution flow by using CE_DEBUG =2 is not just halts after I modified (added my call to decoder) viddec_copy example. I want to check the .map generated file if any help. Please let me know what difference in extra command that actaully made all_codecs generate .map and that did not in video_copy. Many Thanks, Sandeep.Yedire From: Ring, Chris cr...@ti.com To: Sandeep YEDIRE sandee...@yahoo.co.in; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Sent: Thursday, 9 July, 2009 7:32:16 PM Subject: RE: How to generate .map file when creating server. Depending on how you build your server, there may be one auto-generated already - search for a *.map file in your package/cfg/ directory tree. As a concrete example, the CE all_codecs example has a .map file in ti/sdo/ce/examples/servers/all_codecs/package/cfg/bin/platname/all.xext.map Chris From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Sandeep YEDIRE Sent: Thursday, July 09, 2009 3:43 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: How to generate .map file when creating server. Hi all, Can you please suggest me How to generate .map file when creating server ? I dont have ccs v3.3. Many Thanks, Sandeep.Yedire See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. Looking for local information? Find it on Yahoo! Local Looking for local information? Find it on Yahoo! Local http://in.local.yahoo.com/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Debugging or using trace on evmDM6446
Hello there, I am currently working on my own algorithm on evmDM6446. I m able to create video server and want to debug on DSP 64XX. Can you please inform how to debug on DSP side and any info or link is really appreciated. Many Thanks, Sandeep.Yedire Yahoo! recommends that you upgrade to the new and safer Internet Explorer 8. http://downloads.yahoo.com/in/internetexplorer/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Debugging or using trace on evmDM6446
I am sorry, I do not have CCS v3.3 IDE. Is it possible to debug without that on DSP core? is there Any other alternate way to check data on DSP side ? Many Thanks, Sandeep.Yedire From: Ring, Chris cr...@ti.com To: Sandeep YEDIRE sandee...@yahoo.co.in; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Cc: bmi...@acmet.com bmi...@acmet.com Sent: Wednesday, 8 July, 2009 2:23:40 AM Subject: RE: Debugging or using trace on evmDM6446 http://tiexpressdsp.com/index.php/Debugging_the_DSP_side_of_a_CE_application_on_DaVinci_using_CCS Chris From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Sandeep YEDIRE Sent: Tuesday, July 07, 2009 7:25 AM To: davinci-linux-open-sou...@linux.davincidsp..com Cc: bmi...@acmet.com Subject: Debugging or using trace on evmDM6446 Hello there, I am currently working on my own algorithm on evmDM6446. I m able to create video server and want to debug on DSP 64XX. Can you please inform how to debug on DSP side and any info or link is really appreciated. Many Thanks, Sandeep.Yedire Looking for local information? Find it on Yahoo! Local http://in.local.yahoo.com/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
error library:member ' ' has incompatible byte ordering when building servers
hello there,
I am currently working on building my own algorithm by modifying viddec_copy in
your examples.
When building codec engine, I have added below lines in package.bld file.
Pkg.addLibrary(name, target, {
/* any other exeAttrs */
copts: -mem_model:data=far
}
);And able to create library successfully. Without using
-mem_model:data=far, I get relocation error message when building server. So
I have used this option for now,even though it hinders performance.
When I build servers for the same , I get this error message below.
I understand that this might be due to different compiler options, Since I am
not using CCS v3.3 IDE I am not familiar how to do this in dvsdk_1_30_xx on
linux platform.
error: library
'/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy/lib/viddec_copy.a64P',
member 'viddec_copy.o64P' has incompatible byte ordering
error: library
'/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy/lib/viddec_copy.a64P',
member 'ldecod.o64P' has incompatible byte ordering
-
-
-
like this I get many.
--
Please suggest where to set the same compile options
I also found that, if I add -mem_model:data=far in makefile in
servers/viddec_copy/evmDM6446/
# [CE] Augment the standard $(CFLAGS) variable, adding the
# Configuro-generated compiler file.
CFLAGS = -@ $(COMPILER_FILE) -mem_model:data=far //Added by me.
I get different error for libraries which are being shared (not built by me). I
dont get error for libraries built by me.
error: library
'/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages/ti/sdo/ce/lib/ce.a64P',
member 'Engine.o64P' has incompatible byte ordering
error: library
'/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages/ti/sdo/ce/lib/ce.a64P',
member 'visa.o64P' has incompatible byte ordering
-
-
-
Like this many more...
---
Many Thanks,
Sandeep.Yedire
Yahoo! recommends that you upgrade to the new and safer Internet Explorer
8. http://downloads.yahoo.com/in/internetexplorer/___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Using buildinstructions fatal error #5: could not open source file ti/xdais/dm/ividdec.h
Hello there, i have been working on DM6446 for about a week now but not able to set-up properly. I followed instructions given in sprue66d.pdf for installation on my RHEL -4 pc. I did this twice as I got strange error message when working with one of examples. Which I already posted with subject :xdc.loadPackage: can't find package 'ti.sdo.ce' when building viddec_copy examples date:22/06/09. I could not find casue for this error and try to set-up everything again. When I finished with setting up everything, With refering to build instruction in codec_engine/examples/, I mdofied changes in xdcpath.mak and user.bld file accordingly. I have copied both the files below. When I did gmake in dir ~/work/examples/ti/sdo/ce/examples/codecs/viddec_copy/, I get this error message which is given below. I found these header files, in dir /home/sandeep/dvsdk_1_30_01_41/xdais_6_00_01/packages/ti/xdais/dm/ But these are not included when I build them. I also set my env variable for XDCPATH accordingly. Please find my XDCPATH below with heading. It looks like, I have not included the correct XDCPATH which actually is the problem for my earlier failure. Please look for below files for any help in this issue. I can copy the contents of /home/sandeep/dvsdk_1_30_01_41/xdais_6_00_01/packages/ti/ to ~/work/examples/ti/ for this error. But When I have given path in xdcpath.mak file, and the makefile in viddec_copy folder will refer to this xdcpath.mak for its packages. Please look for below files for any help/advice in this issue I am having. --- Error message: [sand...@evmdm6446 viddec_copy]$ gmake /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xdc XDCPATH=/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy/../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages \ XDCOPTIONS=v all -PD . making all: Wed Jun 24 14:31:14 IST 2009 ... .interfaces [/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy] gmake[1]: `.interfaces' is up to date. .interfaces files complete: Wed Jun 24 14:31:14 IST 2009. .libraries [/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy] rm -f package/lib/lib/viddec_copy/viddec_copy.o64P # # cl64P viddec_copy.c ... /home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15/bin/cl6x -c -oe -qq -pdsw225 -pden -pds=195 -mv64p -eo.o64P -ea.s64P -Dxdc_target_name__=C64P -Dxdc_target_types__=ti/targets/std.h -Dxdc_bld__profile_release -Dxdc_bld__vers_1_0_6_0_15 -o2 -I. -I/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy/../../../../../.. -I/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages -I/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages -I/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages -I/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages -I../../../../../.. -I/home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15/include -fs=./package/lib/lib/viddec_copy -fr=./package/lib/lib/viddec_copy -fc viddec_copy.c viddec_copy.c, line 20: fatal error #5: could not open source file ti/xdais/dm/ividdec.h 1 fatal error detected in the compilation of viddec_copy.c. Compilation terminated. Compilation failure gmake[1]: *** [package/lib/lib/viddec_copy/viddec_copy.o64P] Error 1 gmake: *** [/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy,.libraries] Error 2 gmake: *** [all] Error 2 [sand...@evmdm6446 viddec_copy]$ printenv XDCPATH /home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy;/home/sandeep/dvsdk_1_30_01_41/xdais_6_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/framework_components_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15;/home/sandeep/dvsdk_1_30_01_41/biosutils_1_00_02/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages;/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages;/home/sandeep/dvsdk_1_30_01_41/cmem_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/dsplink_140-05p1/packages; File:user.bld /* * user.bld * * User note: YOU MUST MODIFY THIS FILE TO SPECIFY THE COMPILER TOOL PATHS. */ // This table list the targets for which to build libraries and programs, and for // each target it lists where the compiler tools are and for what platforms // the programs should be built. For all build variants where you specify // that
Re: Using buildinstructions fatal error #5: could not open source file ti/xdais/dm/ividdec.h
Thanks. seems working. This seems buggy as I dont have cetools folder. so it shud take it as zero. Many Thanks, Sandeep.Yedire From: JayaKumar, PremKumar premkuma...@ti..com To: Sandeep YEDIRE sandee...@yahoo.co.in; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Cc: bmi...@acmet.com bmi...@acmet.com; Sandeep Yedire sande...@acmet.com Sent: Wednesday, 24 June, 2009 3:42:42 PM Subject: RE: Using buildinstructions fatal error #5: could not open source file ti/xdais/dm/ividdec.h From the error message you can see that the xdais path is tried to be picked from the cetools. Try setting USE_CETOOLS_IF_EXISTS = 0 in the xdcpaths.mak so that the path which you want to be set as xdais path in the XDCPATH will take effect. Regards, Prem From:davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Sandeep YEDIRE Sent: Wednesday, June 24, 2009 3:17 PM To: davinci-linux-open-source@linux.davincidsp.com Cc: bmi...@acmet.com; Sandeep Yedire Subject: Using buildinstructions fatal error #5: could not open source file ti/xdais/dm/ividdec.h Hello there, i have been working on DM6446 for about a week now but not able to set-up properly. I followed instructions given in sprue66d.pdf for installation on my RHEL -4 pc. I did this twice as I got strange error message when working with one of examples. Which I already posted with subject :xdc.loadPackage: can't find package 'ti.sdo.ce' when building viddec_copy examples date:22/06/09. I could not find casue for this error and try to set-up everything again. When I finished with setting up everything, With refering to build instruction in codec_engine/examples/, I mdofied changes in xdcpath.mak and user.bld file accordingly. I have copied both the files below. When I did gmake in dir ~/work/examples/ti/sdo/ce/examples/codecs/viddec_copy/, I get this error message which is given below. I found these header files, in dir /home/sandeep/dvsdk_1_30_01_41/xdais_6_00_01/packages/ti/xdais/dm/ But these are not included when I build them. I also set my env variable for XDCPATH accordingly. Please find my XDCPATH below with heading. It looks like, I have not included the correct XDCPATH which actually is the problem for my earlier failure. Please look for below files for any help in this issue. I can copy the contents of /home/sandeep/dvsdk_1_30_01_41/xdais_6_00_01/packages/ti/ to ~/work/examples/ti/ for this error. But When I have given path in xdcpath.mak file, and the makefile in viddec_copy folder will refer to this xdcpath.mak for its packages. Please look for below files for any help/advice in this issue I am having. --- Error message: [sand...@evmdm6446 viddec_copy]$ gmake /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xdc XDCPATH=/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy/../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages \ XDCOPTIONS=v all -PD . making all: Wed Jun 24 14:31:14 IST 2009 ... .interfaces [/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy] gmake[1]: `.interfaces' is up to date. .interfaces files complete: Wed Jun 24 14:31:14 IST 2009. .libraries [/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy] rm -f package/lib/lib/viddec_copy/viddec_copy.o64P # # cl64P viddec_copy.c ... /home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15/bin/cl6x -c -oe -qq -pdsw225 -pden -pds=195 -mv64p -eo.o64P -ea.s64P -Dxdc_target_name__=C64P -Dxdc_target_types__=ti/targets/std..h -Dxdc_bld__profile_release -Dxdc_bld__vers_1_0_6_0_15 -o2 -I.. -I/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy/../../../../.../.. -I/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages -I/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages -I/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages -I/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages -I../../../../../.. -I/home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15/include -fs=./package/lib/lib/viddec_copy -fr=./package/lib/lib/viddec_copy -fc viddec_copy.c viddec_copy.c, line 20: fatal error #5: could not open source file ti/xdais/dm/ividdec.h 1 fatal error detected in the compilation of viddec_copy.c. Compilation terminated. Compilation failure gmake[1]: *** [package/lib/lib/viddec_copy/viddec_copy.o64P] Error 1 gmake: *** [/home/sandeep/work/examples/ti/sdo/ce/examples/codecs/viddec_copy,.libraries] Error 2 gmake: *** [all] Error 2 [sand...@evmdm6446 viddec_copy
xdc.loadPackage: can't find package 'ti.sdo.ce' when building viddec_copy examples
Hello there, I am currently working on 'viddec_copy' example in ceutils_1_07 folder . I have used the existing wizard_mycompany_mygroup.codecs.xml while RTSC genpackage wizard. And I got succes message at the end. I saved the output respository to /home/sandeep/Desktop/test/ Now I created the server using RTSC wizard and existing mycompany_mygroup_servers_viddec_copy_unitserver_evmdm6446_wizard.xml provided with in the example. I have placed xdcpath.mak anc user.bld files in /home/sandeep/Desktop/test/ folder . Later I cd into /home/sandeep/Desktop/test/mycompany/mygroup/codecs/viddec_copy/ I did /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xdc release -PR . I get below error message when building for codecs. -- [sand...@davinci viddec_copy]$ /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xdc release -PR . making release: Mon Jun 22 15:57:12 IST 2009 ... .interfaces [.] .interfaces [./ce] .interfaces files complete: Mon Jun 22 15:57:12 IST 2009. .libraries [.] .libraries [./ce] .libraries files complete: Mon Jun 22 15:57:12 IST 2009. .dlls [.] .dlls [./ce] .dlls files complete: Mon Jun 22 15:57:12 IST 2009. .executables [.] .executables [./ce] .executables files complete: Mon Jun 22 15:57:12 IST 2009. release [.] all files complete. generating external package references package/package.ext.xml ... release [./ce] all files complete. generating schema include file list ... js: /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/xdc.tci, line 270: exception from uncaught JavaScript throw: Error: xdc.loadPackage: can't find package 'ti..sdo.ce' along the path '/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02;/home/sandeep/Desktop/test;/home/sandeep/dvsdk_1_30_01_41/ceutils_1_07/examples/viddec_copy_packaged;/home/sandeep/dvsdk_1_30_01_41/cmem_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15/bin;/home/sandeep/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages;/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/sandeep/dvsdk_1_30_01_41/biosutils_1_00_02/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages;/home/sandeep/dvsdk_1_30_01_41/dsplink_140-05p1/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/ceutils_1_07/packages;/home/sandeep/dvsdk_1_30_01_41/framework_components_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/sandeep/Desktop/test/mycompany/mygroup/codecs/viddec_copy/ce/./../../../../..;'; try redefining the package path (XDCPATH). /home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages/ti/sdo/ce/video/package/ti.sdo.ce.video.sch, line 12 /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/include/utils.tci, line 697 /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/xdc.tci, line 297 ./package/mycompany.mygroup.codecs.viddec_copy.ce.sch, line 10 /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/include/utils.tci, line 697 /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/xdc.tci, line 297 /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/cfginc.js, line 56 /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/include/utils.tci, line 588 /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/xs.js, line 125 gmake[1]: *** [package/package.cfg.xdc.inc] Error 1 gmake: *** [ce,release] Error 2 Below is my XDCPATH env variable. [sand...@davinci codecs]$ printenv XDCPATH /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02;/home/sandeep/Desktop/test;/home/sandeep/dvsdk_1_30_01_41/ceutils_1_07/examples/viddec_copy_packaged;/home/sandeep/dvsdk_1_30_01_41/cmem_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15/bin;/home/sandeep/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages;/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/sandeep/dvsdk_1_30_01_41/biosutils_1_00_02/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages;/home/sandeep/dvsdk_1_30_01_41/dsplink_140-05p1/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/ceutils_1_07/packages;/home/sandeep/dvsdk_1_30_01_41/framework_components_2_00_01/packages; Please let me know what is the cause of this error message. Is there anything which I missed? I do not have cetools directory. Regards, Sandeep.Yedire Many Thanks, Sandeep.Yedire Cricket on your mind? Visit the ultimate cricket website. Enter http://cricket.yahoo.com___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Instructions for making library file for C64 on evmDM6446 using xdc tools
Hi, I am new user on evmDM6446. I am able to build and run your examples on target. My current task to to port our codec on evmDM6446. From your documents, XDC User guide.pdf, I am able to get hello.out binary file. From mail previous discussions, I understand that I need a library file which is genarated from CCS v3.3 I do not have CCS v3.3 simulator. Can I make library file with XDC tools? If so, Please give me instructions Is CCS v3.3 FET any use for me? I understand and read wiki..davincidsp.com, that after I get library file .a64P I can use RTSC wizard to create server and .x64P. Can you please provide any link for basic instructions without using CCS v3.3. I have read the document on Xdc_Userguide-Part1.pdf. It mentions about CCS v3.3 pjt. Many Thanks, Sandeep.Yedire Explore and discover exciting holidays and getaways with Yahoo! India Travel http://in.travel.yahoo.com/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Instructions for making library file for C64 on evmDM6446 using xdc tools
Thanks for your email. I will go thru. Best Wishes, Sandeep.Yedire -- 2009/6/16 Ring, Chris cr...@ti.com The XDC docs are good, but [intentionally] vague as they're targeted at a huge range of developers. Assuming you're interested in the Codec Engine development flow, this article is a decent starting point to help understand the basics from codec developer up the stack to application developer: http://tiexpressdsp.com/index.php?title=Codec_Engine_Roles It defines the 4 roles Codec Engine users play, the inputs/outputs each role incorporates/generates, and tools/docs which further describe the steps required. The Codec Engine examples are shaped by these 4 roles, too, as described here: http://tiexpressdsp.com/index.php?title=Codec_Engine_Examples#Physical_Layout Chris -- *From:* davinci-linux-open-source-boun...@linux.davincidsp.com [mailto: davinci-linux-open-source-boun...@linux.davincidsp.com] *On Behalf Of *Sandeep YEDIRE *Sent:* Tuesday, June 16, 2009 4:44 AM *To:* davinci-linux-open-source@linux.davincidsp.com *Cc:* Sandeep Yedire *Subject:* Instructions for making library file for C64 on evmDM6446 using xdc tools Hi, I am new user on evmDM6446. I am able to build and run your examples on target. My current task to to port our codec on evmDM6446. From your documents, XDC User guide.pdf, I am able to get hello.out binary file. From mail previous discussions, I understand that I need a library file which is genarated from CCS v3.3 I do not have CCS v3.3 simulator. Can I make library file with XDC tools? If so, Please give me instructions Is CCS v3.3 FET any use for me? I understand and read wiki.davincidsp.com, that after I get library file .a64P I can use RTSC wizard to create server and .x64P. Can you please provide any link for basic instructions without using CCS v3.3. I have read the document on Xdc_Userguide-Part1.pdf. It mentions about CCS v3.3 pjt. Many Thanks, Sandeep.Yedire -- Bring your gang together. Do your thing. Find your favourite Yahoo! Group.http://in.rd.yahoo.com/tagline_groups_9/*http://in.promos.yahoo.com/groups/ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Example code servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp'
Hello Everyone, I am currently working on building codec_engine examples for evmDM6446 target provided along with dvsdk_1_30_01_41 version. Following build instructions in codec_examples folder, I was able to perfrom gmake successfully in folder codecs, extensions. And when I did same in folder servers, I do get the following error. Error message below. I have aslo attached user.txt (nothing but user.bld) and xdcpath.txt (xdcpath.mak) files at bottom of this email. Please let me know what went wrong.. -- [sand...@davinci servers]$ gmake clean gmake -C video_copy clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 clean gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' rm -rf video_copy.x64P ti_sdo_ce_examples_servers_video_copy_evmDM6446.tar *.obj package package.* video_copy gmake[2]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C all_codecs clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xdc XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs/../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages \ XDCOPTIONS=v clean -PD . making clean: Thu Jun 11 16:48:51 IST 2009 ... clean [/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs] cleaning complete: Thu Jun 11 16:48:51 IST 2009. gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' [sand...@davinci servers]$ gmake gmake -C video_copy all gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 all gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446/../../../../../../...;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xs xdc.tools.configuro -c /home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15 -o video_copy \ -t ti.targets.C64P -p ti.platforms.evmDM6446 \ --tcf video_copy.cfg making package.mak (because of package.bld) ... generating interfaces for package video_copy (because package/package.xdc.xml is older than package.xdc) ... configuring video_copy..x64P from package/cfg/video_copy_x64P.cfg ... platform = ti.platforms.evmDM6446 ti.sdo.ce.bioslog.init() ... ti.sdo.ce.examples.codecs.videnc_copy.close() ... ti.sdo.ce.bioslog.close() ... ti.sdo.ce.osal.close() ... js: /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/Main.xs, line 248: exception from uncaught JavaScript throw: Error: xdc.loadPackage: can't find package 'dsplink.dsp' along the path '/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages;/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446/video_copy/./..;'; try redefining the package path (XDCPATH). /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/Main.xs, line 154 /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/xs.js, line 144 gmake: *** [package/cfg/video_copy_x64P.c] Error 1 gmake: *** [package/cfg/video_copy_x64P.c] Deleting file `package/cfg/video_copy_x64Pcfg.cmd' gmake: *** [package/cfg/video_copy_x64P.c] Deleting file `package/cfg/video_copy_x64Pcfg_c.c' gmake: *** [package/cfg/video_copy_x64P.c] Deleting file `package/cfg/video_copy_x64Pcfg.s62' gmake[2]: *** [video_copy] Error 2 gmake[2]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' gmake[1]: *** [all] Error 2 gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy'
Re: Example code servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp'
Thanks for your reply. My Codec_Engine installation does not have cetools in it. As you mentioned, I will try with 'USE_CETOOLS_IF_EXISTS := 0' Let you know if I get any problem. Many Thanks, Sandeep.Yedire From: JayaKumar, PremKumar premkuma...@ti.com To: Sandeep YEDIRE sandee...@yahoo.co..in; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Cc: Sandeep Yedire sande...@acmet.com Sent: Friday, 12 June, 2009 3:40:29 PM Subject: RE: Example code servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp' From the xdcpaths.mak file it looks like your DVSDK installation is having all the required components. So, cetools reference may not be required. And further not sure if your CE installation has the cetools in it. So, try setting USE_CETOOLS_IF_EXISTS := 0 instead of 1 in the xdcpaths.mak Regards, Prem TexasInstruments India From:davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Sandeep YEDIRE Sent: Friday, June 12, 2009 11:29 AM To: davinci-linux-open-source@linux.davincidsp.com Cc: Sandeep Yedire Subject: Example code servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp' Hello Everyone, I am currently working on building codec_engine examples for evmDM6446 target provided along with dvsdk_1_30_01_41 version. Following build instructions in codec_examples folder, I was able to perfrom gmake successfully in folder codecs, extensions. And when I did same in folder servers, I do get the following error. Error message below. I have aslo attached user.txt (nothing but user.bld) and xdcpath.txt (xdcpath.mak) files at bottom of this email. Please let me know what went wrong. -- [sand...@davinci servers]$ gmake clean gmake -C video_copy clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 clean gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' rm -rf video_copy.x64P ti_sdo_ce_examples_servers_video_copy_evmDM6446.tar *.obj package package.* video_copy gmake[2]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C all_codecs clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xdc XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs/../../../../.../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages \ XDCOPTIONS=v clean -PD . making clean: Thu Jun 11 16:48:51 IST 2009 ... clean [/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs] cleaning complete: Thu Jun 11 16:48:51 IST 2009. gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' [sand...@davinci servers]$ gmake gmake -C video_copy all gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 all gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446/../../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xs xdc.tools.configuro -c /home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15 -o video_copy \ -t ti.targets.C64P -p ti.platforms.evmDM6446 \ --tcf video_copy.cfg making package.mak (because of package.bld) ... generating interfaces for package video_copy (because package/package.xdc.xml is older than package.xdc) configuring video_copy.x64P from package/cfg/video_copy_x64P.cfg platform = ti.platforms.evmDM6446 ti.sdo.ce.bioslog..init() ... ti.sdo.ce.examples.codecs.videnc_copy.close() ... ti.sdo.ce.bioslog.close() ... ti.sdo.ce.osal.close() ... js: /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/Main.xs, line 248: exception from uncaught JavaScript throw: Error: xdc.loadPackage: can't find package 'dsplink.dsp' along the path
Re: Playing H264 encoded with CE file with VLC player-issue
Thank you. Its working now. I am able to build all the examples and able to run on target. I will be working displaying yuv on LCD tomorrow. I just found this, I tried to encode YUV 420 QCIF file to .264 format with CE and able to decode to yuv. I did not find any noticeable difference in YUV. But when I tried to play .264 (encoded by CE), I found its not playing as it has w.r.t to input yuv file. I understand CE implementation might not be according to reference. What I actually is picture in RED color and 4 small images scale down video being played in VLC player. Please comment on this behaviour. Many Thanks, Sandeep.Yedire From: JayaKumar, PremKumar premkuma...@ti.com To: Sandeep YEDIRE sandee...@yahoo.co.in; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Cc: Sandeep Yedire sande...@acmet.com Sent: Friday, 12 June, 2009 3:40:29 PM Subject: RE: Example code servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp' From the xdcpaths.mak file it looks like your DVSDK installation is having all the required components. So, cetools reference may not be required. And further not sure if your CE installation has the cetools in it. So, try setting USE_CETOOLS_IF_EXISTS := 0 instead of 1 in the xdcpaths.mak Regards, Prem TexasInstruments India From:davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Sandeep YEDIRE Sent: Friday, June 12, 2009 11:29 AM To: davinci-linux-open-source@linux.davincidsp.com Cc: Sandeep Yedire Subject: Example code servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp' Hello Everyone, I am currently working on building codec_engine examples for evmDM6446 target provided along with dvsdk_1_30_01_41 version. Following build instructions in codec_examples folder, I was able to perfrom gmake successfully in folder codecs, extensions. And when I did same in folder servers, I do get the following error. Error message below. I have aslo attached user.txt (nothing but user.bld) and xdcpath.txt (xdcpath.mak) files at bottom of this email. Please let me know what went wrong. -- [sand...@davinci servers]$ gmake clean gmake -C video_copy clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 clean gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' rm -rf video_copy.x64P ti_sdo_ce_examples_servers_video_copy_evmDM6446.tar *.obj package package.* video_copy gmake[2]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C all_codecs clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xdc XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs/../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages \ XDCOPTIONS=v clean -PD . making clean: Thu Jun 11 16:48:51 IST 2009 ... clean [/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs] cleaning complete: Thu Jun 11 16:48:51 IST 2009. gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' [sand...@davinci servers]$ gmake gmake -C video_copy all gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 all gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446/../../.../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xs xdc.tools.configuro -c /home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15 -o video_copy \ -t ti.targets.C64P -p ti.platforms.evmDM6446 \ --tcf video_copy.cfg making package.mak (because of package.bld) ... generating interfaces for package video_copy (because package/package.xdc.xml is older than package.xdc
Re: Build error servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp'
Thank you. I actually did not set the path in 'xdcpath.mak' file. This was the cause of error for dsplink.dsp. XDC_PATH := $(DSPLINK_INSTALL_DIR)/packages;$(XDC_PATH) Many Thanks, Sandeep.Yedire From: Griffis, Brad bgrif...@ti.com To: Sandeep YEDIRE sandee...@yahoo.co.in Cc: bmi...@acmet.com bmi...@acmet.com; Sandeep Yedire sande...@acmet.com; davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Sent: Friday, 12 June, 2009 8:37:08 PM Subject: RE: Build error servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp' In xdcpaths.mak set USE_CETOOLS_IF_EXISTS :=0. From:davinci-linux-open-source-boun...@linux..davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Sandeep YEDIRE Sent: Thursday, June 11, 2009 7:31 AM To: davinci-linux-open-source@linux.davincidsp.com Cc: bmi...@acmet.com; Sandeep Yedire Subject: Build error servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp' Hello Everyone, I am currently working on building codec_engine examples for evmDM6446 target provided along with dvsdk_1_30_01_41 version. Following build instructions in codec_examples folder, I was able to perfrom gmake successfully in folder codecs, extensions. And when I did same in folder servers, I do get the following error. Error message below. I have aslo attached user.bld and xdcpath.mak files to this email. Please let me know what went wrong. -- [sand...@davinci servers]$ gmake clean gmake -C video_copy clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 clean gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' rm -rf video_copy.x64P ti_sdo_ce_examples_servers_video_copy_evmDM6446.tar *.obj package package.* video_copy gmake[2]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C all_codecs clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xdc XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs/../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages \ XDCOPTIONS=v clean -PD . making clean: Thu Jun 11 16:48:51 IST 2009 ... clean [/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs] cleaning complete: Thu Jun 11 16:48:51 IST 2009. gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' [sand...@davinci servers]$ gmake gmake -C video_copy all gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 all gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446/../../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xs xdc.tools.configuro -c /home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15 -o video_copy \ -t ti.targets.C64P -p ti.platforms.evmDM6446 \ --tcf video_copy.cfg making package.mak (because of package.bld) ... generating interfaces for package video_copy (because package/package.xdc.xml is older than package.xdc) ... configuring video_copy.x64P from package/cfg/video_copy_x64P.cfg platform = ti.platforms.evmDM6446 ti.sdo.ce.bioslog.init() ... ti.sdo.ce.examples.codecs.videnc_copy.close() ... ti.sdo.ce.bioslog.close() ... ti.sdo.ce.osal.close() ... js: /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/Main.xs, line 248: exception from uncaught JavaScript throw: Error: xdc.loadPackage: can't find package 'dsplink.dsp' along the path '/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages;/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/sandeep
Build error servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp'
Hello Everyone, I am currently working on building codec_engine examples for evmDM6446 target provided along with dvsdk_1_30_01_41 version. Following build instructions in codec_examples folder, I was able to perfrom gmake successfully in folder codecs, extensions. And when I did same in folder servers, I do get the following error. Error message below. I have aslo attached user.bld and xdcpath.mak files to this email. Please let me know what went wrong. -- [sand...@davinci servers]$ gmake clean gmake -C video_copy clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 clean gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' rm -rf video_copy.x64P ti_sdo_ce_examples_servers_video_copy_evmDM6446.tar *.obj package package.* video_copy gmake[2]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C all_codecs clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xdc XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs/../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages \ XDCOPTIONS=v clean -PD . making clean: Thu Jun 11 16:48:51 IST 2009 ... clean [/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs] cleaning complete: Thu Jun 11 16:48:51 IST 2009. gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/all_codecs' [sand...@davinci servers]$ gmake gmake -C video_copy all gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake -C evmDM6446 all gmake[2]: Entering directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' XDCPATH=/home/sandeep/workdir_4.0..1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446/.../../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/xs xdc.tools.configuro -c /home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15 -o video_copy \ -t ti.targets.C64P -p ti.platforms.evmDM6446 \ --tcf video_copy.cfg making package.mak (because of package.bld) ... generating interfaces for package video_copy (because package/package.xdc.xml is older than package.xdc) ... configuring video_copy.x64P from package/cfg/video_copy_x64P.cfg ... platform = ti.platforms.evmDM6446 ti.sdo.ce.bioslog.init() ... ti.sdo.ce.examples.codecs.videnc_copy.close() ... ti.sdo.ce.bioslog.close() ... ti.sdo..ce.osal.close() ... js: /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/Main.xs, line 248: exception from uncaught JavaScript throw: Error: xdc.loadPackage: can't find package 'dsplink.dsp' along the path '/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08/packages;/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446/video_copy/./...;'; try redefining the package path (XDCPATH). /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/Main.xs, line 154 /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/xs.js, line 144 gmake: *** [package/cfg/video_copy_x64P.c] Error 1 gmake: *** [package/cfg/video_copy_x64P.c] Deleting file `package/cfg/video_copy_x64Pcfg.cmd' gmake: *** [package/cfg/video_copy_x64P.c] Deleting file `package/cfg/video_copy_x64Pcfg_c.c' gmake: *** [package/cfg/video_copy_x64P.c] Deleting file `package/cfg/video_copy_x64Pcfg.s62' gmake[2]: *** [video_copy] Error 2 gmake[2]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy/evmDM6446' gmake[1]: *** [all] Error 2 gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/servers/video_copy' gmake: *** [all] Error 2 [sand...@davinci
Regarding build example on DM6446.
Hello Every one, I am newbie on DM6446 EVM. I am currently working on Codec Engine examples and trying to build it. I have downloaded DVEVM 1_30_01_41 version from ti website. I have gone thru the build instructions.html and modified the two files in the example directory. xdcpaths..mak and user.bld. I have attached these two files. When I do gmake clean in viddec_copy directory, I get this error message I have double checked the path, but i still get error message. -- [sand...@davinci codecs]$ gmake clean gmake -C viddec1_copy clean gmake[1]: Entering directory `/home/sandeep/workdir_4.0.1/ filesys/opt/ce_examples/ti/sdo/ce/examples/codecs/viddec1_copy' /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02 /xdc XDCPATH=/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/codecs/viddec1_copy/../../../../../..;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01 /packages;/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01 /cetools/packages \ XDCOPTIONS=v clean -PD . /bin/sh: /home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02: is a directory gmake[1]: *** [clean] Error 126 gmake[1]: Leaving directory `/home/sandeep/workdir_4.0.1/filesys/opt/ce_examples/ti/sdo/ce/examples/codecs/viddec1_copy' gmake: *** [clean] Error 2 --- Please suggest where I am wrong. Best Wishes, Sandeep.Yedire Many Thanks, Sandeep.Yedire Cricket on your mind? Visit the ultimate cricket website. Enter http://beta.cricket.yahoo.com user.bld Description: Binary data # # xdcpaths.mak # definition of XDC paths and commands # # This makefile constructs the search path for the XDC tools where it finds # numerous components and packages needed to build Codec Engine examples and # programs. # # USER NOTE: # 1) you must specify various component_INSTALL_DIRs directores below to # reflect your installation, where component is CE for Codec Engine, # BIOS for DSP/BIOS, etc. # 2) you can remove some of the devices from the DEVICES list and/or remove # some of the types of binaries from the PROGRAMS list to reduce # the build time (and possibly avoid checking for presence of a component # you don't need) # (Optional) Remove from this list the devices you're not interested in building DEVICES := DM6446 ## DM355 DM6437 DM648 #Removed from list_Jun 10, 2009, Sandeep. # (Optional) Remove from the list the types of programs you're not intersted in # building: # APP_CLIENT -- Arm client for codecs running on the DSP, on dual-CPU systems # DSP_SERVER -- DSP server with the codecs, running on the DSP, on dual-CPUs # APP_LOCAL -- Client+codecs in a single program, whether Arm only or DSP only PROGRAMS := APP_CLIENT #DSP_SERVER APP_LOCAL # (Mandatory) Specify where various components are installed. # What you need depends on what device(s) you're building for, what type(s) of # programs you are building for, and whether your Codec Engine distribution # is a big one that contains all the minor components in its cetools # directory. The legend: # CE - Codec Engine (needed for Arm and for DSP) # XDC - XDC tools (Arm and DSP) # BIOS- DSP/BIOS (DSP only) # XDAIS - XDAIS header files (Arm and DSP) # FC - Framework components, various resource managers (ARM and DSP) # CMEM- Continuous memory manager (Arm only) # DSPLINK - Arm-DSP communication software (Arm + DSP) # # you can ommit directory specifications for the components you think you don't # need (will be warned if you do, based on your DEVICES + PROGRAMS selection # above). CE_INSTALL_DIR:=/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01 XDC_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02 BIOS_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08 # no need to specify the installation directories below if your CE installation # has cetools/ directory on top USE_CETOOLS_IF_EXISTS := 1 XDAIS_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/xdias_6_00_01 DSPLINK_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/dsplink-140-05p1 CMEM_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/cmem_2_00_01 FC_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/framework_components_2_00_01 BIOSUTILS_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/biosutils_1_00_02 # (Mandatory) specify correct compiler paths and names for the architectures # you'll be building for: # compiler path and name for Montavista Arm 9 toolchain. NOTE: make sure the # directory you specify has a bin subdirectory CGTOOLS_MVARM9 =/opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le CC_MVARM9 =bin/arm_v5t_le-gcc # compiler path and name for TI C64x toolchain. NOTE: make sure the # directory you specify has a bin subdirectory CGTOOLS_C64X =/home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15 CC_C64X =bin/cl6x # - # determine which components are necessary based on DEVICES and
