152 replies to this topic

[Jay Beavers]

FYI, I've deployed 4.2.0 RC4 to a NetDuino Rev B. and after deployment I am able to Ping and Device Caps the device, but when I deploy/debug the application doesn't run. I'm testing with the 'blinky' sample app from getting started and I've confirmed that the same app compiled and deployed to a 4.1.0.5 NetDuino works properly. I flashed the bootloader on the 4.2.0 device and I have confirmed that Device Caps returns the device as 4.2.0. I've reset power on the board a few times to no effect. Each time I deploy the app, I see deployment messages go by, then a device reset message. Debugger never attaches and the LED doesn't blink.

[Chris Walker]

Hi Jay, How big is your app? <=48KB? Chris

[emg]

Hi nakchak,

That's the release date for the source for Netduino Go firmware...plus the RC5 source for Netduino.

If RC5 works well for everyone, we'll switch the PWM and AnalogInput classes over to the new 4.2 ones (the same ones implemented already on Netduino Go) and then ship a final RC6/RTM for Netduino.

Chris

Where is the v4.2.0 RC5 for Netduino+ located?

[Chris Walker]

Hi emg,

Where is the v4.2.0 RC5 for Netduino+ located?

It's in testing right now. We're working out a deployment glitch. We hope to post it soon...

Chris

[smarcus3]

When updating to 4.2 RC4 I get the following error: An error has occurred: please check your hardware. Object reference not set to an instance of an object. Source: Microsoft.SPOT.Debugger.CorDebug Stack : at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.Deploy() in c:\depot\current\CLIENT_V4_2\Framework\CorDebug\VsProjectFlavorCfg.cs:line 893 at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.<Microsoft.VisualStudio.Shell.Interop.IVsDeployableProjectCfg.StartDeploy>b__0() in c:\depot\current\CLIENT_V4_2\Framework\CorDebug\VsProjectFlavorCfg.cs:line 634 ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

[smarcus3]

Nvm I got it working. Sorry for the double posting.

[2Elemental]

Hi, I have just erased and reflashed my Netduino Plus to firmware 4.2 RC4. When deploying new projects, I get complains about mscorlib being the wrong version. I have already tracked this down (thanks to other posts on this forum) that this happens because I am running Netduino SDK 4.1. I can't find Netduino SDK 4.2 RC4 though. Would it be possible to provide links for both the x86 and x64 versions together with the firmware in these posts? That would save a lot of time. Thanks in advance and keep up the good work, Netduino is a fantastic product! Regards, 2LM

[Cabadam]

Hi,

I have just erased and reflashed my Netduino Plus to firmware 4.2 RC4.
When deploying new projects, I get complains about mscorlib being the
wrong version. I have already tracked this down (thanks to other posts
on this forum) that this happens because I am running Netduino SDK 4.1.
I can't find Netduino SDK 4.2 RC4 though. Would it be possible to provide
links for both the x86 and x64 versions together with the firmware in these
posts? That would save a lot of time. Thanks in advance and keep up the good
work, Netduino is a fantastic product!

Regards,
2LM

In the opening post in this thread, check out the first bolded sentence at the beginning - that link has what you are looking for.

Version: 4.2.0 RELEASE CANDIDATE (version 4.2.0.0 RC4)

This firmware requires use of the .NET Micro Framework v4.2 RTM SDK. Users must completely erase and reflash their Netduinos to use this firmware.

[2Elemental]

In the opening post in this thread, check out the first bolded sentence at the beginning - that link has what you are looking for.

Hi,

Thanks for your response. I have indeed been able to download the Netduino SDK.
It was however not clear to me that I had to look for the Netduino SDK in a link
for the .NET Micro Framework. No criticism, just feedback, I'm just thinking that
more people might make this honest mistake…

Regards,
2LM

[Jay Beavers]

Small, I was testing with Blinky.

Hi Jay,

How big is your app? <=48KB?

Chris

[emg]

Hi emg,

It's in testing right now. We're working out a deployment glitch. We hope to post it soon...

Chris

Hi Chris,
Installed latest 4.2 SDK (no problems) and just realized this does not have RC5 firmware for N+? Is this correct? I must have misunderstood you, I thought 'deployment issues' were for the just released SDK?

[gfcwfzkm]

Hi, i have a little Problem. I cant type the old MAC-Address. I have Netduino+ The Error: "Network Configuration" - Unable to write configuration And: Pinging... TinyBooter Bootloader build info: Netduino Plus (v4.2.0.0 RC4) by Secret Labs LLC Chk signature Signature FAIL Please, i need help in this. thx gfcwfzkm - Beginner

[tknman0700]

Having issues with the SDK giving compile errors when using vb and referencing reserved words like vbcr vbcrlf vblf. Solution is to reference them as Constants.vbCr Thank you

[tknman0700]

I decided to go through the entire process again. MFDeploy says: Pinging... TinyCLR HalSystemInfo.halVersion: 4.2.0.0 HalSystemInfo.halVendorInfo: Netduino Plus (v4.2.0.0 RC4) by Secret Labs LLC HalSystemInfo.oemCode: 34 HalSystemInfo.modelCode: 177 HalSystemInfo.skuCode: 4097 HalSystemInfo.moduleSerialNumber: 00000000000000000000000000000000 HalSystemInfo.systemSerialNumber: 0000000000000000 ClrInfo.clrVersion: 4.2.0.0 ClrInfo.clrVendorInfo: Netduino Plus (v4.2.0.0 RC4) by Secret Labs LLC ClrInfo.targetFrameworkVersion: 4.2.0.0 SolutionReleaseInfo.solutionVersion: 4.2.0.0 SolutionReleaseInfo.solutionVendorInfo: Netduino Plus (v4.2.0.0 RC4) by Secret Labs LLC SoftwareVersion.BuildDate: Feb 2 2012 SoftwareVersion.CompilerVersion: 410713 FloatingPoint: True SourceLevelDebugging: True ThreadCreateEx: True LCD.Width: 0 LCD.Height: 0 LCD.BitsPerPixel: 0 AppDomains: True ExceptionFilters: True IncrementalDeployment: True SoftReboot: False Profiling: False ProfilingAllocations: False ProfilingCalls: False IsUnknown: False The problem now is that I can get my code to it but it seems VS cannot attach a debugger or something because my break points are not working. I put the simple blnky vb code on it and it still seems like the debugger is a bit peculiar - not attaching all the time, etc. In fact if I am debugging inside VS and pull teh USB cord our my computer instantly reboots... thats a nice feature. ; )

[gbreder]

In fact if I am debugging inside VS and pull teh USB cord our my computer instantly reboots... thats a nice feature.

Yeah,
this 'feature' is also discussed in Drivers for .NET MF 4.2.
There is an issue in Codeplex describing this behaviour. But sadly this bug can only be reproduced by another bug: Read on a disconnected I2C Bus takes forever.
This is not ideal. However you can try the repro and vote for it.
If something should be added or changed please send me a message.

Guido

[Firegun]

We're still working out a deployment glitch with RC5, but hope to have it passed off soon for the community.

We will also have an updated Netduino 4.2 SDK installer.

Chris

News?

[emg]

Chris, what is the 'deployment glitch'? RC5 ER_CONFIG and ER_FLASH are just unzipped and then flashed to the device I thought?

[Chris Walker]

Chris, what is the 'deployment glitch'? RC5 ER_CONFIG and ER_FLASH are just unzipped and then flashed to the device I thought?

Deployment of an app via Visual Studio... One of our beta testers was having troubles, although it looks like it might have been an unrelated issue. I should know soon.

[Several people have been testing RC5...if you'd like to be added to that list, please PM me with your e-mail address and the board you're using.]

Chris

[JerseyTechGuy]

I think I found an issue. Not sure this has been reported. The following code worked in 4.1, but in 4.2 it fails:

double Temperature = 79.78374927437;

string formattedTemp = Temperature.ToString().Substring(0,5) + "F";

Debug.Write(formattedTemp);

For some reason it seems to think Temperature.ToString() is null however, reworking the code this way works:

double Temperature = 79.78374927437;

string formattedTemp = Temperature.ToString();

Debug.Write(formattedTemp.Substring(0,5) + "F");

[Cabadam]

Chris, I sent you a PM regarding possibly testing RC5. Thanks,