112 replies to this topic

[PepLluis]

Hi Pete, Thanks for your help... in this case, the problem is myself :-) the mistake are becouse I'm selecting an 'sam9' processor... provably my brain is thinking inside the end year party! Happy new year and thanks for your comments. PepLluis,

[DrJaymz]

I tried this update to fix my issue with the I2C and repeated start. It did not fix my repeated start issue and I noticed the following.

• system.math.pow(x,y) is not implemented, which is a pain because I cannot easily implement this another way.
• (float).tostring(f2) gives a result like 1.0000 regardless of the argument placed in the tostring.
• port.read is working in an inverted manner for some reason.

Am a bit peeved to be honest.

[Chris Walker]

Hi DrJaymz, With the .NET MF 4.2 beta firmware, there are a few known bugs. The new emulated math library has a few missing or mis-calculating routines. There are a few networking and driver glitches. These are all being worked on, to make the production 4.2 firmware as high-quality as possible. If you're looking for stable firmware and repeated-start-bit, perhaps you can try the v4.1.1 beta firmware (which is more or less release quality--we just haven't stamped it as such)? We have created an I2C wrapper which will let you do repeated start bit with it as well. Sorry for the troubles with the beta firmware, Chris

[DrJaymz]

Hi DrJaymz,

With the .NET MF 4.2 beta firmware, there are a few known bugs. The new emulated math library has a few missing or mis-calculating routines. There are a few networking and driver glitches. These are all being worked on, to make the production 4.2 firmware as high-quality as possible.

If you're looking for stable firmware and repeated-start-bit, perhaps you can try the v4.1.1 beta firmware (which is more or less release quality--we just haven't stamped it as such)? We have created an I2C wrapper which will let you do repeated start bit with it as well.

Sorry for the troubles with the beta firmware,

Chris

Thanks for your reply.

Well OK, I got miffed with it and went to the pub instead. I have posted the problems I had with it anyway so that someone can fix them in due course.

If I use the 4.1.1 firmware where is the *current* beta release and can I keep my 4.2 SDK and change the target to 4.1 in VS? If this is the case how do I use the repeated start functionality out of the available functions - is there an example of this? I guess I was lucky that all my other I2C went so smoothly but it means I didn't learn anything! So far I have not had a bean out of the Melexis Temp Sensor.

On a positive note, with the shipped firmware, I frequently got a lock up when trying to debug some code. It would get stuck on the deployment part. I would then force it with a remove and reinsert which would then make VS go nuts with a null reference error and then another error (hardware), following that it worked. When I updated to 4.2 this lock up did not occur once, but deployment was a little slower.

[Jamie Lewis]

Hello all, Just wondering if there is any eta on the 4.2 firmware? It's a little frustrating the number of NotSupported exceptions that are in the production release. I've tried flashing RC3 a couple of times now but I can't seem to get it to work, always results in an error to the effect of 'cant find entry point' after flash with MFDeploy and VS just bombs out with CNC_ENTRY_POINT_SOMETHING when trying to deploy. anyone happen to know a fix? I'm hoping RC3 is going to be just around the corner as it will save me a load of coding for even a basic network device, but looking at some of the open issues that seem's unlikely Thanks, Jamie

[DrJaymz]

Hello all,

Just wondering if there is any eta on the 4.2 firmware? It's a little frustrating the number of NotSupported exceptions that are in the production release. I've tried flashing RC3 a couple of times now but I can't seem to get it to work, always results in an error to the effect of 'cant find entry point' after flash with MFDeploy and VS just bombs out with CNC_ENTRY_POINT_SOMETHING when trying to deploy. anyone happen to know a fix?

I'm hoping RC3 is going to be just around the corner as it will save me a load of coding for even a basic network device, but looking at some of the open issues that seem's unlikely

Thanks,
Jamie

There doesn't appear to be any roadmap for this development so I guess you are stuck with 4.1.1 for now. As for your error, did you fully erase the firmware? It might be that the bootloader is pointing to the wrong address and thus it cannot execute your program.

[Jamie Lewis]

No roadmap ... is there any wild guesses? if we are talking 6 months I could just about hangon but any longer i might have to look at alternatives ... presumably that would be getting into the firmware source to make a custom build? In regards to erasing ... yes i did the v3 to gold pin erase, then sam-ba, then mfdeploy ... all seems fine right to the last moment and mfdeploy goes to validate where it complains about no entry point ... however all seems responsive to device queries / reboot etc. On deploying via VS I then get the CNC_ error and fails to deploy. I can run through it again and get more specifics if it helps.

[Chris Walker]

A few quick thoughts: 1. The Netduino 4.2 RC3 firmware is based on the RTM version of .NET MF 4.2. If there are any bugs in it, they are technically bugs to be fixed in a .NET MF 4.2 service pack. 2. Since there are a few bugs left in .NET MF 4.2 which are affecting users, we're still considering the firmware beta. That's out of an abundance of caution...we want to set expectations a bit lower to make sure that community members have a good experience. 3. We're hoping that all the bugs will be cleaned up this quarter. We are doing some extensive testing offline with a few community members to try to nail down the causes. 4. If you're experiencing a certain bug, _please_ vote for it at netmf.codeplex.com. While the majority of .NET MF users are Netduino users, a few votes from users goes a long ways farther than a list of bug reports from us to Microsoft Together with Microsoft and the community, we should be able to make .NET MF an even stronger platform. Chris

[Robert L.]

We're hoping that all the bugs will be cleaned up this quarter.

Thanks Chris,

I appreciate your candor and I am glad I decided to start shipments last week as "soon" was dragging out beyond what I could deal with. I may have to do some product recalls eventually, but the damage of waiting another 3 months until the bugs *might* be fixed, would have been worse. In the mean time, I have disclosed what effect the bugs will have on the product and the work-arounds I have added to recover from the occasional freeze up.

I have been using LWIP in another product of mine for over 10 years (not a Netduino hardware platform, of course), so I know first hand that it is not easy to get that stack to work reliably especially with limited resources and horsepower. The code in LWIP is first rate, but the details of how to interface to it are not as clear.

And, yes, I did vote.

[Chris Walker]

And, yes, I did vote.

Thank you, Robert.

Chris

[CaptUnderpants]

Just thought I'd add my 2 cents worth. I've experienced the same issue others have with regards to flashing the latest firmware only to find the board unresponsive. Had to go back to 4.1.0.6 to get any joy. As a side note I did have 4.2 rc1 loaded successfuly..... oh, by the way it's a Rev A board

[bobk]

I now have a new PC running win 7 64. Under winxp I could not load the beta on a n+. I was able to install 4.2 on a n+ under win 7. Yeh. I was able to write to an 2 gig SD card. I was NOT able to write to an 8 gig drive tho. I installed 4.1.1 beta and using that same 8 gig SD card, that worked. Went back to 4.2, and card still did not work. Bob

[Chris Walker]

The new RC4 (beta) firmware was just posted at: http://forums.netdui...-netduino-plus/ Several of the bugs reported here have been fixed (DHCP, floating point, etc.) but there may be more to work on... Please post your experiences with the new release in that thread. Thanks for all the feedback; we're hoping to make 4.2 the highest-quality release to date. Chris

[Travis B.]

Hi to all! I've installed the new bootloader and the new firmware without errors, but when I want run my project the visual studio says "An error has ocurred. Please check your hardware". I was working with the v4.2 RC3 release and all was working fine. Any idea? Thanks so much!! Mario

[Chris Walker]

Hi Travis, I'd double-check the deployment settings. Change from USB to Serial and back again. That may take care of it. Also, try erasing your current Netduino app using MFDeploy. Does that help? Chris

[jeffdrew]

Hi, I'm having trouble after updating my netduino plus firmware to v4.2 RC4. I also tried v4.1.1 RC3 listed in the link. Once the firmware is installed, there's no eithernet. I used MyDeploy, setting the network values the same as using firmware v4.1. Doesn't work... Any Help?

[satkye]

Any onewire support yet?

[tknman0700]

The very first step says: 1. Download and unzip the attached file to a directory on your computer. Where is this attached zip file you speak of?

[lvw]

The very first step says:

1. Download and unzip the attached file to a directory on your computer.

Where is this attached zip file you speak of?

I'm also looking for this.. I think i'm going blind!

[lvw]

I found the download links (http://wiki.netduino.com/Firmware.ashx), but im unable to download, it keeps asking for my username and password again and again