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.
Running Windows 8 and updating my Plus from 4.1 to 4.2. I managed to get through all the steps in about 15 minutes. Had MFDeploy showing me the new firmware. I was so happy with myself. I then went to deploy my program from VS to the netduino, and that's when the fun started. The deploy started and then was hanging. To make a long story (2 hours) short, I managed to get at least 75% of the errors in this thread as I went through debugging the problem. I'm finally able to deploy. A few hints... Rebooting my PC between device manager changes made a huge difference. Things that wouldn't work magically did after a reboot (obviously since this is Windows). And when unplugging the netduino and plugging it back in, I found i needed at least a 10s pause, otherwise it would show up as an unrecognized device. This led me to perform all sorts of unneeded steps. So throw in some reboots, and count to 10, slowly.
Thank you for your post and your feedback.
If you manually switch to the legacy MFUSB drivers, do things work better for you? The MFUSB drivers seem to work great on most machines...but on the few where the two don't agree, reverting to the legacy drivers tend to make things better.
I have a N+ and can't find the Netduino during the "http://wiki.netduino...ep-by-step.ashx" after flashing to "Enable Flash access".
...
At this moment the N+ led stays on, but I can't reach the device to update/flash to any new or old firmware.
After "enabling flash access", do you then flash the TinyBooterloaderDecompressor.bin file? And verify that it was written correctly?
If yes, what does your Netduino appear as in Device Manager?
Hi Toine db,
After "enabling flash access", do you then flash the TinyBooterloaderDecompressor.bin file? And verify that it was written correctly?
If yes, what does your Netduino appear as in Device Manager?
Chris
Tnx for the response.
I had selected the TinyBooterloaderDecompressor.bin to Flash and pushed "Execute".
But I have never seen the 'lock region' question.... (waited for 10 minutes)
The device is now in the device manager as "unknown device".
But I have tried it with winusb or mfusb and it gave error code 10, could not start device and not visible at MFDeploy and SAMBA.
I had selected the TinyBooterloaderDecompressor.bin to Flash and pushed "Execute".
But I have never seen the 'lock region' question.... (waited for 10 minutes)
The device is now in the device manager as "unknown device".
But I have tried it with winusb or mfusb and it gave error code 10, could not start device and not visible at MFDeploy and SAMBA.
Could you please erase and re-flash the board one more time? But this time, do a few extra things?
After executing "enable flash", execute "erase all flash". Then "set flash as boot" as before.
After starting the firmware flashing, be careful not to switch windows. It's possible for the status box and questions to appear _behind_ the current window.
BTW, just to verify: are you using the latest SAM-BA (2.12 + patch)?
Hi strent,
An update with OneWire will be published in mid-December. Hopefully .NET MF 4.3 will be ready to go too. It'll be a big month for firmware updates.
Chris
Could you please erase and re-flash the board one more time? But this time, do a few extra things?
After executing "enable flash", execute "erase all flash". Then "set flash as boot" as before.
After starting the firmware flashing, be careful not to switch windows. It's possible for the status box and questions to appear _behind_ the current window.
BTW, just to verify: are you using the latest SAM-BA (2.12 + patch)?
Chris
Hello Chris,
Sorry for the late response and thank you very much for your help.
It finaly worked for me, I don't know exactly what went wrong.
The only thing I missed was the Patch for sam-ba, after I patched sam-ba all worked fine.
It looks like I may have bricked the Netduino Plus during the update:
1) Erased via the gold contact
2) Using SAM-BA I deployed new bootloader
3) Using MFDeploy I uploaded new FW - all was fine, all the pings were OK
4) I tried to this step: b. Select the Target > Configuration > Networking menu. Re-enter your IP address settings and MAC address.
---
it ended with an error and after power cycle, blue LED wouldn't come on, now I have no ping from device, I can still erase and use SAM-BA just fine to upload new bootloader, but after a power cycle, no ping in MFDeploy. Erase all flash does not help me. Blue LED is on.
Is it possible that corrupted network settings persist and prevent the device from functioning properly? It still identifies as Netduino in device manager, but that's about it. I can't upload FW to it. Is there something I can do to make it work again? I'm pretty sad now.
Hi, I followed the procedure to load the latest bootloader into my netduino plus 1 using sam ba. but when i run mfdeploy and select USB i don't see the netduino in the select box. It used to come up when it was a 4.1. Any ideas?
4) I tried to this step: b. Select the Target > Configuration > Networking menu. Re-enter your IP address settings and MAC address.
With .NET MF 4.2, you need to put the board into TinyBooter mode to change the network settings. To do this, press and hold the pushbutton while plugging in the Netduino Plus to your PC. Then release the pushbutton and change the network settings.
In TinyBooter mode, you can also re-deploy the ER_CONFIG and ER_FLASH files (which should get your board booting again).
Does that help?
Chris
Hi, I followed the procedure to load the latest bootloader into my netduino plus 1 using sam ba. but when i run mfdeploy and select USB i don't see the netduino in the select box. It used to come up when it was a 4.1. Any ideas?
Did you install the latest Netduino 4.2.2 SDK? The Netduino 4.2 firmware uses WinUSB instead of MFUSB drivers by default. These drivers are included in the 4.2.1+ SDKs.
You will also need to make sure you're running the NETMF 4.2 QFE2 SDK or newer. If in doubt, uninstall both SDKs and then re-install them from the links on the Downloads page.
Does that help?
Chris
It worked but naturally, I lost the SD card too so I guess there's a better way after all.
Does anybody know how to disable networking on the Netuino 1 plus?
You can add back in the SD support using the SecretLabs.NETMF.IO assembly. Call StorageDevice.MountSD and be sure to pass in the "card inserted" pin. That should put you on par with Netduino Plus 1--minus networking
Chris