How to install (or upgrade to) .NET Micro Framework v4.2 SDK
#21
Posted 19 September 2012 - 05:42 AM
- kekzenevito, Brantsl, WilliamWog and 3 others like this
http://diybrewery.com
#22
Posted 16 October 2012 - 12:46 PM
Sorry that my first post on the forum had to be a "I can't get the stuff to work"-kind, but still:
After installing VS2010 (I used to have 2010 Express, which I understand won't be enough), and the .Net MF4.2.0 and the Netduino SDK, I get this boring error:
This is what I select just berfore the error is displayed:
Any suggestions to what I should check/try?
Thanks,
Eriond
#23
Posted 16 October 2012 - 06:14 PM
#24
Posted 21 October 2012 - 11:29 PM
#25
Posted 03 November 2012 - 09:16 PM
No worries, let's see if we can get you up and running.I am in the middle of this update and I believe I have followed every instruction thus far to the letter but now I am on the step to install TinyBooterDecompresssor.bin and I cannot find that file anywhere on my system drive or other drives.
TinyBooterDecompressor.bin is included with the flash files for each Netduino firmware release.
Here's a link to the v4.2.0.1 firmware for Netduino Plus, as an example:
http://forums.netdui...-v420-update-1/
When you unzip the main attachment, the TinyBooterDecompressor.bin file will be in the folder you unzipped to.
The latest firmware is generally posted at the top of each product forum.
Please let us know if you need any other help getting your board reflashed,
Chris
#26
Posted 15 November 2012 - 02:12 PM
#27
Posted 15 November 2012 - 06:52 PM
For Netduino Plus 1, the new WinUSB drivers in NETMF have changed the operation steps for MFDeploy a bit.I reconnect to the Netduino using MFDeploy and when I try to setup networking, I get an error after a long delay. The
After flashing your board, unplug it. Hold down the pushbutton and then plug it into your PC using USB. This will put it back into TinyBooter mode.
Then go ahead and change the network settings. When you've saved them, unplug and reattach your Netduino Plus 1. You should be good to go.
This is a feature/limitation of the built-in WinUSB drivers. We've added extra hardware to Netduino Plus 2 and Netduino Go so that users don't need this extra step. So this is specific to Netduino Plus 1 only.
Does that get you back up and running?
Chris
#28
Posted 15 November 2012 - 07:34 PM
Hi Dave,
For Netduino Plus 1, the new WinUSB drivers in NETMF have changed the operation steps for MFDeploy a bit.
After flashing your board, unplug it. Hold down the pushbutton and then plug it into your PC using USB. This will put it back into TinyBooter mode.
Then go ahead and change the network settings. When you've saved them, unplug and reattach your Netduino Plus 1. You should be good to go.
This is a feature/limitation of the built-in WinUSB drivers. We've added extra hardware to Netduino Plus 2 and Netduino Go so that users don't need this extra step. So this is specific to Netduino Plus 1 only.
Does that get you back up and running?
Chris
Changing this one step, it now says "Unable to erase configuration section memory" when I try to click OK on the Network Configuration window.
After this happens, MFDeploy cannot seem to find the board anymore.
#29
Posted 15 November 2012 - 08:04 PM
So sorry for the troubles that you're experiencing. Can you please erase the board and follow the steps exactly one more time? And then if it doesn't work, let me know and I can hop on chat and help diagnose?Changing this one step, it now says "Unable to erase configuration section memory" when I try to click OK on the Network Configuration window.
After this happens, MFDeploy cannot seem to find the board anymore.
Chris
#30
Posted 15 November 2012 - 08:36 PM
Hi Dave,
So sorry for the troubles that you're experiencing. Can you please erase the board and follow the steps exactly one more time? And then if it doesn't work, let me know and I can hop on chat and help diagnose?
Chris
I've tried it about a 1/2 dozen times with the same results.
#31
Posted 15 November 2012 - 08:42 PM
You have PM.I've tried it about a 1/2 dozen times with the same results.
Chris
#32
Posted 15 November 2012 - 09:55 PM
1) Erase board
2) Use SAM-BA to install TinyBooter
3) Use MFDeploy to update firmware to 4.2.0.1
4) Reboot board into Bootloader (hold button and power up).
5) Try to set Network configuration and it would fail with message that it could not update memory location.
So, this problem ended up as a Driver issue. I was using the WinUSB driver. When I switched to the MFUSB driver, everything was configured correctly. (Here's a good link by Chris on switching drivers)
After this, I swapped drivers back to prevent the BSOD I would get while using MFUSB. Everything seems to work correctly now.
- Bert Plus likes this
#33
Posted 16 November 2012 - 12:52 PM
#34
Posted 16 November 2012 - 01:04 PM
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#35
Posted 16 November 2012 - 03:21 PM
Hi Jake,
The 4.3 firmware is not yet available. When it is available, it'll be posted in the beta-section of this forum:
http://forums.netdui...re-and-drivers/
Thank you for the info.
#36
Posted 02 February 2013 - 10:02 PM
#37
Posted 12 March 2013 - 07:44 AM
Thanks DaveVanderWekke and Chris for your earlier posts on the USB driver.
I thought I had bricked my very first Netduino Plus when I ran into exactly the same problem DaveVanderWekke describes.
After flashing the firmware I never got a succesful 'Signature check' message but consistently got something like 'sig ch'.
Also, I wasn't able to change the network configuration and instead got a timeout or 'Device has old or unsupported configuration' message.
Changing to the MF USB drivers solved it and I'm up and running again!
#38
Posted 10 July 2013 - 01:12 AM
To install the .NET Micro Framework v4.2 SDK
[*]Install the .NET Micro Framework SDK v4.2 (QFE2)
[*]Install the Netduino SDK v4.2: 64-bit or 32-bit
[/list]To upgrade to the .NET Micro Framework v4.2 SDK
[*]Uninstall the Netduino SDK v4.1
[*]Uninstall the .NET Micro Framework SDK v4.1
[*]Install the .NET Micro Framework SDK v4.2 (QFE2)
[*]Install the Netduino SDK v4.2: 64-bit or 32-bit
[/list]To upgrade a project (for Netduinos flashed with .NET MF 4.2)
[*]Click on the Project menu, then click on "<ProjectName> Properties" in the menu.
[*]Select the "Application" tab
[*]Select the desired "Target Framework" in the pull-down (either v4.1 or v4.2)
[/list]If you try to deploy a .NET MF 4.1 project to a .NET MF 4.2 board (or vice-versa), Visual Studio will tell you that the assembly libraries' versions do not match.
Compatibility with .NET MF 4.1 projects and boards
The new SDKs will work with Netduinos flashed with .NET MF v4.1.
New AnalogInput and PWM classes -- backwards-compatibility notes
.NET MF 4.2 adds new AnalogInput and PWM classes. To use the earlier SecretLabs' AnalogInput and PWM classes, add the respective assembly as a reference in your project and use the full "namespace + class name" of the classes.
For instance, to use SecretLabs.NETMF.Hardware.PWM (instead of the new Microsoft.SPOT.Hardware.PWM class):// add SecretLabs.NETMF.Hardware.PWM.dll as a reference to your project.// PWM pwm = new PWM(Pins.GPIO_PIN_D5);// becomes...SecretLabs.NETMF.Hardware.PWM pwm = new SecretLabs.NETMF.Hardware.PWM(Pins.GPIO_PIN_D5);Chris
Hello!
Chris I'm just returning to the Netduino families, and, ah, as it happens I recall that I did indeed succeed in flashing the appropriate boot engines to both devices, and the equally appropriate firmware sets to them. In starting up all over again I installed those sets. Is there anything else I need to do? [Update: The available downloads for N2 boards are not appropriate for N1 boards. And that includes the Mini.]
Chris for those of us who still use the N1 family of boards, but not the N+ series would need the SDK for 4.2 but not the 4.2.20 one. The 4.2 one needs to be put back up, or complete instructions for working out how to have an original board both the N1 and the Mini respond to the 4.2.20 one, and that includes the bootloader we flash to our boards.
Edited by Dr Who, 10 July 2013 - 03:17 AM.
Doctor Who
"This signature does not exist!"
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users