Main Site Documentation

Deploying to a Fez Hydra results in: Device not found or cannot be opened - USB:Gadgeteer


#1

Hi
I’m deploying a project to my Fez Hydra, but I get Device not found or cannot be opened - USB:Gadgeteer =(
I have tested depploying a File->new project and then only adding the Hydra board and the UsbClientDP but the problem persist.
I have tested with different usb cabels and connect via powered usb hub and directly to the computer but no change.
If I check the “.NET Micro Framework” tab under project properties it says Tranport: USB and Device “FEZ Hydra_FEZHydra”.
Using the same setup (changing only the motherbord to a FEZ Spider) it works without any problem.
This is the first time I use my hydra could it be broken or am I miss something else?

Cheers
/Jimmy


#2

Did you update the firmware?


#3

That was my first thoght, but the firmware updater doesn’t fint the Hydra either, forgot to mention that.


#4

Then you can try to do it manually http://wiki.tinyclr.com/index.php?title=Firmware_Update_FEZ_Hydra

But maybe your PC is not seeing it at all. What do you see under device manager? Can you ping it from MFDeploy?


#5

Thanks I’ll try that
My device manager says a .Net Micro Framework Device is connected
No response when pinging from MFDeploy


#6

What do you see in “Devices & Printers”?


#7

Under Device & Printers I see “FEZ Hydra”


#8

If you are correctly booted into the TinyBooter then you should see an icon like this one. Try the method of placing a wire between pins 8 & 10 of socket 3 to get into this mode before trying to update the firmware.


#9

Now I have tested to update the firmware using an SD card.
After reboot I get a GPS Camera Detect (COM3) and when running UpdateFEZHydra.bat it takes a REALLY (30+ min) long time and the log doesn’t open.
Looking in the log (in the same folder) the last rows are:

-I- Erasing: 0x18C0 bytes at address 0x41D6C0
-I- Erasing: 0x18C0 bytes at address 0x41EF80
-I- Send File FEZ_HYDRA_TINYBOOTER.bin at address 0x8400
GENERIC::SendFile FEZ_HYDRA_TINYBOOTER.bin at address 0x8400
-I- File size : 0xEA4C byte(s)
-I- Writing: 0x18C0 bytes at 0x8400 (buffer addr : 0x302CD8)
-I- 0x18C0 bytes written by applet
-I- Writing: 0x18C0 bytes at 0x9CC0 (buffer addr : 0x302CD8)
-I- 0x18C0 bytes written by applet
-I- Writing: 0x18C0 bytes at 0xB580 (buffer addr : 0x302CD8)
-I- 0x18C0 bytes written by applet
-I- Writing: 0x18C0 bytes at 0xCE40 (buffer addr : 0x302CD8)
-I- 0x18C0 bytes written by applet
-I- Writing: 0x18C0 bytes at 0xE700 (buffer addr : 0x302CD8)
-I- 0x18C0 bytes written by applet
-I- Writing: 0x18C0 bytes at 0xFFC0 (buffer addr : 0x302CD8)
-I- 0x18C0 bytes written by applet
-I- Writing: 0x18C0 bytes at 0x11880 (buffer addr : 0x302CD8)
-I- 0x18C0 bytes written by applet
-I- Writing: 0x18C0 bytes at 0x13140 (buffer addr : 0x302CD8)
-I- 0x18C0 bytes written by applet
-I- Writing: 0x18C0 bytes at 0x14A00 (buffer addr : 0x302CD8)
-I- 0x18C0 bytes written by applet
-I- Writing: 0xB8C bytes at 0x162C0 (buffer addr : 0x302CD8)
-I- 0xB8C bytes written by applet
-I- Temp file : C:/Users/Jimmy/.sam-ba.testCompareFile
-I- Compare File : FEZ_HYDRA_TINYBOOTER.bin with memory at address : 0x8400 , for 59980 byte(s)
-I- Read File C:/Users/Jimmy/.sam-ba.testCompareFile at address 0x8400
GENERIC::ReceiveFile C:/Users/Jimmy/.sam-ba.testCompareFile : 0xEA4C bytes from address 0x8400
-I- Reading: 0x18C0 bytes at 0x8400 (buffer addr : 0x302CD8)
-I- Reading: 0x18C0 bytes at 0x9CC0 (buffer addr : 0x302CD8)
-I- Reading: 0x18C0 bytes at 0xB580 (buffer addr : 0x302CD8)
-I- Reading: 0x18C0 bytes at 0xCE40 (buffer addr : 0x302CD8)
-I- Reading: 0x18C0 bytes at 0xE700 (buffer addr : 0x302CD8)
-I- Reading: 0x18C0 bytes at 0xFFC0 (buffer addr : 0x302CD8)
-I- Reading: 0x18C0 bytes at 0x11880 (buffer addr : 0x302CD8)
-I- Reading: 0x18C0 bytes at 0x13140 (buffer addr : 0x302CD8)
-I- Reading: 0x18C0 bytes at 0x14A00 (buffer addr : 0x302CD8)

Nothing else
Any suggestions?

/Jimmy


#10

FEZs can be finicky about which SD cards they like. If you have a different SD card, give that a try. It looks like it’s losing communications or data in the middle of the process. Also, you might try downloading the firmware files again just to be sure they aren’t corrupt.


#11

Sorry for not replying sooner.

Got it working finaly =) \o/

What I did was updating the firmware manually following the guide above.
Connected to a power usb hub I got the “interuption” problem sbove , but when connnected directly to the computer everything worked.

Thanks for all the help

Cheers
/Jimmy


#12

Glad it is working for you.


#13

I was just now struggling with a similar problem with FEZ Spider. I’m posting my solution just for the case anybody else is having the same problem.

SYMPTOMS:
Visual Studio was reporting linking errors with some assemblies, so I updated the firmware. After that, I was unable to deploy anything to the device. I was only getting the error “Device not found or cannot be opened - USB:Gadgeteer”.

SOLUTION:
The config tool was connecting to the device without any problems, and was reporting the device name ESX_ESX. I noticed however, that under Devices & Printers in the Control Panel, the name is just ESX. I updated the name in VS Project Properties, Micro Framework tab, and now everything works as a charm.