1 reply to this topic

[emg]

Chris,
The issue I reported NETMF Codeplex (at your request):

Flashing tinyclr 4.2RTM to Netduino fails

has been rejected and closed with the comment: Please refer to your device manufacturer

Okay.

I take it from this that NetMF Core team feel the issue resides with the Secret Labs implementation of 4.2RC3 on the Netduino Plus? If so, what does Secret Labs plan to do about this? And when?

As it stands, I'm (and probably others) a bit frustrated with the apparent lack of progress or even some feedback to say 'hey we are working on this, this and this' or even 'we have a fix for this, but are stuck trying to fix this and this' - you get the idea. As I can't event flash 4.2RTM to my device, I don't even get to experience all the other bugs/issues people are having!

IMHO, if firmware flashing and project debug/deployment are not solid, this reflects poorly on the Netduino and will turn many away to other similar hardware (GHI).

Sorry to rant, but it has been a long day...

[Chris Walker]

Hi emg, Thank you for ranting. I can empathize with how you feel. Please understand that the .NET MF 4.2 still has a few bugs in the core implementation, which is why the firmware is still beta. I just sent an e-mail to the .NET MF team to see what we can do about this. We've put .NET MF 4.2 beta firmware out there (and I believe we're the only group that has done so) to help ferret out these bugs and to give users the latest and greatest features. I can confirm that these bugs occur on other hardware, including the Atmel SAM7X devboard and other non-Atmel microcontrollers. We're hoping to have a resolution on this issue and a few others soon, so that we can get .NET MF 4.2 out to all users...and take advantage of the new features (including VB) support that it provides. The .NET MF team at Microsoft and the community have put a lot of work into .NET MF 4.2. I will be very excited to see firmware for it ship as well. Chris