cjc

Hi cjc,

There are several pins with multiple features. Actually pin 4 is the only one which hasn't got special features (yet!). For a complete list, see http://www.netduino....duino/specs.htm

SPI is also explained a bit at http://wiki.netduino.com/SPI.ashx

Thanks Stefan - now it makes sense. I was reading "SPI_Devices.SPI1" as a single pin (hadn't decided if it meant 11 or 13...), but now I get that it is the 3-pin "set" of 11, 12, 13 - thus declaring pin 12 as "used". I imagine that using UART1 or UART2 or I2C devices will have a similar behavior.

Cheers,
Corey

Thanks Chris - sounds great. I am also realizing that since you release the source, if I get stuck between firmwares I could always roll my own - allowing me to make the tough decisions about features/memory tailored specifically to my needs. Cheers, Corey

If I remember well the D12 is used as SPI input, thus cannot be used as general purpose pin. That when you're using the SPI, however.
Cheers

Thanks Mario - I suspected that might be the case but I haven't run across any documentation that indicates that is how things work. (is this also the case for the other special purpose pins??? when does it happen?) Hoping that someone can explain the behavior definitively. I thought that because Pin 12 isn't actually declared for use in the app, you could use it for general purpose...

Cheers,
Corey

Hi tibel,

We're syncing 4.1.1 and 4.2. So they'll probably become "final" at the same time (most likely in 30-60 days), although we may ship 4.1.1 a bit earlier.

The difference between the two will be that 4.2 has new features (StringBuilder, RegEx, Visual Basic support, more bugfixes, etc.) Once 4.2 is released, the next releases will be 4.2.x (i.e. we won't update v4.1.1 unless there's a critical bugfix).

Chris

Currently I am using the 4.1.1 1-wire version of the firmware. On the 1-wire alpha thread it was stated that 4.1.2 was the target to merge those features into the trunk. Granted alot has happened since that statement (e.g. MF 4.2) so I was hoping to get a feeling for when the 1-wire code will become a main part of the firmware. I would love to have access to Stringbuilder and RegEx. and native 1-wire too!
I am hoping that the release of 4.2 in a month or two will include the 1-wire code, but haven't seen a clear statement of that intent yet...

Thanks,
Corey

P.S. as a new user I find it a little confusing with all the versions floating around (1-wire, 50% less network memory, 4.1.1 beta, 4.2 beta, mini, plus, standard, banana peeling version, etc.) a thread with all the various firmwares linked to (Secret Labs and user rolled) with the various proper caveats (e.g. this is a one-off, this is not supported, etc.) and a road-map of rough timelines and feature sets would be awesome to have and save on confusion...