Dan Watts

Chris, I tried using D1 as an Output Port. The reboot occurs if I set its state to false, but not if I set its state to true. So, it looks like the proper description of my problem would be "Setting D1 low causes reboot". Not really a COM port or bootloader problem after all. Probably still an obscure result of hardware damage - maybe I managed to fry the internal resistor on that pin? Dan.

Hi Chris, Thanks for the quick reply. (And on a Sunday. And on Boxing Day here in Canada, eh). Yes, the problem does occur with just the USB cable plugged in - no DC power and nothing inserted into any header pins. It also occurs when just on DC power, with no USB cable. I noticed that if I plug in the Netduino with MFDeploy running, then Ping the Netduino, MFDeploy logs the "COM1 Opened" Debug.Print message. Also, the blue LED flickers every 5 seconds or so. I suspect that the Netduino is repeatedly booting, hitting that Write statement for COM1, then rebooting. My original guess about the blue LED indicating the bootloader being run might be off the mark. I'll try your suggestion about reflashing TinyBooterDecompressor once I figure out how to use SAM-BA. But for now, off to do some Boxing with the family. Dan.

Seeed Studio's Grove shield and accessory components work well. This is Seeed's follow-up to the Electronic Bricks product line, which as others have mentioned also works well with the Netduino.

The only Grove component I haven't tried with the Netduino yet is the LCD. I've written about my experiences with the Netduino and Grove here.

Dan.