Device not found or cannot be opened - USB:Gadgeteer

I have upgraded from 4.2.0 to 4.2.5 with my Spider. Now when I try to deploy a gadgeteer project I get:
“Device cannot be opened - USB:Gadgeteer”

Here is the scenario:

I am using DP with secondary 9v power
I have the screen attached and it shows version 4.2.5.0
I can ping it with MFDeploy
I can change its USB Name with MFDeploy
I have deployed a “hello world console” Net mf application successfully.
It shows up in printers and devices as "EMX"
I have uninstalled and reinstalled the device drivers.
When I ran the updater application, it took like 10 or so tries to finally get the the “This will delete all your…” screen

Any Ideas?

I am getting very frustrated as each device I try (Cerberus, Hydra, Spider) has something that seems to get in the way of running the program I was running on a Cobra.

thanks for your time,

Tal

As soon as you changed the device name you have gone into non-standard territory.

I am not sure what is the current state or your device and drivers. I suggest
you uninstall the SDKs and device drivers and reinstall. We can try to
help you with a standard installation…

Its name is “Gadgeteer” like the documentation says it should be on the page “http://wiki.tinyclr.com/index.php?title=Firmware_Update_EMX

how do i uninstall the sdk from the device?

Tal, lets step through this.

Disconnect your device from the PC; set the switches to “normal” mode (whatever that is; I don’t have a spider)

Open mfdeploy

Open Device Manager and check whether you have visible devices in the serial/COM and LPT ports.

Connect your device, listen for the device connected sound, and see what appears in Device Manager. Tell us the result.

In mfdeploy, select the port that just showed up - if a COM port appeared, select Serial then the device port; if a GHI debuggable .net device appeared, select USB and tell us the name of the devices in the next drop down list - from your post it seems it should be Gadgeteer.

Ping it, and tell us what the response is, this will tell us where your firmware install is up to.

Then you will probably need to step through the manual loading of the firmware (some times I just don’t trust the installers :slight_smile: )

Report back your findings/progress.

o.k.
Followed steps.

in device manager, “GHI NETMF Debug interface” is under Universal Serial bus Controllers.
in MFDeploy, it showed up under USB as EMX_Gadgeteer, Pinging… TinyCLR

on screen it says:
[em]EMX
Version 4.2.5.0
Debug: USB1
LCD:320X240

Waiting for debug commands…
[/em]

I did a device capabilities:

[quote]Pinging… TinyCLR
HalSystemInfo.halVersion: 4.2.0.0
HalSystemInfo.halVendorInfo: Microsoft Copyright © Microsoft Corporation. All rig
HalSystemInfo.oemCode: 255
HalSystemInfo.modelCode: 0
HalSystemInfo.skuCode: 65535
HalSystemInfo.moduleSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
HalSystemInfo.systemSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
ClrInfo.clrVersion: 4.2.0.0
ClrInfo.clrVendorInfo: Microsoft Copyright © Microsoft Corporation. All rig
ClrInfo.targetFrameworkVersion: 4.2.0.0
SolutionReleaseInfo.solutionVersion: 4.2.5.0
SolutionReleaseInfo.solutionVendorInfo: Copyright © GHI Electronics, LLC
SoftwareVersion.BuildDate: Oct 24 2012
SoftwareVersion.CompilerVersion: 410462
FloatingPoint: True
SourceLevelDebugging: True
ThreadCreateEx: True
LCD.Width: 320
LCD.Height: 240
LCD.BitsPerPixel: 16
AppDomains: True
ExceptionFilters: True
IncrementalDeployment: True
SoftReboot: True
Profiling: False
ProfilingAllocations: False
ProfilingCalls: False
IsUnknown: False
[/quote]

@ Tal_McMahon - looks like you are ready to go. looks normal for a device with new firmware.

So now, as Mike says, you look right to go. What ever you do, don’t open an old project (or one you download) and try to deploy that. Only create new projects (this will get the correct 4.2 referenced DLLs into your project) and then copy code over that you might want to “reinvigorate”.

File–>New Project
select gadgeteer 4.2
hit “f5”

windows pops up that says, "There were deployment errors. Continue?"
I said "No"
on the error list in VS it says “Device not found or cannot be opened - USB:Gadgeteer”

Hit “F5” again
windows pops up that says, "There were deployment errors. Continue?"
I said “Yes”

Pop up with title of "TinyCLR Error"
and message of:
“An exception occurred while attempting to launch the debugger: Object reference not set to an instance of an object.”

2nd Pop Up Title of "Microsoft Visual Studio"
With Red X and message of “The operation could not be completed. Unspecified Error”

This is what was in the Output window under Build:
------ Deploy started: Project: GadgeteerApp3, Configuration: Debug Any CPU ------
------ Deploy started: Project: GadgeteerApp3, Configuration: Debug Any CPU ------
Device not found or cannot be opened - USB:Gadgeteer========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Did you make sure your project was targeting the USB device not the emulator?

Yes, it is pointed at thew usb

Are you using a VM?

no, just plain old box (laptop) with win7 on it.
2 Cerberus work, hydra works I havent tried my cerbuino yet

powered usb hub?

Tried both ways.

just want to reiterate, it worked with a console app, just fails with gadgeteer

@ Tal_McMahon - remove the gadgeteer reference and re add it

no love on the remove references either.

I am having the same issue as you. I received my Spider yesterday and have just finished installing and remedying the driver issue. I’ve successfully installed the newest firmware.
I get the same results when I try to debug.

I am pointed at the correct USB device
My Ping returns same result
My default boot displays the same information.

Hi Mattyb, welcome to the forum.

Can you tell us what your device capabilities shows, from mfdeploy? Can you also then tell us if you’re creating a Gadgeteer 4.2 or 4.1 project, or a 4.2 or 4.1 console project?

Thank you for the welcome.

Device Capabilities:
HalSystemInfo.halVersion: 4.2.0.0
HalSystemInfo.halVendorInfo: Microsoft Copyright © Microsoft Corporation. All rig
HalSystemInfo.oemCode: 255
HalSystemInfo.modelCode: 0
HalSystemInfo.skuCode: 65535
HalSystemInfo.moduleSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
HalSystemInfo.systemSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
ClrInfo.clrVersion: 4.2.0.0
ClrInfo.clrVendorInfo: Microsoft Copyright © Microsoft Corporation. All rig
ClrInfo.targetFrameworkVersion: 4.2.0.0
SolutionReleaseInfo.solutionVersion: 4.2.5.0
SolutionReleaseInfo.solutionVendorInfo: Copyright © GHI Electronics, LLC
SoftwareVersion.BuildDate: Oct 24 2012
SoftwareVersion.CompilerVersion: 410462
FloatingPoint: True
SourceLevelDebugging: True
ThreadCreateEx: True
LCD.Width: 320
LCD.Height: 240
LCD.BitsPerPixel: 16
AppDomains: True
ExceptionFilters: True
IncrementalDeployment: True
SoftReboot: True
Profiling: False
ProfilingAllocations: False
ProfilingCalls: False
IsUnknown: False

To the best of my knowledge I am creating a Gadgeteer 4.2, here is a screenshot of what I select: