skyjumper

Good evening, can you please tell me how you did to configure NUT/OS to be compatible with netduino.

Best Regards,

I would love to know this as well. I know its an old thread, but I just figured I would bump it ;-)

In my own tests a while ago, I determined that the C# code runs roughly 100 to 1000 TIMES slower than the equivalent C++ code. The bottom line is that it is very slow but you get an excellent development environment and a managed language that makes coding up complex tasks much easier and faster, as long as you don't need super fast execution.

Not sure whether that helps or not.

I guess I could always throw more hardware at it! What's nice about .NET is the threading. It would be very easy to code up my custom web server. If I want to do this as native I probably need a threaded RTOS.

Netduino does not expose the JTAG pins of the CPU but as you can upload new firmware via serial, it would surprise me if you cannot do this via AVR, especially since AVR is an Atmel development tool.

Found this howto on programming using AVR and serial programmers are mentioned but could be they are merely serial interfaces for JTAG headers:
http://www.ladyada.n...rogrammers.html

If I'm not mistaken Secret Labs used/use AVR when porting tinyCLR.

See also this thread discussing toolchains for native programming of the Netduino:
http://forums.netdui...ools-do-i-need/

Thanks very much! That thread is very interesting. I'm glad I'm not the only one who is overwhelmed by all this ARM stuff.

AVR Studio 6 seems to support Atmel's Mega, XMega and Cortex M offerings. That last part I'm not so sure about, "Cortex M." I think that means the SAM7x is not supported since its not listed. Back to Wikipedia I guess... I gotta learn more about the ARM variations.

Is it too late to say AYE to SPI slave mode? For what its worth, I think an Arduino, Netduino or anything similar is much more useful if it can act as an I2C or SPI slave device. As someone pointed out, UARTs are a limited and precious resource, while I2C and SPI are much better for collecting data from sensors.

The biggest reason that .NET MF probably doesn't have support for SPI Slave natively is that most SPI slaves seem to need to respond to an incoming request within the same SPI transaction and typically within 1 SPI clock cycle...and .NET MF is not real time. If you're just wanting to send data to the Netduino, that should totally be possible.

Chris, about the real time constraint, is it possible to write an ISR to handle the incoming data from SPI? Your earlier note seems to imply that the code would have to poll the SPI registers for incoming data. I'm okay with code and micro processors, but I know nothing at all about .NET.