Problem downloading code to c-Rio

[Johnny_5]

As I was preparing our code for use at a science camp demo, I experienced a problem I had never seen before on the classmate.

As I was downloading the code to the c-Rio(not in a build/deploy, just temp) and the classmate was tethered to the c-Rio it got to about 75% when it said it had lost comms with the rio and about 10 seconds after that the classmate just turned off.

As I look at it right now I turned it back on and the 2GoPC logo came up and I hit tab to skip logo boot because it was not doing anything. And now it is on the bootloader page with the status bar for W7 with nothing happening.

Anyone have any ideas?

[torihoelscher]

I dont know about the computer but for the C-rio I would make sure that the wireless is off, the firewall is off, and make sure you have the correct I.P address on your computer. If those dont work, use the cursed word reimage it should work once you troubleshoot it. It works for Team 79!!

[Fletch1373]

It almost sounds like your classmate's battery was low and put itself into hibernate/standby. That would cause the loss of comms and it turning off. Could you better describe (or take pictures) of the classmate starting up? I'm having difficulty understanding what it's doing.

[Johnny_5]

The classmate was plugged in when the code was being downloaded. And after it lost comms then it shut down, and not a normal shutdown sequence. It just turned off.

When I went to turn it back on it was froze at the 2goPC logo until I hit the <tab> key to skip the logo boot. And after that it went to the windows 7 status bar where it then totally locked up. Normally the status lines go across the bar as windows is loading but this time nothing was happening

[Mark McLeod]

If the Windows 7 loading page stays up, then I'd think it wasn't a battery problem, but the Classmate not being able to properly access either memory or drive. It sounds like it can access the bootloader and BIOS.

Possibly reseating the hardware might help.

Reimaging is a last resort if you have your user files/code backed up somewhere.

[Fletch1373]

I'm with Mark on this one. It's definitely getting through the BIOS and bootloader. Seems like RAM may have been loose and was unseated during the download. Try to get into the BIOS page and see how much RAM is listed. If it's different than what the machine actually has, I would open the bottom and try reseating it. It's also possible that there's a corrupt system file(either by virus or other means). I would check and reseat the RAM, then try booting into safe mode with F8.

Let us know how it goes!