CCS/TMS320DM648: How to fix xdc.PACKAGE_NOT_FOUND

I mightt be Gmake, rather than Make or Timake!

I found out how to rebuild the packages using

Xdc all

from rtsc.eclipse.org/.../Lesson_5

provided that I'm in a dir with a package.mak

e.g. in C:\dvsdk_1_11_00_00_DM648\examples\video_encdec_fio\evmDM648\xdcconfig>

however, despite appearing to do something, it didnt change the result of a build in CCS. I think I need to understand what XDC is, what packages  are (if they aren't source code or libraries)...

Sorry - that should have read
"provided that I'm in a dir with a package.bld". However, there is no package.bld in any of the ti target dirs, only in the dirs for Arm or Microsoft. My XDCPATH is pointing to C:\Program Files\Texas Instruments\xdctools_3_10_05_61, which I think is correct, but CCS's Build isn't finding the packages & I don't know how to build them.

There is indeed a package_xdcconfig.c in C:\dvsdk_1_11_00_00_DM648\dm648_demo_0_92_04\xdcconfig\package, but I'm non the wiser:

#include <xdc/std.h>
#ifndef __config__
__FAR__ char xdcconfig__dummy__;
#define __xdc_PKGVERS null
#define __xdc_PKGNAME xdcconfig
#define __xdc_PKGPREFIX xdcconfig_
#ifdef __xdc_bld_pkg_c__
#define __stringify(a) #a
#define __local_include(a) __stringify(a)
#include __local_include(__xdc_bld_pkg_c__)
#endif

#else

#endif

Hi,

kenneth Macfarlane said:

My XDCPATH is pointing to C:\Program Files\Texas Instruments\xdctools_3_10_05_61, which I think is correct, but CCS's Build isn't finding the packages

It has been a very long time since I built any packages from this DVSDK, but if memory serves me correctly the XDC tools used above seems too new for this SDK and chances are that it will fail to properly build (as you reported).

The XDC tools provided with the SDK (2.95.xx) should be used by your project, and I think this is set by an environment variable called XDCROOT (or XDC_ROOT).

One incidental detail: Windows UAC causes interference when accessing files in key places in the OS. The directory C:\Program Files is one of them. In this case, I would refrain from installing anything under this directory (we tend to use C:\ti for that). 

Hope this helps,

Rafael

Thanks - I've backed out of xdctools_3_10_05_61 & now I'm back to using C:\dvsdk_1_11_00_00_DM648\xdc_2_95_02 i.e. I've got XDCPATH set to C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02;C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/ti/sdo/ce/osal (having corrected the direction fo \'s !).

I'm getting further now, so I think the version of xdc dopes have to be older e.g. 2_95_02  & now  I can do a command line or IDE build with only one error, which is that xdcconfig can't find ti.sdo.ce.osal - I'm supposed to add the path to that package to the Java null file but I can't figure out what file that is, in a  Windows environment.

Hi,

The ti.sdo.ce.osal refers to the Codec Engine, and I suspect your XDCPATH goes too further into its subdirectory. I suspect the error about the ti.sdo.ce.osal will be corrected if you set your XDCPATH to:
C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02;C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages

Hopefully that will fix this (sorry, I am getting all this from the top of my head)

Regards,
Rafael

Tried that, but unfortunately not. I tried commenting out the ref to ti.blah de blah.osal in

C:\dvsdk_1_11_00_00_DM648\dm648_demo_0_92_04\dm648_demo.cfg

but that just changed which package it complained about: 

configuring dm648_demo.x64P from package/cfg/dm648_demo_x64P.cfg ...

js: "C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02/packages/xdc/xdc.tci", line 254: exception from uncaught JavaScript throw: Error: xdc.loadPackage: can't find package 'ti.bios.utils' along the path 'C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02;C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02/packages;C:/dvsdk_1_11_00_00_DM648/dm648_demo_0_92_04;C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02/packages;C:/dvsdk_1_11_00_00_DM648/dm648_demo_0_92_04/xdcconfig/./..;'; try redefining the package path (XDCPATH).

What does the output mean - that xs parses its way thorugh all of the .tci & main.xs files? So why does it make explicit mention of certain lines? 

I've tried redefining the package path (XDCPATH)  - it seems to be appended to on the fly c/w what's in C:\dvsdk_1_11_00_00_DM648\xdcpaths_evmDM648.dat  which is pointed to by the demo's 

C:\dvsdk_1_11_00_00_DM648\dm648_demo_0_92_04\xdcpaths.dat

I guess that the demo used to build correctly with the previous version of the VideoSDK and XS.exe isn't now searching the path quite like it used to. 

 

Find "ti.sdo.ce.osal" *.* , from the DVSDK root,

(I think!) proves that I do have the packages:

---------- .INSTALLINFO
Ver C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/ti/sdo/ce/osal/package/ti.sdo.ce.osal.sch 6.00.00.02
Ver C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/ti/sdo/ce/osal/alg/package/package_ti.sdo.ce.osal.alg.c 6.00.00.02
Ver C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/ti/sdo/ce/osal/alg/package/ti.sdo.ce.osal.alg.ccs101 6.00.00.02
Ver C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/ti/sdo/ce/osal/package/package_ti.sdo.ce.osal.c 6.00.00.02
Ver C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/ti/sdo/ce/osal/package/ti.sdo.ce.osal.ccs101 6.00.00.02
Ver C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/ti/sdo/ce/osal/alg/package/ti.sdo.ce.osal.alg.sch 6.00.00.02

but putting C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages into the XDCPATH isn't being picked up.

In other environments, Osal stands for Operating system abstraction layer - is that what it means here?

I got the original problem to disappear by searching the directory structure for all of the packages then defining XDCPATH to mathc that i.e.:

the packages are :

+---biosutils_1_00_02
| \---packages

+---codec_engine_1_20_02
| \---packages

+---edma3_lld_1_05_00

+---framework_components_1_20_03
| +---fctools
| | \---packages

+---ndk_1_92_00_22_eval
| \---packages

+---pspdrivers_1_10_00
| \---packages

+---xdais_5_21
| \---packages

\---xdc_2_95_02

so I set XDCPATH to 
C:/dvsdk_1_11_00_00_DM648/biosutils_1_00_02/packages/;
C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/;
C:/dvsdk_1_11_00_00_DM648/edma3_lld_1_05_00/;
C:/dvsdk_1_11_00_00_DM648/framework_components_1_20_03/;
C:/dvsdk_1_11_00_00_DM648/framework_components_1_20_03/fctools/;
C:/dvsdk_1_11_00_00_DM648/ndk_1_92_00_22_eval/;
C:/dvsdk_1_11_00_00_DM648/pspdrivers_1_10_00/;
C:/dvsdk_1_11_00_00_DM648/xdais_5_21/;
C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02;

or strictly (all in one 1259 character long string!):

C:/dvsdk_1_11_00_00_DM648/biosutils_1_00_02/packages/;C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/;C:/dvsdk_1_11_00_00_DM648/edma3_lld_1_05_00/;C:/dvsdk_1_11_00_00_DM648/framework_components_1_20_03/;C:/dvsdk_1_11_00_00_DM648/framework_components_1_20_03/fctools/;C:/dvsdk_1_11_00_00_DM648/ndk_1_92_00_22_eval/;C:/dvsdk_1_11_00_00_DM648/pspdrivers_1_10_00/;C:/dvsdk_1_11_00_00_DM648/xdais_5_21/;C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02;

I'm still getting one error, with ti.bios:

js: "C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02/packages/xdc/xdc.tci", line 254: exception from uncaught JavaScript throw: Error: xdc.loadPackage: can't find package 'ti.bios' along the path 'C:/dvsdk_1_11_00_00_DM648/biosutils_1_00_02/packages;C:/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages;C:/dvsdk_1_11_00_00_DM648/edma3_lld_1_05_00;C:/dvsdk_1_11_00_00_DM648/framework_components_1_20_03;C:/dvsdk_1_11_00_00_DM648/framework_components_1_20_03/fctools;C:/dvsdk_1_11_00_00_DM648/ndk_1_92_00_22_eval;C:/dvsdk_1_11_00_00_DM648/pspdrivers_1_10_00;C:/dvsdk_1_11_00_00_DM648/xdais_5_21;C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02;C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02/packages;C:/dvsdk_1_11_00_00_DM648/dm648_demo_0_92_04;C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02/packages;C:/dvsdk_1_11_00_00_DM648/dm648_demo_0_92_04/xdcconfig/./..;'; try redefining the package path (XDCPATH).

this seems to be a red herring, because there is no overarching ti.bois package. Still..baby steps!

the path mod worked, to the extent that it allows the examples to build (e.g. video encdec), although not the dm648_demo, thanks, desouza!

Hi,

Thanks for reporting your progress and please apologize for disappearing; I am in the middle of an office move and things are a bit backed up.

The package ti.bios refers to the DSP/BIOS version used by the demo - its release notes mention this package was tested with DSP/BIOS 5.31.08, which can be downloaded from the link below.
software-dl.ti.com/.../index.html

Thus you can add the path to the package similarly to what you have done before.

Hope this helps,
Rafael

Thanks for getting back to me.  

Re

Unfortunately, I've already added in the path for the package ti.bios  i.e.

/dvsdk_1_11_00_00_DM648/biosutils_1_00_02/packages/;

Dos's tree when run in the DVSDK dir reports:

Folder PATH listing for volume OS

Volume serial number is 005F0030 565D:4FC1

C:.

+---ais_utility

|   \---essBoot

+---biosutils_1_00_02

|   +---doc

|   \---packages

|       +---ti

|       |   \---bios

|       |       +---log

|       |       |   +---ndk

|       |       |   |   +---examples

|       |       |   |   |   +---common

|       |       |   |   |   +---evmdm642

|       |       |   |   |   +---evmdm6437

|       |       |   |   |   \---package

|       |       |   |   +---lib

|       |       |   |   \---package

|       |       |   \---support

|       |       |       +---lib

|       |       |       \---package

|       |       +---rtadecode

|       |       |   +---bin

|       |       |   \---package

|       |       \---utils

|       |           +---lib

|       |           \---package

|       \---xdoc

|           \---ti

|               +---bios

|               |   +---log

|               |   |   +---ndk

|               |   |   |   \---examples

|               |   |   \---support

|               |   \---utils

|               |       \---test

|               +---psl

|               \---rtdx

but  there's no .sch file called ti.bios - they are all ti.bios.something e.g. ti.bios.utils.sch  - this is different from all of the other packages & the paths to them.

I've got v5.31.08 - that's the most recent version that still works with CCSv3.3

There's a ti.bios in
C:\ti\ccsv5_5\bios_6_35_04_50\packages\ti\bios\package - can I mix & match versions?

That helped a bit - it seems that I can mix versions:

After browsing www.ti.com/.../spruex4.pdf

the ti.bios error was fixed by adding C:\ti\ccsv5_5\bios_6_35_04_50\packages to –xdcpath in xdc tab (quicker than PATH – no CCS restart needed –

making package.mak (because of .xdcenv.mak) ...

configuring dm648_demo.x64P from package/cfg/dm648_demo_x64P.cfg ...

"ti/sysbios/heaps/HeapMem.xdc", line 39:  can't find imported unit: xdc.rov.ViewInfo (xdc.rov.ViewInfo)

so I  add C:\ti\xdctools_3_50_01_12_core\packages

but now I've got a different kind of error:

making package.mak (because of .xdcenv.mak) ...
js: "C:/ti/xdctools_3_50_01_12_core/packages/xdc/xdc.tci", line 74: exception from uncaught JavaScript throw: TypeError: Env is not a function, it is org.mozilla.javascript.NativeJavaPackage. (C:/ti/xdctools_3_50_01_12_core/packages/xdc/xdc.tci#74)
"C:/dvsdk_1_11_00_00_DM648/xdc_2_95_02/include/utils.tci", line 566

Any .tci file experts out there?

Sounds like there's something wrong with my .tcf file, as e2e.ti.com/.../255553 says not to fiddle with the .tci as its a generated file.

I'm back on this, building the DM6437_demo project. Is there any way to get xdc to tell me all of the offending packages in one go? I'm currently playing "whackamole" i.e. hit one on the head & another one pops up.

This discussion seems to be continued here:
e2e.ti.com/.../2185316