Can't download any program to my spider board

Archive
1

I updated my system to .NET MF 4.2
and I updated my firmware on my Spider board to 4.2.4.0 (that I can read from my display_TE35)
I do have a very simple program with a debug.print line and every time I got the same message below.
I have spent the last two days searching this form for a solution, I gave up now, please help.

Found debugger!

Create TS.

Loading start at a0e00000, end a0e0bd18

Assembly: mscorlib (4.2.0.0) Assembly: Microsoft.SPOT.Native (4.2.0.0) Loading Deployment Assemblies.

Attaching deployed file.

Assembly: GTM.GHIElectronics.Display_HD44780 (1.0.1.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Hardware.SerialPort (4.2.0.0) Attaching deployed file.

Assembly: GHI.Premium.IO (4.2.4.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Graphics (4.2.0.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Hardware (4.2.0.0) ***********************************************************************

  •                                                                 *

  • ERROR!!! Firmware version does not match managed code version!!! *

  •                                                                 *

  •                                                                 *

  • Invalid native checksum: Microsoft.SPOT.Hardware 0x7765AC69!=0xBF718024 *

  •                                                                 *

Attaching deployed file.

Assembly: GadgeteerApp3 (1.0.0.0) Attaching deployed file.

Assembly: System (4.2.0.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Net (4.2.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.Display_TE35 (1.0.0.0) Attaching deployed file.

Assembly: GHI.Premium.Hardware (4.2.4.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1) Attaching deployed file.

Assembly: GHIElectronics.Gadgeteer.FEZSpider (1.0.5.0) Resolving.

Link failure: some assembly references cannot be resolved!!

Assembly: GTM.GHIElectronics.Display_HD44780 (1.0.1.0) needs assembly ‘Gadgeteer’ (2.42.0.0)

Assembly: Microsoft.SPOT.Hardware.SerialPort (4.2.0.0) needs assembly ‘Microsoft.SPOT.Hardware’ (4.2.0.0)

Assembly: GHI.Premium.IO (4.2.4.0) needs assembly ‘GHI.Premium.System’ (4.2.4.0)

Assembly: Microsoft.SPOT.Graphics (4.2.0.0) needs assembly ‘Microsoft.SPOT.Hardware’ (4.2.0.0)

Assembly: GadgeteerApp3 (1.0.0.0) needs assembly ‘Gadgeteer’ (2.42.0.0)

Assembly: GadgeteerApp3 (1.0.0.0) needs assembly ‘GTM.GHIElectronics.Display_HD44780’ (1.0.1.0)

Assembly: GadgeteerApp3 (1.0.0.0) needs assembly ‘GTM.GHIElectronics.Display_TE35’ (1.0.0.0)

Assembly: GadgeteerApp3 (1.0.0.0) needs assembly ‘GTM.GHIElectronics.UsbClientDP’ (1.0.0.0)

Assembly: GadgeteerApp3 (1.0.0.0) needs assembly ‘Microsoft.SPOT.Graphics’ (4.2.0.0)

Assembly: GadgeteerApp3 (1.0.0.0) needs assembly ‘GHIElectronics.Gadgeteer.FEZSpider’ (1.0.5.0)

Assembly: System (4.2.0.0) needs assembly ‘Microsoft.SPOT.Net’ (4.2.0.0)

Assembly: Microsoft.SPOT.Net (4.2.0.0) needs assembly ‘Microsoft.SPOT.Hardware’ (4.2.0.0)

Assembly: GTM.GHIElectronics.Display_TE35 (1.0.0.0) needs assembly ‘Gadgeteer’ (2.42.0.0)

Assembly: GTM.GHIElectronics.Display_TE35 (1.0.0.0) needs assembly ‘Microsoft.SPOT.Hardware’ (4.2.0.0)

Assembly: GTM.GHIElectronics.Display_TE35 (1.0.0.0) needs assembly ‘Microsoft.SPOT.Graphics’ (4.2.0.0)

Assembly: GTM.GHIElectronics.Display_TE35 (1.0.0.0) needs assembly ‘Microsoft.SPOT.TinyCore’ (4.2.0.0)

Assembly: GTM.GHIElectronics.Display_TE35 (1.0.0.0) needs assembly ‘Microsoft.SPOT.Touch’ (4.2.0.0)

Assembly: GHI.Premium.Hardware (4.2.4.0) needs assembly ‘Microsoft.SPOT.Hardware’ (4.2.0.0)

Assembly: GHI.Premium.Hardware (4.2.4.0) needs assembly ‘GHI.Premium.System’ (4.2.4.0)

Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1) needs assembly ‘Microsoft.SPOT.Hardware’ (4.2.0.0)

Assembly: GHIElectronics.Gadgeteer.FEZSpider (1.0.5.0) needs assembly ‘Gadgeteer’ (2.42.0.0)

Assembly: GHIElectronics.Gadgeteer.FEZSpider (1.0.5.0) needs assembly ‘Microsoft.SPOT.Hardware’ (4.2.0.0)

Assembly: GHIElectronics.Gadgeteer.FEZSpider (1.0.5.0) needs assembly ‘GHI.Premium.IO’ (4.2.4.0)

Assembly: GHIElectronics.Gadgeteer.FEZSpider (1.0.5.0) needs assembly ‘GHI.Premium.Hardware’ (4.2.4.0)

Assembly: GHIElectronics.Gadgeteer.FEZSpider (1.0.5.0) needs assembly ‘GHI.Premium.System’ (4.2.4.0)

Error: a3000000

Waiting for debug commands…

The program ‘[3] Micro Framework application: Managed’ has exited with code 0 (0x0).

2

Hi Camaney,

here’s the giveaway:

This means you’re using an old project.

Two options. Rip out all your “references” in your project and re-add them, or start a new project and move your code over. This is because the project has a VS cache of all the deployed DLLs, that don’t match.

3

Looks like firmware on Spider wasn’t updated properly. Try it again.

4

Brett, I tried your recommendation w/o success, same messages.

Architect, I updated two more times the firmware on Spider, same messages.

Do you think I don’t have the correct firmware? the version I have is 4.2.4.0

Note: In the same computer I use a Cerberus board using .NET MF 4.2 and I have no issues at all.

Please help me.

5

Please connect to your device using mfdeploy and show device capabilities output. Thats how you guarantee you know what firmware version you have installed and whether your update has worked.

Then create a brand new project, that just blinks a LED, and deploy that.

6

@ camaney - Go into your project options and ensure that Visual Studio is in fact using the 4.2 Framework over 4.1. It does not happen a lot however, sometimes 4.1 gets selected over 4.2 even when starting a 4.2 project. Also, manually navigate to the installation folder, and run the updater from there.

7

I have to tell you guys, thanks for your patience and quick responses, but still can’t make it work. Setting up my Cerberus didn’t have this much trouble.

I tried all your recommendations, the error message is still the same, asking for a whole list of assemblies.

I checked my references in the Object Browser of VS2010 and they all point to the right location, for instance:
C:\Program Files (x86)\Microsoft .NET Gadgeteer\Core\Assemblies.NET Micro Framework 4.2\Gadgeteer.dll
C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Graphics.dll
C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\System.IO.dll
etc.

I checked all around VS2010 to have the right references to the right folders, I remove them and add them back again, I am running out of ideas.

Please advise, Thanks.

8

you haven’t shown us Device Capabilities from MFDeploy.

9

Brett, how do I show Device Capabilities from MFDeploy?
I have the software on, but can’t find that option.
Thanks

10

Target
Device Capabilities
(well that’s where it is in my 4.1 version )

11

Brett, I have version 2.0
Can’t find the download of 4.1, any link?
Thanks again for keeping up.

12

Found it!
Let me try now.

13

This is the info I received back:

ClrInfo.targetFrameworkVersion: 4.2.0.0
SolutionReleaseInfo.solutionVersion: 4.2.4.0
SolutionReleaseInfo.solutionVendorInfo: Copyright © GHI Electronics, LLC
SoftwareVersion.BuildDate: Aug 22 2012
SoftwareVersion.CompilerVersion: 410462
FloatingPoint: True
SourceLevelDebugging: True
ThreadCreateEx: True
LCD.Width: 320
LCD.Height: 240
LCD.BitsPerPixel: 16
AppDomains: True
ExceptionFilters: True
IncrementalDeployment: True
SoftReboot: True
Profiling: False
ProfilingAllocations: False
ProfilingCalls: False
IsUnknown: False

I did a simple project using VS2010, I got the same results; asking for a list of assemblies.

14

You have 4.2 firmware so are you making a 4.2 project?

15

Yes, I am sure.

16

How are you powering your device?

17

I am using the USB cable.

18

While USB specifications say ports should provide 500mA, we rarely see a port that can actually provide 500mA. We always recommend the use of powered hubs or a power pack instead of relying on the USB power. Use a powered hub from a known brand, not a cheap hub. If your device has the option of using a power pack (for example the USB Client DP Module) then you can use a power pack instead. 9V 1A is typically recommended but check the bottom of the circuit board for printed voltage range. All power connectors on GHI products are 2.1mm with positive on the inside and negative on the outer ring.

Not using a powered hub or power pack can cause:
[ul]Unexplained behavior
Device does not function
Device functions intermittently
Device functions but network fails
Device functions but SD card fails
Device functions but firmware update fails[/ul]
(Generated by QuickReply)