17 replies to this topic

[Chris Walker]

Version: 4.2.2 (version 4.2.2.0)

This firmware requires use of the .NET Micro Framework v4.2 SDK (QFE2) and Netduino 4.2.2.0+ SDK.

Note: The USB device name for Netduino Go has changed from "NetduinoGo" to "Netduino" with this release. This permanent change enables Netduino Go to become more code-compatible with Netduino and Netduino Plus 2. Please update the deployment transport in "Project Properties > .NET Micro Framework" (by changing from "USB" to "Serial" and back to "USB").

With this firmware, you will have the following resources available for your code:
384KB Flash
100KB+ RAM

This firmware includes the following updates:
1. Netduino Go USB Name is now "Netduino", for enhanced compatibility with traditional Netduino projects
2. COM1 (shieldBase.SerialPorts.COM1) is now available for use on Shield Base
3. Now compatible with legacy SecretLabs AnalogInput and PWM classes (requires 4.2.2 SDK)
4. New: more reliable rebooting during deployment

This update also includes the previous updates:
1. Pushbutton now works as reset button (unless used as GPIO)
3. Bug fix: flash deployment should now work consistently
4. Bug fixes: to support Ambient Light, SD Card, and Ethernet modules
5. 4.2.1 SDK: RgbLed.SetColor(...) now supports arguments of type 'double'.
6. New GoBus feature: SerialPort support (COM2/COM3 on Shield Base)
7. New GoBus feature: SPI support (SPI1 on Shield Base)
8. New GoBus feature: InterruptPort (pins D0, D2-D13 on Shield Base)
9. GoBus enhancement: GoBus packets can now span multiple frames
10. GoBus bug fix: single-frame window now enforced for asynchronous events
11. Added preliminary support for GoBus 1.5 beta
12. GoBus 1.5 now supports Virtual I/O from any thread (including events)

To find the current version of your Netduino firmware:
1. Go to the Start Menu > Programs > Microsoft .NET Micro Framework 4.2 > Tools
2. Run MFDeploy.exe. Be careful to run MFDeploy.exe and not MFDeploy.exe.config (as file extensions are hidden by default)
3. Plug your Netduino into your PC using a Micro USB cable.
4. In the Device section at top, select USB instead of Serial. Your Netduino should appear in the drop-down; if not, select it.
5. Select the Target menu, Device Capabilities option.
6. In the output box, find the "SolutionReleaseInfo.solutionVersion" value. This is your firmware version.

To flash this firmware:
1. Detach your Netduino
2. Press and hold your Netduino's pushbutton while plugging it in via USB; this will put it in bootloader mode.
3. Erase the firmware on your Netduino using the STDFU Tester application
> a. Select the "Protocol" tab
> b. Press the "Create from Map" button
> c. Select the "Erase" radio button option
> d. Press the "Go" button
> e. Wait for erase process to complete
4. Flash the attached .DFU file using the ST DfuSe Demonstrator application (included with STDFU Tester)
> a. Locate the "Upgrade or Verify Action" pane (bottom-right pane)
> b. Press "Choose..." and select the attached DFU file
> c. Check the "Verify after download" option
> d. Press "Upgrade". It will take a few minutes to update your Netduino.
> e. Detach and reattach your Netduino (power cycle) or press "Leave DFU mode"

Enjoy, and please let us know if you run into any troubles.

Chris

Attached Files

•  NetduinoGo_Firmware_4.2.2.0.zip   243.08KB   56 downloads

[Nevyn]

So I've just deployed this to the board with no problem.  Next thing tried Blinky and that seemed to go OK.  Now trying the temperature/humidity module and this is where things got interesting.  I have a breakpoint set on the very first line of the application but the breakpoint does not fire instead I get an error saying that there were some deployment errors.

 

The looks to have deployed correctly as the application starts running pretty soon after the deployment error dialog appears as I start to see information displayed on the Komodex seven segment module.

 

If I tell the system to continue even though there were deployment errors then the debugger connects to the application OK.

 

To convert the project I removed the GoBus.dll and added the new one in the Shieldbase update 5 post (as I want to try and use the ShieldBase later).  Changed the transport to serial and then back to USB.

 

Regards,

Mark

[Chris Walker]

Hi Nevyn, Which temperature/humidity module are you using? Also, after the initial Visual Studio deployment error...when you run the app, does it run fine? Chris

[Nevyn]

Which temperature/humidity module are you using? Also, after the initial Visual Studio deployment error...when you run the app, does it run fine?

 

It's the DHT22 module I'm working on with Arron.  It's been working fine for a while now but the deployment this afternoon was problematic.  It could be something I've done converting the project.

 

The code looks to be deployed OK as the display (Komodex) is showing good data.

 

Also, if I say Yes to the continue following deployment errors then the debugger attaches to the code fine and the breakpoint is hit.

 

If I disconnect the Go from the USB and then reconnect it then the code starts running.

 

Regards,

Mark

[Chris Walker]

Okay, thanks for the update. It may have just been a temporary issue with Visual Studio trying to reboot and reconnect to the device. That happens sometimes. In those cases, just run the app again and everything should be fine. Chris

[Nevyn]

It may have just been a temporary issue with Visual Studio trying to reboot and reconnect to the device. That happens sometimes. In those cases, just run the app again and everything should be fine.

 

I don't think it's temporary - I've closed th project/vs and even rebooted the machine and there still seems to be a problem.

 

Just tried deploying again - about the 6/7th time this afternoon and I still get a deployment error.

 

Scenario 1

Hit F5 to deploy the application.

Message in the output window stating that VS is trying to deploy the application ------ Deploy started: Project: DHT22Module, Configuration: Debug Any CPU ------.

Debug.Print messages start to appear in the output window.

Dialog box appears stating that there is a deployment error, do I wish to continue - Press no.

Application carries on running

 

Scenario 2

Hit F5 to deploy the application. Message in the output window stating that VS is trying to deploy the application ------ Deploy started: Project: DHT22Module, Configuration: Debug Any CPU ------.

Debug.Print messages start to appear in the output window.

Dialog box appears stating that there is a deployment error, do I wish to continue - Press Yes. VS generates an exception.

 

The debug messages show a serial number for the message.  Each new message increments the counter.  Looking at the counter it is as if the application was never deployed as the counter in in the thousands and it should have reset to one.

 

This is reproducible but I'm not sure if I have made a mistake upgrading the project.

 

Regards,

Mark

[Nevyn]

A little more digging - It looks like I'm getting this error:

 

------ Deploy started: Project: DHT22TestApplication, Configuration: Debug Any CPU ------ Unable to communicate with device - USB:Netduino

========== Build: 2 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== ========== Deploy: 0 succeeded, 2 failed, 0 skipped ==========

[supra]

------ Deploy started: Project: DHT22TestApplication, Configuration: Debug Any CPU ------ Unable to communicate with device - USB:Netduino

========== Build: 2 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== ========== Deploy: 0 succeeded, 2 failed, 0 skipped ==========

 

 

Thank goddness. I still had same  error problem. But mine had one failed

[Frickr]

i think im getting the same error on mine. except i get an error saying "Error 2 Device not found or cannot be opened - USB:NetduinoGo"

 

 edit: ok i think i see what im doing wrong here, i just need to read a little more closely. ill report back on if i solved my own issues.  

[Chris Walker]

Hi Frickr,

i think im getting the same error on mine. except i get an error saying "Error 2 Device not found or cannot be opened - USB:NetduinoGo"    edit: ok i think i see what im doing wrong here, i just need to read a little more closely. ill report back on if i solved my own issues.

Did you change your deployment target from "NetduinoGo" to "Netduino"? We needed to make the name change to enable some of the new and future scenarios for Netduino Go. The new Netduino Go application templates will all use the new name by default. Chris

[Frickr]

Hi Frickr, Did you change your deployment target from "NetduinoGo" to "Netduino"? We needed to make the name change to enable some of the new and future scenarios for Netduino Go. The new Netduino Go application templates will all use the new name by default. Chris

 

yes i did change it, and that was my problem. it still comes up as NetduinoGo_netduino but everything functions as it should as far as i can tell.

[Nevyn]

A little more digging - It looks like I'm getting this error:

 

------ Deploy started: Project: DHT22TestApplication, Configuration: Debug Any CPU ------ Unable to communicate with device - USB:Netduino

========== Build: 2 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== ========== Deploy: 0 succeeded, 2 failed, 0 skipped ==========

 

Just created the project from scratch, made the changes to DLL's etc and it looks to be working OK now as the debugger is stopping at the breakpoints.

 

Regards,

Mark

[Denisetoo]

I was successful in erasing my netduingo, but not successful in downloading the 4.2.2 firmware.  I received an error at 49%.  Perhaps I have something blocking access to complete this task?  Now Netduingo does not show up in the DfuSe demo when I click on USB from Serial.  The USB light does light up on the Netduingo.  Now my Netduinogo is dead.  It does not show up on the Device Manager anymore.  What may I do to have it recognized again?

 

Thank you, for your time.

[Chris Walker]

Hi Denisetoo, Unplug your Netduino Go from your computer. Press and hold the pushbutton, and then plug it into your PC via USB, and _then_ release the push-button. Start up "STDFU" Tester" and follow the "erasing" instructions in the first post. Finally, use DFUSE to flash your board. Does that get you back on your feet? Chris

[Denisetoo]

Erasing again and downloading NetduinoGo_Firmware_4.2.2.0.dfu does not bring the Netduingo back.  I notice It takes less than a second to 'Upgrade" while in your instructions it should take a minute.  NetduinoGo_Firmware_4.2.2.0.dfu is 417 Kb which I downloaded from this topic.  I believe I just followed the instructions in your first post.  I want to attach a screenshot but my IE browser settings won't let me.  When netduingo is in DFU/reset mode it is recognized in the device manager.

 

I did notice when I initially downloaded firmware 4.2.0 there were more files than just one for firmware 4.2.2

[Denisetoo]

When I attempt to leave DFU mode I get an error at 49% using DFUSE button instead of unplugging the USB.  I will attempt to go back to previous netduingo settings.

[Denisetoo]

Chris,

 

I was able to bring back Netduino (not Netduinogo) in the device manager.  The USB port recognizes netduino now.  I made two changes, one is I disconnected all of the go ports from the netduingo, the second change is to use DFUSE Demo 3.0.2 instead of 3.0.

[skobyjay]

Version: 4.2.2 (version 4.2.2.0) This firmware requires use of the .NET Micro Framework v4.2 SDK (QFE2) and Netduino 4.2.2.0+ SDK. Note: The USB device name for Netduino Go has changed from "NetduinoGo" to "Netduino" with this release. This permanent change enables Netduino Go to become more code-compatible with Netduino and Netduino Plus 2. Please update the deployment transport in "Project Properties > .NET Micro Framework" (by changing from "USB" to "Serial" and back to "USB"). With this firmware, you will have the following resources available for your code: 384KB Flash 100KB+ RAM This firmware includes the following updates: 1. Netduino Go USB Name is now "Netduino", for enhanced compatibility with traditional Netduino projects 2. COM1 (shieldBase.SerialPorts.COM1) is now available for use on Shield Base 3. Now compatible with legacy SecretLabs AnalogInput and PWM classes (requires 4.2.2 SDK) 4. New: more reliable rebooting during deployment This update also includes the previous updates: 1. Pushbutton now works as reset button (unless used as GPIO) 3. Bug fix: flash deployment should now work consistently 4. Bug fixes: to support Ambient Light, SD Card, and Ethernet modules 5. 4.2.1 SDK: RgbLed.SetColor(...) now supports arguments of type 'double'. 6. New GoBus feature: SerialPort support (COM2/COM3 on Shield Base) 7. New GoBus feature: SPI support (SPI1 on Shield Base) 8. New GoBus feature: InterruptPort (pins D0, D2-D13 on Shield Base) 9. GoBus enhancement: GoBus packets can now span multiple frames 10. GoBus bug fix: single-frame window now enforced for asynchronous events 11. Added preliminary support for GoBus 1.5 beta 12. GoBus 1.5 now supports Virtual I/O from any thread (including events) To find the current version of your Netduino firmware: 1. Go to the Start Menu > Programs > Microsoft .NET Micro Framework 4.2 > Tools 2. Run MFDeploy.exe. Be careful to run MFDeploy.exe and not MFDeploy.exe.config (as file extensions are hidden by default) 3. Plug your Netduino into your PC using a Micro USB cable. 4. In the Device section at top, select USB instead of Serial. Your Netduino should appear in the drop-down; if not, select it. 5. Select the Target menu, Device Capabilities option. 6. In the output box, find the "SolutionReleaseInfo.solutionVersion" value. This is your firmware version. To flash this firmware: 1. Detach your Netduino 2. Press and hold your Netduino's pushbutton while plugging it in via USB; this will put it in bootloader mode. 3. Erase the firmware on your Netduino using the STDFU Tester application > a. Select the "Protocol" tab > b. Press the "Create from Map" button > c. Select the "Erase" radio button option > d. Press the "Go" button > e. Wait for erase process to complete 4. Flash the attached .DFU file using the ST DfuSe Demonstrator application (included with STDFU Tester) > a. Locate the "Upgrade or Verify Action" pane (bottom-right pane) > b. Press "Choose..." and select the attached DFU file > c. Check the "Verify after download" option > d. Press "Upgrade". It will take a few minutes to update your Netduino. > e. Detach and reattach your Netduino (power cycle) or press "Leave DFU mode" Enjoy, and please let us know if you run into any troubles. Chris

 

 

I was nervous, worked like a charm. Thanks Chris.