I don’t know if the mainboard had multiple problem or the root cause of this behaviors. By sure I’m available to collect the information to help to understand the root cause of this problem and to have a solution.
I can start to collect the information detailed on step 1,2, and 3 of your last post.
Next, if the problem still appear as “unknown”, by sure, I’m available to organize a conf-call or live meeting to show directly to you my desktop and mainboard trought webcam. I think this can help to speed-up the resolution.
Wait next post to read the result of step 1,2 and 3.
Have nice evening and again thank you for your Support.
I too think that there should be more checks as the CLR files get loaded… Until all the files are loaded you won’t get it booting properly, so please re-try the deployments.
I have erased the mainboard via TeraTerm (Success), then used FezUpdater to upload the firmware but the result was the same. “GHI” on the first line of display.
In attach the print screen of FezUpdater output… nothing bad …
Note: After the upload of Tinybooter the mainboard restarted correctly in Tynibooter mode and FezUpdater upload the firmware. At end of firmaware update (with success) FeZUpdater reboot the mainboard and it AGAIN show GHI instead of boot EMX. As described in previous post in this situation the mainboard is not recognized by PC. unusable.
After firmware upload I wait 3 hours with mainboard powered but nothing change always GHI on the first line of display.
When you are done, put config jumpers back to the off position and tell us what you see when you plug in the USB cable. and what you get when you ping from MFDeploy.