See this, especially post 3.
http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&p=649123
Get that inf file. Change, in both locations, the VID, PID and REV to exactly match your descriptor in your image, and try to install that inf…
if you google “usb vid_03eb&pid_6124&rev_0110” then you will see that this is sometimes an issue. Don’t know why though…
Hydra will not function properly with a virtual machine. Known issue.
@ Mike: ok…it’s right to know that Hydra doesn’t work with virtual machine… I will avoid this solution
@ GMod(Errol): this is an interesting idea! Thank you for the hint ! I will try this way, but I have a question before going on: what are the right drivers to be modified? Can I try with this: C:\Program Files (x86)\GHI Electronics\GHI Premium NETMF v4.2 SDK\USB Drivers\GHI_NETMF_Interface ? note that first time I connected the board to the PC it has been correctly recognized as a COM port (by using the GHI drivers, I suppose), whereas the issue has started during the firmware updating procedure, after memory erasing. So I think that the drivers I have to modify are others than GHI… or not?
No. Download the INF file on that page that I gave you. Edit that INF file. This is the file: CVS Info for project contiki
There are two lines in that file reading “USB\VID_03EB&PID_2021&MI_02”. Change that to read “USB\VID_03EB&PID_6124&REV_0110”, this will tell the driver that it is intended for a blank Hydra board.
The GHI drivers are all for when NETMF is running on the board. Even when there was a com port with the GHI drivers, that was when tinybooter was running which is part of the NETMF stuff.
But when everything is erased from the board the built in software in the CPU takes over. This was written by ATMEL, the chip manufacturer, and can’t be erased or changed in any way. The driver for this software does not seem to be installed on your PC. On my PC it shows up as a “GPS Cammera” with a com port. But the INF file that that page points to will call it “Atmel Raven USB Debug Port”, but you can change that to anything you like by editing the INF to show something else.
Finally a great step ahead ! Thanks to GMod(Errol) now the board is recognized as an “Atmel Raven USB Debug Port” (COM3). But now, how can I go on with the firmware updating? I tried to click the “update” button on the Hydra Updater but it says that it fails to communicate with Hydra over serial port… is there another way?
Great news. Next time using the updater should be flawless now that the driver is installed.
To update the firmware the “hard way”:
Under the GHI folder under program files, there is an OSHW folder, then Hydra folder, then Firmware folder, then FEZ Hydra TinyBooter Updater folder. Copy that folder to your desktop or somewhere you can find. The updater tries to create a log file and under Win7 that fails(almost nobody can write to any folder under program files) and then the updater fails.
After you have copied the folder, run CommandPrompt.bat from that folder. This should give you a command prompt.
Then type “UpdateFEZHydra COM3” if I recall correctly. This will update only the Tinybooter.
Then you might be able to use the Hydra Updater again, or you can use MF Deploy to load the main firmware onto the board…
BTW. For future reference. This is the driver that downloads from Microsoft. Copy it to an INF file and use that as the driver.
[quote];
; WPUSBSERIAL.INF (for Windows 2000)
;
; Copyright © 2000, WondeProud Technology Inc.
[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%WinARM%
CatalogFile = WP.cat
LayoutFile=layout.inf
DriverVer=10/01/2006,5.2.3790.0
[SourceDisksNames]
;1=%Pro.Disk%,
[SourceDisksFiles]
[MANUFACTURER]
%WinARM_SAM7%=Models, NT.5.1,NTamd64
[Models]
%WinARM_SAM7_CDC0%=BTCD,USB\VID_03EB&PID_6124
%WinARM_SAM7_CDC1%=BTCD,USB\VID_03EB&PID_6125
%WinARM_SAM7_CDC2%=BTCD,USB\VID_03EB&PID_6126
%WinARM_SAM7_CDC3%=BTCD,USB\VID_03EB&PID_6130
%WinARM_SAM7_CDC4%=BTCD,USB\VID_03EB&PID_6160
[Models.NT]
%WinARM_SAM7_CDC0%=BTCD.NT,USB\VID_03EB&PID_6124
%WinARM_SAM7_CDC1%=BTCD.NT,USB\VID_03EB&PID_6125
%WinARM_SAM7_CDC2%=BTCD.NT,USB\VID_03EB&PID_6126
%WinARM_SAM7_CDC3%=BTCD.NT,USB\VID_03EB&PID_6130
%WinARM_SAM7_CDC4%=BTCD.NT,USB\VID_03EB&PID_6160
[Models.NT.5.1]
%WinARM_SAM7_CDC0%=BTCD.XP,USB\VID_03EB&PID_6124
%WinARM_SAM7_CDC1%=BTCD.XP,USB\VID_03EB&PID_6125
%WinARM_SAM7_CDC2%=BTCD.XP,USB\VID_03EB&PID_6126
%WinARM_SAM7_CDC3%=BTCD.XP,USB\VID_03EB&PID_6130
%WinARM_SAM7_CDC4%=BTCD.XP,USB\VID_03EB&PID_6160
[Models.NTamd64]
%WinARM_SAM7_CDC0%=BTCD.64,USB\VID_03EB&PID_6124
%WinARM_SAM7_CDC1%=BTCD.64,USB\VID_03EB&PID_6125
%WinARM_SAM7_CDC2%=BTCD.64,USB\VID_03EB&PID_6126
%WinARM_SAM7_CDC3%=BTCD.64,USB\VID_03EB&PID_6130
%WinARM_SAM7_CDC4%=BTCD.64,USB\VID_03EB&PID_6160
;[Reader_Install.NTx86]
;Windows2000
[DestinationDirs]
DefaultDestDir=12
BTCD.NT.Copy=12
[BTCD.NT]
include=mdmcpq.inf
CopyFiles=BTCD.NT.Copy
AddReg=BTCD.NT.AddReg
[BTCD.NT.Copy]
usbser.sys
[BTCD.NT.AddReg]
HKR,DevLoader,*ntkern
HKR,NTMPDriver,usbser.sys
HKR,EnumPropPages32,“MsPorts.dll,SerialPortPropPageProvider”
[BTCD.NT.Services]
AddService = usbser, 0x00000002,ServiceNT_Inst
[ServiceNT_Inst]
DisplayName = %Serial.SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1 ;SERVICE_ERROR_NORMAL
ServiceBinary = %12%\usbser.sys
LoadOrderGroup = Base
;;==================================================================
[Reader.NT]
include=mdmcpq.inf
CopyFiles=Reader.NT.Copy
AddReg=Reader.NT.AddReg
[Reader.NT.Copy]
usbser.sys
[Reader.NT.AddReg]
HKR,NTMPDriver,*ntkern
HKR,NTMPDriver,usbser.sys
HKR,EnumPropPages32,“MsPorts.dll,SerialPortPropPageProvider”
[Reader.NT.Services]
AddService = usbser, 0x00000002,Service_Inst
[Service_Inst]
DisplayName = %Serial.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 0 ;SERVICE_ERROR_NORMAL
ServiceBinary = %12%\usbser.sys
LoadOrderGroup = Base
;;=================================================================
[BTCD.XP]
include=mdmcpq.inf
CopyFiles=BTCD.XP.Copy
AddReg=BTCD.XP.AddReg
[BTCD.XP.Copy]
usbser.sys
[BTCD.XP.AddReg]
HKR,NTMPDriver,*ntkern
HKR,NTMPDriver,usbser.sys
HKR,EnumPropPages32,“MsPorts.dll,SerialPortPropPageProvider”
[BTCD.XP.Services]
AddService = usbser, 0x00000002,ServiceXP_Inst
[ServiceXP_Inst]
DisplayName = %Serial.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 0 ;SERVICE_ERROR_NORMAL
ServiceBinary = %12%\usbser.sys
LoadOrderGroup = Base
;;=================================================================
[BTCD.64]
include=mdmcpq.inf
CopyFiles=BTCD.64.Copy
AddReg=BTCD.64.AddReg
[BTCD.64.Copy]
usbser.sys
[BTCD.64.AddReg]
HKR,NTMPDriver,*ntkern
HKR,NTMPDriver,usbser.sys
HKR,EnumPropPages32,“MsPorts.dll,SerialPortPropPageProvider”
[BTCD.64.Services]
AddService = usbser, 0x00000002,Service64_Inst
[Service64_Inst]
DisplayName = %Serial.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 0 ;SERVICE_ERROR_NORMAL
ServiceBinary = %12%\usbser.sys
LoadOrderGroup = Base
;;=================================================================
[Strings]
WinARM = "WONDE PROUD"
WinARM_SAM7 = "WinARM"
WinARM_SAM7_CDC0 = "GPS Camera Detect"
WinARM_SAM7_CDC1 = "GPS DATA LOGGER"
WinARM_SAM7_CDC2 = "GPS DATA LOGGER"
WinARM_SAM7_CDC3 = "Persional Tracer"
WinARM_SAM7_CDC4 = "AVL VT-SERIAL"
Serial.SvcDesc = “USB Serial emulation driver”
[/quote]
YES YES YES !!! Thank you very much GMod(Errol) !!! I used the last driver (your post #32) and now it works perfectly !!! I’m happy because finally I’m able to start working with Hydra ! Thanks also to the others who tried to help me !
Glad that it worked. 
@ andre.marschalek - Guess now that it works it will have to be added to the wiki somewhere…
BTW, it seems that the cause of the problem was that my machine is not setted up to look for drivers on the Microsoft Updates site… I’m not sure about this. How can I look to see if it is true or not ?
Go to Devices And Printers.
Right click on your computer and click Device Installation Settings.
There you will see your options for installing from MS.
@ GMod(Errol): thanks! I confirm that the problem was that my computer was not configured for installing drivers from Windows Update. This fact may be useful for other people with the same issue.