August 24th, RC2 for NETMF 4.2 QFE2

@ Aron - No, I use USB Client DP Module only

@ lerg98 - Great advice, thank you very much! After this way of erasing dataflash works FEZHydraMainboardUpdater.exe perfectly.

Are Seeed modules supported?

I tried to add seeed relays in gadgeteer 4.1 project after installing this and get 'thismodule installer was not correctly setup…'
Don’t see any seeed assembly references…

Never mind…doesn’t work on my laptop …for some reason…went back to 4.1
Desktop works…

@ Josh - The order of steps is very important:
Uninstall all GHI SDKs
Uninstall Gadgeteer Core (very important)
Uninstall Microsoft NETMF 4.1 and/or 4.2 SDK
Install Microsoft’s NETMF 4.2 QFE2 SDK
Install GHI NETMF v4.1 v4.2 and .NET Gadgeteer Package (RC2 8-24-2012).zip
Cerberus firmware included in GHI OSHW SDK had some issues. Use the following firmware instead: http://www.ghielectronics.com/downloads/NETMF/Beta/Cerb-4_2_3_1.zip
Start new project and do not use old projects.

Since the gadgeteer is aimed at no experience necessary - where do i locate the uninstallersw? (I use ccleaner to try and locate Gadgeteeer core with no joy).

Maybe you do not have older versions. The uninstall step is only needed now but not in future.

It is in control panel where it shows all installed application. You should be able to uninstall from there.

Finally updated to 4.2 on my Win 7 64bit.

Now I can’t get USB to connect properly. The display is showing the normal boot-up info. My project can’t publish my solution.

I’ve not uploaded the firmware yet.

Load the usb driver manually please. Looks like windows didn’t load them automatically.

Next time I connected it, it worked.

Thanks

Any ETA on this?

During my one evening of using this new configuration, I’ve had 2 BSODs.

One of the times, I was in the midst of deploying and it was taking forever, so I pressed the reset and it happened.

Guaranteed BSOD in that state. The only way i have found around this one is to kill the VS2010 process. If you wait it never returns and if you reset then Boom!

Just right click on the project in the solution tree and click “Cancel”. When the run button is enabled again, it is safe to reset.

1 Like

If you’re still victim to this (it seems to be PC independent at this point), I recommend not hitting reset. Just unplug the cable and you should be fine. If you’re also using external power, cycle it AFTER you unplug the cable.

I have found that pulling the USB out has the same effect. Also cancelling the deploy sometimes doesn’t come back and never cancels. In that situation I end the devenv taks and re launch vs2010

:frowning: Well, this is the process that was working for me before the last SDK release. Now I don’t have the problem at all :smiley: