Btw Chris, I notice you respond to virtually every post on this newsgroup. That is a lot of time and effort!! I for one really appreciate that!
I wish I knew something about compilers and especially ARM back end code generation. Seems like a 50% reduction (if some of the other posts I read are accurate on sizes) in code size would be pretty low hanging fruit
Anyway, thanks for the response, I hope they get gcc up to speed soon. In the mean time, I guess living without TinyBooterDecompressor isn't such a big deal. I will have to try that first.
There is work happening behind the scenes right now, trying to get the latest versions of GCC working...which will hopefully free up some space.
You could also maybe get rid of TinyBooterDecompressor entirely, to save a bit of space. This would mean that you'd need to erase your Netduino and use SAM-BA if you needed to erase/upgrade your firmware...but it would save another 40KB of flash space (useful for the larger GCC code).
On the USB note...you can actually make your Netduino look like many USB devices as well. It's a bit advanced, and it generally requires using serial for debug and powering via an AC power adapter, but many users do it (including us...our test jigs use Netduino in that mode).