The results from previous code were OK, I think it's a bug in the debugger. I posted the details here [^]. BR.

#dts #nrf52

Hi, I originally posted this question to stackoverflow [^] so I think its better not to duplicate the whole story here. Supposing I have a DTS file with a content like this one below: n: detectors { c

#dts #nrf52

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

The Kconfig.defconfig doesn’t look right config BOARD default "fuse board" I think it should be “fuseboard” or maybe “fuse_board” but I didn’t test it. I looked at every other board name in the zephyr

#customboard #dts

Created a custom board file, based on the DTS for a sample board. Changed the name of the file, and the references to the new board. Attempting to build, I received this error. C:\zephyrproject\zephyr

#customboard #dts

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

#dts #customboard

I created some local GPIO pins in a custom device tree for the project. It build correctly and I can see the entries in both the "build/zephyr.dts" and "build/includes/generated/devicetree_unfixed.h".

#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

Hello, I am studying this which mentions that the MCUboot is placed to immutable section of flash. How is this implemented? I can not see anywhere information about immutable MCUboot partition.

#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

Good morning! I'm a total newbie to Zephyr, learning the basics to implement in a project for an IoT sensor, more specifically IIoT(Industrial IoT). The module I'm using is a NINAB302, which incorpora

#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 I had a question to setup the MCP2515 driver in the zephyr project. We made a custom board for the decawave DWM1001 module, which uses a nRF52832 chip. They have a device tree file in the zephyr pr

#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

Is it compulsory to add the node "virtualcom" to configure a USB virtual com port via USB-OTG-HS for STM32F407 under Zephyr 2.0.99? I got the following code in DTS from a partner but it cannot be buil

#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

Is there a way to detect programmatically if a given pin can be configured as interrupt using Zephyr? (e.g. some sort of a map/list or macros that I could reuse). Are there any side effects in configu

#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