hookedup

Thanks again for providing the files to load directly. I was able to erase and flash the bootloader (once moved to XP) and reload the firmware, which is a major step forward. Still working out some odd errors in loading the hex files and when using the bit banger runtime - may be missing something still. I will provide more details on the errors when I into it again unless it becomes part of the base firmware by the time I get back into it, in which case I'll report back on progress using that. Thanks for all the help from you and the netduino team in providing a solid base to work from.

Hookedup: if you want to flash this you will need to reflash your bootloader (tinybooterdecompressor.bin is included) and then flash the hex files included.
-(e)

Thank you very much for providing the files and for contributing such a great updates. I am super busy for a couple of days but will work to do the updates and test usage asap.

I enjoy working with netduino and have high hopes that using your code will get me over the minor bump in the road to doing really cool stuff with the netduino

Thanks Chris. I will put one on back order. Which one do you recommend ordering from to get the fastest delivery?

My experience with MakerShed and USPS Priority Mail (FAST)
I added my name to the "notify me when in" list from MakerShed. I ordered the day I got the message which was a Friday. It made it all the way from Cali to Florida and was in my mail box on Monday.

Shipping method was "Priority Mail Small Flat Rate Box - 6.95 shipping", which I think was the lowest price shipping on the page .. but was listed all the way at the bottom of the list.

Those links are pretty daunting for someone coming new into this technology. After reading those links am pretty sure I have no desire to go native for some time. That said, the current method of direct pin control is too slow. I tried FEZ Panda and it has the same slow pin speed, I guess it is the .NET layer. This seems very similar to standard pin control in the arduino being too slow, in which direct port access helps at the cost of portability. This bit banger driver seems to be a great solution for this problem. Is there is a way to put up a test firmware with big banger included? That would help see if bit banging will do the trick. I would think having bit banger built in would be best case. Is there a case to not include bit banger in the base outside firmware size? Thanks for building and posting bit banger, good to know there is a way to have fast pin access like direct port access in arduino.

You may want to have a look at the following two articles Using Interop in the .NET Micro Framework V3.0 and Your first interop project walkthrough to get the overview and step-by-step instructions how to write native drivers for .NET Micro Framework. Also, the Porting Kit documentation contains detailed description (Adding Features to the .NET Micro Framework by Interoperating with Unmanaged Code) and introduction of the build system. There are also threads in this forum that discuss various firmware build issues and what is needed to use GCC 4.4 compiler.

Thanks for the links.