Netduino Plus Firmware v4.2.0

Hi Igor,


The ADC precision is 10-bits. There is just the one option.

Chris

Thank you Chris,


My question was due to the fact the new AnalogInput class constructor on netmf 4.2.0 has an overload that you can specify precision. So, if you do not use it, what is the default value? This seems not to be detailed on MSDN.

Thank you for the answer!

Igor.

Hi Igor,

My question was due to the fact the new AnalogInput class constructor on netmf 4.2.0 has an overload that you can specify precision. So, if you do not use it, what is the default value? This seems not to be detailed on MSDN.

If you don't specify the precision, it defaults to 10 bits on Netduino Plus. I believe it defaults to 12 bits on the Shield Base.

Chris

Just updated to this version of the firmware. Lots of problems getting Visual Studio to recognize the ND+. Basically, it will recognize it the "first" time, but if the device reboots, gets unplugged, etc, then Visual Studio will no longer recognize it (it does not show up under the "USB" device selection in project properties). Only way I have found to workaround it: Go to Device Manager, right click on the Netduino Device -> Update Drivers. Select "Browse my computer for driver software." Then "Let me pick from a list of device drivers on my computer." Select the Netduino device that shows up there and hit next. That (I think) is forcing a reinstall of the drivers. Any other selection just results in Windows telling me I already have the best drive installed, and does not fix the problem. Nothing else I have tried fixes it (including power cycling the ND+ again). This is on Windows 7 x64, Visual Studio 2010.

Hi Chris,

Could you please try upgrading to the .NET MF 4.2 QFE2 SDK and the Netduino 4.2.0.1 SDK on the downloads page?

You'll need the new WinUSB drivers for the device to work once TinyBooter is flashed.

I tried to install both packages, but they told me that they are already installed (that could be right, I reinstalled my system not long ago) - but now I looked in my installed programs and there are these versions listed:

• Microsoft .Net Micro Framework SDK 4.2 (QFE1)
• Netduino SDK v4.2.0 (August 2012)

After manually uninstalling them and installing the newest version these versions are listed:

• Microsoft .Net Micro Framework SDK 4.2 (QFE2)
• Netduino SDK v4.2.0 (August 2012)

Now I redeployed the bootloader and the firmware and it seams to work.

Thanks!
Stefan

OneWire is still not available in this new version. Why? Is this expected in a future release?

Hi finizi, We're working with CW2 to add his enhancements to the NETMF OneWire drivers (and/or keep compatibility with his current classes). It's quite a bit of work, but we're hoping to have a special build of the 4.2 firmware with OneWire fairly soon. Chris

Hi finizi,

We're working with CW2 to add his enhancements to the NETMF OneWire drivers (and/or keep compatibility with his current classes). It's quite a bit of work, but we're hoping to have a special build of the 4.2 firmware with OneWire fairly soon.

Chris

Thank you.

I, too, would like to have the OneWire functionality returned.

Doug

but until then, you are stuck with <=2GB cards (which are still widely available and cheap btw!)

Uncommon and getting rarer where I live. Alas, before I could even think about fixing it myself I would have to

• Learn to build the framework.
• Learn to deploy the framework.
• Learn how SDHC works.
• Learn how the <2G driver works.
• Figure out what is needed for larger cards.

I wish I'd known it would take so long, I would have started this learning process immediately.

Uncommon and getting rarer where I live.

I agree... I have had a hard time finding 2gig cards. I am sure I can probably find them online, but if I want to produce my ND+ based product and sell it without the SD and allow the customer to buy their own SD Card, it needs to support larger than 2gig. It really is embarrassing for the ND+ to not support anything larger. My video camera, trap camera, voice recorders and many other tools I use for Paranormal Investigation all support large cards (I even have 32gb in some).

How hard is it to get this problem resolved once an for all. This has been one of my holdups on continuing with my project as I might need to reconsider the use of the ND+ in my product and go with another type of board simply for the SD support.

Throwing my hat into the ring - I also agree - no local stores to me sell 2Gb Mini/Micro SD. 2Gb in standard size, sure..

Hi guys, I completely understand your problem and I wish SDHC would be supported already. But 2GB µSD cards are available through a few channels: http://www.amazon.co...=A15S1YSPRYIXOQ https://www.sparkfun.com/products/8163 http://dx.com/s/micr...tm_rid=85138133

I agree... I have had a hard time finding 2gig cards. I am sure I can probably find them online, but if I want to produce my ND+ based product and sell it without the SD and allow the customer to buy their own SD Card, it needs to support larger than 2gig. It really is embarrassing for the ND+ to not support anything larger. My video camera, trap camera, voice recorders and many other tools I use for Paranormal Investigation all support large cards (I even have 32gb in some).

How hard is it to get this problem resolved once an for all. This has been one of my holdups on continuing with my project as I might need to reconsider the use of the ND+ in my product and go with another type of board simply for the SD support.

I believe the crux of the problem is to do with licensing, high capacity SD cards requires a patent to be licensed, which would then cause problems for the open source aspect of the ND. Even if the appropriate licenses were obtained then the firmware couldn't be open sourced, and the cost of the license would also be passed on to all purchasers of an ND. Which IMHO wouldn't be worth while due to the loss of aspects of open source, and the easy availability of 2gb micro sd cards, Amazon carry hundreds, as do most large component suppliers, also i suspect the licensing costs and thus the rise in price of an ND would be considerably more than the cost of a 2gb micro sd with shipping included.

Nak.

Arbiter, One possible source that you may have over looked is old cell phones. I was looking for a 2gb micro when I realized a had a couple of old cell phones that had SD cards still in them (AT&T Samsung dumb phone). If you don't have any old phone some phone stores recycle the old phones and may give you a SD card. Chuck

I usually buy my MicroSD cards at Amazon. http://www.amazon.co...47671419&sr=8-8 Chris

Nak, the patent issue relates to compatibility between SDHC readers and SDXC cards.

SDXC cards shipped with Microsoft exFAT which is proprietary, patented and mostly undocumented.

SDXC host devices accept all previous families of SD memory cards.^[26] Conversely, SDHC host devices will accept SDXC cards that follow Version 3.0, since the interface is identical,^[3] but the following issues may affect usability:

• SDXC cards are pre-formatted with Microsoft's proprietary and patented exFAT file system, which the host device might not support. Since Microsoft does not publish the specifications of exFAT and its use requires a non-free license, many alternative or older operating systems do not support exFAT for technical or legal reasons. The use of exFAT on some SDXC cards may render SDXC unsuitable as a universal exchange medium, as an SDXC card that uses exFAT would not be usable in all host devices. Since the FAT32 file system supports volumes up to the SDXC's maximum theoretical capacity of 2 TB as well, a user could reformat an SDXC card to use FAT32 for greater portability between computers (see below). FAT32-formatted SDXC cards can be used in a host device built for SDHC if the host device can handle 64 GB and larger volumes.
• SDHC host devices will not test the new capability bits defined for SDXC 4.0 cards. It will therefore not be able to use the new features of SDXC, such as transfer speeds above UHS104 (104 MB/s).

The difference between SDSC and SDHC is mostly redefinition of the Card-Specific Data register (CSD), plus SDHC cards ship with FAT32. SDHC is "limited" to 32G. I think this is probably enough for an embedded logger even with video. Any more than this and you may as well build something with an underclocked ITX mobo and an SSD drive.Although I notice in the Wikipedia text that you can dodge the patent by reformatting with FAT32.

Look what I stumbled across and thought of you lot. Just pretend to be interested in Fluke Thermal Imaging and they'll send you a 2GB card full of info about it. It might be EU only judging by the URL. http://eupromo.fluke...uken&product=sd

Look what I stumbled across and thought of you lot. Just pretend to be interested in Fluke Thermal Imaging and they'll send you a 2GB card full of info about it. It might be EU only judging by the URL.
http://eupromo.fluke...uken&product=sd

Nice find, now waiting for my fluke branded micro to SD adaptor to arrive (the 2gb card will be useful as well, just a sucker for branded generic adaptors)...

Hi Chris. I did the upgrade from your very well formed guide and it turned out fine. Seems it helped some of my problems in "rebooting" always have to disconnect/connect the USB cord to the netduinoplus. That was fine. and thanx. I would have tried to check the enlarged RAM after starting up my program but it seems that "Debug.GC(true);" now is not listing out the tabel of used memory numbers in "output" window as before?. Is this something you know about?

any ETA on when the PWM classes would be fixed? Chris stated it would be in a week or so here http://forums.netdui...dpost__p__34924 , but that has already passed. Thanks.

Hi bene331,

I would have tried to check the enlarged RAM after starting up my program but it seems that "Debug.GC(true);" now is not listing out the tabel of used memory numbers in "output" window as before?.
Is this something you know about?

The Debug.GC(true) call should return the amount of ram available. I would try this:

Debug.Print("freemem: " + Debug.GC(true));

Chris