144 replies to this topic

[ash]

we know. it says so in the specs

[Woodlands-Glen]

Ok, so I have read through 8 months of posts mentioning Firmware version 4.3 coming and various references to "This month".

 

What is the status of 4.3?  Has there been any update to 1-wire support?  There were a couple of posts about them being related.

 

Thanks,

 

Glen

[Boog]

I was on one of the 4.2 betas and put away the Netduino for some number of months. I am not trying to upgrade, on first attempt I was getting erase errors and the upgrade failed. I then determined I needed to update my bootloader so I downloaded SAM-BA 2.12 and flashed to TinyBooter 4.2 without issue (said YES when prompted to unlock). I had to use the MFUSB for my Windows 7 VM to recognize the Netduino again after SAM-BA flash. Once I do that MFDeploy pings,

 Pinging... TinyBooterBootloader build info: Netduino Plus (v4.2.0.1) by Secret Labs LLC

I use MFDeploy to flash to 4.2 Firmware from this thread - flash completes successfully but after rebooting the board (unplug/replug) the board boots back to TinyBooter and pings the same as above. I should get a ping result from TinyCLR - correct? I am not able to deploy any .NET projects in this state. Can someone help me get out of bootloader mode or troubleshoot what is happening?

 

Thanks.

[Riverside]

Hello Chris, I'm trying to upgrade the firmware of my Netduino Plus. The BIN file loaded succesfully, according to the SAM-BA, after that I don't seem to be able to connect to the Netduino from MFDEPLOY, in Windows 8 device manager it say's it's missing the driver for the Netduino! Any ideas?

 

ErikU

[Gauss]

Ok, I'm not sure what exactly is going on here...

 

So I have updated my Netdunio Plus (v1) to the TinyBooter 4.2.0.1

After following these steps (http://wiki.netduino...ep-by-step.ashx) this is what I get in MFDeploy:

 

 

Pinging... TinyBooter Bootloader build info: Netduino Plus (v4.2.0.1) by Secret Labs LLC

 

 

The problem comes when I try to send the ER_FLASH and ER_CONFIG files.

 

It just hangs on the 'Chk' step, I never get 'Chk Signature... Signature Passed!'

 

And when I cycle power on the device and ping, this is all I get:  

 

Pinging... TinyCLR

 

 

No version, no updates after that (which seems atypical given every guide I've read on this). However, 'Device Capabilities...' nets:  

 

HalSystemInfo.halVersion: 4.2.0.0 HalSystemInfo.halVendorInfo:   Netduino Plus (v4.2.0.1) 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.1) by Secret Labs LLC ClrInfo.targetFrameworkVersion: 4.2.0.0 SolutionReleaseInfo.solutionVersion:   4.2.0.0 SolutionReleaseInfo.solutionVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC SoftwareVersion.BuildDate:   Sep 19 2012 SoftwareVersion.CompilerVersion:   410894 FloatingPoint:   True SourceLevelDebugging: True ThreadCreateEx: True LCD.Width:   0 LCD.Height: 0 LCD.BitsPerPixel: 0 AppDomains: True ExceptionFilters: True IncrementalDeployment:   True SoftReboot: True Profiling:   False ProfilingAllocations: False ProfilingCalls: False IsUnknown:   False

 

 

Any ideas? Could it be related to what I believe to be random disconnects (the Blue LED on my Netdunio Plus will turn off at a certain point in time).

[Lewis_Schmitt]

Hello,

 

I've updated my netduino pro 1 to 4.2.0. Have done it three times.

But i cannot use my Analog Inputs.

 

Any Ideas?

 

Lewis

[Chris Walker]

Hi Lewis, Can you please share your code (<= 10 lines of code) that you're using to access the analog inputs? We test every board before it leaves Secret Labs to make sure that the ADC channels are working. Chris

[NeonMika / Markus VV.]

Hi Chris. I can imagine that you get asked this a lot, but are there still any plans on an V4.3 firmware for the ND+1?

 

Greets, Markus

[Chris Walker]

Hi Markus,

Hi Chris. I can imagine that you get asked this a lot, but are there still any plans on an V4.3 firmware for the ND+1?

Yes, and yes we're going to try. It's a really tight fit flash-wish. We do have v4.3.x running on SAM7X--but we need to free up a bit of room so that you can also fit an app on a NP1. We may have to go back to the original spec of 48KB of code storage to fit 4.3.1 on there.

ETA on SAM7X firmware is in the next 90 days (March-May timeframe).

Chris

[NeonMika / Markus VV.]

Hi Markus,

Yes, and yes we're going to try. It's a really tight fit flash-wish. We do have v4.3.x running on SAM7X--but we need to free up a bit of room so that you can also fit an app on a NP1. We may have to go back to the original spec of 48KB of code storage to fit 4.3.1 on there.

ETA on SAM7X firmware is in the next 90 days (March-May timeframe).

Chris

 

Thanks for the quick response

 

I can imagine that storage space is a really hard thing to manage on these devices

 

For me personell it would be no such big deal if the storage would get smaller again, but I'm sure you'll give your best... I'll just wait and see what comes

 

Greets, Markus

[Dave Robinson]

Hi Markus,

Yes, and yes we're going to try. It's a really tight fit flash-wish. We do have v4.3.x running on SAM7X--but we need to free up a bit of room so that you can also fit an app on a NP1. We may have to go back to the original spec of 48KB of code storage to fit 4.3.1 on there.

ETA on SAM7X firmware is in the next 90 days (March-May timeframe).

Chris

 

Hi Chris, it's now July, so I feel the 90 days are up.  Do you have an update on 4.3.1 for the N+ ?

 

(I bought a N2 in the meanwhile, so it makes development a little more difficult having two different versions)

[FourT2]

I was able to update my Netduino Plus to 4.2. Had to force the system to use MFUSB driver from

C:\Program Files (x86)\Secret Labs\Netduino SDK\Drivers after using SAM-BA because MFDeploy could not see the device. 

 

I completed the update, reset the networking settings and verified that I am updated to 4.2 in MFDeploy. However, the device is now not recognized by the system and Visual Studio is not able to deploy and debug the code on the device. 

 

I tried different USB ports, disabling / re-enabling Netduino in device manager, forcing it to use the MFUSB driver from C:\Program Files (x86)\Secret Labs\Netduino SDK\Drivers, removing / reinstalling the device.. Still the device manager says the driver is missing. 

 

What do you guys suggest to get the updated netduino to be recognized again? 

 

thanks

 

[Chris Walker]

Hi FourT2,

I'd recommend reflashing the device one more time, to see where its driver gets un-synced. Also--be sure to set the network settings while in TinyBooter (not TinyCLR) mode or you can get stuck in TinyBooter afterwards.

Chris

[FourT2]

Hi Chris, 

 

it is all good now. I spent the most time forcing Windows to use the correct driver after the update. Happy to be breathing new life into this old device with the new update!

 

thanks

[FourT2]

Hi Chris, any timeline for 4.3 support for Netduino 1 / Netduino Plus 1? Also, would support for VS 2012 / 2013 IDE be included? I have a Netduino Plus 2 on order but I would prefer common framework version for better code portability. 

[Laurelle]

Hi,

I've upgraded a Netduino Plus board to V 4.2.0.1 and I'm using PWM. I still get the following errors whatever I do (either using the Hardware PWM or the Secretlabs one):

A first chance exception of type 'System.ArgumentException' occured in System.IO.dll

any idea from where it is coming?

The code was working before on previous versions.

[Chris Walker]

Hi FourT2,

We may be able to build NETMF 4.3 for Netduino 1, but Netduino Plus 1 probably just doesn't have enough flash/RAM.

Chris

[Chris Walker]

Hi Laurelle,

I've upgraded a Netduino Plus board to V 4.2.0.1 and I'm using PWM. I still get the following errors whatever I do (either using the Hardware PWM or the Secretlabs one):
A first chance exception of type 'System.ArgumentException' occured in System.IO.dll
any idea from where it is coming?
The code was working before on previous versions.

Can you copy and paste your code here? We can take a look and make some recommendations.

Also--does this exception break your code? Or is it something that just appears in the Debug window with no apparent effect? [System.IO.dll generally deals with MicroSD cards and such...so I'm surprised you're getting an exception from there when using PWM--which is supported by the Microsoft.SPOT.Hardware.dll assembly.]

Chris

[Laurelle]

Thanks Chris. You're right, I get this message thru the degugger and it does not stop the code.

And I've created a brand new project, put a simple code on PWM and it was working.

So I've removed all references, clear the project, rebuild it and finally it was working like previously.

I still get the error message in the debugger but as mentionned, it's working.

Thanks!

[vz10]

I've stucked after the first step, after I erased my nenduino the MFDeploy doesn't see it at all. What I have to do now?