Does the fez hydra updater work correctly, as I cannot update my hydra its reporting more than one hydra detected or the device connected is not Hydra. Note MFDeploy works fine.
I updated mine with it last week w/o any problems. Are you providing the com port parameter? Also, try unplugging all your other USB devices. I’ve had problems in the past with conflicts with my FTDI cable.
Is there any GHI’s device (Panda, EMX, Spider, Corba…) connected to your PC except Hydra that you are going to update?
if not, try to restart your PC.
@ ianlee74 Why do I need an FTDI cable? I am using the USB client DB connected to socket 2 on the Hydra and connecting via USB to my computer.
@ DAT I rebooted and got the same result. I have also tried all 3 options under Device they all report back the same as my first post.
@ Davef
When you use MFDeploy, what device’s name did you see when you select “USB” interface?
And what version of the Hydra Updater app that you are using?
@ DAT
USB device FEZ Hydra_FEZHydra
Updater version 1.0.3
When you click ping, tell to us what you saw so we can know where we are now?
there are only 2 ways maybe cause the Hydra Updater reports that detected more than one device or the device connected is not Hydra…
So make sure that:
Both pictorials are different for me.
-
USB returns FEZ Hydra_FEZHydra, not FEZ Hydra_Gadgeteer
-
Devices and Printers show unspecified FEZ Hydra, not the gps. The FEZ Hydra points to the USB debugger!
You don’t. I was just stating that I had a problem with my Hydra conflicting with an FTDI cable that I had plugged in at one time.
@ ianlee74 Yeh sorry, I guessed that after posting. It looks like something is confusing the updater, but at the moment I cant see what, and I had to wait over 3 months for the USB client DP module in the UK. I’ve been poking at this on and off for the last few weeks!
Yeah, I found a problem. It seems you changed Hydra’s default name so the application can not see it. There 2 ways you can do to update your board:
- Change the Hydra name to default name (FEZ Hydra_Gadgeteer)
- Or : Use MFDeloy, go to Plug-in -> Debug -> Erase Firmware
After Erasing firmware, you should unplug your Hydra and then plug it in again to make a refresh for your PC.
Try to use Hydra Updater now, it should work fine.
And finally, thank you for helping us to find out new problem on Hydra Updater.
@ Dat , Thanks! I cant try for a few hours I will be away from my computer. I havent intentionally changed the Hydra’s name? Will post back later with results.
@ Dat. Sorry I think I’ve made things worse, without thinking I hit the erase next to ping in MFDeploy, now nothing is working. How can I change the Hydra’s name to FEZ Hydra_Gadgeteer?
This is good. Now follow the firmware update steps found on wiki.
@ Dat, @ GUS
Thankyou, all done, but I dont understand why the name had changed, it now says FEZ Hydra_Gadgeteer. From the first time I used it, it was called FEZ Hydra_FEZHydra, as they say, alls well that ends well! Now I hope I can use it.
Dave, you may have just proven what I thought was not possible - that more “FEZ” is not always a good thing 
Because you had old firmware and now you have the correct one
Hi,
I tried to update my FEZ Hydra from 4.1 to 4.2 but unfortunately I think the tools provided just screwed my board totally 
After downloading the latest release package (10-24-2012) installed it. Everything looked fine until the last step where it asks you to upgrade the firmware on the board where the other boards are listed except the FEZ Hydra. So after reading the forums, I decided to run FEZHydraMainboardUpdater.exe to update it. When starting the app I get an unhandled exception on Hydra.HydraUpdater.ReadSDKPathInReg(). Clicking on Continue (as suggested in forum) the app start. When selected the firmware files and clicking on update got an error message saying that TinyBoot files were missing even though they were there.
So the next step was to use command prompt. After erasing the data with the command prompt (which unfortunately worked only too well) now my board is recognized only as “unspecified Device” with the name “FEZ Hydra”. And now none of the apps recognize it (Visual Studio, FEZHydraMainboardUpdater, MFDeploy). After 4 solid sleepless night I decided to give up and purchased a new board.
I was really looking forward to using the board for prototyping but after the experience I had with it, I must admit that I am quite disappointed with the product (spending in excess of $600 with the modules and few G120 boards) and I am starting to doubt that the product is ready to be using in a production environment.
I really hope (out of desperation) that someone who had similar problem has solved it and is willing to walk me through a solution.
Regards