Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

Netduino Firmware v4.2.0 RC3 (all editions)


  • Please log in to reply
112 replies to this topic

#61 couchounou

couchounou

    Advanced Member

  • Members
  • PipPipPip
  • 31 posts
  • LocationFrance

Posted 27 November 2011 - 08:57 PM

Any progress/work-arounds on this issue? Unfortunately, I've got the same problem. v4.1.x is no good for me as I'm looking for VB.Net support...

Thanks,
Mike


I haven't eard any new on this issue,I'm still waiting for a solution and i'm avalaible for any needed tests.

#62 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 27 November 2011 - 09:10 PM

Hi couchounou,

I haven't eard any new on this issue,I'm still waiting for a solution and i'm avalaible for any needed tests.

What issue regarding .NET MF 4.2 are you inquiring about in particular?

Chris

#63 couchounou

couchounou

    Advanced Member

  • Members
  • PipPipPip
  • 31 posts
  • LocationFrance

Posted 27 November 2011 - 09:39 PM

Hi couchounou,

What issue regarding .NET MF 4.2 are you inquiring about in particular?

Chris


After several upgrade to 4.2 no response from tinyclr :
Pinging... Error: No response from device.

#64 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 27 November 2011 - 11:57 PM

After several upgrade to 4.2 no response from tinyclr :
Pinging... Error: No response from device.

Are you using the 4.2 beta drivers or the production drivers?

Perhaps we should move this part of the conversation to a dedicated thread?

Chris

#65 emg

emg

    Advanced Member

  • Members
  • PipPipPip
  • 129 posts

Posted 27 November 2011 - 11:58 PM

Chris, Same issue for me as well, trying to flash v4.2 RC3 on a brand new Netduino Plus (as noted earlier up the thread by others). Cleared via gold pin, loaded latest TinyBooterDecompressor.bin from Firmware_NetduinoPlus_4.2.0.0_RC3 via SAM-BA 2.10. This looks OK. Try to send ER_CONFIG and ER_FLASH to the device and it seems to hang at checksum (I assume as it stops with 'che'). Power-cycle the device and it can't be found via ping, etc. Repeated several times. Do Netduino boards all have the same version of chips? Any work-around or progress on this? Thanks, Mike

#66 Bainesbunch

Bainesbunch

    Advanced Member

  • Members
  • PipPipPip
  • 61 posts
  • LocationFrance

Posted 28 November 2011 - 12:22 AM

Just a thought on this, i was having all sorts of issues not dislike those here until i realised that i was using the WRONG version of MFDeploy. Eventualy i found the one in the 2.4 MF install folder in the tools folder and everything flashed as expected. Cheers Pete.
I was going to change the world, then I discovered Netduino.
The world will have to wait.

#67 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 28 November 2011 - 12:25 AM

Oh, that's an excellent point Bainesbunch. Is everyone trying to flash with MFDeploy from the 4.2 SDK (and using the 4.2 beta drivers)? Chris

#68 emg

emg

    Advanced Member

  • Members
  • PipPipPip
  • 129 posts

Posted 28 November 2011 - 12:46 AM

Oh, that's an excellent point Bainesbunch. Is everyone trying to flash with MFDeploy from the 4.2 SDK (and using the 4.2 beta drivers)?

Chris


Yes, Rev B board, using v4.2 MFDeploy and the driver was from the SDK v6.1.7600.16385, I assume that's the latest? I just noticed there is another thread on this named 'Problema after upgrade', and I tried the suggestion for sending ER_CONFIG then ER_FLASH, but still no joy.

Mike

EDIT: Also, I've never had any previous MF installed, only 4.2 RC3.

#69 couchounou

couchounou

    Advanced Member

  • Members
  • PipPipPip
  • 31 posts
  • LocationFrance

Posted 28 November 2011 - 08:36 AM

Yes, Rev B board, using v4.2 MFDeploy and the driver was from the SDK v6.1.7600.16385, I assume that's the latest? I just noticed there is another thread on this named 'Problema after upgrade', and I tried the suggestion for sending ER_CONFIG then ER_FLASH, but still no joy.

Mike

EDIT: Also, I've never had any previous MF installed, only 4.2 RC3.

As my board : REV.B using MFDeploy for 4.2 tool and beta drivers... also tried sequence ER_CONFIG and ER_FLASH...

#70 emg

emg

    Advanced Member

  • Members
  • PipPipPip
  • 129 posts

Posted 29 November 2011 - 11:26 AM

Hi Chris, Has Secret Labs managed to reproduce this issue a few of us are having trying to get 4.2 RC3 flashed?

#71 Kevin Hazzard

Kevin Hazzard

    New Member

  • Members
  • Pip
  • 8 posts
  • LocationMid-Atlantic USA

Posted 18 December 2011 - 11:57 PM

Perhaps I've missed it because I've been out of the NETMF loop for a while but has the 4.2 firmware RTMed?

Thanks, Chris.

Kevin

Version: 4.2.0 RELEASE CANDIDATE (version 4.2.0.0 RC3)

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.

WARNING: This firmware is pre-release firmware. It may temporarily cause your Netduino to cease functioning properly. If this firmware does not work for you, you will likely need to erase your Netduino completely and re-flash the production v4.1.0.6 bootloader using Atmel SAM-BA tools and the production v4.1.0.6 firmware using MFDeploy.

NOTE: This beta firmware must be used with the production version of the Microsoft .NET Micro Framework SDK.

If you're an early adopter and would like to help us test and refine these new features, this beta release may be for you.

If you experience any blue screens or crashes with this release, please try out the new .NET MF beta drivers.

NETDUINO MINI NOTE: select the appropriate firmware zip file (RS232 or TTL) based on the deployment port you are currently using (RS232 = pins 1 and 2; 3.3V TTL UART = pins 11 and 12).

This firmware includes the following updates:
1. For Netduino Plus, 38KB+ RAM (10KB+ more than before)
2. Visual Basic support (including Visual Basic Express 2010)
3. StringBuilder support
4. Regular Expressions
5. IP broadcast support
6. Extension method support
7. Dozens of bugfixes

The following features are planned for the v4.2 release:
1. More feature-rich, core ADC and PWM classes
2. Etc.

This firmware also includes the following previous updates:
1. Early support for some 4GB+ MicroSD cards (courtesy of community member KodeDaemon)
2. Early UsbClient support (requires deploy/debug via serial)
3. Pushbutton (SW1) now returns true when pushed, false when not pushed
4. DHCP support now works on more/all routers
5. Network cable may now be plugged in at any time
6. I2C internal address ("repeated start bit") support
7. Bugfixes: SerialPort.DataReceived event should now fire properly
8. Bugfixes: SerialPort.Read() timeout now implemented properly
9. Bugfix: SD card support no longer interferes with digital pin 2
10. Variable-bit SPI (9 to 15 bit) capabilities
11. Enhanced Parallels, VMWare, and VirtualBox compatibility
12. RS232 and TTL UART deployment now selectable via software tool
13. Enhanced deployment reliability (software reset enhancements)
14. SPI bugfixes

Before deploying the attached firmware, you should erase your board completely and flash the v4.2 RC3 bootloader (included in the attached ZIP file).

You may update to this pre-release firmware using the MFDeploy tool:
1. Download and unzip the attached file to a directory on your computer.
2. Go to the Start Menu > Programs > Microsoft .NET Micro Framework 4.2 > Tools
3. Run MFDeploy.exe. Be careful to run MFDeploy.exe and not MFDeploy.exe.config (as file extensions are hidden by default)
4a. For Netduino and Netduino Plus: Plug your Netduino into your PC using a Micro USB cable. If your Netduino does not connect successfully, try plugging the USB cable into your Netduino first...and then your PC.
4b. For Netduino Mini: Plug your Netduino Mini into your PC using an RS232 or TTL UART cable.
5a. For Netduino and Netduino Plus: In the Device section at top, select USB instead of Serial. Your Netduino should appear in the drop-down; if not, select it.
5b. For Netduino Mini: In the Device section at top, select Serial. Select the serial port assigned to your RS232 or TTL UART cable.
6. Click "Browse..." and select the unzipped files from step #1 (ER_CONFIG and ER_FLASH).
7. Press "Deploy". It will take a few minutes to update your Netduino.
8. For Netduino Plus: Select the Target > Configuration > Networking menu. You will need to re-enter your IP address settings and MAC address. We will try to eliminate this step in the future.

Chris



#72 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 22 December 2011 - 07:26 PM

Hi Kevin, The .NET MF 4.2 did RTM a few months ago, but we're still working with the RTM as a "beta" until a few more bugs get fixed. There was a lot of great work done before RTM, but there's still a bit more to go. Chris

#73 Johnaa

Johnaa

    New Member

  • Members
  • Pip
  • 9 posts

Posted 24 December 2011 - 06:50 PM

After loading ER_CONFIG and EA_FLASH (Firmware v4.2.0 RC3) in netduino, The computer (mfdeploy v4.2.0.0) doesn't define a board on usb.

#74 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 24 December 2011 - 11:25 PM

After loading ER_CONFIG and EA_FLASH (Firmware v4.2.0 RC3) in netduino, The computer (mfdeploy v4.2.0.0) doesn't define a board on usb.

Does it show up under "USB" devices in Device Manager?

Chris

#75 Johnaa

Johnaa

    New Member

  • Members
  • Pip
  • 9 posts

Posted 25 December 2011 - 07:00 AM

Does it show up under "USB" devices in Device Manager?

Chris

It is not found out in Device Manager. MFDeploy write message runing aplication, board to become inaccessible "USB" devices.

#76 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 28 December 2011 - 09:19 AM

It is not found out in Device Manager. MFDeploy write message runing aplication, board to become inaccessible "USB" devices.

Does it show up as an unknown device? If you right-click on that device, what error does it show?

Chris

#77 PepLluis

PepLluis

    New Member

  • Members
  • Pip
  • 9 posts

Posted 30 December 2011 - 03:01 AM

Hello all, Trying to update to RC3 ... after fully reset of netduino, applying 3.3V to gold pin, when I try to connect samba to send the tinybooter always get "communication error" when push connect button. I've proven with versions 2.9, 2.10, 2.11, in XP and Win7. Is there any way to recover netduino from scratch?. Any idea? Thank you, PepLluis,

#78 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 30 December 2011 - 03:58 AM

Hi PepLluis, Try erasing your Netduino again (3.3V to the gold ERASE pad). Then plug it into your PC and make sure that it shows up as an Atmel serial port in Device Manager. Finally, connect via SAM-BA 2.11. BTW, what serial port # is being assigned to it in Device Manager? Chris

#79 PepLluis

PepLluis

    New Member

  • Members
  • Pip
  • 9 posts

Posted 30 December 2011 - 10:35 AM

Hi Chris, When plug into pc after apply 3.3v to erase pad, in device manager appears like "AT91 Usb to serial converter" in COM9. The problem absentmindedly was selecting a board "at91sam9" in combobox... not an "at91sam7". Sorry for this rookie noise. :-( Thanks, PepLluis,

#80 Bainesbunch

Bainesbunch

    Advanced Member

  • Members
  • PipPipPip
  • 61 posts
  • LocationFrance

Posted 30 December 2011 - 11:17 AM

I had EXACTLY this same issue when trying to re-flash the bootloader with samba. It was due to some odd serial USB drivers I had on my PC. when I tried the same board on another PC it all worked according to plan. I had some pololu serial USB drivers that seemed to mess with the netduino USB interface and installed the wrong drivers so samba could not talk with it. Hope this is of some help. Cheers Pete.
I was going to change the world, then I discovered Netduino.
The world will have to wait.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.