View Full Version : After updates windriver will not connect to cRIO
z.s.tar.gz
16-02-2010, 17:47
I ran the latest updates that were emailed out, and now I can not connect to the cRIO because I get errors every time.
I imaged it to the latest v20, and that's when things started going wrong. According to the error messages it has something to do with wpilib/vxworks conflicting with the new cRIO image.
Does anyone know how I can fix this or when I can get an older image?
Can you post the exact error message you are getting with copy and paste?
z.s.tar.gz
17-02-2010, 16:48
Here is the first error message it gives:
0x49e 0xaf 0x03
Stopping dump. Other errors might exist.
Error: The systems running on the target and loaded into the target server memory are different.
Either wrong core file is selected on the host or text section is corrupted on target side.
Error during target server core initialization
Target Server will exit
The second error box does not allow copying and pasting.
You need to FTP the /ni-rt/system/vxWorks file from the cRIO and put it in the c:\windriver\WPILib\ directory.
-Joe
z.s.tar.gz
17-02-2010, 16:54
ok I'll try it out
edit: thanks a ton! it totally works now!
for anyone who has the same problem, here's the new file:
gvarndell
17-02-2010, 17:08
ok I'll try it out
edit: thanks a ton! it totally works now!
for anyone who has the same problem, here's the new file:
It would be more useful if we could figure out how it came to be that you were able to image the cRio with the wrong kernel.
When I installed the latest Labview updates, the v19 stuff was deleted, replaced by the v20.
vBulletin® v3.6.4, Copyright ©2000-2017, Jelsoft Enterprises Ltd.