I was trying an application using FEZ Spider with Display_T35, SD Card and Ethernet modules. After an OutOfMemoryException error, I tried to reset the board.
From now on, if I power on the mainboard, connecting to it only the USBClientDP and Display_T35 modules, after the information messages (version, header size, etc.), I can see a strange message “Starting application at 0x00” (or something like this), and, after an instant, the display turns black.
The device doesn’t respond to ping. If I try to set the bootloader mode and power on the board again, the display remains white, and I cannot do anything.
most likely you are experiencing an exception soon after booting. try using Mfdeploy to erase application. if that does not work try to reload firmware.
After some tries, I have managed to erase the application. When the board first rebooted, the usual “Waiting for commands…” message appeared.
Unfortunately, despite this, when I try to reboot the board again, I obtain the same behavior I have described before (“Starting application at 0x00” message and then white display)… But now there isn’t any applications on the device!
Continuing with my tests, now I’m noticing that, when I try to power on the board, on the first line of the display it is written EMX instead of GHI and, on the second line, the message “Tinybooter Mode” is shown. But all the configuration switches are set to Off.
I have also tried to set all of it to On and then to Off again, but nothing… But the real mysterious thing is that the board boots up correctly, say, a time every 20-30 tries…
I have already managed to erase the last deployed application, in fact the rare time that the board boots up, it shows the “Waiting for debug commands” message.
Do you mean to use the FEZ Spider Mainboard Updater program?
Excuse me, but can you explain me in which program must I use the “E” command? Do you mean the “Erase firmware” command in the Plug-in | Debug menu of MFDeploy?
