We were one of the teams that they tested the latest update on at the end of the BAE Regional and we had no issues. We did not have to re-image our cRIO or make any changes to our code other than rebuilding and downloading the updated executable.
Quote:
Originally Posted by catacon
As expected, this update also bricked our cRIO. After reimaging, we can get the cRIO to talk, but the update has introduced some incompatibilities with our code. Everything but the bare template gives us a "No Robot Code" error which implies a runtime error. We are making heavy use of threads this year and we are suspecting that is the issue. We are going through our code block by block to try and find the issue.
|
Quote:
Originally Posted by catacon
Looks like we hit a fatal error during runtime.
Fatal Error!
Machine Status Register: 0x0008b012
Condition Register: 0x24004448
No idea what that means.
But, they did narrow the issue down to the cypress.cpp file.
|
Note that we are not using threads or the cypress board, so perhaps those potential differences mentioned are related to the problems you are experiencing. Can anyone else who is using these features indicate whether they are also seeing issues?
looks like he was getting ready for a sprint! be careful chuck, its only like 2 feet from the line to the controls... - vivek16 [more] 
13-03-2013, 09:15
Threaded Mode