After SI_SCOPE boots you will need to configure its RS232 settings to match those one the line you are trying to debug. SI_SCOPE allows you to set all of its RS232 parameters from its menu interface. Select the correct setting for the Word Length, Parity, Stop Bits, and Baud Rate from the options in the equivalent menus.
SI_SCOPE supports custom baud
rates by allowing you to supply the value to use in the UART'S Baud Rate Divisor
(BRD) register. To use this feature select the "Custom" option off the Baud
menu. SI_SCOPE will prompt you with a dialog box asking you for
the hexadecimal value to use for the BRD. Enter in the correct value according
to the following formula: BRD = 115200/Baud Rate. For example to configure
SI_SCOPE for 2400 baud you would enter in the value 30h since
115200/2400 = 48 decimal = 30 hex.
If you receive a "Line Status Error" message from SI_SCOPE it means that you have set one of SI_SCOPE'S RS-232 parameters incorrectly. SI_SCOPE will display a two letter abbreviation for each line status error it has detected as follows:
| ABBREVIATION | MEANING | CORRECTION |
| FE | Framing Error | Error detected in serial frame. Word length most likely incorrect. |
| PE | Parity Error | Parity error detected. Check the parity settings on your line. Can also be caused by incorrect word length. |
| OE | Over run Error | Serial over run error detected. Double check line settings. This error may be caused by running SI_SCOPE on a machine that is too slow to analyze a line at your configured baud rate. |
You can turn off line status error checking from the run time options menu in ScopeCfg.