24 replies to this topic

[CW2]

For my point of view, OneWire issue is not related to processor speed. It's more related to C# latency inducted. So, the solution, like other vendors, is to provide a OneWire feature in native code and a library in C# to use it.

The processor itself is surely fast enough for 1-Wire, at this time the problem is with native (C++) code generated by GCC, but it works. Please note there are several abstraction layers in TinyCLR, to handle hardware platforms differences - typical architecture tradeoffs apply here. There is always possibility to write one long asm { ... } block (or whatever is the compiler's syntax).

I use onewire with a AVR 328p at 8 Mhz !!!

I use AT89LP4052

[Szymon]

The processor itself is surely fast enough for 1-Wire, at this time the problem is with native (C++) code generated by GCC, but it works.

It works on Arduino so it would be weird if Netduino's much superior CPU couldn't handle it :-)

[Chris Walker]

Based on what you folks are saying, I don't see any reason why we couldn't integrate a native driver for OneWire into the core Netduino firmware. CW2 is working on one--and we've offered to open up any capabilities necessary to do that (open drain configs, etc.)

[segu]

Based on what you folks are saying, I don't see any reason why we couldn't integrate a native driver for OneWire into the core Netduino firmware. CW2 is working on one--and we've offered to open up any capabilities necessary to do that (open drain configs, etc.)

At least OneUser (me) will be VERY VERY happy . By the way more IO be good, always there is a project that needs more pins than available

[Coding Smackdown]

I'd be another user that would be very happy with One Wire support baked in to the firmware. There are a lot of cool devices out there that use the One Wire protocol. Since they can all be accessed over the same one wire interface it sure helps out a lot when you have a bunch of devices you want to talk with but don't have a lot of GPIO pins. I'd even be interested in seeing both master and slave type of capabilities, so the Netduino could control device and be controlled by a PC or other device. If you need help, I'm willing to lend a hand.