General Trouble

| IV.1 General Trouble These are problems that may occur on all host platforms: The RESET51 program terminates without any error, but the target system is not reset. The (reset) cable may be plugged into the wrong (printer) port. First of all try the other ports. There may also be something wrong with the cable itself. Employ the BOOT-51 User's Manual and the circuit diagram of the target board, and check the cable. Furthermore, the reset pulse may be too short. Specify a greater pulse width. You may also decrease the reset capacitor of the MCS-51 system. The target system is reset all the time. When tailoring the reset cable, you may have mixed up the RESET and -RESET lines. Simply interchange them. In batch (or script) mode everything seems to work fine on the PC, but on the target system you get absolutely nothing. Try the interactive mode and reset the target system. If nothing happens, you may have mixed up the receive and transmit lines of the target board. If you get some garbage, the baudrates and/or serial data formats of the target system and the PC are probably different. Configure your terminal emulation program correctly, and change BOOT.BAT (under MS-DOS) or the boot script (under Linux) accordingly. (correct data format: 8 data bits, 1 stop bit, no parity) Everything is working fine in batch (or script) mode, but when you try to upload the same HEX file in interactive mode, BOOT-51 aborts with the error message "unexpected character". Check the ASCII upload configuration parameters of your terminal emulation program. It has to terminate every line with a CR and/or LF character, and it must not send any pace characters! Of course it is always best, to send the HEX file exactly as it is.