incompatible use of package 'ti.rtdx' when upgraded to a new BIOS 5.33.06 from BIOS 5_31_08

Ja Maitan

Other Parts Discussed in Thread: CCSTUDIO

I am trying to upgrade the CCS to BIOS 5_33_06 and can not rebuild demo application. It fails when I am rebuilding dm6437_demo.cfg

"C:\dvsdk_1_11_00_00\xdc_2_95_02\xs.exe" xdc.tools.configuro.ccs --xdcpathsfile="xdcpaths.dat" -pti.platforms.evmDM6437 -rdebug --tcf -t ti.targets.C64P -c "C:/CCStudio_v3.3/C6000/cgtools" --bios "C:/CCStudio_v3.3/bios_5_33_06" -o "xdcconfig" dm6437_demo.cfg

Info: running XDC configuration using package path:
C:\dvsdk_1_11_00_00\codec_engine_1_20_02\packages
C:\dvsdk_1_11_00_00\codec_engine_1_20_02\examples
C:\dvsdk_1_11_00_00\framework_components_1_20_03\packages
C:\dvsdk_1_11_00_00\xdais_5_21\packages
C:\dvsdk_1_11_00_00\codecs_1_10\packages
C:\dvsdk_1_11_00_00\ndk_1_92_00_22_eval\packages
C:\dvsdk_1_11_00_00\biosutils_1_00_02\packages
C:\dvsdk_1_11_00_00\pspdrivers_1_10_00\packages
C:\dvsdk_1_11_00_00\edma3_lld_1_05_00\packages
C:\dvsdk_1_11_00_00\examples\common\evmDM6437
C:\CCStudio_v3.3\bios_5_33_06\packages
C:\dvsdk_1_11_00_00\xdc_2_95_02\packages

The configuration step is now running:

configuring dm6437_demo.x64P from package/cfg/dm6437_demo_x64P.cfg ...
ti.sdo.ce.osal.close() ...
ti.sdo.ce.osal.validate() ...
js: "C:/dvsdk_1_11_00_00/xdc_2_95_02/packages/xdc/cfg/Main.xs", line 170: exception from uncaught JavaScript throw: Error: incompatible use of package 'ti.rtdx': imported ti.rtdx [2,0,0,4,0], ti.bios.utils was built with ti.rtdx [], ti.bios.log.support was built with ti.rtdx [], ti.bios.log.ndk was built with ti.rtdx []; incompatible use of package 'xdc.bld': imported xdc.bld [1,0,0,0,1183011756898], ti.pmi was built with xdc.bld [1, 0, 1], ti.bios was built with xdc.bld [1, 0, 1]; incompatible use of package 'xdc': imported xdc [1,1,0,0,1183011749422], ti.rtdx was built with xdc [1, 1, 1, 0], ti.pmi was built with xdc [1, 1, 1, 0], ti.bios was built with xdc [1, 1, 1, 0]
Adding the following line to your configuration script:
environment['xdc.cfg.check.fatal'] = 'false';
converts this incompatibility error into a warning. Please, check the documentation for the package xdc.cfg for more information.
"C:/dvsdk_1_11_00_00/xdc_2_95_02/packages/xdc/xs.js", line 137
xdc_2_95_02\gmake.exe: *** [package/cfg/dm6437_demo_x64P.c] Error 1

I have found that similar question was asked in the past

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/99/p/6723/25751.aspx#25751

Any suggestions?

over 15 years ago

0 David Friedland over 15 years ago

TI__Mastermind 18320 points

Ja,

It appears that you are using the DVSDK and are trying to update just one part of it to a newer version. That is not recommended. When a version of the DVSDK is released, it means that all of the components included in that release have been tested together to make sure they are compatible. Just because one of the components released a newer version as a stand-alone does not mean that it will automatically work with an older set of DVSDK components. In reality, the work of getting this BIOS upgrade to work may not be all that bad, but nobody has done it and you would be doing this by yourself. You can certainly try adding the line to your configuration script that the error message suggested in order to see what happens. But a much better route would be to use the version of components that were included in a DVSDK release -- that is actually the whole reason for the DVSDK's existence.

It also appears that you are using an older DVSDK release. Not sure what platform you're running on, but if you want to upgrade your components, you should check to see if a newer DVSDK release is available for your platform.

Dave

0 Ja Maitan over 15 years ago in reply to David Friedland

Prodigy 70 points

Dave,

Thank you for the response.

You may are perfectly right and I would certainly like to download a proper and newest DVSDK and save myself work, but I could not find a DVSDK for 6437 which matches TI's requirements listed for h264 codec for 6437 in the user guide for this decoder document SPRUEA1C:

This version of the codec has been validated with DSP/BIOS version 5.32.02 and
Framework Component (FC) version 2.20.00.15.

Where can I find a newest and working dvSDK with proper tools? The one list on the web site had bugs so I was not sure whether it was properly tested.

0 Ja Maitan over 15 years ago in reply to David Friedland

Prodigy 70 points

Dave,

Thank you for the response.

This version of the codec has been validated with DSP/BIOS version 5.32.02 and
Framework Component (FC) version 2.20.00.15.

Where can I find a newest and working dvSDK with proper tools? The one list on the web site had bugs so I was not sure whether it was properly tested.

0 David Friedland over 15 years ago in reply to Ja Maitan

TI__Mastermind 18320 points

It doesn't appear that there has been a specific update to the DM6437 DVDP product.

You may very well be able to get past this problem by following the advice of the error message:

Adding the following line to your configuration script:
environment['xdc.cfg.check.fatal'] = 'false';

Have you tried that yet?

0 David Friedland over 15 years ago in reply to David Friedland

TI__Mastermind 18320 points

BTW, I have also asked someone from the codecs team to take a look at this issue to see if they can provide better advice. They are located in India, so there will be a bit of a lag in responding.

0 David Friedland over 15 years ago in reply to David Friedland

TI__Mastermind 18320 points

I asked the codec developers (in this case, a 3rd party) to provide more detailed versioning information for this codec:

Newer version of H264 decoder with version “2_00_002” can be used and it has been verified on DM6446 but not on DM6437.

Please find the in lined answers to the following queries:

- What version of the codec should they be using?

H264 decoder with version “2_00_002”

- What version of BIOS, CE, FC, XDC, etc should they be using?

The following versions have been used during the verification,

BIOS: 5.32.02

CE : 2_00_01

FC : 2.20.00.15

XDC: 3_00_06

- Was that version of the codec validated against a particular DVSDK? Which one (perhaps they should use that)?

The codec is verified using the DVSDK version “1_30_01_41.

0 jacek maitan over 15 years ago in reply to David Friedland

Intellectual 415 points

David,

Thanks for the reply. We were able to run the codec using a small Client app that comes with the h264 decoder. It solved one of our problems.

I have posted some other problems when I tried to upgrade standard TI demo project (see http://e2e.ti.com/support/embedded/f/354/p/40413/142396.aspx#142396 ) to run with the same codec.

It seems that Configuro has problems with .cfg files or other configuration files. If you have a chance pls check the link and I would appreciate your comments.

Thanks,