Guys, thanks for sticking with me on this. I checked the socket and I was #1. I then removed the seal on the DIP switches and change the right hand three to ON-ON-ON (Loader) and things started to happen again. I saw the device in Device Manger and could connect to it using MFDeploy. I flashed the CLR with V4.1 again and then rebooted the board and this is what was output when I clicked SHow Device Info.
DeviceInfo:
HAL build info: 4.1.2821.0, Microsoft Copyright (C) Microsoft Corporation. All rig
OEM Product codes (vendor, model, SKU): 255, 0, 65535
Serial Numbers (module, system):
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Solution Build Info: 4.1.8.0, GHI Electronics, LLC
AppDomains:
default, id=1
Assemblies:
mscorlib,4.1.2821.0
Microsoft.SPOT.Native,4.1.2821.0
When I clicked Device Capablities I got
HalSystemInfo.halVersion: 4.1.2821.0
HalSystemInfo.halVendorInfo: Microsoft Copyright (C) Microsoft Corporation. All rig
HalSystemInfo.oemCode: 255
HalSystemInfo.modelCode: 0
HalSystemInfo.skuCode: 65535
HalSystemInfo.moduleSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
HalSystemInfo.systemSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
ClrInfo.clrVersion: 4.1.2821.0
ClrInfo.clrVendorInfo: Microsoft Copyright (C) Microsoft Corporation. All rig
ClrInfo.targetFrameworkVersion: 4.1.2821.0
SolutionReleaseInfo.solutionVersion: 4.1.8.0
SolutionReleaseInfo.solutionVendorInfo: GHI Electronics, LLC
SoftwareVersion.BuildDate: Dec 22 2011
SoftwareVersion.CompilerVersion: 410561
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 then moved the DIP to their normal position and nothing shows up in Device Manager. I move them to ON-ON-ON and I see the Debuggable .Net Micro Framework Deivce in Device Manager again. WHen I click Connect in MFDeploy I get this response.
Connecting to EMX_EMX…Connected
If I click Reboot and Stop I get
Reboot and Stop Command
Reboot and Stop Complete
If I click Ping I get
Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
I have flashed the CLR with the following by selected them and clicking Deploy
C:\Program Files (x86)\GHI Electronics\GHI NETMF v4.1 SDK\EMX\Firmware\CLR.HEX
C:\Program Files (x86)\GHI Electronics\GHI NETMF v4.1 SDK\EMX\Firmware\CLR2.HEX
C:\Program Files (x86)\GHI Electronics\GHI NETMF v4.1 SDK\EMX\Firmware\Config.HEX
This is the output
Connecting to EMX_EMX…Connected
DeviceInfo is not valid!
DeviceInfo is not valid!
Chk signature
Signature PASS
Chk signature
Signature PASS
Now when I click Device Info I get
ip address from interface info: 192.168.1.200
mac addrress from interface info: 0.1a.f1.0.42.d
EMX
Version: 4.1.8.0
Debug: USB1
LCD: 320x240
IP: 192.168.1.200
MAC: 00.1A.F1.00.42.0D
Managed heap size: 13041664
Custom heap size: 1048576
.NetMF v4.DeviceInfo is not valid!
1.2821.0
EMX, Build Date:
Dec 22 2011 16:27:20
ARM Compiler version 410561
TinyCLR (Build 4.1.2821.0)
Starting…
Created EE.
Started Hardware.
No debugger!
Create TS.
Loading start at a0200000, end a0209b4c
Attaching file.
Assembly: mscorlib (4.1.2821.0) (3880 RAM - 33236 ROM - 19134 METADATA)
AssemblyRef = 0 bytes ( 0 elements)
TypeRef = 0 bytes ( 0 elements)
FieldRef = 0 bytes ( 0 elements)
MethodRef = 0 bytes ( 0 elements)
TypeDef = 1112 bytes ( 139 elements)
FieldDef = 272 bytes ( 135 elements)
MethodDef = 1572 bytes ( 786 elements)
Attributes = 0 bytes ( 0 elements)
TypeSpec = 16 bytes ( 4 elements)
Resources = 232 bytes ( 29 elements)
Resources Files = 16 bytes ( 2 elements)
Resources Data = 437 bytes
Strings = 1551 bytes
Signatures = 2126 bytes
ByteCode = 11702 bytes
Attaching file.
Assembly: Microsoft.SPOT.Native (4.1.2821.0) (1144 RAM - 6516 ROM - 4479 METADATA)
AssemblyRef = 4 bytes ( 1 elements)
TypeRef = 80 bytes ( 20 elements)
FieldRef = 0 bytes ( 0 elements)
MethodRef = 60 bytes ( 15 elements)
TypeDef = 336 bytes ( 42 elements)
FieldDef = 192 bytes ( 95 elements)
MethodDef = 224 bytes ( 111 elements)
Attributes = 48 bytes ( 6 elements)
TypeSpec = 0 bytes ( 0 elements)
Resources = 72 bytes ( 9 elements)
Resources Files = 8 bytes ( 1 elements)
Resources Data = 747 bytes
Strings = 648 bytes
Signatures = 595 bytes
ByteCode = 418 bytes
Loading Deployment Assemblies.
Resolving.
Total: (4124 RAM - 39752 ROM - 23613 METADATA)
AssemblyRef = 4 bytes ( 1 elements)
TypeRef = 80 bytes ( 20 elements)
FieldRef = 0 bytes ( 0 elements)
MethodRef = 60 bytes ( 15 elements)
TypeDef = 1448 bytes ( 181 elements)
FieldDef = 464 bytes ( 230 elements)
MethodDef = 1796 bytes ( 897 elements)
DebuggingInfo = 900 bytes
Attributes = 48 bytes ( 6 elements)
TypeSpec = 16 bytes ( 4 elements)
Resources Files = 72 bytes ( 3 elements)
Resources = 304 bytes ( 38 elements)
Resources Data = 1184 bytes
Strings = 2199 bytes
Signatures = 2721 bytes
ByteCode = 12120 bytes
GC: 1msec 5136 bytes used, 13035912 bytes available
Type 0F (STRING ): 24 bytes
Type 15 (FREEBLOCK ): 13035912 bytes
Type 17 (ASSEMBLY ): 5040 bytes
Type 34 (APPDOMAIN_HEAD ): 72 bytes
Total: (4124 RAM - 39752 ROM - 23613 METADATA)
AssemblyRef = 4 bytes ( 1 elements)
TypeRef = 80 bytes ( 20 elements)
FieldRef = 0 bytes ( 0 elements)
MethodRef = 60 bytes ( 15 elements)
TypeDef = 1448 bytes ( 181 elements)
FieldDef = 464 bytes ( 230 elements)
MethodDef = 1796 bytes ( 897 elements)
DebuggingInfo = 900 bytes
Attributes = 48 bytes ( 6 elements)
TypeSpec = 16 bytes ( 4 elements)
Resources Files = 72 bytes ( 3 elements)
Resources = 304 bytes ( 38 elements)
Resources Data = 1184 bytes
Strings = 2199 bytes
Signatures = 2721 bytes
ByteCode = 12120 bytes
Ready.
Cannot find any entrypoint!
Done.
Waiting for debug commands…
I can disconnect the and reconnect and then ping. If I do this is the output I see
Connecting to EMX_EMX…Connected
User Cancel…
Connecting to EMX_EMX…Connected
Pinging… TinyCLR
If I move teh DIP switches back I get nothing again…
Any thing else you guys think I should try before sending this back??
Thanks, Jason.