Home » Archived » DSDP - Real-Time Software Components (RTSC) » Problem with RTSC module primer lesson 5
| | | | | | | |
Re: Problem with RTSC module primer lesson 5 [message #707353 is a reply to message #685176] |
Mon, 01 August 2011 14:44 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
linkinsebas![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=linkinsebas%40gmail.com) Messages: 22 Registered: April 2011 |
Junior Member |
|
|
Sorry for taking too long, I've been a little busy.
I recently upgraded to xdctools 3.22.01.21, and I am still having the same problem. I do not have access to the 32-bit computer anymore, so I used instead my own Windows 7's XP-mode virtual PC. It turns out that lesson 5 runs successfully in XP mode (at least for p64P target).
File "prog_p64P.dep" in both cases have the following lines:
Windows 7 64-bit
define EXEC.prog.x64P
'C:/Program Files (x86)/Texas Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin' -quiet -mem_ignore 'D:\examples\lesson5\prog.x64P'
endef
XP-Mode
define EXEC.prog.x64P
'C:/Program Files/Texas Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin' -quiet -mem_ignore 'C:\examples\lesson5\prog.x64P'
endef
It seems to me that xdc (or whatever is executed in the background) cannot process "(" or ")" in a filename. And since the default path in a x64 PC for non-64-bit applications is "Program Files (x86)", this problem only occurs in my 64-bit Windows 7. I hope you can correct this issue in a future release, and if you have a quick solution, please let me know.
I have another problem. Now lesson 1 does not run. Everything seems fine when I run "gmake all", but when I run "gmake test", the following appears:
C:/Progra~2/TexasI~1/xdctools_3_22_01_21/xs xdc.tools.loader prog.out
Cannot find 'C:/Program along the path [D:\examples\lesson1\., C:\Progra~2\Texas
I~1\xdctools_3_22_01_21, C:\Program Files (x86)\Texas Instruments\xdctools_3_22_
01_21, C:\Program Files (x86)\Microchip\mplabc30\v3.25\bin, C:\watcom-1.3\binnt,
C:\watcom-1.3\binw, C:\Program Files\Common Files\Microsoft Shared\Windows Live
, C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live, C:\Program
Files (x86)\ATI Stream\bin\x86_64, C:\Program Files (x86)\ATI Stream\bin\x86, C:
\Windows\system32, C:\Windows, C:\Windows\System32\Wbem, C:\Windows\System32\Win
dowsPowerShell\v1.0, C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static
, C:\Program Files (x86)\Windows Live\Shared, C:\Program Files (x86)\Microchip\M
PLAB C32 Suite\bin, C:\Program Files\MATLAB\R2010b\runtime\win64, C:\Program Fil
es\MATLAB\R2010b\bin, C:\Program Files (x86)\Common Files\Acronis\SnapAPI, C:\Pr
ogram Files (x86)\Microsoft SQL Server\100\Tools\Binn, C:\Program Files\Microsof
t SQL Server\100\Tools\Binn, C:\Program Files\Microsoft SQL Server\100\DTS\Binn,
C:\Program Files\Microsoft Windows Performance Toolkit, C:\Program Files (x86)\
Texas Instruments\xdctools_3_22_01_21]
It looks like an issue with the space in the "Program Files" name. I tried changing the pathnames in "common.mak" and "config.bld" for their 8.3 versions, and still got the same result. It looks like a bug with the 3.22.01 version, since the correct result is shown if I run:
D:\examples\lesson1>C:/Progra~2/TexasI~1/xdctools_3_20_08_88/xs xdc.tools.loader
prog.out
Hello World
The behavior is the same in the XP-mode PC. What can I do?
Thanks in advance for your help.
|
|
|
Re: Problem with RTSC module primer lesson 5 [message #708580 is a reply to message #707353] |
Wed, 03 August 2011 00:20 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Dave Russo![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=d-russo%40ti.com) Messages: 172 Registered: July 2009 |
Senior Member |
|
|
As you guessed, spaces and '()' characters in files names cause quite a
problem for GNU make (the underlying tool used by xdc).
In some cases we are convert these files to 8.3 names, in other cases we
are able to quote the spaces but, in the end, problems are always
possible because at it's core GNU make simply does not support file
names with special characters in them.
The best answer is to install XDCtools in a directory _without_ spaces
or '()' characters. If this is not possible, you may be able to
"manually" override offending paths with their 8.3 equivalents.
For example, in your example below, you can get the 8.3 equivalent name
for "C:/Program Files (x86)/Texas
Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin"
and use this to define the command used to run the test via
Program.execCmd; see
http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/cfg/Program.html#exec.Cmd.
For what it's worth, running xdc with XDCOPTIONS=v often help diagnose
these problems; xdc will display _exactly_ what it's trying to execute.
xdc XDCOPTIONS=v ...
On 8/1/2011 7:44 AM, linkinsebas wrote:
> Sorry for taking too long, I've been a little busy.
>
> I recently upgraded to xdctools 3.22.01.21, and I am still having the
> same problem. I do not have access to the 32-bit computer anymore, so I
> used instead my own Windows 7's XP-mode virtual PC. It turns out that
> lesson 5 runs successfully in XP mode (at least for p64P target).
> File "prog_p64P.dep" in both cases have the following lines:
>
> Windows 7 64-bit
> define EXEC.prog.x64P
>
> 'C:/Program Files (x86)/Texas
> Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin'
> -quiet -mem_ignore 'D:\examples\lesson5\prog.x64P'
> endef
>
> XP-Mode
>
> define EXEC.prog.x64P
>
> 'C:/Program Files/Texas
> Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin'
> -quiet -mem_ignore 'C:\examples\lesson5\prog.x64P'
> endef
>
> It seems to me that xdc (or whatever is executed in the background)
> cannot process "(" or ")" in a filename. And since the default path in a
> x64 PC for non-64-bit applications is "Program Files (x86)", this
> problem only occurs in my 64-bit Windows 7. I hope you can correct this
> issue in a future release, and if you have a quick solution, please let
> me know.
>
> I have another problem. Now lesson 1 does not run. Everything seems fine
> when I run "gmake all", but when I run "gmake test", the following appears:
> C:/Progra~2/TexasI~1/xdctools_3_22_01_21/xs xdc.tools.loader prog.out
> Cannot find 'C:/Program along the path [D:\examples\lesson1\.,
> C:\Progra~2\Texas
> I~1\xdctools_3_22_01_21, C:\Program Files (x86)\Texas
> Instruments\xdctools_3_22_
> 01_21, C:\Program Files (x86)\Microchip\mplabc30\v3.25\bin,
> C:\watcom-1.3\binnt,
> C:\watcom-1.3\binw, C:\Program Files\Common Files\Microsoft
> Shared\Windows Live
> , C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live,
> C:\Program
> Files (x86)\ATI Stream\bin\x86_64, C:\Program Files (x86)\ATI
> Stream\bin\x86, C:
> \Windows\system32, C:\Windows, C:\Windows\System32\Wbem,
> C:\Windows\System32\Win
> dowsPowerShell\v1.0, C:\Program Files (x86)\ATI
> Technologies\ATI.ACE\Core-Static
> , C:\Program Files (x86)\Windows Live\Shared, C:\Program Files
> (x86)\Microchip\M
> PLAB C32 Suite\bin, C:\Program Files\MATLAB\R2010b\runtime\win64,
> C:\Program Fil
> es\MATLAB\R2010b\bin, C:\Program Files (x86)\Common
> Files\Acronis\SnapAPI, C:\Pr
> ogram Files (x86)\Microsoft SQL Server\100\Tools\Binn, C:\Program
> Files\Microsof
> t SQL Server\100\Tools\Binn, C:\Program Files\Microsoft SQL
> Server\100\DTS\Binn,
> C:\Program Files\Microsoft Windows Performance Toolkit, C:\Program Files
> (x86)\
> Texas Instruments\xdctools_3_22_01_21]
> It looks like an issue with the space in the "Program Files" name. I
> tried changing the pathnames in "common.mak" and "config.bld" for their
> 8.3 versions, and still got the same result. It looks like a bug with
> the 3.22.01 version, since the correct result is shown if I run:
> D:\examples\lesson1>C:/Progra~2/TexasI~1/xdctools_3_20_08_88/xs
> xdc.tools.loader
> prog.out
> Hello World
> The behavior is the same in the XP-mode PC. What can I do?
>
> Thanks in advance for your help.
|
|
|
Re: Problem with RTSC module primer lesson 5 [message #714964 is a reply to message #708580] |
Thu, 11 August 2011 22:34 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
linkinsebas![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=linkinsebas%40gmail.com) Messages: 22 Registered: April 2011 |
Junior Member |
|
|
I have reinstalled all to C:\TI, so the new path to xdctools is C:/TI/xdctools_3_22_01_21. Lesson 5 seems to work now for target 64P:
D:\examples\lesson5>xdc all
making package.mak (because of package.bld) ...
gnu.targets.Mingw: warning: exec of 'C:/MinGW/mingw32/bin/ld -v' failed:; check
tools installation
gnu.targets.Mingw: warning: can't determine binutils version;
Check if C:/MinGW/bin/ld can run on
Windows.
Also, try explicitly setting the BINVERS configuration parameter.
generating interfaces for package lesson5 (because package/package.xdc.inc is ol
der than package.xdc) ...
configuring prog.p64P from package/cfg/prog_p64P.cfg ...
cl64P package/cfg/prog_p64P.c ...
configuring prog.p86GW from package/cfg/prog_p86GW.cfg ...
cl86GW package/cfg/prog_p86GW.c ...
cl64P prog.c ...
lnk64P prog.x64P ...
cl86GW prog.c ...
lnk86GW prog.x86GW ...
all files complete.
D:\examples\lesson5>xdc test,64P
running prog.x64P ...
Hello World
However, target 86GW still has problems:
D:\examples\lesson5>xdc test,86GW
running prog.x86GW ...
A window appears here saying that "The program can't start because libstdc++-6.dll is missing from your computer. Try reinstalling the program to fix this problem.". After I close the window, the following additional output appears:
gmake.exe[1]: *** [prog.x86GW.test] Error -1073741515
xdctools_3_22_01_21\gmake.exe: *** [prog.x86GW.test] Error 2
In addition, lesson 1 still does not work.
D:\examples\lesson1>gmake all
C:/TI/xdctools_3_22_01_21/xs xdc.tools.configuro -c C:/TI/ccsv4/tools/compiler/c
6000 -t ti.targets.C64P -p ti.platforms.sim64Pxx -o cfgsite prog.cfg
making package.mak (because of package.bld) ...
generating interfaces for package cfgsite (because package/package.xdc.inc is ol
der than package.xdc) ...
configuring prog.p64P from package/cfg/prog_p64P.cfg ...
cl64P package/cfg/prog_p64P.c ...
C:/TI/ccsv4/tools/compiler/c6000/bin/cl6x -q -@cfgsite/compiler.opt -c prog.c
C:/TI/ccsv4/tools/compiler/c6000/bin/cl6x -q -z -c prog.obj cfgsite/linker.cmd -
o prog.out -l C:/TI/ccsv4/tools/compiler/c6000/lib/rts64plus.lib
D:\examples\lesson1>gmake test
C:/TI/xdctools_3_22_01_21/xs xdc.tools.loader prog.out
Cannot find 'C:/TI/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/ke
lvin' along the path [D:\examples\lesson1\., C:\TI\xdctools_3_22_01_21, C:\TI\xd
ctools_3_22_01_21, C:\Program Files (x86)\Microchip\mplabc30\v3.25\bin, C:\watco
m-1.3\binnt, C:\watcom-1.3\binw, C:\Program Files\Common Files\Microsoft Shared\
Windows Live, C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live,
C:\Program Files (x86)\ATI Stream\bin\x86_64, C:\Program Files (x86)\ATI Stream
\bin\x86, C:\Windows\system32, C:\Windows, C:\Windows\System32\Wbem, C:\Windows\
System32\WindowsPowerShell\v1.0, C:\Program Files (x86)\ATI Technologies\ATI.ACE
\Core-Static, C:\Program Files (x86)\Windows Live\Shared, C:\Program Files (x86)
\Microchip\MPLAB C32 Suite\bin, C:\Program Files\MATLAB\R2010b\runtime\win64, C:
\Program Files\MATLAB\R2010b\bin, C:\Program Files (x86)\Common Files\Acronis\Sn
apAPI, C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn, C:\Program Fi
les\Microsoft SQL Server\100\Tools\Binn, C:\Program Files\Microsoft SQL Server\1
00\DTS\Binn, C:\Program Files\Microsoft Windows Performance Toolkit, C:\TI\xdcto
ols_3_22_01_21]
D:\examples\lesson1>
File C:\TI\xdctools_3_22_01_21\packages\ti\platforms\sim64Pxx\Windows\kelvin DOES exist, I can even run it manually and it works:
D:\examples\lesson1>C:\TI\xdctools_3_22_01_21\packages\ti\platforms\sim64Pxx\Win
dows\kelvin prog.out
20110811-17:25:27: C:\TI\xdctools_3_22_01_21\packages\ti\platforms\sim64Pxx\Wind
ows\kelvin prog.out
simulating Joule ISA
Hello World
Simulation done:
(lots of numbers and statistics...)
This has nothing to do with spaces in pathnames, since I am not using them anymore, and because 'gmake test' works perfectly fine with version 3.20.08.88 even when I use xdctools in "C:/Program Files/Texas Instruments.....", so this looks like a bug that should be fixed.
Finally, a suggestion: if spaces in pathnames give so much trouble, xdctools should not have as the default installation path one that has spaces in it.
Well, in summary: lesson1 is now giving trouble, and the original problem with lesson5 was "solved" for target 64P, but I could still use some help for target 86GW. Any help will be appreciated. Thanks in advance.
|
|
|
Re: Problem with RTSC module primer lesson 5 [message #714972 is a reply to message #714964] |
Thu, 11 August 2011 23:10 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Dave Russo![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=d-russo%40ti.com) Messages: 172 Registered: July 2009 |
Senior Member |
|
|
On 8/11/2011 3:34 PM, linkinsebas wrote:
> I have reinstalled all to C:\TI, so the new path to xdctools is
> C:/TI/xdctools_3_22_01_21. Lesson 5 seems to work now for target 64P:
>
>
Excellent!
>
>
> However, target 86GW still has problems:
> D:\examples\lesson5>xdc test,86GW
> running prog.x86GW ...
> A window appears here saying that "The program can't start because
> libstdc++-6.dll is missing from your computer. Try reinstalling the
> program to fix this problem.". After I close the window, the following
> additional output appears:
> gmake.exe: *** [prog.x86GW.test] Error -1073741515
> xdctools_3_22_01_21\gmake.exe: *** [prog.x86GW.test] Error 2
>
Hummmm. This looks like a mingw installation/path issue.
libstdc++-6.dll looks like a mingw dll that gcc is trying to use. If
this DLL is not in the installation you may have to use the
"-static-libstdc++" switch for the linker to avoid this message.
> In addition, lesson 1 still does not work.
> D:\examples\lesson1>gmake test
> C:/TI/xdctools_3_22_01_21/xs xdc.tools.loader prog.out
> Cannot find
> 'C:/TI/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/ke
> lvin' along the path [D:\examples\lesson1\., C:\TI\xdctools_3_22_01_21,
> C:\TI\xd
> ctools_3_22_01_21, C:\Program Files (x86)\Microchip\mplabc30\v3.25\bin,
This is a bug in the sim64Pxx platform package on Windows.
>
> Finally, a suggestion: if spaces in pathnames give so much trouble,
> xdctools should not have as the default installation path one that has
> spaces in it.
>
We were forced to make the default installation the "Windows standard"
which is quite unfriendly to programmers accustomed to make-based
command line tools.
> Well, in summary: lesson1 is now giving trouble, and the original
> problem with lesson5 was "solved" for target 64P, but I could still use
> some help for target 86GW. Any help will be appreciated. Thanks in advance.
|
|
| |
Re: Problem with RTSC module primer lesson 5 [message #715173 is a reply to message #714996] |
Fri, 12 August 2011 14:56 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Dave Russo![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=d-russo%40ti.com) Messages: 172 Registered: July 2009 |
Senior Member |
|
|
On 8/11/2011 7:50 PM, linkinsebas wrote:
> Where do I have to put this "-static-libstdc++"?
> I discovered that the solicited files are in "C:\MinGW\bin" and
> "C:\MinGW\mingw32\bin", so I tried adding them to the path, and at least
> "xdc all" does not display any error message:
In this case, you don't need to add "-static-libstdc++". Using this
option causes the mingw compiler to statically link in the C standard
library (which makes your executable bigger) but also has the effect of
avoiding the need to load the "missing" DLLs.
> However, "xdc test" still does not work:
> D:\examples\lesson5>xdc test,86GW
> running prog.x86GW ...
> process_begin: CreateProcess(D:\examples\lesson5\prog.x86GW,
> ./prog.x86GW, ...)
> failed.
> make (e=193): Error 193
> gmake.exe[1]: *** [prog.x86GW.test] Error 193
> xdctools_3_22_01_21\gmake.exe: *** [prog.x86GW.test] Error 2
>
Hummm. Are you able to run prog.x86GW directly from the command line?
If so, the problem is in how the generated makefile is running the
executable. If not, there is a problem in the build of the executable.
Can you post the output when you run "xdc XDCOPTIONS=v test,86GW"? This
will display _exactly_ what the makefile is running.
> As for the bug with sim64Pxx, do you have any idea about when it will
> get fixed? Is there something I can do in the meantime?
Yes. Sasha is looking at the issue now and will post a patch to the
platform. It looks like a "simple" (but subtle) quoting problem when
the platform constructs the command to run.
If you're feeling adventurous, take a look at the file
ti/platforms/sim64Pxx/Platform.xs. The following line constructs the
command line used to run the executable.
command = "'" + packagePath + os + "/kelvin' -quiet -mem_ignore '"
+ java.io.File(prog.name).getAbsolutePath() + "'";
This probably needs to be changed to eliminate the "'" characters
surrounding the command. Something like the following _might_ work:
command = packagePath + os + "/kelvin -quiet -mem_ignore '"
+ java.io.File(prog.name).getAbsolutePath() + "'";
|
|
| | |
Re: Problem with RTSC module primer lesson 5 [message #715930 is a reply to message #715284] |
Tue, 16 August 2011 02:38 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Sasha Slijepcevic![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=sascha%40ti.com) Messages: 115 Registered: July 2009 |
Senior Member |
|
|
The problem with lesson5 is caused by a mismatch between the content of the linker command script package/cfg/prog_p86GW.xdl and the option -T passed for it.
The linker command line for MinGW in XDCtools 3.22.01 is:
D:/MinGW/bin/mingw32-gcc.exe -Wl,--gc-sections -o prog.x86GW package/cfg/prog_p86GW.o86GW package/cfg/prog/prog.o86GW -Wl,-T,package/cfg/prog_p86GW.xdl -Wl,-Map=package/cfg//prog.x86GW.map -lstdc++ -LD:/MinGW/lib
The option -T should not preceed that file, and the correct command line is:
D:/MinGW/bin/mingw32-gcc.exe -Wl,--gc-sections -o prog.x86GW package/cfg/prog_p86GW.o86GW package/cfg/prog/prog.o86GW package/cfg/prog_p86GW.xdl -Wl,-Map=package/cfg//prog.x86GW.map -lstdc++ -LD:/MinGW/lib
The workaround requires editing a file ITarget.xs, in xdctools_3_22_01_21/packages/gnu/targets. The line 90
if (target.BINVERS >= "2.19") {
should be replaced with
if (target.BINVERS >= "2.19" && target.$name != "gnu.targets.Mingw") {
Once you fix that, you'll be able to run from the command line by simply typing
prog.x86GW
[Updated on: Tue, 16 August 2011 02:39] Report message to a moderator
|
|
| | |
Goto Forum:
Current Time: Sun Sep 01 04:40:13 GMT 2024
Powered by FUDForum. Page generated in 0.06599 seconds
|