vxworks remote system connection w/ crio II

[enrique]

Yes, In fact the problem here is the crio has a higher version than the winriver vxworks. So if anything I think I'm missing an update for winriver.
The last update I did is the WorkbenchUpdate20120108rev2993.exe

[enrique]

I also did the FRC2012Utilities.zip update on
http://joule.ni.com/nidu/cds/view/p/id/2262

And FRC2012DriverStationUpdate.zip on
http://joule.ni.com/nidu/cds/view/p/id/2263

[RufflesRidge]

Originally Posted by enrique

Yes, In fact the problem here is the crio has a higher version than the winriver vxworks. So if anything I think I'm missing an update for winriver.
The last update I did is the WorkbenchUpdate20120108rev2993.exe

You're reading the message backwards. Target (cRIO) is 6.3 as it should be. "Selected OS version" is 6.8. Now why you are getting this message is a good question as the only thing visible in the screenshot says 6.3

[enrique]

Originally Posted by RufflesRidge

You're reading the message backwards. Target (cRIO) is 6.3 as it should be. "Selected OS version" is 6.8. Now why you are getting this message is a good question as the only thing visible in the screenshot says 6.3

Under remote systems it says:
VxWorks 6.8:MPC5200B - MPC5200B
That's not on the crio?

Interesting that right above it it says target debugger 6.3. lol
I'm going to reformat it with v43 just in case.
Cause, I'm stumped.

[enrique]

ok finally figured it out. Instead of MPC5200B for processor, I chose MPC5200 and it worked.