Deploy failed
#1
Posted 22 July 2012 - 08:25 PM
When I run that sample program, I get:
-----------------------------------------------------------------------------------------
------ Build started: Project: AdaFruitVC0706Test, Configuration: Debug Any CPU ------
AdaFruitVC0706Test -> E:\netduino\netduinohelpers_249dd927c92e\Samples\AdaFruitVC0706Test\AdaFruitVC0706Test\bin\Debug\AdaFruitVC0706Test.exe
------ Skipped Deploy: Project: netduino.helpers, Configuration: Debug Any CPU ------
Project not selected to build for this solution configuration
------ Deploy started: Project: AdaFruitVC0706Test, Configuration: Debug Any CPU ------
An error has occurred. Please check your hardware========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 1 skipped ==========
---------------------------------------------------------------------------------------------------
Does this point to hardware problem or short circuit between the headphones?
Lou
#2
Posted 22 July 2012 - 08:34 PM
I'm curious how that happened. Is that all the output window gave back?------ Skipped Deploy: Project: netduino.helpers, Configuration: Debug Any CPU ------
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#3
Posted 22 July 2012 - 08:45 PM
#4
Posted 23 July 2012 - 06:09 AM
That's why it's not working;The deployment output is:
------------------------------------------------------------------------------------
Incrementally deploying assemblies to device
Deploying assemblies for a total size of 104964 bytes
Assemblies not successfully deployed to device.
Deployment to the device was not successful.
--------------------------------------------------------------------------------------
From http://www.netduino....plus/specs.htm:
Your code is 102,5kB big.Code Storage: 64 KB
If you have included -all- code from the netduino helpers, I'd suggest just include the .cs files you'll need.
They normally are very relyable. I suggest to erase code memory completely for now, with this tool: "C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Tools\MFDeploy.exe"EDIT: Never mind for now, I can no longer run the simple LED blinking test. It thinks it ran but it doesn't. I am thinking that it is a hardware issue. Are these N+'s usually reliable? This has done nothing but run some simple LED and ethernet test programs.
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#5
Posted 23 July 2012 - 06:39 PM
10-4 thanks, dumb me, I should have seen that.That's why it's not working;
From http://www.netduino....plus/specs.htm:
Your code is 102,5kB big.
If you have included -all- code from the netduino helpers, I'd suggest just include the .cs files you'll need.
They normally are very relyable. I suggest to erase code memory completely for now, with this tool: "C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Tools\MFDeploy.exe"
I had erased it all but it still won't run even the simplest program. I have a new one arriving tomorrow. In the meantime, the day job is calling.
Thanks again.
Lou
#6
Posted 23 July 2012 - 09:07 PM
That's odd. It's very difficult to really brick a netduino, believe me, I tried!I had erased it all but it still won't run even the simplest program.
You could always reflash it's firmware. Instructions are on the wiki
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#7
Posted 24 July 2012 - 12:19 AM
Thanks, I did that as well..That's odd. It's very difficult to really brick a netduino, believe me, I tried!
You could always reflash it's firmware. Instructions are on the wiki
Lou
#8
Posted 25 July 2012 - 05:19 AM
#9
Posted 25 July 2012 - 05:24 AM
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#10
Posted 25 July 2012 - 05:30 AM
cege7480: Which firmware version? Firmware 4.2rc5 (beta) still has some bsod issues.
I found that if my Netduino doesn't deploy, I disconnect my netduino, thén press F5, and then connect my netduino. A work-around, but it helps against the bsod issue in 4.2
Here is the output when I ran an Erase from MFDeploy (the only thing that seemed to be able to talk to it... If I unplug the Netduino I don't even go BSOD, just right to POST.
Rebooting...
AutoNegotiate complete
DM9161_GetLinkSpeed passed
Link detected 0x0
ip address from interface info: 192.168.254.73
TinyCLR (Build 4.1.2821.0)
Starting...
Created EE.
Started Hardware.
Found debugger!
Create TS.
Loading start at 14d324, end 162e8c
Attaching file.
Assembly: mscorlib (4.1.2821.0) (3880 RAM - 33236 ROM - 19134 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Native (4.1.2821.0) (1144 RAM - 6516 ROM - 4479 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Hardware (4.1.2821.0) (1752 RAM - 11440 ROM - 7371 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Net (4.1.2821.0) (704 RAM - 5060 ROM - 2452 METADATA)
Attaching file.
Assembly: System (4.1.2821.0) (872 RAM - 5992 ROM - 3206 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.IO (4.1.2821.0) (740 RAM - 4620 ROM - 2522 METADATA)
Attaching file.
Assembly: System.IO (4.1.2821.0) (1548 RAM - 13292 ROM - 5862 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Hardware.SerialPort (4.1.2821.0) (512 RAM - 3488 ROM - 1543 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Hardware.Usb (4.1.2821.0) (580 RAM - 3740 ROM - 1844 METADATA)
Attaching file.
Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) (256 RAM - 1108 ROM - 491 METADATA)
Attaching file.
Assembly: SecretLabs.NETMF.Diagnostics (4.1.0.0) (180 RAM - 440 ROM - 166 METADATA)
Loading Deployment Assemblies.
Resolving.
Total: (10500 RAM - 88932 ROM - 49070 METADATA)
Total: (10500 RAM - 88932 ROM - 49070 METADATA)
Ready.
Cannot find any entrypoint!
Done.
Waiting for debug commands...
#11
Posted 25 July 2012 - 07:55 AM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users