I’ve run into a wall attempting to upgrade my Netduino Mini from NetMF 4.1 to 4.2.
I've learned that the bootloader will need to be updated before upgrading from NetMF 4.1. I learned I’ll need to use SAM-BA to install the bootloader, and I can only flash the Mini over its RS232 serial interface (not its TTL interface)
The theory’s great, but things seem to come unstuck for me when I try to use SAM-BA.
I followed these setup steps:
- Completely reset the Mini with 5v to the tiny reset pad for ~1 second.
- My laptop does not have native serial RS232 so I’ve set up for the bootloader flash with a USB->RS232 FTDI breakout board. Board RX connected to Mini TX. Board TX connected to Mini RX. Board Gnd connected to Mini Gnd. My setup looks pin perfect to Frode’s.
- Powered up the Mini with 9v to pin24 and Gnd to pin23. The obligatory breadboard LED glows to confirm that I had indeed provided power to the device
- Checked all the COM settings were good, 115200 8 N 1
- Run SAM-BA 2.15, selected the FTDI-presented COM port (the only COM port listed), selected AT91SAM7X512-EK, and hit Connect
There’s a flurry of TX/RX traffic on the FTDI LEDs and then SAM-BA returns a dialog titled “Invalid Chip ID”. I get the same dialog when any AT91 device is selected in step 5.
Thinking that my Mini could be dead, I lifted it from the ZIF socket and tried again – checking the RX/TX LEDs. This time there was no RX traffic, which I’ve interpreted as meaning the Mini is alive and can respond to SAM-BA when I click the Connect button.
I’ve googled until Chrome shows every relevant link in purple (been there, read that!).. so now I’m kinda stuck.
I’d be stoked to hear anyone’s wisdom on this topic. Thanks in advance!