The child nodes of the I2C device tree cannot be parsed.

RE: The child nodes of the I2C device tree cannot be parsed.

Vidar Berg — Thu, 06 Nov 2025 10:38:42 GMT

It’s possible to create a custom i2c child node, like the “mysensor” node in the DevAcademy course, and not create a proper binding to a Zephyr driver, but instead use the i2c driver directly from your application. Do you see any actual errors/warnings reported in the build output here:

If so, could you please post the log here?

RE: The child nodes of the I2C device tree cannot be parsed.

lizhaoming634 — Wed, 05 Nov 2025 11:29:34 GMT

description: BME280 integrated environmental sensor

compatible: "zephyr,custom-bme280"

include: [sensor-device.yaml, spi-device.yaml]

like this, you need .yaml, not .overlay

RE: The child nodes of the I2C device tree cannot be parsed.

HHJ — Wed, 05 Nov 2025 09:42:12 GMT

In the tutorial, it's possible to add one's own device tree files, but in my current device tree setup, there doesn't seem to be a place to add device tree files. Currently, there are two device tree files: nrf5340dk_nrf5340_cpuapp_ns.dts and app.overlay. The app.overlay file is the one I modified to configure device tree pins, and I'm not sure if app.overlay is my custom device tree file.

RE: The child nodes of the I2C device tree cannot be parsed.

lizhaoming634 — Wed, 05 Nov 2025 08:46:19 GMT

It looks like the LT3582 isn’t supported in NCS at the moment. You might need to create a custom Devicetree binding (YAML) for it

Exercise 1 – Connecting an BME280 temperature sensor - Nordic Developer Academy