Some experience accumulated when debugging a system using Keil C

Some experience we have accumulated when debugging a system using Keil C

1. Since Keil C does not support Chinese very well, the displayed cursor will be inconsistent with the actual cursor position, which will affect the modification of Chinese comments. Under Windows 2000, we can set the font to Courier, so that it can be displayed normally.
2. When using an MCU with off-chip memory (such as W77E58, which has 1K off-chip memory), you must set the flag bit and choose the large mode for compilation, otherwise there will be errors.
3. When using Keil C to track the program running status, you must block the statement that causes Warning, otherwise there may be errors when tracking the statement.
4. When calling an array, Keil C first loads the array into memory. If you want to use a long array in C, you can use the code keyword, so that the DB function of the assembly is realized. Keil C will not load the array marked with code into memory, it will directly read Rom.
5. When programming involves communication, timing is very important. The execution speed of pulling up the pin is much faster than checking the pin level.
6. When waiting for the pin level to change, we need to set a timeout process, otherwise the program will deadlock due to an unexpected error.
7. Where C language can be used, try not to use assembly language, especially in the implementation of algorithms, which are obscure and difficult to understand.
8. Several parameter arrays of the program occupy a large space, among which the LCD background array is the longest, with 4,000 bytes. Therefore, those initialization arrays are placed in another C file, and the keyword extern is used in the main file to define them, so as not to interfere with the writing of the main file.
9. The lower the correlation between all functions, the more conducive it is to the expansion of functions in the future.
10. When compiling an array with the code keyword in version 6.20, the compilation passes but the result of the microcontroller operation is wrong. It is normal after switching to version 6.14.