RE: Missing device ord mapping when compiling drivers locally with nRF5340DK

bgx561 — Mon, 04 Jul 2022 19:42:54 GMT

Edvin, I appreciate the reply.

I found the issue, and I'm hoping that posting here will same someone else a lot of pain troubleshooting their devicetree.

https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/application_development/out_of_tree_driver

I was not including my "vendor_testdevice" as a Zephyr module.

Pushing my entire project down a subdirectory into <project>\my_custom_module\drivers\*

and then including it as a module

list(APPEND ZEPHYR_EXTRA_MODULES

${CMAKE_CURRENT_SOURCE_DIR}/my_custom_module

)

fixes the issue I was seeing with the mapping not being generated and the build still being successful.

I tested this with an exact copy of the BME280 files to create a BME280TEST custom device and loaded it using the solution above, and was able to verify it gets mapped correctly in the build\zephyr_pre0.map and build\zephyr_final.map files.

---

*(SORT_BY_NAME(SORT_BY_ALIGNMENT(.z_device_POST_KERNEL[1-9][0-9]_*)))

.z_device_POST_KERNEL50_

0x000000000000c730 0x18 zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim.c.obj)

0x000000000000c730 __device_dts_ord_135

.z_device_POST_KERNEL50_

0x000000000000c748 0x18 zephyr/drivers/mbox/libdrivers__mbox.a(mbox_nrfx_ipc.c.obj)

0x000000000000c748 __device_dts_ord_21

.z_device_POST_KERNEL70_

0x000000000000c760 0x18 zephyr/drivers/spi/libdrivers__spi.a(spi_nrfx_spim.c.obj)

0x000000000000c760 __device_dts_ord_112

.z_device_POST_KERNEL90_

0x000000000000c778 0x18 zephyr/drivers/sensor/bme280/libdrivers__sensor__bme280.a(bme280.c.obj)

0x000000000000c778 __device_dts_ord_136

.z_device_POST_KERNEL90_

0x000000000000c790 0x18 modules/my_custom_module/drivers/bme280test/lib..__..__..__dev__Documents__Nordic_Semiconductor__bgx561test__my_custom_module__drivers__bme280test.a(bme280test.c.obj)

0x000000000000c790 __device_dts_ord_137

0x000000000000c7a8 __device_APPLICATION_start = .

^Now both devices correctly show up in the device mapping.

RE: Missing device ord mapping when compiling drivers locally with nRF5340DK

Edvin — Mon, 04 Jul 2022 17:09:37 GMT

Hello,

[quote user=""]The footprint is there is no driver child nodes generated in the build\zephyr_pre0.map or build\zephyr_final.map that corresponds to the ord node found in in the build\zephyr.dts or build\include\devicetree_unfixed.h [/quote]

I don't understand what you are saying here. In fact, I struggle a bit to understand anything after this point.

Where does the error regarding "__device_dts_ord_XXX" come from? What are you trying to add?

Is this really a question on how to add custom .c and .h files? Or are you trying to use one of the drivers in Zephyr?

Or are you trying to create your own overlay or board file?

Best regards,

Edvin