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.

Starting RTSC Packaging tool

Dear Friends!

I'm just on the very beginning of learning the TI products. I have a PC workstation with Ubuntu, DVSDK 2.0 and other necessary software.

I've began with the "OMAP and DaVinci software for dummies" book. Although the book is quite simple and clear, I've already faced the problem. When I'm trying to start the RTSC Packaging tool Wizard, I do all the necessary procedures according to the book, but when I type the "make genpackage" command (according to instructions on page 74) I recieve back the message:

"No rule to make target genpackage"

Then I've tried to do the same opperation using the instructions in http://processors.wiki.ti.com/index.php?title=RTSC_Codec_Package_Wizard_FAQ, but when I enter the command xs ti.sdo.codecutils.genpackage -g I recieve the message

can't locate the package "ti.sdo.codecutils.genpackage" along the path

I've checked the path. There are /ti/sdo/codecutils/genpackage folder chain in CE utils folder, but it doesn't work.

What am I doing wrong?

 

  • When you say that you have "checked the path", what do you mean?  How is your XDCPATH currently set up?

  • "cheked the path" Iäve ment that I've cheked that theese folders are exist.

    My  XDCPATH is set for:

    /home/<username>/dvsdk_2_00_00_22/codec_engine_2_23_01/packages

    /home/<username>/dvsdk_2_00_00_22/xdais_6_23/packages

    home/<username>/dvsdk_2_00_00_22/ceutils_1_06/packages

  • The most likely explanation for xs not finding the package is that the XDCPATH does not contain the repository is it in, or it is represented incorrectly. Is the ceutils path as it appears in the post:

    "home/<username>/dvsdk_2_00_00_22/ceutils_1_06/packages"

    or is it actually:

    "/home/<username>/dvsdk_2_00_00_22/ceutils_1_06/packages"

    If there is no leading forward slash, that may expalin it.

    Joe

  • I've entered XDCPATH correctly, with the forward slash.

    Here is the full reply message for  xs ti.sdo.codecutils.genpackage -g

    js: "./xdc_3_00_02/packages/xdc/xdc.tci", line 270: exception from uncaught JavaScript throw: Error: xdc.loadPackage: can't find package 'ti.sdo.codecutils.genpackage' along the path '/home/mikhail/dvsdk_2_00_00_22/codec_engine_2_23_01/packages; /home/mikhail/dvsdk_2_00_00_22/xdais_6_23/packages; /home/mikhail/dvsdk_2_00_00_22/ceutils_1_06/packages;/home/mikhail/dvsdk_2_00_00_22/xdc_3_00_02/packages;'; try redefining the package path (XDCPATH).
        "./xdc_3_00_02/packages/xdc/xs.js", line 139

  • Can you please list the contents of   /home/mikhail/dvsdk_2_00_00_22/ceutils_1_06/packages?

     

    Joe

  • At last I've succeeded in launching the RTSC Wizard with "make genpackage" command. The xs ti.sdo.codecutils.genpackage -g still does not work. But somehow or other I've started the Wizard. Thank you for your help and attention.

    Now I have another problem. When I try to load the example mycompany_mygroup_codecs_viddec_copy_wizard.xml file into the wizard, it answers:

    The processing instruction target matching "[xX][mM][iL]" is not allowed

    I've asked Google about it, but most of the links say that the problem must be in faulty xml-scripts. I haven't changed the example scripts and don't understand, what does it mean.

  • Mikhail,
    I am not familiar with the wizard you are using, but the error you got is most likely caused by a bug in Rhino (https://bugzilla.mozilla.org/show_bug.cgi?id=336551). You can verify if that bug is a problem by opening mycompany_mygroup_codecs_viddec_copy_wizard.xml in a text editor, and removing the XML header. The header looks like this <?xml version="1.0" encoding="US-ASCII"?>.

    If removing the header helps, it means the wizard calls 'new XML()' somewhere, which can't be done on an XML object with a header.

  • Sasha Slijepcevic said:

    If removing the header helps, it means the wizard calls 'new XML()' somewhere, which can't be done on an XML object with a header.

    Yes, the removing solved the problem. Thank you.