View Single Post
  #4   Spotlight this post!  
Unread 04-09-2014, 20:10
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: cRio requires imaging before every deployment

Adding to Mark's suggestion. This failure to download is generally caused by errors that are being caught and logged to the DS while the download occurs. It is complicated, but basically the error handling, as implemented six years ago for FRC uses an obscure hook that transitions to the UI thread in order to catch the error. This is time consuming, and it turns out, not something the download code ever expected to happen. So if the phase of the moon and other things align, the deployment code will get its state confused and it will give up trying to download, but won't really tell you that.

We are using a new error catching mechanism in 2015, BTW. No more thread switches for us.

Greg McKaskle
Reply With Quote