
Netduino Firmware v4.2.0 RC3 (all editions)
#81
Posted 30 December 2011 - 02:44 PM
#82
Posted 30 December 2011 - 08:14 PM
- 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.
#83
Posted 31 December 2011 - 01:15 AM
#84
Posted 31 December 2011 - 05:39 PM
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.
#85
Posted 05 January 2012 - 04:24 PM

#86
Posted 06 January 2012 - 09:18 AM
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.
#87
Posted 06 January 2012 - 02:12 PM
#88
Posted 06 January 2012 - 10:56 PM

#89
Posted 07 January 2012 - 01:08 AM
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.
#90
Posted 07 January 2012 - 03:16 AM
Thank you, Robert.And, yes, I did vote.
Chris
#91
Posted 19 January 2012 - 12:28 AM
#92
Posted 02 February 2012 - 02:36 AM
#93
Posted 04 February 2012 - 12:17 AM
#94
Posted 01 March 2012 - 07:01 AM
#95
Posted 01 March 2012 - 07:02 AM
#96
Posted 10 March 2012 - 12:55 AM
#97
Posted 30 March 2012 - 03:26 PM
#98
Posted 24 April 2012 - 03:27 PM
#99
Posted 23 May 2012 - 07:34 PM
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!
#100
Posted 23 May 2012 - 07:37 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users