Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

4.2 Confusion


  • Please log in to reply
11 replies to this topic

#1 DrJaymz

DrJaymz

    Advanced Member

  • Members
  • PipPipPip
  • 42 posts

Posted 14 October 2012 - 11:03 AM

Hi all, I have dusted off the netduino VMware system and aquired another netduino plus. I am confused because I cannot find a definitive guide to what I should be using with versions, the front page mentions 4.1 4.2 sdk, 4.2 firmware, 4.1.0 sdk for the plus and I can't figure out what I need. I have 4.2.0.0 RC4 firmware in my netduino and 4.2 SDK and latest netduino DSK but I cannot use the PWM because its all messed up and the checksums don't match and its all confused. So. Lets start over... Uninstall SDK's , Netduino and just have VS2010. Now, what to install and in what order? I'm happy to update the netduino firmware. Presumably even now, the bug where it cannot be reliably deployed is still with us?

#2 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 14 October 2012 - 11:58 AM

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

#3 DrJaymz

DrJaymz

    Advanced Member

  • Members
  • PipPipPip
  • 42 posts

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 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 14 October 2012 - 06:56 PM

Hi DrJaymz,

So presumably the device is working. The output is set to deploy to netduino over USB.

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.

#5 DrJaymz

DrJaymz

    Advanced Member

  • Members
  • PipPipPip
  • 42 posts

Posted 14 October 2012 - 07:02 PM

OK, trying now, BRB

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 DrJaymz

DrJaymz

    Advanced Member

  • Members
  • PipPipPip
  • 42 posts

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 DrJaymz

DrJaymz

    Advanced Member

  • Members
  • PipPipPip
  • 42 posts

Posted 14 October 2012 - 07:19 PM

It does deploy the application, then afterwards it says preparing to deploy and then that times out.

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 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 14 October 2012 - 07:28 PM

Hi DrJaymz,

I cannot install the MFUSB.ini because windows says:

The specified location does not contain information about your hardware.

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

#9 DrJaymz

DrJaymz

    Advanced Member

  • Members
  • PipPipPip
  • 42 posts

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 DrJaymz

DrJaymz

    Advanced Member

  • Members
  • PipPipPip
  • 42 posts

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 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 14 October 2012 - 08:14 PM

Then let it install it again.

then just now it worked.

Very interesting, thank you for the update.

Let us know if you run into any other troubles.

Chris

#12 DrJaymz

DrJaymz

    Advanced Member

  • Members
  • PipPipPip
  • 42 posts

Posted 15 October 2012 - 07:43 AM

There must be something iffy with the driver caching or something - but I rebooted the VM and changed my LED blink rate just to check, rebuild and deploy - it works fine. Now back to my original issue - I couldn't work out the PWM syntax as usual the MIcrosoft help file says exactly what the function name is and that it has parameters such as duty ratio, but doesn't bother to tell you what units they might be. Really I want to start a PWM signal 10k bananas with a duty ratio of 50 pears. On say D5. Just to add to the confusion, I saw a number of questions in the forum about this and they were using the secret labs definition of PWM and were told not to use the SPOT ones. If people were using the SPOT function then PWM_0 doesn't relate to any pin so I never did get a straight answer to this.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.