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

Blue socket LEDs stay lit


  • Please log in to reply
4 replies to this topic

#1 T&N

T&N

    New Member

  • Members
  • Pip
  • 3 posts

Posted 14 April 2012 - 04:45 PM

The blue LEDs will not go off even though there are no modules plugged in. When I plug in the rgbLED module nothing changes. I've tried rebooting, other usb power sources (another computer, another cable), reflashed (the firmware),... without success. I'm using Microsoft MF 4.2. while using the MFDeploy utility, ping pruduces "TinyCLR" and device capabilities shows version 4.2.0.0. Upon inititial power up (with the rgb led plugged in), ony the white power light was lit. After unplugging and repluuging into the USB the current all blue lights situation occured. I've tried deploying the rgb led sample and get the following messages while deploying: "the debugging target is not in an initialized state; rebooting" and then "the debugging target initialized successfully" I've run out of idea's, hope someone can help. Todd

#2 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 14 April 2012 - 09:03 PM

Hi T&N, Hmm, very interesting. It sounds like the app on your Netduino Go is keeping it from booting properly. Can you please try the following? 1. Unplug modules from your Netduino Go 2. Plug the Netduino Go into your PC Do the blue LEDs all turn on? Do they all then turn off? 3. In MFDeploy, select your device and press Ping. 4. Once you get a response "TinyCLR" press the ERASE button and clear off your current app. Does that fix things for you? If not, the information you provide will help us diagnose the issue and get you back up and running... Chris

#3 T&N

T&N

    New Member

  • Members
  • Pip
  • 3 posts

Posted 15 April 2012 - 03:21 AM

Chris, Thanks for the reply. After step1 1 & 2 the blue lights are on immediately and stay on. After steps 4 & 5, the blue lights go away. I then plugged the RgbLed module in and there was no blue light. I tried different sockets and a different cable, but no blue lights. Tried to redploy the sample rgbled program and nothing changed, only the white power button is lit. Unplugged the Go from the pc and replugged back in and all the blue lights have returned and won't go off unless i "erase". Thanks again for your help. Todd

#4 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 15 April 2012 - 03:27 AM

Hi Todd, It sounds like there may be an issue with the code being deployed to your device. Did you create a .NET Micro Framework 4.2 project? Are you using the newer .NET Micro Framework 4.2 "QFE1" SDK? QFE1 is important. When you deploy your app, do you see any issues in the deployment window? Finally...if you plug in your Netduino Go while MFDeploy is open...and then press PING, can you grab the startup debug text so we can see exactly what's going on? Chris

#5 T&N

T&N

    New Member

  • Members
  • Pip
  • 3 posts

Posted 15 April 2012 - 05:05 AM

Chris, Success! I was not using the QFE1 version of the Micro Framework 4.2 just like you called it.(I was using the 4.2 RTM version.) I uninstalled the previous version and installed the QFE1. I made another mistake, in that I opened my project as a Netduino application instead of a console application. Also, I tried to get the debug information from pinging in the MFDeploy executable before the fixes, but I was unable to capture anything. I got my first Netduino program working. Thanks again for all your help. Todd




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.