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

I just reflashed my Netduino and the board refuses to respond

reflash Netduino

Best Answer Anthony Glenwright, 11 July 2013 - 04:26 AM

Sometimes I find that in Visual studio (in project properties/.NET Micro Framework) you have to re-select the Netduino as a deployment target by changing the transport from USB to serial and back again.

Go to the full post


  • Please log in to reply
5 replies to this topic

#1 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 10 July 2013 - 04:16 PM

[font="'times new roman', times, serif;"]Hello![/font]

[font="'times new roman', times, serif;"]I needed to reflash my Netduino. And I am getting the exact same response from VS2010 Express C#. And as it happens both the device and the IDE are disagreeing. Flashing it followed the steps laid down in the original Wiki pages. [/font]

 

[font="'times new roman', times, serif;"]Those pages are http://wiki.netduino...ep-by-step.ashx. I started there, and ended up with http://wiki.netduino...ep-by-step.ashx I went through those two steps again, when I had issues with the device along those lines below. [/font]

 

[font="'times new roman', times, serif;"]But the response is here:[/font]

------ 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_2FrameworkCorDebugDebugPort.cs:line 290
   at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.Deploy() in c:depotcurrentCLIENT_V4_2FrameworkCorDebugVsProjectFlavorCfg.cs:line 809
   at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.<Microsoft.VisualStudio.Shell.Interop.IVsDeployableProjectCfg.StartDeploy>b__0() in c:depotcurrentCLIENT_V4_2FrameworkCorDebugVsProjectFlavorCfg.cs:line 634
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
 
I freely admit I am clueless here. I had thought that following those steps to flash the device would fix things. Advice here please.


Doctor Who
"This signature does not exist!"

#2 iced98lx

iced98lx

    Advanced Member

  • Members
  • PipPipPip
  • 134 posts
  • LocationSouth Dakota

Posted 10 July 2013 - 05:07 PM

What does MF Deploy state about your board? What shows in device manager when it's plugged in?



#3 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 10 July 2013 - 05:41 PM

What does MF Deploy state about your board? What shows in device manager when it's plugged in?

 

Hello!

Device manager obviously says its at home. because the deploy tool let me ping it. I then confirmed that the tinyCLR object I posted to the thing  worked from seeing the legend "Pinging... TinyCLR" in the events window.

 

And this is what the deploy program insists about the board:

"DeviceInfo:

  HAL build info: 4.2.0.0, Netduino (v4.2.0.1) by Secret Labs LLC
  OEM Product codes (vendor, model, SKU): 34, 177, 4096
  Serial Numbers (module, system):
    00000000000000000000000000000000
    0000000000000000
  Solution Build Info: 4.2.0.0, Netduino (v4.2.0.1) by Secret Labs LLC
  AppDomains:
    default, id=1
  Assemblies:
    mscorlib,4.2.0.0
    Microsoft.SPOT.Native,4.2.0.0
    Microsoft.SPOT.Hardware,4.2.0.0
    Microsoft.SPOT.Hardware.SerialPort,4.2.0.0
    Microsoft.SPOT.IO,4.2.0.0
    System.IO,4.2.0.0
    Microsoft.SPOT.Hardware.PWM,4.2.0.1
    SecretLabs.NETMF.Diagnostics,4.2.0.0
    SecretLabs.NETMF.IO,4.2.0.0"
 
Oh and this is the device capabilities screen:
"Connecting to Netduino_Netduino...Connected
HalSystemInfo.halVersion:               4.2.0.0
HalSystemInfo.halVendorInfo:            Netduino (v4.2.0.1) by Secret Labs LLC
HalSystemInfo.oemCode:                  34
HalSystemInfo.modelCode:                177
HalSystemInfo.skuCode:                  4096
HalSystemInfo.moduleSerialNumber:       00000000000000000000000000000000
HalSystemInfo.systemSerialNumber:       0000000000000000
ClrInfo.clrVersion:                     4.2.0.0
ClrInfo.clrVendorInfo:                  Netduino (v4.2.0.1) by Secret Labs LLC
ClrInfo.targetFrameworkVersion:         4.2.0.0
SolutionReleaseInfo.solutionVersion:    4.2.0.0
SolutionReleaseInfo.solutionVendorInfo: Netduino (v4.2.0.1) by Secret Labs LLC
SoftwareVersion.BuildDate:              Sep 19 2012
SoftwareVersion.CompilerVersion:        410894
FloatingPoint:                          True
SourceLevelDebugging:                   True
ThreadCreateEx:                         True
LCD.Width:                              0
LCD.Height:                             0
LCD.BitsPerPixel:                       0
AppDomains:                             True
ExceptionFilters:                       True
IncrementalDeployment:                  True
SoftReboot:                             True
Profiling:                              False
ProfilingAllocations:                   False
ProfilingCalls:                         False
IsUnknown:                              False"
 
I'm going to try and make use of the IDE and see what happens next. It was the same as before.

Edited by Dr Who, 11 July 2013 - 03:19 AM.


Doctor Who
"This signature does not exist!"

#4 Anthony Glenwright

Anthony Glenwright

    Advanced Member

  • Members
  • PipPipPip
  • 71 posts

Posted 11 July 2013 - 04:26 AM   Best Answer

Sometimes I find that in Visual studio (in project properties/.NET Micro Framework) you have to re-select the Netduino as a deployment target by changing the transport from USB to serial and back again.



#5 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 11 July 2013 - 06:32 AM

Sometimes I find that in Visual studio (in project properties/.NET Micro Framework) you have to re-select the Netduino as a deployment target by changing the transport from USB to serial and back again.

 

Hello!

Oddly enough Anthony, that worked. I plugged it back in, and brought up the classic example. blink, it hung up claiming that there was a problem with the hardware. I told it on the properties page it wasn't there, it was supposed to be a serial connection. Waited a moment, and switched back and tried again. It's still running. It seems iced98lx we now have our answer when problems surface. Did that one occur to you? I did reflash it before, because something caused the mechanism behind the scenes to promptly go "crash-bang" and I knew that doing those steps earlier would correct it.

 

Anthony, if you're ever playing tourist in NYC, I owe you something. Same with you iced98lx but you knew that already.



Doctor Who
"This signature does not exist!"

#6 iced98lx

iced98lx

    Advanced Member

  • Members
  • PipPipPip
  • 134 posts
  • LocationSouth Dakota

Posted 11 July 2013 - 03:59 PM

Brilliant! I've had it hang like that on me but un-plugging, rebooting the board, and plugging back in always fixed it. This is likely an easier way to solve both problems. 







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.