Solution:

There is a strange phenomenon about ADAM-5510 booting. We assume you execute ADAM-5510 utility under Host PC to communicate with ADAM-5510, when you reboot 5510 ( no matter reset by manual or press "Config" under [Utility] label ) under the terminal mode of ADAM-5510 utility, the screen sometimes could be locked at the point of memory test, it seems the booting action is not completed. Actually, the booting inside ADAM-5510 is successful, just something about communication between ADAM-5510 and Host PC is wrong. That is to say, ADAM-5510 is still working, just the screen display on the Host PC is incorrect. At this moment, you can try to press "ALT-R" to improve this situation, however, this way could not be always effective, it depends on the Super I/O chip which is built in the Host's motherboard. According to our survey, the key point caused this problem is the Super I/O chip (We also try to use HyperTerminal to replace ADAM-5510 utility for checking this problem, but the result is still the same. That proves this problem is not caused by AP). For example, the booting of ADAM-5510 is successful for UMC 8669 and ITE 8661F, but not for Winbond W83977TF-A. In addition, if you use general communication card ( UART chip ) instead of on-board COM Port, you'll find out everything is ok. To sum up, if this problem is occurred, please follow the below ways to improve it: 1. ALT-R: Press "ALT-R" under the terminal mode to reset Host's COM Port. 2. Booting first, then run utility: If you don't want to see this problem, you can consider to power on or reboot ADAM-5510 first, then execute ADAM-5510 utility for advanced operation. 3. Communication card: The good way to eliminate this phenomenon is to use general communication card instead of on-board COM Port.