I played with Zephyr back in 2018 -- I had a working setup with custom out-of-tree board for CJMCU8223 -- a Chinese thingy with NRF51. Some days ago, I decided to revive this setup and use it for a to

#dts

Hi there, The error message may have gotten lost in the rest of the output, but it describes what went wrong, a stack trace where it went wrong, and how to fix it: "wbasser via lists.zephyrproject.org

#customboard #dts

Do you have a dts binding for compatible = “gpio”. - k

#dts #customboard

Hello, I am getting this error Error: nrf5340pdk_nrf5340_cpuapp.dts.pre.tmp:710.1-6 Label or path temp not found when I try to load a project in SES v5.34a (File > Open nRF Connect SDK Project ...). H

#nrf5340 #dts

In general, that's left as an exercise for the user, as far as I know. "Nikos Karamolegkos via lists.zephyrproject.org" <nkaram=ics.forth.gr@...> writes:

#nrf52840 #crypto #dts

Hi there, Most of the questions you ask are covered in the DT documentation: https://docs.zephyrproject.org/latest/guides/dts/index.html# The macros are generated by a Python script at build time, see

#dts #eclipse #nrf52840

I think you need a few more things turned on in your config file. To figure out what you need turned on I always use the menuconfig tool and diff the old and new .config files, then I take the changes

#dts #nrf52832

Hi, You can just remove virtualcom stuff, samples/subsys/usb/console/prj.conf should assign right console with: CONFIG_UART_CONSOLE_ON_DEV_NAME="CDC_ACM_0" Best regards Andrei Emeltchenko

#dts #defconfig

Hello again :) "leonardomt via Lists.Zephyrproject.Org" <leonardomt=gmail.com@...> writes: I would say that if the hardware supports interrupts, then the Zephyr GPIO driver for it

#gpio #dts

Hi Stefan, If your board selects HAS_DTS_I2C_DEVICE, then you should define CONFIG_LSM6DS0_I2C_MASTER_DEV_NAME and CONFIG_LSM6DS0_I2C_ADDR in your board dts.fixup file rather than myboard_defconfig. S

#sensor #dts #defconfig