The 2 picture is not done at the same time. It is the last picture after firmware update.
In the last hour, I have tried again to update, 1 out of 5 times it was with successfully,
but when deploying a simple program from scratch it hang and
the display showing ******** ASSERT *****
If there is a mismatch, why could I used the Spiderboard in 10 days without any errors? Se first post.
Sometimes when the Spiderboard has been without power turn off for 1 hours and more, I can do an update, but after a couple of minute the Spiderboard hangs.
The other way I notice you can get TinyBooter version info is if you go into the network configuration from within MFDeploy. That resets into bootloader mode and shows on the LCD (at least on my Cobra) the tinybooter version.
One thing I would do is step through the firmware update manual process http://wiki.tinyclr.com/index.php?title=Firmware_Update_EMX You will want TeraTerm so get that ready, and that should at least get you to a stable state, if that’s actually the issue.
Can I ask what kind of app you are working on? Is it something exotic? Have you just let a simple app run for a long time (time update on screen and LED flash for instance)? Perhaps there’s something else there that we can find that might help.
Yes, I have tried manual update with Tera Term 4.53, and thereafter MFDeploy, But with same result.
What I am doing with Spider Kit.
It has been working for 10 days without any firmware error.
In that time I have been working on library to software control an audio DAC with SPI interface.
It is possible to control more option in software mode, than hardware mode.
It working and are almost done.
Later on it should also controlling ASRC and a Transceiver.
The whole things control by a Touch screen.
You have both loader and firmware loaded. Maybe the updater somehow showed failed but it actually finished. Try updating again please.