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 Plus 2 Firmware v4.2.1 (Update 2)


  • Please log in to reply
57 replies to this topic

#41 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 27 December 2012 - 10:49 PM

Yes i did press and hold. MFdeploy responds to ping with

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

 

The DFU Tester v3.0.1 shows no devices.

 

Is this update only for Plus 2 ??

 

If only for Plus 2 is there an update 2 for regular old netduino Plus as i'm hoping the

receive UDP broadcast is fixed

and dhcp only works on boot is fixed  

 

Yes, this update is only for Netduino Plus 2.  Netduino Plus (gen1) uses an older Atmel SAM7X micro, and has its own firmware (sticky attached at the top of this forum).

 

The DHCP bugfix is in the upcoming .NET MF 4.3 firmware, I believe.  We're in early testing on it now.

 

Chris



#42 korbai

korbai

    Member

  • Members
  • PipPip
  • 17 posts

Posted 28 December 2012 - 02:35 PM

Hi Zoltan,

 

 

When you find out what the issue in the larger application, please let us know.  We'd love to learn more about your scenario and see if there are ways to make board upgrades even more seamless for others.

 

Thank you for the update,

 

Chris

Hi Chris,

 

I have additional information: it works when I run under the debugger,

but there is nothing output from I2C when run standalone. I know it is

strange but I did the test a couple of times and it is reproducible. It is

not dependent the USB is connected or not. It is dependent only how

to start the program. From debugger then works, from standalone does

not work. I have not got analyser but only a simple digi scope. Under

debugger I see the communication. Without the debugger the clock

is fixed high level. So the previous info (DS1307 works, PCF8574 not)

was false. These works only under the debugger.

 

If you have any idea what should I check please tell me! Thanks!

 

Zoltan



#43 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 28 December 2012 - 08:21 PM

Hi Zoltan,

 

I have additional information: it works when I run under the debugger,

but there is nothing output from I2C when run standalone.

 

If you have any idea what should I check please tell me! Thanks!

 

Where are you creating your I2C objects?  And where are you using them?  There may be some slight differences in available memory and thread scheduling...and therefore the way that garbage collection affects your app...when the debugger is not attached.

 

My first guess is that the garbage collector is kicking in and cleaning up your objects, but there are other possibilities as well.  If you can boil the non-working I2C sample down to a short repro (<20 lines of code) we'll be happy to help diagnose it with you as well.

 

Chris



#44 JohnGuin

JohnGuin

    New Member

  • Members
  • Pip
  • 8 posts
  • LocationRedmond WA

Posted 29 December 2012 - 01:52 AM

Hmm... I'm running 64 bit Vista and the DfuSe Demonstration app is crashing on boot.  I've wiped my Netduino already - I assumed it is bricked until I can figure out how to boot the Demo app, right?

 

Anyone else seeing this crash?  FWIW, my machine has VS2010 Pro, Vista and Office 2010 with all patches and nothing else.



#45 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 29 December 2012 - 02:25 AM

Hi JohnGuin,

 

Hmm... I'm running 64 bit Vista and the DfuSe Demonstration app is crashing on boot.  I've wiped my Netduino already - I assumed it is bricked until I can figure out how to boot the Demo app, right?

 

Anyone else seeing this crash?  FWIW, my machine has VS2010 Pro, Vista and Office 2010 with all patches and nothing else.

 

Do you have a Netduino or a Netduino Plus 2?  If you have a regular Netduino, please grab the "Netduino 4.2.0.x" firmware from the Netduino forum.

 

If you have a Netduino Plus 2, booting the board into bootloader mode does not erase anything.

 

Chris



#46 JohnGuin

JohnGuin

    New Member

  • Members
  • Pip
  • 8 posts
  • LocationRedmond WA

Posted 29 December 2012 - 03:16 AM

I wasn't clear with my original post - I had run the SDFU Tester and completed all those steps.  Then starting the Demo app crashed.  I assumed since I had run "Go" in Erase mode wiht the Tester that the device was wiped.

 

But the good news is that I had a Win7 machine and installed everything I needed on it to get my NP2 updated to 4.2.1.2.

 

So I am back in business - sorry for the noise.



#47 Kevgor

Kevgor

    New Member

  • Members
  • Pip
  • 2 posts
  • LocationVancouver, Canada

Posted 29 December 2012 - 07:31 AM

Hi Kevgor, Can you verify that the device ("ST DFU...") appears in the pull-down at the top of the STDFU Tester application? If so, could you please take a screenshot (shift+prtscr) after selecting 'Erase' and pressing 'Go' and attach it to a reply to this thread? Chris

 

Hi, sorry for the delay I was away for the Holidays.

 

My problem was that I had my Dev Environment and ST DFU utilities installed on Windows Server 2008 R2. Once I reinstalled everything onto my Windows 8 Notebook, all appears to be working perfectly according to the instructions, and I was able to upgrade the firmware.

 

Kevgor



#48 Martijn

Martijn

    Member

  • Members
  • PipPip
  • 13 posts

Posted 30 December 2012 - 01:03 PM

Any update on supporting BitBanger? I used Fez Panda II before and I'm disappointed to see DPWS and OutputCompare is not implemented in the firmware.



#49 korbai

korbai

    Member

  • Members
  • PipPip
  • 17 posts

Posted 30 December 2012 - 01:59 PM

Hi Zoltan,     Where are you creating your I2C objects?  And where are you using them?  There may be some slight differences in available memory and thread scheduling...and therefore the way that garbage collection affects your app...when the debugger is not attached.   My first guess is that the garbage collector is kicking in and cleaning up your objects, but there are other possibilities as well.  If you can boil the non-working I2C sample down to a short repro (<20 lines of code) we'll be happy to help diagnose it with you as well.   Chris
  Hi Chris,   I have more info (more strange than before). I minimized the code but I cannot solve the problem in my application when I realized the difference: my app use +3.3V for PCF8574, and on my desk I use +5V for one PCF8574 testing. When I switch to 3.3V on my desk I can reproduce the problem. Summarize: on 5V everything works with / without debugger. But on 3.3V not works standalone but works under the debugger. Unbelievable. I test a couple of times but it is true. PCF8574 works from 3-5V supply by datasheet. The Netduino and Netduino Plus work too on my desk. But Plus2 not with PCF8574 on 3.3V without the debugger. I attach the code which reproduce the problem. I powered the netduinos with usb during the test (I tried external 5V power supply, the same).   I will think about change my application to 5V but it is not so simple, so if you have any idea how can I override this problem it would be welcomed.   Thanks, Zoltan  
    public class Program    {        public static void Main()        {            var device = new I2CDevice(new I2CDevice.Configuration(0x38, 100));            I2CDevice.I2CTransaction[] actionsWrite;            var buffer = new byte[1];            actionsWrite = new I2CDevice.I2CTransaction[]            {                I2CDevice.CreateWriteTransaction(buffer),            };            for (; ; )            {                buffer[0] = 255;                device.Execute(actionsWrite, 1000);                Thread.Sleep(1000);                buffer[0] = 0;                device.Execute(actionsWrite, 1000);                Thread.Sleep(1000);            }        }    }


#50 iced98lx

iced98lx

    Advanced Member

  • Members
  • PipPipPip
  • 134 posts
  • LocationSouth Dakota

Posted 03 January 2013 - 05:57 PM

Chris/ All-
I recently got my N+2 and went about testing a "hello world" program (which worked great) but noticed during it that the MAC was wrong according to my router. I had seen this update, and figured it would solve my MAC issues. I opened up .netMF Deployment tool, grabbed the information and this is what I saw:
 

Posted Image

 

That to me says my N+2 was updated before it shipped (Thanks Cana Kit) would you say the same?

 

If so, my MAC, though correct in the "Network Configuration" area is not being used, anything I can do to fix this? Not an issue for me most likely as it'll be behind a NAT Firewall, but someone might want it to work.



#51 Lunddahl

Lunddahl

    Advanced Member

  • Members
  • PipPipPip
  • 152 posts
  • LocationEurope, Denmark

Posted 05 January 2013 - 09:26 AM

No, your board is NOT updated, it should read:

 

 

SolutionReleaseInfo.solutionVersion:    4.2.1.2SolutionReleaseInfo.solutionVendorInfo: Netduino Plus 2 (v4.2.1.2) by Secret Labs LLCSoftwareVersion.BuildDate:              Dec  3 2012

 

When you have upgraded, your MAc address issues should be fixed, but remember that after the upgrade you should set your MAC address manually with MFDEPLOY - Target - Configuration - Network, i suggest you set it to the values from the sticker on the board.

 

- Ulrik Lunddahl

 
 


#52 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 05 January 2013 - 10:41 AM

Hi iced98lx, This was a bug in the 4.2.1.0 firmware. To echo Ulrik's recommendation, if you upgrade your board to 4.2.1.2 then it should use the correct IP settings. Chris

#53 iced98lx

iced98lx

    Advanced Member

  • Members
  • PipPipPip
  • 134 posts
  • LocationSouth Dakota

Posted 05 January 2013 - 06:49 PM

Ah, the addition of the last  dot release got me. 4.2.1.X I kept reading 

Netduino Plus 2 Firmware v4.2.1 (Update 2)

 

As 4.2.1 is the latest version, but your release scheme uses another dot to denote "update". 

 

My fault, I'll update and see where that gets me.



#54 qsnapper

qsnapper

    New Member

  • Members
  • Pip
  • 8 posts

Posted 06 January 2013 - 09:16 PM

Hi Chris,

 

Hi Jeff,

 

 

When you plug in your board, does it show up in Device Manager?  Under USB, as a Netduino?

 

If not, please try erasing and re-flashing your board to get it back into a known-good-state.  Instructions are in the firmware sticky at the top of the forum.

 

BTW, what does your PWM code look like?

 

Chris

 

I had pretty much the same experience as JeffJohnson (although I am using VS Express 2012, and it didn't crash). Couldn't get the Netduino Plus 2 to do anyting anymore. Re-flashing got my Netduino working again, ran the code and same issue. I skipped the PWM example, the code of which is: http://nedx.org/src/...R01-MB-code.txt

 

Then wanted to try another example which also includes PWM (code here: http://nedx.org/src/...NCIR06-code.txt) and that also had the same effect. 

 

Then read your 2nd post in this thread saying "The legacy ... SecretLabs.NETMF.Hardware.PWM classes have been replaced by ... Microsoft.SPOT.Hardware.PWM classes". Removed the SecretLabs MWM class and added the Microsoft one, but in VS get this error 

"Error 1 'Microsoft.SPOT.Hardware.PWM' does not contain a constructor that takes 1 arguments"

 

Any tips on how to get this working?

 

Thanks,

 

Quintus



#55 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 06 January 2013 - 11:42 PM

Hi Quintus, The new Microsoft.SPOT.Hardware.PWM class requires a few more parameters than the SecretLabs PWM class did. I'd recommend passing in a Frequency of 100000.0 and a DutyCycle of 0.5 (and 'invert' of false) as defaults. Then use the PWM.Start() function to start up PWM. It should be fairly self-explanatory from there. We are currently testing a new version of the legacy SecretLabs PWM and AnalogInput classes, with the goal of bringing these back for the new boards. I should have more to share on those within roughly the next ten days. Chris

#56 mattcro

mattcro

    New Member

  • Members
  • Pip
  • 8 posts

Posted 07 January 2013 - 05:00 PM

I've just updated my shiny new Netduino2 Plus to the 4.2.1.2 firmware. I got it erased with STDFU tester OK, but could not get it to flash properly with Dfuse. I tried a couple of times to erase/flash, even unplugging the N2+ in between and double-checking that it was in DFU mode but no joy. I'm using Win7 64bit, and Dfuse/STDFU version is 3.0.1.

 

I ended up doing everything in STDFU. After re-erasing in STDFU just in case, I did this:

  • Click "Load DFU file" and select the 4.2.1.2 DFU file. You should see a bunch of data in the Images window.
  • Select "Download" radio button and clock "Go" and it does the actual programming cycle. Hopefully you'll get a "success" message.
  • Select "Leave DFU mode" radio button and click "Go".
  • Unplug Netduino and plug back in, then check firmware version in MFDeploy->Target->Device Capabilities


#57 iced98lx

iced98lx

    Advanced Member

  • Members
  • PipPipPip
  • 134 posts
  • LocationSouth Dakota

Posted 07 January 2013 - 05:57 PM

mattcro I almost did that as well, Dfuse refused to launch on my windows 7 box until I put it into xp compatibility mode, then for three attempts it didn't get all the way through writing. Finally on attempt 4 it finished. While looking at how to get dfuse to  launch I noticed the options you looked at in sdfu tester, and was about to to it, glad to know it's possible.



#58 iced98lx

iced98lx

    Advanced Member

  • Members
  • PipPipPip
  • 134 posts
  • LocationSouth Dakota

Posted 07 January 2013 - 06:00 PM

also as pointed out, I was not on the latest, and got updated, MAC working properly now of course. Thank you for noticing what I overlooked.






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.