Chengdu Ebyte Electronic Technology Co., Ltd.
E32-900MBL-1 User Manual
Copyright © 2012–20 21 , Chengdu Ebyte Electronic Technology Co., Ltd.
10
2.5 Programming
File
Key note
1
ebyte_core.h
A module structure is defined, the basic functions are abstracted, and the functions of
the underlying module will be bound to the structure. When used in simple sending and
receiving applications, there is no need to understand the underlying working details of
each module, and the data can be sent and received by directly calling the abstracted
function. If you need to customize some functions, you can also consider integrating them
into the structure. If you know enough about the functions of the underlying modules, you
can also directly remove the ebyte_core.c/h file, and there is no strong coupling between
the layers.
2
ebyte_exx.c
It is a specific module driver file, which is generally packaged and does not need to
be modified by the user. It only needs to consider how to input and output data from this
"box".
3
ebyte_port.c
It is specially used to bind SPI and GPIO under different hardware platforms ,
abstracted as the input of "box". Users need to fill the communication interface in their
own hardware platform to a fixed position according to the comments. Generally
speaking, it is to provide the SPI transceiver function and the level control of the pin.
Some modules are slightly special, for example, E49 uses half-duplex SPI, if you are too
lazy to write a communication driver, you can directly bind the IO to a fixed position, and
leave the rest to the module driver to simulate IO to realize communication. As shown in
the figure below, in the comments, it is required to provide the SPI interface position to
fill in the specific sending and receiving functions, send the data into the SPI to send data,
and return the SPI received data from the result.
ebyte_callback.c
It is specially used to bind the user's own sending and receiving logic, abstracted as
the output of the "box". Essentially, the module driver is to directly call the user's callback
