Thanks Mark.
Little did I know that amount of stress and stupidity I would apply to the problem.
Long story short, my USB cable to the Netduino was flakey and would only work intermittently. I changed cables and ports and all is well.
However stupidity kicked in:
I made sure I got the correct Yagarto, being very careful to browse to the "older" version. However, SourceForge in it's infinite wisdom ensure that the "current" version is listed first and highlighted - so I got the wrong gcc build, which totally occupied several hours of my day trying to figure out why it didn't work.
My first flash didn't work and I was sure I bricked the board. I was soo afraid of doing that. However, once I knew that the board was not working, it sorta relieved my stress for trying different things.
DfuSe Demonostrator constantly crashes (mostly when doing 'reads', and I was using 3.03. However, when trying to downgrade to the 3.02, it wouldn't work at all. So, now I'm back to the 3.03.
I pulled the 4.2.2.2 DFU and tried to flash that. It would sometimes work and be seen by MFDeploy, but rarely twice in a row. After my first successful operation with MFDeploy, it would not reconnect for anything. I would have to either reflash, reboot, or un-plug/re-plug.
Finally, decided to change USB cables, the computer port and also remove all other USB devices ( I had two phones charging as well ).
Then, and only then I started to have success.
I've managed to reduce the precision of the analog line from 12 to 6 (or so .NET reports it as such) But seeing the same time latencies. I'll have to work at it a bit. I'm probably going to do a lot of work on the analog channels - and do a bunch of reading.
But, it is nice to know I can change the firmware a bit, by actually having done it, as opposed to reading that it can be done.
However, here's a question: Is there any place to commit changes?