Document NI roboRIO Safemode

[Daltz333]

Per discussion, we should document safemode to get out of lockups due to bad code (very rare!) or other obscure issues.

1. Boot into safemode
2. SSH in and delete userprogram or reimage

[sciencewhiz]

This page shows how to do it if it's not to dead to run the web browser. https://docs.wpilib.org/en/stable/docs/software/labview/resources/waiting-for-target-to-respond.html

[Daltz333]

I'm not quite sure I understand you. Should we rename that article and move it into the roboRIO section? Does it need any updates?

[sciencewhiz]

That process works for normal cases of "bad" code and is much less invasive the safe mode. The particular instance that was discussed where safe mode is needed assumes that not only is the code bad, but you've modified other priority settings so that not even the web-server works.

[jasondaming]

I have seen teams do what is the link above a lot when they get code stuck. I think the best course of action might be to take the: Set No App, Reboot, and Clear no App sections from that article and place them somewhere under roboRIO so they can be found more generically.

We already have safemode documentation here maybe we should just add it to that?

[Daltz333]

That doesn't work if you can't access the web dash. See Joe's comment.

[jasondaming]

I don't understand why we are catering to the very slim possibility that the web dash isn't accessible after booting into safe mode. I have actually never seen that.