Using modules to write microcontroller programs

Environment description: Keil + Proteus circuit simulation

First, create a project in Keil and create three files in the project. The file names are: "header file.c", "delay.c", and "delay.h"

Write the corresponding content in the header files .c, delay.c, and delay.h respectively: (Be careful not to insert the delay.h file into the project file)

 1 #include 2 #include"delay.h" 3 4 main() 5 { 6 while(1) 7 { 8 P1 = 0x00; 9 delay();10 P1 = 0xff;11 delay(); 12 }13 }

1 #include"delay.h"2 delay()3 {4 int x;5 for(x = 0;x < 250;x++)6;7 }

1 #ifndef _DELAY_H_2 #define _DELAY_H_3 delay();4 5 #endif

Set the directory for generating Hex files:

Click Rebuild all target files, and the generated effect is as follows:

Insert an 80C51 microcontroller chip into the Proteus simulation software, and then burn the newly generated Hex file into the chip:

The simulation results are as follows:

The entire process of writing an LED light program using modules has been introduced.

Kind tips:

1. Delay plays a delay role in the program.

2. The difference between #include and #include"delay.h"

#include is stored in the header file directory of the microcontroller

#include "delay.h" is a custom function, stored in your new working directory

3. The main purpose of writing this article is not to introduce how to write a microcontroller program for turning an LED on and off, but to introduce the steps of writing programs using modules through this small program.

When I was writing C language, I only used a header file and a main function. At that time, I was thinking, if I do engineering projects in the future, do I have to write a very long C language file like this?

This problem has been bothering me for a long time, but it was solved today. In this way, a large project can be divided into several sub-modules, and then the modules can be tested one by one. Where there are problems, targeted debugging can be carried out, which improves the overall efficiency.