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

Network disabled on Netduino Plus


  • Please log in to reply
6 replies to this topic

#1 dodgyrabbit

dodgyrabbit

    Member

  • Members
  • PipPip
  • 12 posts

Posted 22 September 2013 - 09:17 PM

I tried to upgrade my Netduino Plus (first generation) to version 4.2 and followed all the steps - replacing bootloader, firmware etc. Although it all seemed to work OK, problems started happening when I tried to deploy code in Visual Studio.

 

I then reverted to 4.1 (the latest in the forums) and everything works OK.

 

However, my Ethernet Port seems to be dead now. If I run MFDeploy and go to Target->Configuration->Network it fails with an error about the configuration being old and I can't set it.

 

My question is - how do I reset things to the way it was with 4.1 completely? Do I have to revert the bootloader or something? 

 

FYI: If I plug a network cable in, none of the lights come on or anything.



#2 dodgyrabbit

dodgyrabbit

    Member

  • Members
  • PipPip
  • 12 posts

Posted 22 September 2013 - 10:00 PM

Never mind... looks like Netduino (not plus) firmware got loaded by mistake. Doh!



#3 TinkeringTurtle

TinkeringTurtle

    Advanced Member

  • Members
  • PipPipPip
  • 55 posts

Posted 22 September 2013 - 10:01 PM

When you initially upgraded to 4.2, did you remember to set the MAC address while the unit was still in bootloader mode?



#4 dodgyrabbit

dodgyrabbit

    Member

  • Members
  • PipPip
  • 12 posts

Posted 23 September 2013 - 03:36 AM

Yes, I set it to the MAC address printed on the back.

I retraced my steps tonight and same issue happened - visual studio gets stuck on deployment.

 

I switched to mfusb and rebooted - then I could deploy but then it failed because the project was still referencing SecretLabs 4.1 assemblies. I switched that and successfully deployed. However, these drivers are a bit fiddly because a surprise removal causes Windows 8 to crash. 

 

So I reverted back to the winusb drivers and suddenly everything started working.

 

Which makes me think perhaps the whole "stuck deploying" is some weird state if your project references a mix between 4.2 (spot assemblies) and 4.1 (secretlabs). I've read some other people having trouble upgrading from 4.1 to 4.2 with N+, so hopefully this helps someone.



#5 TinkeringTurtle

TinkeringTurtle

    Advanced Member

  • Members
  • PipPipPip
  • 55 posts

Posted 23 September 2013 - 12:15 PM

I've had a board that acted as if it were stuck deploying endlessly. The easiest way for me to resolve was to plug up the Netduno via USB about five seconds AFTER you begin the debug deployment. Once doing this once, the problem never came back again.



#6 dodgyrabbit

dodgyrabbit

    Member

  • Members
  • PipPip
  • 12 posts

Posted 25 September 2013 - 08:34 PM

I learned a few new things that might be useful for others:

 

My NetDuino Plus stopped deploying after I made some code changes. Could not get it to recover by unplugging, plugging, rebooting PC etc.

 

Turns out that I deployed something bad that makes the NetDuino hang. 

To "fix" that - you just go to MFDeploy and click Erase and just erase the "app" and not the Firmware.

 

This allows me to instantly deploy again.

 

Now, weird thing is I manage to hang the netduino plus by creating a PWM for digital pin 1 and setting the duty cycle to 100. Anyways, this might be a known issue or something else I'm doing wrong...



#7 Anthony Glenwright

Anthony Glenwright

    Advanced Member

  • Members
  • PipPipPip
  • 71 posts

Posted 26 September 2013 - 05:08 AM

Which enum did you use for the PWM constructor?  I remember having strange results like this (not with PWM, it was one of the digital ports) and it turned out that I was using the Microsoft.SPOT pin enum instead of the SecretLabs.NetDuino one, and was therefore accessing some unknown pin, which in my case also affected Ethernet.






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.