Bricked my Netduino Plus?
#1
Posted 11 November 2012 - 06:05 AM
I wanted to hook up my Netduino Plus, so I had a brilliant idea to upgrade it to .NET MF 4.2 with the info on the following link: http://wiki.netduino...ep-by-step.ashx
I connected the pad to 3.3V, which apparently reset the Netduino somehow, because when I power cycled it, it came up in the Windows Device Manager as an Unknown Device. I tried to update its driver to no avail. I also followed the wiki page to try using the "GPS Connect" device driver, but that didn't work either. When I plug in the Netduino, I get the three fast low-pitch beeps.
Did I brick my Netduino Plus? Is there anything I can do to get it to update so I can switch between the Plus and Plus 2 easily?
#2
Posted 11 November 2012 - 08:09 AM
When you connect 3V3 power to the ERASE pad, it erases everything off your Netduino Plus 1. At that point you need to install Atmel SAM-BA (see the firmware reflashing instructions) so that you have an Atmel bootloader driver for your board.Did I brick my Netduino Plus? Is there anything I can do to get it to update so I can switch between the Plus and Plus 2 easily?
Once you flash TinyBooter via SAM-BA, you'll see your Netduino Plus in MFDeploy again.
Does that help? The operation should be pretty straightforward once we get past the first steps here.
Chris
#3
Posted 11 November 2012 - 06:25 PM
Thanks for the reply, and the clarification. I did already download and install the Atmel tool, but when I launch it, I can't select any hardware. I had assumed this was because the Netduino comes up as an unknown device now. Basically, in SAM-BA, all I can click is Exit -- everything else is grayed out. So I thought that my next step would be to get the Netduino Plus to be recognized by the OS as a serial port. BTW, I'm running Windows 7 x64.
Thanks!
Hi Dave M.,
When you connect 3V3 power to the ERASE pad, it erases everything off your Netduino Plus 1. At that point you need to install Atmel SAM-BA (see the firmware reflashing instructions) so that you have an Atmel bootloader driver for your board.
Once you flash TinyBooter via SAM-BA, you'll see your Netduino Plus in MFDeploy again.
Does that help? The operation should be pretty straightforward once we get past the first steps here.
Chris
#4
Posted 11 November 2012 - 06:34 PM
#5
Posted 11 November 2012 - 06:36 PM
SAM-BA is a great tool, but it can be finickyVery odd. I found another post here from a person that had the same problem. I tried re-erasing about five times, and the last time it actually recognized the hardware when I plugged it in! (as GPS Camera Detect). I'll continue with SAM-BA now.
Chris
#6
Posted 11 November 2012 - 06:51 PM
And it looks like my memory was bad. The Netduino Plus, running in a tight loop, could toggle the LED at about 6.25kHz, vs. the Plus 2's 13.9kHz.
SAM-BA is a great tool, but it can be finicky
Chris
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users