Still getting 'An error has occurred: please check your hardware.'

[kdekok]

No matter what i do, after about 2 or 3 compile&deploy actions, the embedded master becomes unresponsive.
(No matter what code runs, even just displaying hello world)
I do get TinyCLR back as a result from a ping in MFDeploy, but Visual Studio does nothing anymore, and throws me an error: An error has occurred: please check your hardware.

Even after i reset the EM, still the same result.
The only way to get this working, is connect it via the comport, startup in tinybooter, do an erase, en reboot the entire thing.

This is really annoying to do in an development environment, where i'll be debugging and deploying at least 50 times a day!

I have the latest fimware:

TinyBooter 3.0.0.0
Build date 22-oct-2008
Enbedded Master 09.09.000
Tinybooter build 001

CLR
Embedded Master version 09.09.000
Build date 3-dec-2008

Using VS2008 SP1 and the latest .Net Micro Framework SDK.

What can i do to solve?!

[kdekok]

Okay, additional info:

when i get this error, but very stubbornly keep pressing F5 very fast, like 10 to 15 times in a row... it takes on!
(Don't ask me how i found out, let's just say i was very frustrated when it didn't work... again  )

So somehow VS gets his expected response from port 26000 on the EM and moves on with deployment...
so far working, but this cannot be the intended way, can it?

[SkierHiker]

I was getting odd behavior from VS2008 and EM when I was running code with GPIOButtonInpuitProvider set to the default pin assignments. Changing it to use EM pin assignments fixed all my problems.

[kdekok]

I was getting odd behavior from VS2008 and EM when I was running code with GPIOButtonInpuitProvider set to the default pin assignments. Changing it to use EM pin assignments fixed all my problems.

It doesn't matter what code i run, even the simplest code, where i flush a bitmap to the screen in the static Main is no guarantee.
It just looks very very unstable here.

About every 3rd to 4th time i hit F5, it will not deploy. Sometimes it is enough to just unplug/replug the power of the EM, sometimes i need to restart VS2008, sometimes i suddenly have a connection when i keep hitting F5 like 20 times, and sometimes i really need to erase the application via comport with MFDeploy.

I sure hope i'm doing something wrong myself (although couldn't think of anything), because this unreliable behaviour will extremely slow down our development process, which is already dealing with a very tight schedule 

Besides that, is it normal that, whenever the deployment over TCP/IP is doing its job, it still takes about 20 to 30 seconds before your newly deployed app runs? I was used to the Device Solution Meridian, which was really fast (5-10 secs tops)...

I can't get rid of the feeling that something is off. Maybe incompatible versions of the booter, clr, sdk or library....?

Hoping you guys have some tips or solutions....

[GHI_Support]

We will look into this.
This behavior is on MFW3.0 only! If you use Embedded Master with V2.5, the deployment is very fast! So this might be related some change in 3.0 release.

[sutsch]

I have the same situation described from kdekok since i switched to the MF3 with VS2008. Before with MF2.5 and VS2005 all works like a charm! :-)

To be honest: development with the new combination (MF3 + VS2008) is very frustrating at the moment!

Looking forward for the next release form GHI.

stefan

[daantje]

I also have the same problems with the EM as kdekok describes.
I am running the newest MF3 on VS2008 SP1 pro and all the latest versions from Microsoft and GHI on the non-TFT version of the dev board.
I found that restarting VS2008 is another way to get things going again, but with a few plug-ins in VS2008 that take a while to load that is not really a quick option. I do not reset or power-cycle the EM in that case. I use debugging on TCP/IP.

I hope this helps in tracking down the problem.

Daniël

[kdekok]

i started debugging over COM now.
The speed is about the same (which is strange.... 10mbit vs 115kbit), but it is less error prone, so it seems.

[snupi]

finally i do an upgrade from MF2.5 to MF3.0 and i can confirm that the deployment process it is very slow (VS2008+SP1, deployment over TCP, about 20-30sec) compared to the deployment speed with MF2.5 (about 2-10sec)

did you have found any indication for that deployment speed decreasing ?

[GHI_Support]

We are investigating this now. It seems to be related to MFW3...

[kdekok]

I'm sorry to report that things are still the same here   

Deployment over TCP/IP is just as slow as it is over COM (20-30 secs), with this difference, that deployment over TCP/IP is less stable and sometimes just quits working.... i'm using COM deployment for a while now and it is ok for now i guess.... would appreciate an increase in speed though! 

[Foz]

Same thing here - VS2008 SP1, MFW3.0:

1) Slow deployment over Ethernet
2) Getting "Error 1: An error has occurred: please check your hardware." every other deployment or so ==> Requires restarting VS2008 to recover.

Very frustrating. Makes development almost unusable.

GHI - PLEASE find a fix for this as soon as possible.

[Foz]

Update: I have switched to COM1 debugging and am still getting the "Error 1: An error has occurred: please check your hardware." errors. So it is not an ethernet-only issue.

This computer was just reformatted last week and VS2008 was installed only a few days ago, so it is an almost perfectly clean installation.

[SupportAdmin]

Please start new thread. Did you try to ping using mfdeploy?

[Foz]

MFDeploy reports: "Pinging... Error: No response from device"

Sometimes restarting VS2008 fixes it, sometimes I have to reboot the EM and restart VS2008.

[SupportAdmin]

Like I said before start new thread please so we can help you better. What are you using for transport, USB, UART or TCP? Also, only use MFDeploy to ping for now, once you can ping the device with no errors then go to VS2008.
Do you have the latest firmware installed? What version? Do you have your own board or our dev sys?

There is simply too many questions we need answered so please start new thread!