Thread: cRIO imaging issue
View Single Post
  #7   Spotlight this post!  
Unread 13-01-2013, 10:30
Tom Line's Avatar
Tom Line Tom Line is offline
Raptors can't turn doorknobs.
FRC #1718 (The Fighting Pi)
Team Role: Mentor
  
Join Date: Jan 2007
Rookie Year: 1999
Location: Armada, Michigan
Posts: 2,517
Tom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond repute
Re: cRIO imaging issue
Quote:
Originally Posted by jcbc View Post
We always use a crossover Ethernet cable when imaging. I don't see it in this year's documentation, but last year's documentation (Getting Started with the 2012 FRC Control System) said to use a crossover cable on page 17, step #1 under "Running the cRIO Imaging Tool".
Generally speaking, any newer computer knows when to crossover and when not to, so that shouldn't be the problem (but it might!).

We actually got stuck at the rebooting point, and I'd never seen it before. We found a couple things. First, the battery was nearly dead. Next, the cRio wasn't being powered from the 24V on the power distribution board. Fixing those allowed a reimage (wierd huh?).