driver station firmware update

[Tom Line]

Please note that if you are using windows and have the option turned on that hides file extensions, by naming the file ".bin", you've really named it ".bin.bin" since windows is hiding the file extension.

Find this options in the folder you're working in under tools -> folder options -> view -> hide extentions for known file types (should NOT have an X in it).

Also, by executable, they mean there should be nothing in the root directory of the USB drive except your file. Even better, just wipe the thumb-drive out and ONLY have that one file on it.

[bobbyt14]

Originally Posted by keehun

I almost ripped my hair out.

Let me give you a first clue.

1. THIS IS NOT A HOT PLUG USB DRIVE.

Did you figure it out yet?

Solution: Plug in your USB Drive before powering up the Driver Station!!!

Also you have to name everything lower caps.

as I posted above, we plugged in the USB drive before powering up the DS (and tried a few times after powering up the DS, as the FIRST docs say to do). also (like I said above), most of the attempts to upload the firmware were with a version that was all in lower case, but the first docs seem to hint that case does not matter (since they say to use all caps in section 5.1, but use either all caps or all lower case in the troubleshooting section 3.1.9).

and no, I have not figured out the solution yet... my guess is that we have a defective DS, though (but I hope I'm wrong).

Originally Posted by tanmaker

This means that there are no other programs or files on the drive that open when you plug in the drive to a computer. I would say take a flash drive, copy everything off of it onto a computer, format it, place the firmware file on the drive, then plug it into the DS. See how that works for you.

We tried formatting drives to fat32 and fat16 and that proved to be no help. There were no other partitions on the drives, and the .bin file was the only file on the drives. I'm guessing that FIRST intended to say that we should only have one partition on the drive and that any drive with U3 should be incompatible... because just about any USB drive has an auto-load function for a driver (if it's hot-plug compatible on windows).

Originally Posted by Tom Line

Please note that if you are using windows and have the option turned on that hides file extensions, by naming the file ".bin", you've really named it ".bin.bin" since windows is hiding the file extension.

Find this options in the folder you're working in under tools -> folder options -> view -> hide extentions for known file types (should NOT have an X in it).

Also, by executable, they mean there should be nothing in the root directory of the USB drive except your file. Even better, just wipe the thumb-drive out and ONLY have that one file on it.

I'm not using windows... the file type used on all the drives we tested was exactly dsud_pkg.bin as I said. really, we just deleted all the extraneous parts of the name of the file when we downloaded it, which ends in dsud_pkg.bin

[Team 1708 Dave]

Ahhh... We're not alone with this problem. 1st we couldn't change the team number. We got help from here suggesting to up-grade the firmware. So we tried this option. Here's what happens. Install the flash drive before start up. Connect power and allow to boot up. Held both buttons until told to release. Held "UP" unit told to release the same to the "Down". Held the select and the screen flashes quickly and says this will take up to 3 min. The flash drive indicator flashes 3 times then the screen returns to the normal operating screen. With the "OTB" still on the bottom of the screen.

We can really use some advice as well.

I read on here there are only a few flash drives that a proven to work but can't seem to find the post anymore. We also formated our flash drive and checked to see if we had the ".bin.bin" issue. We don't.

[bobbyt14]

Originally Posted by Team 1708 Dave

Install the flash drive before start up. Connect power and allow to boot up. Held both buttons until told to release. Held "UP" unit told to release the same to the "Down".

we have yet to get that far... is there supposed to be any sort of response by the DS even if you have the incorrect USB device plugged in? In every attempt we've had, the DS looks unchanged when we hold the 2 buttons down.

Shouldn't it enter the firmware update mode even if nothing's plugged in and complain about errors on the screen if something's wrong?

[GregW11]

Here's my two bits: (for Windows users only)
Make sure that Autorun.inf is either nonexistant or COMPLETELY BLANK. In the case of U3, it would point Windows to load the U3 software. If you have something like PortableApps on it, sometimes the autorun is set up to automatically load the launcher. Things like that.

Best bet is to delete the file and then eject the drive (without going through the "safely remove hardware interface/option) since Windows may try to stick the autorun back onto it.

Here's my autorun.inf file, which is supposed to load the PortableApps launcher automatically on Vista.

[Autorun]
Open=StartPortableApps.exe
Action=Start PortableApps.com
Icon=StartPortableApps.exe
Label=PortableApps.com

Obviously this particular file won't work on the DS.