Netduino home hardware projects downloads community

Jump to content


Photo

Netduino 1 Firmware v4.2.0 (update 1)


  • Please log in to reply
44 replies to this topic

#21 Big Bear Brian

Big Bear Brian

    Member

  • Members
  • PipPip
  • 17 posts

Posted 22 November 2012 - 08:30 AM

Was able to get into Sam-Ba.
Was able to run the scripts, and send the bootstrapper.
Upon disconnecting and reconnecting the Netduino, though, it didn't recognize a device (that is, SAW that something was plugged in, but couldn't figure out what it was. Didn't show up in Device Manager, oddly-enough).


AHAH!

Decided to try one more thing prior to shutting down for the evening. Plugged the board into the W7 machine, which also has MF 4.2 (and 4.1, etc.)

Recognized as a Netduino Plus!!!!! :-) *

Retried the driver from Device Manager, telling it explicitly that I "Have Disk", and navigated to
C:\Program Files (x86)\Secret Labs\Netduino SDK\Drivers

I can now Ping from MFDeploy.

Hopefully I'm on my way. May not need the WinXP machine for this after all, but that's OK... it's also around for the Lego Mindstorms, etc. :-)

Brian

* Gee, if it's recognized as a Netduino Plus, does that mean that an Ethernet jack just magically appeared on it? ;-)

#22 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 22 November 2012 - 04:59 PM

Hi Brian, Did you say "no" to lock regions in SAM-BA? Verify that the bootloader was flashed successfully (by using "compare")? BTW...if the Netduino SDK is not installed on the PC, the device will be enumerated as a WinUSB device with no INF file. It should still show up in Device Manager as unknown though. We're here to make sure your little board gets up and running with the latest firmware. And BTW, there are quite a few people at a "little" software company in Redmond who use Netduinos...so I'm sure there's a lot of neighborly help available there too. Chris

#23 jkrarup

jkrarup

    New Member

  • Members
  • Pip
  • 8 posts

Posted 24 November 2012 - 09:49 PM

Brian,

If I PM you with my email address, do you think you could send to me SAM-BA version you used on XP? I am having similar issues with the newest version of SAM-BA (2.12).

Thanks,

Jkrarup



OK, partial success. I suspect it's been so long since I used Windows XP that I had forgotten how to properly run a program under Administrator permissions instead of just elevated user permissions. Shame on me. Too much W7, W8, and so forth.

Was able to get into Sam-Ba.
Was able to run the scripts, and send the bootstrapper.
Upon disconnecting and reconnecting the Netduino, though, it didn't recognize a device (that is, SAW that something was plugged in, but couldn't figure out what it was. Didn't show up in Device Manager, oddly-enough).

Will experiment more tomorrow (that's that this thing is for, right?) I've got another Netduino, a Mini, and a Plus for the projects I'm working on, at least, but I am kinda hoping to get them all flashed up to .NET MF 4.2 so that I can use a common code base in my project.

And I live in Sammamish, WA, working for a "little" software company in Redmond, WA.... ;-)

Brian



#24 Big Bear Brian

Big Bear Brian

    Member

  • Members
  • PipPip
  • 17 posts

Posted 25 November 2012 - 08:06 AM

Hi Brian,

Did you say "no" to lock regions in SAM-BA? Verify that the bootloader was flashed successfully (by using "compare")?

BTW...if the Netduino SDK is not installed on the PC, the device will be enumerated as a WinUSB device with no INF file. It should still show up in Device Manager as unknown though.

We're here to make sure your little board gets up and running with the latest firmware. And BTW, there are quite a few people at a "little" software company in Redmond who use Netduinos...so I'm sure there's a lot of neighborly help available there too.


Yes, I said No. :-)

There wasn't any device, IIRC. Was really confusing.

In the end, I got it flashed properly, and spent an hour last night mucking about with interrupts. I'm thinking of using several of these in controlling model railroad equipment (the turnouts, track power, and a turntable, not the locomotives themselves), and will need to have a control panel with plenty of pushbuttons. Next I'll have to decide if it can perform well-enough with multiplexing inputs and polling them....

Yes, I actually heard of Netduinos first from the "Mad Scientist" alias. I haven't gotten to attend the monthly SLAB (Stay Late And Build) yet, but I'm hoping one of these days. Since the topic was live here, though, I figured I would start out where others might find the results useful as well... I've run into "DenverCoder9", or his ilk, too many times on the Internet when trying to solve problems (Ref: http://xkcd.com/979/) :-)

Brian

#25 jkrarup

jkrarup

    New Member

  • Members
  • Pip
  • 8 posts

Posted 26 November 2012 - 04:13 AM

Well, persistence pays off...after trying 4 different PC's and two different operating system version plus two different SAM-BA versions, I finally went back to the original PC (Windows 7) and SAB-BA 2.12, I returned the the driver at "GPS CAMERA DETECT", realized there were more that one AT91xxxxx512 targets to choose from when launching SAM-BA. Selecting the right one and running SAM-BA as administrator and in Windows 7 mode I was able to finally get the GUI of SAM-BA and load the bootloader.

Finally Blinky now works...off to more advanced programming.

Thanks to Chris, Big Bear Brian and Arron for thier attempt to help.

Sorry Chris,

I tried your suggestions with no luck. I see the sam-ba.exe process in the task manager but after the device selection window on startup, there is nothing. Any other suggestions? This is my first Netduino Plus and I have yet to be able to play with it. Would an older version of SAM-BA work better for me?



#26 korbai

korbai

    Member

  • Members
  • PipPip
  • 17 posts

Posted 26 November 2012 - 11:21 AM

Hi, I updated my old Netduino with this firmware. After programming tinybooter with Samba 2.12 detected as NetduinoPlus (in devices manager and in msdeploy). Should I make a settings somewhere to change to Netduino? Or the tinybooter is not for my old Netduino? (My netduino is Rev.A). Or it is not important and can I use it? Thanks, Zoltan

#27 h3mp

h3mp

    Member

  • Members
  • PipPip
  • 21 posts

Posted 28 November 2012 - 08:33 AM

Sorry to ask what might be a silly question about USB support (as i'm not yet up to speed what the implications of the terms "WINUsb" and "USBClient"...)

But is there any support on the firmware yet for creating a USB HID device? I really want to use the Netduino as a USB HID mouse (I've got mine hooked up to a KJ‐33000 mems micro joystick and what I really want to do is move the mouse cursor on my screen!!)

#28 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 30 November 2012 - 09:07 AM

Hi h3mp,

But is there any support on the firmware yet for creating a USB HID device? I really want to use the Netduino as a USB HID mouse (I've got mine hooked up to a KJ‐33000 mems micro joystick and what I really want to do is move the mouse cursor on my screen!!)

Netduino and Netduino Plus 1 don't have the necessary hardware to do this well, but we did bake extra hardware into Netduino Go and Netduino Plus 2. After the holidays adding UsbClient is one of our top new feature requests.

BTW, if you use a Netduino or Netduino Plus 1 with the 4.1.1 beta 1 firmware (and therefore the older MFUSB drivers) you can do some limited USB HID hacks. If you poke around on the forums a bit you'll probably find some beta code that will let you tinker a bit with your existing gear.

Chris

#29 h3mp

h3mp

    Member

  • Members
  • PipPip
  • 21 posts

Posted 01 December 2012 - 02:26 PM

Thanks Chris, in that case, I've got my Mrs to order me a Netduino Plus 2 for xmas :) Mark

#30 V64

V64

    Member

  • Members
  • PipPip
  • 20 posts

Posted 03 December 2012 - 11:41 AM

Hello Chris, Just done the upgrade on W8 (in Parallels) - one comment/clarification I found that when Flashing the Firmware I could not select both files ER_CONFIG and ER_FLASH 'at the same time', so I flashed ER_CONFIG first and I then found I had to power cycle (with the Reset Button on the board) before I could flash ER_FLASH. Everything seems to be OK but there is a problem - briefly: Starting with a 'new set up' C# OK - debugging an app OK - stop debugging - modify app - start debugging OK! (i.e. the first stop/start cycle is OK) subsequently C# stop and then Start Debugging (same app) gives - Deploy OK - Start Debug - target not initialised - rebooting (i.e. the second stop/start cycle fails) Ping can see but cannot connect to the device C# stuck waiting Disconnected/reconnected the USB device in Parallels Ping cannot connect to it C# finally completes the 'reboot'and starts the debug. Ping still cannot connect Essentially after I Stop a C# Debug session I have to Disconnect/Reconnect the Netduino USB port in Parallels before I can Start a new Debug Session. Netduino or the OSX USB Driver or Parallels? Now I think I have figured out what is happening it not a stopper - but it would be nice to get a fix.

#31 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 03 December 2012 - 05:48 PM

Hi V64,

Are you trying to ping the device from MFDeploy and also deploy from Visual Studio at the same time? Just FYI...the NETMF drivers only allow one connection at a time.

Netduino or the OSX USB Driver or Parallels?

It's most likely how Parallels deals with WinUSB in .NET MF 4.2 QFE2. Can you try changing the driver to the MFUSB driver and see if you have the same experience?
http://forums.netdui...-mfusb-drivers/

Chris

#32 V64

V64

    Member

  • Members
  • PipPip
  • 20 posts

Posted 03 December 2012 - 10:38 PM

Hi V64,

Are you trying to ping the device from MFDeploy and also deploy from Visual Studio at the same time? Just FYI...the NETMF drivers only allow one connection at a time.


It's most likely how Parallels deals with WinUSB in .NET MF 4.2 QFE2. Can you try changing the driver to the MFUSB driver and see if you have the same experience?
http://forums.netdui...-mfusb-drivers/

Chris


Thank-you for the suggestions

Yes I was using mfdeploy/ping with C# running - so that answers that.

I tried the MFSUB driver and I was unable to get past the deploy/rebooting and if I detached/attached the USB port for the Netduino from Parallels it crashed W8.

Reverted to the Winusb driver and I am back to where I started (great relief) I can add that the problem is not very predictable, sometimes I can do several deploys and then it stops on every one. The unpredictability is becoming a bit of a stopper - it has just taken 10 cycles (unplug/replug the Duino - toggling it's attachment to Parallels - restarting C# - before it would deploy and get past the rebooting...

How do I revert to 4.1? This also showed the same reboot .. issue, but to nothing like the same extent.

At least I now know that others have this problem!

#33 korbai

korbai

    Member

  • Members
  • PipPip
  • 17 posts

Posted 04 December 2012 - 08:05 AM

Sorry, to ask again, but I cannot find any solution
for this problem below. So what should I do to fix it?

Hi,

I updated my old Netduino with this firmware.
After programming tinybooter with Samba 2.12
detected as NetduinoPlus (in devices manager
and in msdeploy). Should I make a settings
somewhere to change to Netduino? Or the
tinybooter is not for my old Netduino?
(My netduino is Rev.A). Or it is not important
and can I use it?

Thanks,
Zoltan



#34 bramVD

bramVD

    Member

  • Members
  • PipPip
  • 16 posts
  • LocationDen Bosch, NL

Posted 09 December 2012 - 11:11 PM

Hello I have a problem with flashing. I had a problem with my Netduino, I was playing with the PWM port when suddenly Visual Studio gave the message something containing “State“ and “Reset”. So I thought, time to upgrade the firmware! Downloaded all the data, Flashed “TinyBooterDecompressor.bin” with SAM-BA 2.12. Checked if Send file is the same as Flashed file, and it was. Open “MFDeploy.exe” for flashing Images. but I can’t ping my Netduino, tried everything, form pulling cables to flashing the “TinyBooterDecompressor.bin” again, but nothing helps. Can anyone tell me how I can fix my Netduino? EDIT: Nevermind :( uses the wrong version of MFDeploy.exe, shame on me

Edited by bramVD, 10 December 2012 - 05:08 PM.

Posted Image

#35 Big Bear Brian

Big Bear Brian

    Member

  • Members
  • PipPip
  • 17 posts

Posted 10 December 2012 - 04:13 AM

Sorry, to ask again, but I cannot find any solution
for this problem below. So what should I do to fix it?


Same thing happened to me (Netduino showing up as N+ after Tinybooter update), but once I installed the latest Netduino firmware, it showed as a Netdiuno again.

Brian

#36 korbai

korbai

    Member

  • Members
  • PipPip
  • 17 posts

Posted 11 December 2012 - 10:05 AM

Same thing happened to me (Netduino showing up as N+ after Tinybooter update), but once I installed the latest Netduino firmware, it showed as a Netdiuno again.

Brian


Thanks, I reflashed the firmware and now it is netduino again.
(I have plus and plus 2, probably I mixed something.)

#37 jchalmers

jchalmers

    New Member

  • Members
  • Pip
  • 2 posts

Posted 25 May 2013 - 01:11 PM

I had the same problem as others, I was attempting to upgrade the firmware of my Netduino 1 from 4.1 to 4.2 

I'm doing this on a new Windows 8 64 bit PC that I had not used with the 4.1 version.

 

VS was already installed.

I installed the .NET MicroFramework 4.3

I installed Netduino SDK version 4.2.2

I plugged in my Netduino and checked the version in MF Deploy.  No problems with this step, Netduino was listed under the USB selection.

 

I unplugged the Netduino and used the Erase Pad to wipe it.

I plugged it back in and it showed up as a Port: GPS Camera Detect (COM3)

 

I tried MFDeploy and there wasn't a USB device listed.

I selected COM3 and tried to Deploy and got the error:

Error: No response from Device

 

I saw the prior posts about SAM-BA.  I went to the Amtel website and downloaded SAM-BA 2.12 and Patch4.  I installed both of those and started up SAM-BA.  I can see my netduino on COM3. 

What am I supposed to do at this point?  Do I do something with the TinyBooterDecompressor.bin file?

 

-Josh

 

 



#38 jchalmers

jchalmers

    New Member

  • Members
  • Pip
  • 2 posts

Posted 25 May 2013 - 02:32 PM

Following up on my prior post,

 

I was able to complete the process in SAM-BA 2.12 Patch4,

I needed to select the correct 'board', which I read off of the Amtel Chip on my Netduino Board:

AT91SAM7X512

Then I was automatically on the Flash Tab, so I ran the Boot from Flash, then I sent the TinyBooterDecompressor.bin

 

After doing that and disconnecting/reconnecting the board, it showed up when I ran MFDeploy

From there I was able to Load ER_CONFIG and ER_FLASH

 

However, I'm still having issues.  At this point, I reboot and the Netduino shows up, but when I try to do anything the LED shuts off, and it seems to crash.

 

I've tried, from MFDeploy, checking the version, but it returns 'Not Supported'

and I've tried deploying a simple Blinky app, and it fails to deploy.  In both cases the Onboard LED is on after I reboot, but shuts off as soon as I try to do something.

 

Is it 'crashing'?  Is the problem that I loaded with MFDeploy 4.3 instead of 4.2? 

 

Thanks



#39 Gregory Pilar

Gregory Pilar

    New Member

  • Members
  • Pip
  • 4 posts

Posted 11 July 2013 - 04:20 AM

Following up on my prior post,

 

I was able to complete the process in SAM-BA 2.12 Patch4,

I needed to select the correct 'board', which I read off of the Amtel Chip on my Netduino Board:

AT91SAM7X512

Then I was automatically on the Flash Tab, so I ran the Boot from Flash, then I sent the TinyBooterDecompressor.bin

 

After doing that and disconnecting/reconnecting the board, it showed up when I ran MFDeploy

From there I was able to Load ER_CONFIG and ER_FLASH

 

However, I'm still having issues.  At this point, I reboot and the Netduino shows up, but when I try to do anything the LED shuts off, and it seems to crash.

 

I've tried, from MFDeploy, checking the version, but it returns 'Not Supported'

and I've tried deploying a simple Blinky app, and it fails to deploy.  In both cases the Onboard LED is on after I reboot, but shuts off as soon as I try to do something.

 

Is it 'crashing'?  Is the problem that I loaded with MFDeploy 4.3 instead of 4.2? 

 

Thanks

 

 

 

I Have the same problem

 

checking the version, but it returns 'Not Supported'



#40 conger

conger

    New Member

  • Members
  • Pip
  • 2 posts

Posted 05 September 2013 - 04:43 PM

Hello,

    I just upgraded my NetDuino fw to version 4.2.0.1.

I changed my target framework to 4.2, but I'm having trouble deploying the previously working "blinky" project.

 

Why does it still seem to reference "CLIENT_V4_1" below?

 

thanks for any help,

--Eric

 

------ Deploy started: Project: Blinky, Configuration: Debug Any CPU ------
An error has occurred: please check your hardware.
DebugPort.GetDeviceProcess() called with no argument
Source: Microsoft.SPOT.Debugger.CorDebug
Stack : 
   at Microsoft.SPOT.Debugger.DebugPort.GetDeviceProcess(String deviceName) in c:depotcurrentCLIENT_V4_1FrameworkCorDebugDebugPort.cs:line 270
   at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.Deploy() in c:depotcurrentCLIENT_V4_1FrameworkCorDebugVsProjectFlavorCfg.cs:line 809
   at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.<Microsoft.VisualStudio.Shell.Interop.IVsDeployableProjectCfg.StartDeploy>b__0() in c:depotcurrentCLIENT_V4_1FrameworkCorDebugVsProjectFlavorCfg.cs:line 634
------ Skipped Deploy: Project: PushButton, Configuration: Debug Any CPU ------
Project not selected to build for this solution configuration 
========== Deploy: 0 succeeded, 1 failed, 1 skipped ==========





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.