Tconf conversion problem (DSPBIOS to SYSBIOS)

MikeH,
the package 'ti.bios.conversion' is a SYSBIOS package, so you have to have SYSBIOS in your XDCPATH. Depending on where you installed SYSBIOS and which version you are using, your %XDCPATH% should be something similar to C:\Program Files (x86)\TI\bios_6_31_01_19\packages. You don't need XDCtools in your XDCPATH because you get that component of the package path automatically.

Sasha,

Sasha Slijepcevic said:

You don't need XDCtools in your XDCPATH because you get that component of the package path automatically.

I'm not quite sure what you mean by "automatically", but when I change %XDCPATH% to "C:\Program Files (x86)\TI\bios_6_31_01_19\packages" I get the following error msg.

"'xs' is not recognized as an internal or external command, operable program or batch file."

...which implies that the path to "xs" cannot be found. What am I doing wrong?

thx

MikeH

I think you need to make sure that %XDCROOT% is included in your 'Path' environment variable. The xs.exe executable is found at XDCROOT.

Chris

That error message is coming from Windows. As Chris mentioned, you should be adding XDCROOT to your Path variable, not XDCPATH.
Then, you should check that XDCPATH is actually defined in the environment in which you are running xs. The error message in your first post shows that XDCPATH is not being expanded, which indicates that XDCPATH is not being defined.

So, to summarize:
1. add XDCROOT (C:\Program Files (x86)\TI\xdctools_3_16_02_32) to your Path, so that Windows can find xs
2. add C:/Program Files (x86)/TI/bios_6_31_01_19/packages (notice forward slashes) to your XDCPATH, so that xs can find ti.bios.conversion package

OK folks. I am back at it again. I have successfully added "C:/Program Files (x86)/Texas Instruments/bios_6_30_02_42/packages" to my XDCPATH environment variable. My command line now looks like this:

xs -–xp= "%XDCPATH%" ti.bios.conversion –c DSP_prog_config.cfg –-pr C:\myRepository --pn DSP_prog_Platform DSP_progcfg.tcf

However, I am getting cryptic error message:

illegal option -ûxp=

Usage: xs [options] [<script> | <capsule> | <module> | <package>] [args]

Options:

  -h, --help            Print this message and exit

  -v, --version         Print the version and exit

  @opts-file            Read the specified file and include its contents as

                        arguments to xs

  -i                    Run in interactive mode

  --xdcpath PATH, or

  --xdcpath=PATH        Add PATH to the beginning of the package path

  -D<name>=<val>        Add the "name=value" definition to the XDC

                        Script environment

  -g[=<opts>]           use graphical debugger to run script, and

                        optionally pass <opts> to debugger

                        This option must be last in [options].

 

  -m                    Specifies that the next argument is the name of

                        a module. The module must define a main() function.

                        This option must be last in [options].

  -f                    Specifies that the next argument is the name of

                        a script. This option must be last in [options].

  -c                    Specifies that the next argument is the name of

                        a capsule. The module must define a main() function.

                        This option must be last in [options].

 

  If none of the options '-m', '-f', and '-c' is specified,

  the argument given to xs after [options] is assumed to

  be a package name. This package must have a module named

  Main that defines a main() function.

 

Graphical Debugger Options:

  -i                    break at the first line of the startup script

Mike,
it seems that you have two different dashes preceding 'xp' on your command line. The error message is coming from xs, and it says that the character after the first dash is not recognized. Also, there seems to be a whitespace between --xp and "%XDCPATH%" which should not be there. Can you check those two things and see if you get xs running after fixing them?

Sasha,

You are correct. The dashes came from a text copy of a pdf of the spraas7e doc. The whitespace was also in the doc. I left it there because of the comment "(Notice the space after the --xp= option.)". With both fixed I now get the following:

C:\Users\Mike>xs --xp="%XDCPATH%" ti.bios.conversion –c DSP_prog_config.cfg –-pr

 C:\myRepository --pn DSP_prog_Platform DSP_progcfg.tcf

js: "C:/Program Files (x86)/Texas Instruments/bios_6_30_02_42/packages/ti/bios/c

onversion/Main.xs", line 319: Couldn't open file "C:\Users\Mike\?c".

js: "C:/Program Files (x86)/Texas Instruments/bios_6_30_02_42/packages/ti/bios/c

onversion/Main.xs", line 91: Error: ti.bios.conversion: InternalError: Error

What file is it looking for?

Thx,

MikeH

The most likely cause of that error is that the dash in '-c' is also not recognized, and the conversion tool treats the first string that is not an option as the name of the input file. You might have the same problem with --pr and --pn, so make sure that those are also just regular dashes.

Sasha,

I believe I have now fixed the text errors. However, now I get the following error:

 

C:\Users\Mike>xs --xp="%XDCPATH%" ti.bios.conversion -c C:\Users\Mike\TI Workspaces\AMX\DSP_prog\DSP_prog_config.cfg --pr C:\myRepository --pn DSP_prog_Platform DSP_progcfg.tcf

js: "C:/Program Files (x86)/Texas Instruments/bios_6_30_02_42/packages/ti/bios/conversion/Main.xs", line 319: Couldn't open file "C:\Users\Mike\Workspaces\AMX\DSP_prog\DSP_prog_config.cfg".

js: "C:/Program Files (x86)/Texas Instruments/bios_6_30_02_42/packages/ti/bios/conversion/Main.xs", line 91: Error: ti.bios.conversion: InternalError: Error

The file it says it couldn't open (C:\Users\Mike\Workspaces\AMX\DSP_prog\DSP_prog_config.cfg) is the .cfg file I am generating with the conversion.....right? Of course it can't find the file. It hasn't yet been generated.....? Am I not converting a .tcf file to a .cfg file?

MikeH

You are correct, you are converting to a .cfg file. However, the error message still indicates that the file that can't be opened is considered the input file. I think this time the problem is that you have a space in the name of your output file, but the name is not in quotes. Therefore, the actual name of the input file you are passing to the tool is Workspaces\AMX\DSP_prog\DSP_prog_config.cfg.

C:\Users\Mike>xs --xp="%XDCPATH%" ti.bios.conversion -c "C:\Users\Mike\TI Workspaces\AMX\DSP_prog\DSP_prog_config.cfg" --pr C:\myRepository --pn DSP_prog_Platfo

rm DSP_progcfg.tcf

js: "C:/Program Files (x86)/Texas Instruments/bios_6_30_02_42/packages/ti/bios/conversion/Main.xs", line 319: Couldn't open file "C:\Users\Mike\DSP_progcfg.tcf".

js: "C:/Program Files (x86)/Texas Instruments/bios_6_30_02_42/packages/ti/bios/conversion/Main.xs", line 91: Error: ti.bios.conversion: InternalError: Error

Never mind. I added the full path to the input file and the conversion worked.

How hard would it be to create a small GUI program to get rid of all of this archaic command line hassle?????

OK Sasha.....here we go again..... I am now trying to run the mailbox example.

C:\mailbox>xs --xp "C:/Program Files (x86)/Texas Instruments/bios_5_41_07_24/packages" ti.bios.conversion --pr "C:\Users\Mike\TI Workspaces\myRepository" --pn mbx_evmOMAPL138 -i mailbox.tcf

js: "C:/Program Files (x86)/Texas Instruments/xdctools_3_20_03_63/packages/xdc/xdc.tci", line 325: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: can't locate the package 'ti.bios.conversion' along the path: 'C:/Program Files (x86)/Texas Instruments/bios_5_41_07_24/packages;C:\Program Files (x86)\Texas Instruments\xdctools_3_20_03_63/packages;'. Ensure that the package path is set correctly.

MikeH

ARRGGGHHHH!!! Nevermind, I had the wrong bios path.

God I hate this command line crap!

I am attempting to run the mailbox example however my version of bios5 does not have the files required by the directions in the spraas7e, so I downloaded spraas7d. It apparently also does not have one of the files (packages/ti/bios/examples/common/evmDM6437_common.tci). Also, since I do not have the evmDM6437, I changed the names to evmOMAPl138. However, when I attempt to convert these files I get the following error.

C:\mailbox>xs --xp "C:\Program Files (x86)\Texas Instruments\bios_6_30_02_42\packages" ti.bios.conversion --pr "C:\Users\Mike\TI Workspaces\myRepository" --pn mbx_evmOMAPL138 -i "C:\mailbox\mailbox.tcf"

js: "C:/Program Files (x86)/Texas Instruments/bios_6_30_02_42/packages/ti/bios/conversion/Main.xs", line 91: Error: ti.bios.conversion: Error: Can't find import file: 'evmOMAPL138_common.tci' (not found along 'C:\mailbox/;C:\Program Files (x86)\Texas Instruments\bios_6_30_02_42\packages;C:\Program Files (x86)\Texas Instruments\xdctools_3_20_03_63/packages;;C:/Program Files (x86)/Texas Instruments/bios_6_30_02_42/packages/ti/bios/conversion//bios5;C:\Program Files (x86)\Texas Instruments\xdctools_3_20_03_63/include;C:\Program Files (x86)\Texas Instruments\xdctools_3_20_03_63/packages')

Can you give me some guidance on this?

MikeH

Steve,

Thanks. That was the problem. I overlooked the separate folder "common" and just looked in "mailbox". AFter adding the common file the conversion worked.

MikeH

Rizuan,

I would suggest starting a new thread as opposed to continue this thread since your problem is different.

Judah