Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

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.

Cannot "connect" to N+ after deploying simple app

Started by Ryan Abrahamson, Jul 27 2012 08:59 PM

Please log in to reply

3 replies to this topic

#1 Ryan Abrahamson

New Member

Members
7 posts

LocationMpls, MN

Posted 27 July 2012 - 08:59 PM

I have spent a lot of time today trying to get my N+ up and running on the new 4.2 setup. I finally got my likely led blinking app deployed with a simple debug.print line as well, but now I cannot connect to the device once the code has been deployed . Have I missed something somewhere, I have done just about everything today including going back to 4.1 and back again.

Back to top

#2 Chris Walker

Secret Labs Staff

Moderators
7767 posts

LocationNew York, NY

Posted 27 July 2012 - 09:45 PM

Hi Ryan, Let's see if we can help get you up and running... When you deploy your new app, what happens exactly? And if you push the button on your Netduino Plus to reset it during deployment does that help? Welcome to the Netduino community, Chris

Back to top

#3 Ryan Abrahamson

New Member

Members
7 posts

LocationMpls, MN

Posted 30 July 2012 - 06:01 PM

Hi Ryan,

Let's see if we can help get you up and running...

When you deploy your new app, what happens exactly? And if you push the button on your Netduino Plus to reset it during deployment does that help?

Welcome to the Netduino community,

Chris

Thank you Chris for responding! I got a reply from another post that I had asking if I was using an external power supply to power the board. I thought I could power it with simply the USB connection. But, now that I have added the external power source, the board seems to behaving as expected.

Is there a 'theory of operation' or any documentation around how the systems works together? I seems like the blue led on the board corresponds to the time when the bootloader is available vs when the CLR is running. It seems like I can only change the configuration of the Networking (IP address, etc) components with MFDeploy when the bootloader is running vs. the CLR.

Thanks,
Ryan

Back to top

#4 Chris Walker

Secret Labs Staff

Moderators
7767 posts

LocationNew York, NY

Posted 04 August 2012 - 04:04 AM

Hi Ryan,

Is there a 'theory of operation' or any documentation around how the systems works together? I seems like the blue led on the board corresponds to the time when the bootloader is available vs when the CLR is running. It seems like I can only change the configuration of the Networking (IP address, etc) components with MFDeploy when the bootloader is running vs. the CLR.

The blue LED turns on during boot and then turns off after the NETMF runtime has started up...at which point your app starts running immediately.

You should be able to change your network configuration while TinyCLR is running...but if that ever gives you problems then just start the board up in TinyBooter mode as you have done.

Chris