In this exercise, we will cover the minimal things you need to implement within a device driver. We will use the same sensor (BME280) and the hardware connections used in Lesson 5 – Exercise 1, which uses the SPI interface to communicate between your device and the BME280 sensor. It is assumed that you know this sensor’s features and its hardware capabilities.
However, instead of using the Zephyr device driver as we did in lesson 5, we will implement and use our own custom device driver. Instead of implementing functionality to interact with the BME280 sensor using the SPI driver, we will implement that into the custom driver itself. This new custom driver will have dependency on the SPI driver, and hence we need to make sure that this driver initialization will happen after the SPI driver is initialized.
Important
This exercise is not supported on devices that use TF-M, so nRF9160 DK, nRF9161 DK, nRF5340 DK and nRF7002 DK.
Exercise steps
Open the code base of the exercise by navigating to Create a new application in the nRF Connect for VS Code extension, select Copy a sample, and search for Lesson 7 – Exercise 1.
1. Enable the necessary Kconfigs in the application.
1.1 Enable our custom driver
Add the following line in the prj.conf file
CONFIG_CUSTOM_BME280_DRIVER=y
1.2. Enable application-defined syscalls.
We also need to tell the build system to search for declarations syscalls in the application folder so that they can be parsed and the header files are generated that can be used by the application to interact with the device driver. This is done through the Kconfig CONFIG_APPLICATION_DEFINED_SYSCALL.
Add the following line in the prj.conf file.
CONFIG_APPLICATION_DEFINED_SYSCALL=y
2. Add the driver directory as a Zephyr module.
We want to add the driver directory as a Zephyr module into the project. If your driver is a project managed by west, this step is unnecessary.
In the CMakeLists.txt file, add the following code snippet
3. Add a custom driver initialization priority named CONFIG_DRIVER_INIT_PRIORITY.
Make sure that the priority of the initialization is less than the priority of the SPI driver (CONFIG_SPI_INIT_PRIORITY = 70). Since lower priority here means higher in number, you should set CONFIG_DRIVER_INIT_PRIORITY to at least 71.
Add the custom driver initialization priority in custom_bme280_driver\zephyr\Kconfig,
config DRIVER_INIT_PRIORITY
int "Init priority"
default 71
help
Custom device driver initialization priority, needs be more higher than CONFIG_SPI_INIT_PRIORITY.
4. This is the part of the exercise where you will not change anything but observe a few things in the custom device driver folder.
In the application directory, go to the file custom_bme280_driver\zephyr\custom_bme280_driver_spi.h and try to understand every step mentioned here.
4.1 Define the typedef declaration of the function pointers.
Define the API you want exposed to the application and create a typedef for the function pointers for all the APIs as described here. One can see that there are five typedefs here for the five APIs that are exposed. In this case, we can see that the exposed APIs are for print, open, read_reg, write_reg and close.
typedef void (*custom_bme280_api_print_t)(const struct device * dev);
typedef int (*custom_bme280_api_open_t)(const struct device * dev);
typedef int (*custom_bme280_api_read_reg_t)(const struct device * dev, uint8_t reg, uint8_t *data, int size);
typedef int (*custom_bme280_api_write_reg_t)(const struct device * dev, uint8_t reg, uint8_t value);
typedef int (*custom_bme280_api_close_t)(const struct device * dev);
4.2 Define a struct to have a member for each typedef defined above
Define a structure, custom_bme280_driver_api, using the above mentioned typedefs, for the function pointer and have one member for each of the definitions. It is very common to have these members declared with the same type and arguments as the API definition within the device driver. Doing so will make your next few steps easier. Observe that the members of this struct use the typedef you declared in 4.1.
4.3 Implement the API to be exposed to the application with type and arguments matching the typedef.
Here we declare the API that the application calls directly. The API needs to be prefixed with __syscall. The documentation on the need to do this is well written in the C Prototype documentation. For example, the below declaration for printing all the characteristics (temperature, pressure and humidity) of BME280 to the serial console can be done using the below API.
When you compile inter_less7_exer1, the above is parsed by the scripts/build/parse_syscall.py into the below function in the generated header file in your_proj_directory\build\zephyr\include\generated\syscalls\custom_bme280_driver_spi.h
One can find more documentation on the implementation details of the above generated function in the Zephyr documentation along with the invocation context considerations that come into designing this.
4.4 – Implement the z_impl_* translation function to call the device driver API for this feature
Here we implement a translator function z_impl_custom_bme280_print, which is used inside the generated function by the parses of the syscalls. One can observe that the name of this translator function is the same as the name of the __syscall function with a prefix of z_impl_. The main thing this translator function does is to convert the arguments (if necessary) and pass them to the device driver API function, which can be accessed through the (const device struct * dev)->api member.
static inline void z_impl_custom_bme280_print(const struct device * dev)
{
const struct custom_bme280_driver_api *api = dev->api;
__ASSERT(api->print, "Callback pointer should not be NULL");
api->print(dev);
}
5. Define a macro for the device driver instance.
5.1 Now, we want to plug in the implementation into the Zephyr device driver model, using the DEVICE_DT_INST_DEFINE() macro.
Add the code snippet below to the file custom_bme280_driver\zephyr\custom_bme280_driver_spi.c
The most important thing here is to understand in detail the contents and use of DEVICE_DT_INST_DEFINE(), which has the following signature
inst – This is the instance number passed as a parameter to CUSTOM_BME280_DEFINE(inst).
init_fn – This is the initializing function, called before the main() in the application is called. The other arguments level and prio can be used to manage the actual initialization order and priority of calling this init_fn at the time of the Zephyr boot up. In this exercise, we have used the init()function as the initializing function where we configure the pins and initialize the SPI interface and the BME280 sensor.
pm – This token is used to plug our device driver into the overall Zephyr power management system. You can use PM_DEVICE_DT_DEFINE to define a pm instance and implement the pm action events that are sent to your driver at the time of system power events. In this exercise, we do not implement this, so we set this to NULL.
data – This token is used to pass a pointer to any additional mutable data that you want to pass between the driver and the app. In this exercise, we are passing &bme280_data_##inst.
config – This token is used to pass the device private constant config data, in this exercise &custom_bme280_config_##inst.
level – This is the device’s initialization level, which can be PRE_KERNEL_1, PRE_KERNEL_2 or POST_KERNEL. We are passing POST_KERNEL, which is the same level as the SPIM device driver.
prio – This is the device’s priority within its initialization level, which needs to be of lower priority than the SPIM driver to ensure it is initialized first. We are passing CONFIG_DRIVER_INIT_PRIORITY, which we defined in the Kconfig file to be 71.
api – Pointer to the device’s API structure, in our case the struct custom_bme280_api_funcs().
Note
There are multiple levels of order in which the device initialization function can be called. Our custom device driver depends on the SPIM device driver and looking into<install_path>\zephyr\drivers\spi\spi_nrfx_spim.c, we can see that the DEVICE_DT_DEFINE for this SPI instance uses POST_KERNEL level. Therefore, we cannot use any level that is earlier than that for our custom driver.
5.2 Create a struct device for every status “okay” node in the devicetree.
After we have defined the macro CUSTOM_BME280_DEFINE(inst), we will pass it to DT_INST_FOREACH_STATUS_OKAY(). This macro will call the previously defined macro CUSTOM_BME280_DEFINE() on all nodes with the custom, bme280 compatible and status “okay” that are in the devicetree.
DT_INST_FOREACH_STATUS_OKAY(CUSTOM_BME280_DEFINE)
Testing
6. Connect the sensor to the DK.
Test the application by connecting our sensor to the DK like in Lesson 5 – Exercise 1. Using the nRF52840 DK as an example, we have used P0.28, P0.29, P0.30, and P0.31 for the SPI SCLK, MOSI, CS, and MISO pins, respectively. Therefore, we have to connect the pins of the sensor breakout board to the respective pins on the DK.
7. Build the application and flash it to your board.
The log output should be similar to what you saw in Lesson 5 – Exercise 1, but remember that a lot of the BME280 functionality in that lesson has now been moved from the application into the custom device driver.
You can see that the calibration characteristics of the sensor are initialized and printed before the main application is started. And in the main, you can access the custom device driver and print the sensor values.
The solution for this exercise can be found in the course repository, lesson7/inter_less7_exer1_solution.
Nordic Developer Academy Privacy Policy
1. Introduction
In this Privacy Policy you will find information on Nordic Semiconductor ASA (“Nordic Semiconductor”) processes your personal data when you use the Nordic Developer Academy.
References to “we” and “us” in this document refers to Nordic Semiconductor.
2. Our processing of personal data when you use the Nordic Developer Academy
2.1 Nordic Developer Academy
Nordic Semiconductor processes personal data in order to provide you with the features and functionality of the Nordic Developer Academy. Creating a user account is optional, but required if you want to track you progress and view your completed courses and obtained certificates. If you choose to create a user account, we will process the following categories of personal data:
Email
Name
Password (encrypted)
Course progression (e.g. which course you have completely or partly completed)
Certificate information, which consists of name of completed course and the validity of the certificate
Course results
During your use of the Nordic Developer Academy, you may also be asked if you want to provide feedback. If you choose to respond to any such surveys, we will also process the personal data in your responses in that survey.
The legal basis for this processing is GDPR article 6 (1) b. The processing is necessary for Nordic Semiconductor to provide the Nordic Developer Academy under the Terms of Service.
2.2 Analytics
If you consent to analytics, Nordic Semiconductor will use Google Analytics to obtain statistics about how the Nordic Developer Academy is used. This includes collecting information on for example what pages are viewed, the duration of the visit, the way in which the pages are maneuvered, what links are clicked, technical information about your equipment. The information is used to learn how Nordic Developer Academy is used and how the user experience can be further developed.
2.2 Newsletter
You can consent to receive newsletters from Nordic from within the Nordic Developer Academy. How your personal data is processed when you sign up for our newsletters is described in the Nordic Semiconductor Privacy Policy.
3. Retention period
We will store your personal data for as long you use the Nordic Developer Academy. If our systems register that you have not used your account for 36 months, your account will be deleted.
4. Additional information
Additional information on how we process personal data can be found in the Nordic Semiconductor Privacy Policy and Cookie Policy.
Nordic Developer Academy Terms of Service
1. Introduction
These terms and conditions (“Terms of Use”) apply to the use of the Nordic Developer Academy, provided by Nordic Semiconductor ASA, org. nr. 966 011 726, a public limited liability company registered in Norway (“Nordic Semiconductor”).
Nordic Developer Academy allows the user to take technical courses related to Nordic Semiconductor products, software and services, and obtain a certificate certifying completion of these courses. By completing the registration process for the Nordic Developer Academy, you are agreeing to be bound by these Terms of Use.
These Terms of Use are applicable as long as you have a user account giving you access to Nordic Developer Academy.
2. Access to and use of Nordic Developer Academy
Upon acceptance of these Terms of Use you are granted a non-exclusive right of access to, and use of Nordic Developer Academy, as it is provided to you at any time. Nordic Semiconductor provides Nordic Developer Academy to you free of charge, subject to the provisions of these Terms of Use and the Nordic Developer Academy Privacy Policy.
To access select features of Nordic Developer Academy, you need to create a user account. You are solely responsible for the security associated with your user account, including always keeping your login details safe.
You will able to receive an electronic certificate from Nordic Developer Academy upon completion of courses. By issuing you such a certificate, Nordic Semiconductor certifies that you have completed the applicable course, but does not provide any further warrants or endorsements for any particular skills or professional qualifications.
Nordic Semiconductor will continuously develop Nordic Developer Academy with new features and functionality, but reserves the right to remove or alter any existing functions without notice.
3. Acceptable use
You undertake that you will use Nordic Developer Academy in accordance with applicable law and regulations, and in accordance with these Terms of Use. You must not modify, adapt, or hack Nordic Developer Academy or modify another website so as to falsely imply that it is associated with Nordic Developer Academy, Nordic Semiconductor, or any other Nordic Semiconductor product, software or service.
You agree not to reproduce, duplicate, copy, sell, resell or in any other way exploit any portion of Nordic Developer Academy, use of Nordic Developer Academy, or access to Nordic Developer Academy without the express written permission by Nordic Semiconductor. You must not upload, post, host, or transmit unsolicited email, SMS, or \”spam\” messages.
You are responsible for ensuring that the information you post and the content you share does not;
contain false, misleading or otherwise erroneous information
infringe someone else’s copyrights or other intellectual property rights
contain sensitive personal data or
contain information that might be received as offensive or insulting.
Such information may be removed without prior notice.
Nordic Semiconductor reserves the right to at any time determine whether a use of Nordic Developer Academy is in violation of its requirements for acceptable use.
Violation of the at any time applicable requirements for acceptable use may result in termination of your account. We will take reasonable steps to notify you and state the reason for termination in such cases.
4. Routines for planned maintenance
Certain types of maintenance may imply a stop or reduction in availability of Nordic Developer Academy. Nordic Semiconductor does not warrant any level of service availability but will provide its best effort to limit the impact of any planned maintenance on the availability of Nordic Developer Academy.
5. Intellectual property rights
Nordic Semiconductor retains all rights to all elements of Nordic Developer Academy. This includes, but is not limited to, the concept, design, trademarks, know-how, trade secrets, copyrights and all other intellectual property rights.
Nordic Semiconductor receives all rights to all content uploaded or created in Nordic Developer Academy. You do not receive any license or usage rights to Nordic Developer Academy beyond what is explicitly stated in this Agreement.
6. Liability and damages
Nothing within these Terms of Use is intended to limit your statutory data privacy rights as a data subject, as described in the Nordic Developer Academy Privacy Policy. You acknowledge that errors might occur from time to time and waive any right to claim for compensation as a result of errors in Nordic Developer Academy. When an error occurs, you shall notify Nordic Semiconductor of the error and provide a description of the error situation.
You agree to indemnify Nordic Semiconductor for any loss, including indirect loss, arising out of or in connection with your use of Nordic Developer Academy or violations of these Terms of Use. Nordic Semiconductor shall not be held liable for, and does not warrant that (i) Nordic Developer Academy will meet your specific requirements, (ii) Nordic Developer Academy will be uninterrupted, timely, secure, or error-free, (iii) the results that may be obtained from the use of Nordic Developer Academy will be accurate or reliable, (iv) the quality of any products, services, information, or other material purchased or obtained by you through Nordic Developer Academy will meet your expectations, or that (v) any errors in Nordic Developer Academy will be corrected.
You accept that this is a service provided to you without any payment and hence you accept that Nordic Semiconductor will not be held responsible, or liable, for any breaches of these Terms of Use or any loss connected to your use of Nordic Developer Academy. Unless otherwise follows from mandatory law, Nordic Semiconductor will not accept any such responsibility or liability.
7. Change of terms
Nordic Semiconductor may update and change the Terms of Use from time to time. Nordic Semiconductor will seek to notify you about significant changes before such changes come into force and give you a possibility to evaluate the effects of proposed changes. Continued use of Nordic Developer Academy after any such changes shall constitute your acceptance of such changes. You can review the current version of the Terms of Use at any time at https://academy.nordicsemi.com/terms-of-service/
8. Transfer of rights
Nordic Semiconductor is entitled to transfer its rights and obligation pursuant to these Terms of Use to a third party as part of a merger or acquisition process, or as a result of other organizational changes.
9. Third Party Services
To the extent Nordic Developer Academy facilitates access to services provided by a third party, you agree to comply with the terms governing such third party services. Nordic Semiconductor shall not be held liable for any errors, omissions, inaccuracies, etc. related to such third party services.
10. Dispute resolution
The Terms of Use and any other legally binding agreement between yourself and Nordic Semiconductor shall be subject to Norwegian law and Norwegian courts’ exclusive jurisdiction.