jefe

Stefan, Your suggestion did the trick! Once I loaded the SAM-BA supplied driver, I used SAM-BA to reinstall the boot loader, then I used MFDeploy to load the firmware, and it all works now. You were right. I did, in fact, do a HW erase and was firmware-less. But, I guess I still don't know why the SAM-BA driver installed but the netduino one did not. (Embarrassingly enough, I wrote the first WinNT Nvidia device driver (way a long time ago), but I was unable to figure this out). Thank you so much -- I really appreciate your help.

Hi jefe,

Here's a full set of instructions from the Wiki:
http://wiki.netduino....ashx?HL=sam,ba

Let me know if you need anything else!

Chris

Wow. Thanks, Chris. Perfect! I should have looked harder for this myself. I'll let you know how it works out.

Chris, Could you expand on using SAM-BA to deploy the bootloader or point me to some other links that describe SAM-BA's usage with the Netduino? I have used SAM-BA before on a SAM9260 device, so I'm familiar with it. But, it requires a board configuration file and a serial port spec. I used Atmel's dev board config file and a USB device (the CDC driver that I linked to ttyUSB0) for the 9260 board. But when I connect the Netduino to USB, I don't see any new USB devices show up, either CDC or direct USB. Once I do find a connection to specify, I expect that I will write the bootloader hex file to address 0x100000.

I found that SecretLabs.NETMF.Hardware.Netduino.dll and Microsoft.SPOT.Hardware.dll also had to be present in the development directory (i.e. the one that contains the Makefile).

I had to use "gitk" as the package name for git, under Ubuntu 10.10.