A N 6 3 3
84
Rev. 0.7
10.20. Empty Project
The empty project is created to help users write custom firmware. The project follows the convention for directory
structure introduced in the sample projects. It contains driver modules for the radio and MCU peripherals as well as
a default MCU initialization procedure. The porting of an example project to an MCU of choice can be done easily
thanks to the layered approach of the project structure. This reduces the effort required to compile the code for
other architecture, as only the low-level functions must be modified. The general structure of the project can be
seen in the following figure. All the tasks are separated into two groups: the Hardware Initialization part and the
Main Process part. Host MCU-related tasks initialize the physical interface between the radio and the controller
unit, including the SPI lines (SCLK, SDI, SDO, NSEL), general I/O ports (SDN, NIRQ). The radio related tasks
prepare the radio for the communication and put the radio in ready state.
Figure 64. Structure of the Empty Project
The porting of an example project to an MCU of choice can be done easily thanks to the layered approach of the
project structure. This reduces the effort required to compile the code for other architecture, as only the low-level
functions must be modified.
The following drivers will be modified:
compiler_defs.h, hardware_defs.h, platform_defs.h, application_defs.h
These header files contain definitions for the 8051 architecture and the Silicon Labs hardware platform.
They may be modified according to the new architecture and hardware.
spi.c, spi.h
The SPI driver module will be supplied to enable the communication with the radio.
radio_hal.c, radio_hal.h
The radio hardware abstraction layer may be adjusted, as the GPIOs, nIRQ and SDN pins are defined in
this file.
The above mentioned files may not cover all requirements for porting the project to other MCU, as it depends on
what is to be ported and which other drivers are used by the project. The compiler tool chain setup, the appropriate
startup codes, and linker scripts are out of the scope of this section; the user is responsible for providing them as
appropriate for the given architecture.
Summary of Contents for EZRADIOPRO Si4060
Page 24: ...AN633 24 Rev 0 7 Figure 20 Supply Current versus Time Diagram from Shutdown to RX State...
Page 67: ...AN633 Rev 0 7 67 Figure 48 Variable Length Packet Reception Flowchart...
Page 69: ...AN633 Rev 0 7 69 Figure 50 Packet Matching Reception Flowchart...
Page 73: ...AN633 Rev 0 7 73 Figure 54 Packet Reception with Automatic RX Hopping Flowchart...
Page 75: ...AN633 Rev 0 7 75 Figure 56 Packet Reception with Manual Rx Hopping...
Page 80: ...AN633 80 Rev 0 7 Figure 62 Long Packet Transmission Workflow...
Page 81: ...AN633 Rev 0 7 81 Figure 63 Long Packet RX Flowchart...
