
Unknown device
#1
Posted 24 August 2012 - 07:22 PM
#3
Posted 25 August 2012 - 08:27 AM
#4
Posted 25 August 2012 - 09:21 AM
#5
Posted 25 August 2012 - 11:51 AM
#6
Posted 25 August 2012 - 12:13 PM
This "unknown device" appear just after you get a wire and clear Netduino? If is that problem you need to use a generic GPS Camera Driver, download it here. I made a compilation off role process in my blog (in portuguese... ) you can take a look here,
Sometimes I hate this model of share information in forum don have organization... everything is mixed...
[]s,
Victor
#7
Posted 25 August 2012 - 03:11 PM
#8
Posted 25 August 2012 - 04:18 PM
#9
Posted 25 August 2012 - 05:47 PM

#10
Posted 26 August 2012 - 09:29 AM
#11
Posted 26 August 2012 - 01:59 PM
That VID/PID indicates that Windows can't enumerate the device at all (so it won't be able to match any drivers to it).USB\VID_0000&PID_0000\5&2C77E8C4&0&1
Please try holding down the pushbutton while plugging in your Netduino--and see if you get a different result.
If not, please try re-erasing your Netduino (connecting the 3V3 power header to the ERASE pad for 250ms or so).
If that doesn't work, then it's possible that the Netduino got damaged somehow (shorting out a circuit, etc.)... How long have you had your Netduino?
Chris
#12
Posted 26 August 2012 - 03:23 PM

#13
Posted 26 August 2012 - 04:14 PM
#14
Posted 02 September 2012 - 03:16 PM
When I start the Netduino with the Reset button pushed down, Windows does recognize the Netduino but i get the following error when Deploying:
------ Deploy started: Project: NetduinoLaserGame, Configuration: Debug Any CPU ------
An error has occurred: please check your hardware.
DebugPort.GetDeviceProcess() called with no argument
Source: Microsoft.SPOT.Debugger.CorDebug
Stack :
at Microsoft.SPOT.Debugger.DebugPort.GetDeviceProcess(String deviceName) in c:\depot\current\CLIENT_V4_2\Framework\CorDebug\DebugPort.cs:line 290
at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.Deploy() in c:\depot\current\CLIENT_V4_2\Framework\CorDebug\VsProjectFlavorCfg.cs:line 809
at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.<Microsoft.VisualStudio.Shell.Interop.IVsDeployableProjectCfg.StartDeploy>b__0() in c:\depot\current\CLIENT_V4_2\Framework\CorDebug\VsProjectFlavorCfg.cs:line 634
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
I've already flashed the Netduino with the MFDeploy again. This works only when connecting the Netduino if the reset button is pushed down. Any thoughts what may have happened?
Thanks.
#15
Posted 02 September 2012 - 09:07 PM
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#16
Posted 11 September 2012 - 09:51 PM
#17
Posted 11 September 2012 - 11:00 PM
#18
Posted 04 November 2012 - 05:19 PM
#19
Posted 14 November 2012 - 05:11 PM
I erased the Netduino using the gold pad and 3.3V.
How is this done?, I'm new to this and do not know how well it works MFDeploy and SAMBA.
My netduino plus computaror not recognized.
Thank you.
#20
Posted 05 February 2013 - 02:32 PM
Hi Chris and Faith,
I have also Netduino Plus 1 and I got the same error "device unknown" on Win7 even I've tried everything described above. But My USB VID/PID was different (no such strange hash key at the end).
Then I've connected the Netduino to my older netbook with WinXP, where I have been testing Netduino earlier. The device drive was found and I was able to do update to 4.2
After reflashing on XP, Netduino driver was found for the device on Win7, but I still can't progress on Win7, because combobox in Sam-ba v2.12 is empty, as well as Atmel's Sam-ba v2.9.
I should mention, that my Netduino is unstable in flashing. I've tried NetFM 4.1., 4.2.0.0. RC3, 4.2.0.0. RC4, and today the latest 4.2.0.0. on different computers, before I have suceeded (even only partialy). I've been trying to get working Netduino more then one year and today I've got second positive result. Netduino is somehow life, but I'll see tomorrow morning. Sometimes it is not responding, but finally after many resets I was able to setup IP and even shortly debug. Apart of unexpected behavior when connecting, is obvious one significant problem: MFDeploy doesn't display "Target->Device Capabilities". Ping sometimes doesn't display only "ping ... tinyboot", but also one line of assembly description. Do you have any idea what is crewed up? I have no courage to update again once my device is live. I've spent already to much time with it. Shoult I rather create in this forum new thread for this issue?
Thank you in advance for help also with the Win7 driver issue.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users