In order to write a minidriver, you must first decide on the following:
- the hardware platform you'll work with
- the timing requirements of your driver
- how much data storage (if any) the minidriver needs
- whether or not your minidriver needs to initialize the hardware
- whether or not your minidriver requires hardware access
- how the transition to the full driver is to be accomplished
The BSP associated with your hardware platform includes the source
code to the board's startup program.
You must link your minidriver to this program.
For more information, see the BSP documentation, as well as
Building Embedded Systems.
You'll need to modify these files:
- mdriver_max.c — defines the amount of data copied from flash to RAM between
calls to your minidriver
- main.c — where you'll set up the minidriver's data area and register your
handler
- my_mdriver.c — contains your handler function;
choose an appropriate name for this file.
You can have multiple C and header files as part of your minidriver.
Don't modify the following files unless you're directed to do so by QNX Software Systems, but make sure they're
included in your startup code directory: