Main Site Documentation

Can not deploy to Domino device anymore


#1

Using VS 2010 I used to be able to deploy to my Domino device, but now I get a ‘Check Hardware’ message.

I’ve uninstalled everything, then installed :-

MS Microframework 4.1 SDK
GHI SDK 4.1 (Version 1.0.11)
GHI NETMF USB Drivers 64-Bit Auto Installer

I’ve used MSDeploy and erased the device.
Then I’ve used TeraTerm and Tranmitted C:\Program Files (x86)\GHI Electronics\GHI NETMF v4.1 SDK\USBizi\Firmware\USBizi_CLR.GHI sucessfully, then disconnected.

I still get, when pressing ‘V’ in firmware update mode, 1.07 coming from the board?

It this the correct version??

Using MSDeploy, connecting and list Device Capabilies I get :-

Pinging… TinyCLR
HalSystemInfo.halVersion:
HalSystemInfo.halVendorInfo:
HalSystemInfo.oemCode: 0
HalSystemInfo.modelCode: 0
HalSystemInfo.skuCode: 0
HalSystemInfo.moduleSerialNumber:
HalSystemInfo.systemSerialNumber:
ClrInfo.clrVersion: 4.1.2821.0
ClrInfo.clrVendorInfo: Microsoft Copyright © Microsoft Corporation. All rig
ClrInfo.targetFrameworkVersion: 4.1.2821.0
SolutionReleaseInfo.solutionVersion: 4.1.3.0
SolutionReleaseInfo.solutionVendorInfo: GHI Electronics, LLC
SoftwareVersion.BuildDate: Oct 15 2010
SoftwareVersion.CompilerVersion: 310739
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

And finaly, VS assemblies have been removed and re-added, these are :-

All GHI assemblies are Runtime Version v4.0.30319 and version 4.1.3.0
All Microsoft assemblies are Runtime Version v4.0.30319 and version 4.1.2821.0.

Is version 4.1.2821.0 correct, should it not be 1.4.3.0, if so how do this?

Thanks

Jason.


#2
  1. Have you unplugged your device’s power and plugged back in?
  2. Are u using a powered usb hub? If not, try a powered one.

#3

It’s just taking power from the PC’s USB port. As all other function, i.e. Connecting with TeraTerm and listing Device capabilities using MSDeploy are working and assume it’s power requirements are met and and not effecting the VS deploy function.

I think it’s to do with a version mis-match. I dont even think the board is faulty because of the functionality it’s currently able to do, just no more deploy??


#4

Can you please show VS deploy output here?


#5

Yes,

Output from Microsoft Framework Device Deloyment is :-

Incrementally deploying assemblies to device
Deploying assemblies for a total size of 162028 bytes
Assemblies not successfully deployed to device.
Deployment to the device was not successful.

Output from Build is :-

------ Build started: Project: UAVPilot, Configuration: Debug Any CPU ------
UAVPilot -> C:\Users\Jason\Documents\UAVProject\Development\UAVPilot\UAVPilot\UAVPilot\bin\Debug\UAVPilot.exe
------ Deploy started: Project: UAVPilot, Configuration: Debug Any CPU ------
------ Deploy started: Project: UAVPilot, Configuration: Debug Any CPU ------
An error has occurred. Please check your hardware========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Output from Debug is :-

Found debugger!

Create TS.

Loading start at 4e13c, end 56314

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

Loading Deployment Assemblies.

Resolving.

Total: (3092 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)

DebuggingInfo = 788 bytes

Attributes = 0 bytes ( 0 elements)

TypeSpec = 16 bytes ( 4 elements)

Resources Files = 48 bytes ( 2 elements)

Resources = 232 bytes ( 29 elements)

Resources Data = 437 bytes

Strings = 1551 bytes

Signatures = 2126 bytes

ByteCode = 11702 bytes

Ready.

Cannot find any entrypoint!

Done.

Waiting for debug commands…

Found debugger!

Create TS.

Loading start at 4e13c, end 56314

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

Loading Deployment Assemblies.

Resolving.

Total: (3092 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)

DebuggingInfo = 788 bytes

Attributes = 0 bytes ( 0 elements)

TypeSpec = 16 bytes ( 4 elements)

Resources Files = 48 bytes ( 2 elements)

Resources = 232 bytes ( 29 elements)

Resources Data = 437 bytes

Strings = 1551 bytes

Signatures = 2126 bytes

ByteCode = 11702 bytes

Ready.

Cannot find any entrypoint!

Done.

Waiting for debug commands…

Hope that helps, I desperate to resolve this. Thanks Jason.


#6

Open release motes file in the root of GHI sdk on your pc. What version you see there?


#7

I have :-


GHI Electronics, LLC
NETMF SDK for NETMF v4.1


SDK Version 1.0.11
October 15, 2010

Version Info

Firmware, Tinybooter (if applicable) and libraries are compatible for each SDK release and they may not work with previous releases. Make sure to update all your software components including firmware and library assemblies. Otherwise, your managed application will not run at all or run incorrectly.

Important note: Requires .NET Micro Framework 4.1 and Visual Studio 2010

• USBizi (FEZ Mini, FEZ Domino, FEZ Rhino, FEZ Panda) V 4.1.3.0
• EMX (FEZ Cobra) V 4.1.3.0, TinyBooter V 4.1.3.0
• ChipworkX V 4.1.3.0 TinyBooter V 4.1.3.0
• GHI NETMF Library V 4.1.3.0


#8

Good, now make new console project and do not add any GHI assemblies, can you deploy it?

Also, enter GHI loader, erase all using E command and then reload the firmware.


#9

I made a new console project and it deployed!!

Went back to my project and it failed.

What do you mean by the GHI loader??


#10

Sorry, I know what you mean now.

Did that and got :-

BL
1.07
BL
Erase all memory! Are you sure?
Erasing…BL
Start File Transfer
CCCCCCCCCCCCCCC
File Transfer Finished Successfully

Deploy from VS still fails?


#11

I created a new Fez Domino project and it also deployed?

It’s running the blinking LED example.


#12

Ok so now we verified the firmware + was able to deploy console app + able to blink an LED…only your one project doesn’t work.
You could spend hours trying to figure out what is the problem or just make a new project then add your source files, which can be done in 5 minutes :slight_smile:


#13

I agree, I’ll start pasting code and see what happens!

Thanks for being around, especially on a Sunday! Cheers!


#14

I had a similar problem. I resolved it by removing all of the GHI libraries from my project, then added them back.


#15

Yes this is a must step after you update the SDK and firmware. This step will update the files inside your project folder with the new ones from new SDK


#16

Shouldn’t “Build/Clean Solution” and “Build” again do the same thing? Without having to remove refs and adding them back in. I will try to remember to test that next upgrade.


#17

I had a similar issue, but with the Fez Mini, which I resolved by removing all the references and only adding the ones that were truly needed…

I could reproduce the problem, and after some testing, I think, in my project, its caused by the size of the assembly.

I made a script that slowly increases the size of the assembly, and when it hits a little over 147456 bytes, the deployment breaks.


#18

Which is expected as mini flash size is 148kbytes


#19

So couldn’t that have been the original posters problem?

He posts that the assembly is 162028 bytes.

I know that this is an old thread, and the ‘problem’ has properly been discussed a lot.
Just wanted to share…


#20

Possible.