[Runhe Neptune Review] Three code modifications

hl23889909

[Runhe Neptune Review] Three code modifications [Copy link]

 

I am not familiar with compilation control
at present. How the whole project is built and compiled, so for the time being I can only care about where we can add and modify code and compile and run. See the figure below:

In the red box, Runhe engineers have written a lot of test demos in it. Here you can choose to compile the source files in that directory. There are also several samples under the directory, such as the GPIO control sample, as shown below:

There is also a compilation option in the directory to choose which sample to run. The red box is to comment out other source files with a # sign. Below is the path of the header file that the compilation depends on. After knowing how to modify it, we can choose to test each sample and verify its different functions.
Modification:
Application entry: SYS_RUN(); We see this function after each sample. This is the starting point for the system to run our application. Create your own task here and start playing. I added the uart1 task based on the original GPIO sample. One task is to control the state of the light by pressing a button, and the other is to return whatever data is received by serial port 1.


Test:
After compiling, download and test:

Through serial ports 0 and 1, we can see the running status of the task. After pressing the buttons, we can also see the corresponding changes in the status of the development board LED. This section will briefly explain how to modify or add our application code.

Jacktang

Yes, Runhe engineers have written a lot of test demos in it, which can be easily called

freebsder

Another compilation system? Some use make, some cmake, some nijia, and some gn. It's really troublesome.