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

New user: using VS2013 problems

vs2013 netduino plus 2

  • Please log in to reply
6 replies to this topic

#1 rolandwolters

rolandwolters

    New Member

  • Members
  • Pip
  • 4 posts

Posted 01 December 2014 - 09:54 PM

Hi,

 

So i recently bought my first Netduino Plus 2, and because i already work with Visual Studio 2013 i wanted to program the Netduino with it. To do this I updated the Netduino to 4.3.1 and wrote the first program from the getting started pdf. It does compile and seems to deploy ok but then the debugger kicks in shouting the device is not in the initialized state. The debugger stops and no flashing LED on the device.

 

How do i get it working?

 

 
OutputPort led = new OutputPort(Pins.ONBOARD_LED, false);
            while (true)
            {
                led.Write(false); // turn on the LED
                Thread.Sleep(250); // sleep for 250ms
                led.Write(true); // turn off the LED
                Thread.Sleep(250); // sleep for 250ms 
            }
 
-- MFDeploy output:
 
HalSystemInfo.halVersion:               4.3.1.0
HalSystemInfo.halVendorInfo:            Netduino Plus 2 (v4.3.1.0) by Secret Labs LLC
HalSystemInfo.oemCode:                  34
HalSystemInfo.modelCode:                177
HalSystemInfo.skuCode:                  4102
HalSystemInfo.moduleSerialNumber:       00000000000000000000000000000000
HalSystemInfo.systemSerialNumber:       0000000000000000
ClrInfo.clrVersion:                     4.3.1.0
ClrInfo.clrVendorInfo:                  Netduino Plus 2 (v4.3.1.0) by Secret Labs LLC
ClrInfo.targetFrameworkVersion:         4.3.1.0
SolutionReleaseInfo.solutionVersion:    4.3.1.0
SolutionReleaseInfo.solutionVendorInfo: Netduino Plus 2 (v4.3.1.0) by Secret Labs LLC
SoftwareVersion.BuildDate:              Feb 25 2014
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:                             False
Profiling:                              False
ProfilingAllocations:                   False
ProfilingCalls:                         False
IsUnknown:                              False
 

 



#2 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 02 December 2014 - 03:58 AM

Hi rolandwolters,

What happens if you reboot the device (by pressing the pushbutton) while the debugger is having trouble attaching?

This sounds like it may be an MFUSB glitch in the 4.3.x SDK. Are you using NETMF 4.3 QFE1 or 4.3 R2 Beta?

Sorry for the troubles; welcome to the community!

Chris

#3 rolandwolters

rolandwolters

    New Member

  • Members
  • Pip
  • 4 posts

Posted 02 December 2014 - 08:24 PM

Pressing the pushbutton didn't help.

 

I'm running .NET Micro Framework V4.3 SDK-R2-Beta

 

I tried to re-install the sdk but no success...

 

But, apart from the debugging; should the app, because it's deployed successfully, run anyway and make the on-board led blink?



#4 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 03 December 2014 - 05:10 AM

Hi rolandwolters,

 

Yes, when you deploy your app it's stored in the flash of the device.  When you power up the device, the app will run automatically.

 

If the app doesn't start up, it likely wasn't actually deployed.  If you open up MFDeploy, press F5 to connect, reboot your board and press Ping...you should get a data dump of the board's boot process--including what app it loaded.

 

If you run 4.2 firmware on your board, does that deploy/debug alright?  This may be a WinUSB-in-4.3 issue...

 

Chris



#5 rolandwolters

rolandwolters

    New Member

  • Members
  • Pip
  • 4 posts

Posted 03 December 2014 - 08:41 AM

I'm at work atm so try this tonight (my time; now it's 9:41 am). If i want to run 4.2 on my board, i need to flash it again, right? Like i said; i'm new at this.... so how do i do that. And, when done, do i need to install a previous version of visual studio or still able to use 2013?



#6 rolandwolters

rolandwolters

    New Member

  • Members
  • Pip
  • 4 posts

Posted 22 December 2014 - 09:18 PM

Ok, so i flashed 4.2.2 using the instructions found here: http://forums.netdui...-v422-update-2/

 

Set project build settings to use 4.2, started building and deploying but....... same result.

 

hmm wait, i tried your MFDeploy ping suggestion... hmm that shows lots of errors... what should i do?

 

-----------------

Connecting to NetduinoPlus2_Netduino...Connected
IP Address: 0.0.0.0
No debugger!
Create TS.
 Loading start at 806a988, end 8085288
Assembly: mscorlib (4.2.0.0)
Assembly: Microsoft.SPOT.Native (4.2.0.0)
Assembly: Microsoft.SPOT.Hardware (4.2.0.0)
Assembly: Microsoft.SPOT.Net (4.2.0.0)
Assembly: System (4.2.0.0)
Assembly: Microsoft.SPOT.Hardware.SerialPort (4.2.0.0)
Assembly: Microsoft.SPOT.IO (4.2.0.0)
Assembly: System.IO (4.2.0.0)
Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1)
Assembly: Microsoft.SPOT.Hardware.Usb (4.2.0.0)
Assembly: SecretLabs.NETMF.Diagnostics (4.2.0.0)
Assembly: SecretLabs.NETMF.Hardware.Netduino (4.2.1.0)
Assembly: Microsoft.SPOT.Hardware.OneWire (4.2.0.0)
Assembly: Microsoft.SPOT.Time (4.2.0.0)
Loading Deployment Assemblies.
Attaching deployed file.
Assembly: MFConsoleApplication1 (1.0.0.0)
Attaching deployed file.
Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0)
Attaching deployed file.
Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (4.1.0.0)
Resolving.
Link failure: some assembly references cannot be resolved!!
 
Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0)
Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0) needs assembly 'mscorlib' (4.1.2821.0)
Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (4.1.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0)
Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (4.1.0.0) needs assembly 'mscorlib' (4.1.2821.0)
Error: a3000000


#7 Spiked

Spiked

    Advanced Member

  • Members
  • PipPipPip
  • 129 posts

Posted 22 December 2014 - 11:51 PM

Looks like it was developed against 4.1 and trying to deploy to a 4.2 loaded device.

 

Make sure you are referencing 4.2 in your visual studio project.

 

Which is really bad if you thought you were using 4.3.  Might want to take another go at it, un-install all of the PC stuff and start again.







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.