If you would like step-by-step instructions on how to use SAM-BA, I can write some up here... But basically, you [a] enable boot from flash; [b] enable flash access; [c] flash the TinyBooterDecompressor.bin file to your Netduino. Your erased Netduino will show up as a virtual serial port; you may need to manually point it to the driver in the Program Files > Atmel SAM-BA > Drivers directory.

If you would like step-by-step instructions on how to use SAM-BA, I can write some up here... But basically, you [a] enable boot from flash; [b] enable flash access; [c] flash the TinyBooterDecompressor.bin file to your Netduino. Your erased Netduino will show up as a virtual serial port; you may need to manually point it to the driver in the Program Files > Atmel SAM-BA > Drivers directory.

Chris

I may need a step by step write-up. Basically, I attempted to do what you said, but didnt have much luck. I downloaded SAM-BA, and I got my Netduino to come up using COM4. I selected at91sam7x512-ek when prompted to select my board. I then selected the script "Boot from Flash (GPNVM2)" then "Enable Flash Access". Next I selected the TinyBooterDecompressor.bin file needed from "Send File Name" area, and sent the file. I was then prompted with "Do you want to lock involved regions(s) (0 to 2)"..I didnt know what to select here so I clicked yes. I received the following output:

I may need a step by step write-up. Basically, I attempted to do what you said, but didnt have much luck. I downloaded SAM-BA, and I got my Netduino to come up using COM4. I selected at91sam7x512-ek when prompted to select my board. I then selected the script "Boot from Flash (GPNVM2)" then "Enable Flash Access". Next I selected the TinyBooterDecompressor.bin file needed from "Send File Name" area, and sent the file. I was then prompted with "Do you want to lock involved regions(s) (0 to 2)"..I didnt know what to select here so I clicked yes. I received the following output:

I then tried to redeploy the Netduino firmware via com4 in MFDeploy without luck.. Recieved the error "Error: No response from device"

Scratch that last request chris... i got it to work... Sorry about that. I will write up a step by step process if you like to save you the trouble...I am sure there are going to be some people like me that are new when it comes to this stuff

Scratch that last request chris... i got it to work... Sorry about that. I will write up a step by step process if you like to save you the trouble...I am sure there are going to be some people like me that are new when it comes to this stuff

2. Download the latest Netduino firmware, and the TinyBooterDecompressor_v4.1.0.1.zip file. (Currently both are located Here.)

3. (**WARNING.. no turning back after this point.) Using a jumper, Connect the 3V3 power header to the ERASE pin (gold pad directly underneath digital pin 0) for about 2-3 seconds. After doing this, disconnect the Netduino from your PC.

4. Plug in your Netduino's usb cable back into your pc. At this point for me, windows vista searched automatically for a driver and found the right one for a virtual serial port. If yours does not do this, you may need to point to the driver file in the Program Files > Atmel SAM-BA > Drivers directory.

5. Run SAM-BA. Select the COM port that your device is connected to. In my case this was COM4. Select AT91SAM7X512-ex from the dropdown.

6. When in SAM-BA, you will need to run the following two scripts first: [a] enable boot from flash; [b] enable flash access.

7. Next you will need to flash the TinyBooterDecompressor.bin file to your Netduino. At this point you are asked "Do you want to lock involved regions(s) (0 to 2)".." I wasnt sure what to pick here but I believe I selected no. (Chris Walker confirmed in a later post that "NO" should be selected.) Once this has been completed (only takes a few seconds), you are done flashing the TinyBooterDecompressor.

8. At this point you can unplug the USB cable connecting your computer to your Netduino, and then plug it back in. Now we can readd the Netduino firmware.

7. Next you will need to flash the TinyBooterDecompressor.bin file to your Netduino. At this point you are asked "Do you want to lock involved regions(s) (0 to 2)".." I wasnt sure what to pick here but I believe I selected no. (Can anyone confim the correct option here?)

I may of missed it when reading but at what point do you UNDO what you do in step 3.

You only need to power the ERASE pad (from the 3V3 header) for about 220 milliseconds. We recommend that you plug a jumper wire into the 3V3 power header and then touch the other end to the ERASE pad. Just hold it there for a second or two...and then unplug and reconnect your Netduino.

You only need to power the ERASE pad (from the 3V3 header) for about 220 milliseconds. We recommend that you plug a jumper wire into the 3V3 power header and then touch the other end to the ERASE pad. Just hold it there for a second or two...and then unplug and reconnect your Netduino.

Thanks, (I don't even have a netduino yet) wanted to make sure the steps were clear in case I had to do this. So #3 says connect but it's more of a touch it to the erase pad for a couple of seconds to make sure it's clear of everything.

How did you do that. Could you share a tip so it won't happen to us too?

Thanks

If you can believe it, I had a jumper plugged into 3.3v when I set my Netduino down on my table (Bad practice for sure...) and the jumper lead just happened to touch the erase pin long enough to erase it. 1 in a million chance. lol.

If you can believe it, I had a jumper plugged into 3.3v when I set my Netduino down on my table (Bad practice for sure...) and the jumper lead just happened to touch the erase pin long enough to erase it. 1 in a million chance. lol.

How funny. And to think that we made sure to make the ERASE pad small and to put it in a corner (and to require 220ms+ to erase it).

I guess this is another testament to open source and to having firmware that can be manually installed. Glad it's working well for you, and thanks again for writing up such nice step-by-step instructions for the community.

How funny. And to think that we made sure to make the ERASE pad small and to put it in a corner (and to require 220ms+ to erase it).

I guess this is another testament to open source and to having firmware that can be manually installed. Glad it's working well for you, and thanks again for writing up such nice step-by-step instructions for the community.

Chris

Yeah, I couldnt believe it myself. I think its a great feature on the board, and I wouldnt change a thing about it.. Also, I might have never learned how to use SAM-BA if this didnt happen. Good stuff, and good learning. So far I am loving everything about the Netduino.

As for the Write-up, no problem at all. If it wasn't for good posts on forums, and the huge amount of information online, I would have had to go to college. lol

"The Internet - Saving you thousands of dollars in tuition since 1973."

4. Plug in your Netduino's usb cable back into your pc. At this point for me, windows vista searched automatically for a driver and found the right one for a virtual serial port. If yours does not do this, you may need to point to the driver file in the Program Files > Atmel SAM-BA > Drivers directory.

...

Could it be that Atmel has no drivers for Windows XP 64-bit? Or any 64-bit OS for that matter?
Because when I try to manually point it to that directory, Windows XP 64-bit says that it "couldn't find the necessary software. make sure that the driver works with x64-based systems."
Is there any other driver I could install maybe? Because, it sounds like the COM port over USB could be something generic.

Could it be that Atmel has no drivers for Windows XP 64-bit? Or any 64-bit OS for that matter?
Because when I try to manually point it to that directory, Windows XP 64-bit says that it "couldn't find the necessary software. make sure that the driver works with x64-based systems."
Is there any other driver I could install maybe? Because, it sounds like the COM port over USB could be something generic.

Just FYI...you can also reflash an erased Netduino via pins D0/D1/GND (using a 3V3 USB to TTL cable or an RS232 shield).
If you press F8 during boot and disable driver signing, does that allow you to load the Atmel drivers.
I'll chat with Atmel and see if there's any way to sign their drivers. Not a quick process, but something we'll start looking at.
Chris