AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]() This lockup is a CPU/kernel hang, the roboRIO will completely stop responding and will not be accessible via the DS, webpage or SSH. ![]() This lockup can not be definitively identified on the field and a field fault will not be called for a match where this behavior is believed to occur. Acessing the device less frequently and/or using a different roboRIO may significantly reduce the likelihood/frequency of lockups, it will be up to each team to assess their tolerance of the risk of lockup. Workaround: The only surefire mitigation is to use the MXP I2C port or another device to read the I2C data. different roboRIOs will behave differently) as well as how the bus is being used. The frequency of these lockups appears to be dependent on the specific hardware (i.e. Issue: Use of the onboard I2C port, in any language, can result in system lockups.
0 Comments
Read More
Leave a Reply. |