MVP-8400 will not boot sticks on splash
Mike Annett
Posts: 3
I am working at home and my panel has locked up. The file has been working for weeks and when I tried to use it tonight it lokck up during boot on the splas screen and the green dot at the bottom blinks for a while and hen locks up as well. I tried booting with the bottom left and down ... no help I tried touching the screen during boot to get to calibration or setup... no help. Any suggestions???
Thanks
Thanks
0
Comments
As far as I'm aware transferring projects is unlikely to cause this issue. We mainly see these sorts of failures in older panels that have been in the field for a long time. I don't know of too many people who would send projects to a test panel 100000 times or more.
With limited knowledge of how the OS has been built, what write masking has been implemented and whether a RAM disk is in use, the cause is more likely to be temporary files written to the flash card at run time or simply fatigue due to age.
Sandisk has an interesting and succinct white paper on wear levelling that you can find via a google search (the link on the Sandisk website is currently down).
I was hoping for a silver bullet. I will get a new flash card. Then I have to remember how I rebuilt one on about 8 years ago
I got a new flash card and it still will not boot. I picked up another older 8400 (that works) and tried its card in the dead panel. It would not boot. The old card works in both. The card from the problemed panel will not work in either. The differences in the 2 AMX supplied cards is the older panels (that will boot) is 64M v2.55.43 The panel that will not boot is 256M v2.89.3 and the new card is 1G. Any other suggestions??
Thanks
Mike
There are portions of the bootstrap that are in NVRAM and portions that are on the CF. They have to match, if not exactly, at least enough to be compatible. But it's also possible the NVRAM got corrupted, in which case there is no choice but to send it to AMX. And though Auser is correct that a transfer isn't likely to be the cause of your failure, it can certainly be a trigger. It's generally on a reboot cycle that the memory fails, and a transfer forces a reboot.