4.2 Confusion
#1
Posted 14 October 2012 - 11:03 AM
#2
Posted 14 October 2012 - 11:58 AM
#3
Posted 14 October 2012 - 06:46 PM
Hi DrJaymz,
1. Install the .NET MF 4.2 QFE2 SDK
2. Install the Netduino 4.2 SDK (latest version)
3. Upgrade your board to the latest Netduino firmware
Please let me know how it works for you,
Chris
Done.
It will not deploy now. Whatever I try to do.
Incrementally deploying assemblies to device
Deploying assemblies for a total size of 1456 bytes
Assemblies successfully deployed to device.
You'd think its deployed then? No. The error comes up:
Error 1 Device not found or cannot be opened - USB:Netduino
Using MFDeploy I can get
HalSystemInfo.halVersion: 4.2.0.0
HalSystemInfo.halVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC
HalSystemInfo.oemCode: 34
HalSystemInfo.modelCode: 177
HalSystemInfo.skuCode: 4097
HalSystemInfo.moduleSerialNumber: 00000000000000000000000000000000
HalSystemInfo.systemSerialNumber: 0000000000000000
ClrInfo.clrVersion: 4.2.0.0
ClrInfo.clrVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC
ClrInfo.targetFrameworkVersion: 4.2.0.0
SolutionReleaseInfo.solutionVersion: 4.2.0.0
SolutionReleaseInfo.solutionVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC
SoftwareVersion.BuildDate: Sep 19 2012
SoftwareVersion.CompilerVersion: 410894
FloatingPoint: True
SourceLevelDebugging: True
ThreadCreateEx: True
LCD.Width: 0
LCD.Height: 0
LCD.BitsPerPixel: 0
AppDomains: True
ExceptionFilters: True
IncrementalDeployment: True
SoftReboot: True
Profiling: False
ProfilingAllocations: False
ProfilingCalls: False
IsUnknown: False
So presumably the device is working. The output is set to deploy to netduino over USB.
So surprised it still can't really be used seriously.
#4
Posted 14 October 2012 - 06:56 PM
Can you please try two things really quickly?So presumably the device is working. The output is set to deploy to netduino over USB.
1. Open up your project properties and go to the ".NET Micro Framework" tab. Change transport from USB to Serial. Then change it back to USB. Try to run your app again.
2. If that doesn't work, please try switching back to the MFUSB drivers.
If all that fails, there are two final options:
1. If you're running Visual Studio 2012 (or would like to try Visual Studio Express for Windows Desktop), upgrade to the .NET MF 4.3 beta SDK. It has dramatically better diagnostics when deploying and it supports .NET MF 4.2 boards as usual.
2. Reflash your Netduino with the production 4.1 firmware. That's really a last resort, but if Visual Studio is failing to connect...it may b a bug which needs to be fixed in the NETMF 4.3 SDK.
Chris
P.S. If you're running inside a virtual machine, the standard WinUSB drivers may not be set up to handle that. Switching to the MFUSB drivers may be a solution there.
#5
Posted 14 October 2012 - 07:02 PM
Hi DrJaymz,
Can you please try two things really quickly?
1. Open up your project properties and go to the ".NET Micro Framework" tab. Change transport from USB to Serial. Then change it back to USB. Try to run your app again.
2. If that doesn't work, please try switching back to the MFUSB drivers.
If all that fails, there are two final options:
1. If you're running Visual Studio 2012 (or would like to try Visual Studio Express for Windows Desktop), upgrade to the .NET MF 4.3 beta SDK. It has dramatically better diagnostics when deploying and it supports .NET MF 4.2 boards as usual.
2. Reflash your Netduino with the production 4.1 firmware. That's really a last resort, but if Visual Studio is failing to connect...it may b a bug which needs to be fixed in the NETMF 4.3 SDK.
Chris
P.S. If you're running inside a virtual machine, the standard WinUSB drivers may not be set up to handle that. Switching to the MFUSB drivers may be a solution there.
#6
Posted 14 October 2012 - 07:10 PM
OK, trying now, BRB
Switching to serial and then back again makes no difference.
I cannot install the MFUSB.ini because windows says:
The specified location does not contain information about your hardware.
With only OK as an option.
So I guess were stuffed then.
The only thing I thought about was the bootloader being at fault.
#7
Posted 14 October 2012 - 07:19 PM
Switching to serial and then back again makes no difference.
I cannot install the MFUSB.ini because windows says:
The specified location does not contain information about your hardware.
With only OK as an option.
So I guess were stuffed then.
The only thing I thought about was the bootloader being at fault.
#8
Posted 14 October 2012 - 07:28 PM
Be sure that you're selecting the MFUSB_Netduino.inf file, not MFUSB.ini.I cannot install the MFUSB.ini because windows says:
The specified location does not contain information about your hardware.
We're basically overriding the Windows driver system by forcing it to use MFUSB instead of WinUSB. Unless we select "no, let me choose" at every step it will try to use the driver specified for the VID/PID in the registry.
Chris
#9
Posted 14 October 2012 - 07:57 PM
Hi DrJaymz,
Be sure that you're selecting the MFUSB_Netduino.inf file, not MFUSB.ini.
We're basically overriding the Windows driver system by forcing it to use MFUSB instead of WinUSB. Unless we select "no, let me choose" at every step it will try to use the driver specified for the VID/PID in the registry.
Chris
Yes, understand, but it will not let me. I'm running XP 32 bit.
#10
Posted 14 October 2012 - 08:07 PM
Yes, understand, but it will not let me. I'm running XP 32 bit.
I clicked uninstall driver
Then let it install it again.
then just now it worked.
#11
Posted 14 October 2012 - 08:14 PM
Very interesting, thank you for the update.Then let it install it again.
then just now it worked.
Let us know if you run into any other troubles.
Chris
#12
Posted 15 October 2012 - 07:43 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users