We are a rooking team having issues getting our robot set up in the WindRiver Remote Systems view. We are able to successfully deploy programs to the cRIO. We created a new remote system using the getting started with C++ programming guide, but when we attempt to connect, we get the following series of errors:
The procedure entry point tgtOSIsCertified could not be located in the dynamic link library libtgtsvr.dll
The procedure entry point tsEvtptAdd_64 could not be located in the dynamic link library libtgtsvr.dll
The procedure entry point tgtOSIsCertified could not be located in the dynamic link library libtgtsvr.dll
The procedure entry point tgtCoreFileoffsetGet64 could not be located in the dynamic link library libtgtsvr.dll
Then, the log console displays with the following message in it:
Error: Error parsing command line! Target server will exit.
In the target server connection properties, here is what is displayed in the Command Line box:
tgtsvr -V -R C:/WindRiver/workspace -RW -Bt3 -c C:\WindRiver\WPILib\cRIOFRCII_vxWorks -A 10.42.13.2
Any help would be greatly appreciated!
I am seeing the same errors with Workbench 3.0. With 3.3 I get CPU licensing errors. We could also use some help figuring this out.
I get the same licensing error as well.
I would really like for this to work, as being able to read console output is useful for debugging.
Out of interest, are any of you running this year’s version of windriver on the same windows install as last year? I have a feeling that this issue is related to last years’ version uninstalling incorrectly.
When installed Windriver on Windows 7 64-bit, I had delete the “c:\windriver” directory since the old license info stayed behind. When I installed Windriver the first time on a 64-bit machine, I mistakenly left the checkbox enabled to launch Windriver (using the first DVD). You’ll need to follow the directions and skip the launch.
Here’s what I had to do for 64-bit mode:
- uninstall Windriver
- delete the “c:\windriver” directory
- install Windriver (DVD disk 1)
- uncheck so Windriver doesn’t launch
- install Windriver (DVD disk 2) for Windows 7 64-bit mode
We are a rookie team and have installed WindRiver on a laptop that had no previous versions. We will give the re-install a try when we get a moment.
Thanks!
Ok I fixed it (for me at least). There are 2 shortcuts to launch windriver and you need to choose the right one. Seems stupid that they would do this:confused: . I also re-installed, idk if that actually helped though. Look at the attached picture
