[theCoder]

We are having the same problem. Yesterday we updated the cRio and Driver code to the most current versions from FIRST. We are at a scrimmage match and we toggle 4 seconds on "Watchdog" then one second on "Enable". We get this problem when using the scrimmage SSID as well as stand-alone. We have followed the update instructions very carefully, at least 4 or 5 times. No luck. Is anyone else having problems with the new code? Any suggestions would be greatly appreciated.

<< edit >>
We found the problem. Some code that worked with the older firmware caused problems running with the new firmware. One problem we figured out, the other went away when we commented out a large block of code. The first involved the compressor. We were directly controlling the spike, instead of using the compressor object. This code worked fine before, but with the new firmware caused the cRio to die with a "kernel" error. It took the better part of 4 hours to find. Unfortunately the compiler did not catch the problem. The second was buried somewhere in a large block of under-tested autonomous code. Yesterday at the scrimmage was the first time that code was fully exercised. As mentioned above, the controller was between watchdog and enabled. Commenting out a large block of code made the problem go away.