# Practical Zephyr - Devicetree semantics (Part 4) | Interrupt **URL:** \ **Category:** Blog\ **Created:** [February 15, 2024, 8:13pm UTC](https://community.memfault.com/t/practical-zephyr-devicetree-semantics-part-4-interrupt/812 "2024-02-15T20:13:02Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![discobot](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.memfault.com/discobot/32/1_2.png) [@discobot](https://community.memfault.com/u/discobot)\ **Post date:** [February 15, 2024, 8:13pm UTC](https://community.memfault.com/t/practical-zephyr-devicetree-semantics-part-4-interrupt/812/1 "2024-02-15T20:13:02Z")
Having covered the _Devicetree basics_ in the [previous article](https://interrupt.memfault.com/blog/practical_zephyr_dt), we now add **semantics** to our _Devicetree_ using so-called _bindings_: For each supported type, we’ll create a corresponding _binding_ and look at the generated output to understand how it can be used with Zephyr’s Devicetree API. * * * This is a companion discussion topic for the original entry at [https://interrupt.memfault.com/blog/practical\_zephyr\_dt\_semantics](https://interrupt.memfault.com/blog/practical_zephyr_dt_semantics) ---
**Author:** ![TomP123](https://avatars.discourse-cdn.com/v4/letter/t/35a633/32.png) [@TomP123](https://community.memfault.com/u/TomP123)\ **Post date:** [June 4, 2024, 9:28am UTC](https://community.memfault.com/t/practical-zephyr-devicetree-semantics-part-4-interrupt/812/2 "2024-06-04T09:28:55Z")
Thanks for the article series, I’ve been finding it useful getting up to speed with Zephyr. Following this article, I did get a bit stuck in the [naming section](https://interrupt.memfault.com/blog/practical_zephyr_dt_semantics#naming) of the blog post, the grep for ‘foo’ in devicetre\_generated.h at the end of the section didn’t produce any results for me. I should be using the same version of Zephyr (2.4.0) at the end of the section. Doing a before and after comparison of the devicetre\_generated.h files the only change I could see was the compatible name, and couldn’t see the property values added. Any suggestions on what I might be doing wrong, or how to debug this? Also, there were a few parts of this section I was a bit unsure about - The instructions in the [naming section](https://interrupt.memfault.com/blog/practical_zephyr_dt_semantics#naming) start off specifying using the name custom as the vendor name, but mid-way through it seems like these instructions describe the files having used the vendor name dummy which doesn’t seem to have been mentioned before. - I wasn’t completely sure about what it means to have the generator script update devicetree\_generated without compiling (e.g. “Without recompiling, we can check whether the generator script has added our properties to devicetree\_generated.h”). I was running the following as done in previous examples: ```auto west build --board nrf52840dk_nrf52840 --build-dir ../build -- \ -DEXTRA_DTC_OVERLAY_FILE="dts/playground/props-basics.overlay" ``` If it’s possible to clear any of this up for me that would be great, but either way thanks for creating this blog series 🙂 ---
**Author:** ![discobot](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.memfault.com/discobot/32/1_2.png) [@discobot](https://community.memfault.com/u/discobot)\ **Post date:** [June 4, 2024, 9:28am UTC](https://community.memfault.com/t/practical-zephyr-devicetree-semantics-part-4-interrupt/812/3 "2024-06-04T09:28:55Z")
---
**Author:** ![martin](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@martin](https://community.memfault.com/u/martin)\ **Post date:** [September 12, 2024, 6:02pm UTC](https://community.memfault.com/t/practical-zephyr-devicetree-semantics-part-4-interrupt/812/4 "2024-09-12T18:02:40Z")
Hi - sorry for the late reply. You’re completely right, the `custom,` vendor prefix should be mentioned consistently. The same is true for the compilation. It is of course necessary to recompile since otherwise the output isn’t generated by the compiler. I updated the article!