dts: edtlib: Error running devicetree tests

[pdgendt]

Describe the bug

Commit f55358b introduced an issue for EDTLIB, bisecting

f55358bcbfcfc4e7bd7d5c00bf6a16a13f01e8f6 is the first bad commit
commit f55358bcbfcfc4e7bd7d5c00bf6a16a13f01e8f6 (HEAD)
Author: Kyle Bonnici <kylebonnici@hotmail.com>
Date:   Tue Dec 16 13:36:04 2025 +0100

    dts: use lowercase hex values in DTS files.

    Apply chnages from dts-linter 0.3.9.

    Improve compliance with DTS Coding Style which says that:

    4) Hex values in properties, e.g. “reg”, shall use lowercase hex.
       The address part can be padded with leading zeros.

    Signed-off-by: Kyle Bonnici <kylebonnici@hotmail.com>

Regression

• This is a regression.

Steps to reproduce

$ pip install tox
$ cd scripts/dts/python-devicetree
$ tox

Relevant log output

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Captured log call -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
WARNING  devicetree.edtlib:edtlib.py:1778 'oldprop' is marked as deprecated in 'properties:' in test-bindings/deprecated.yaml for node /test-deprecated.
WARNING  devicetree.edtlib:edtlib.py:2577 unit address and first address in 'reg' (0x1) don't match for /reg-zero-size-cells/node
WARNING  devicetree.edtlib:edtlib.py:2577 unit address and first address in 'reg' (0x5) don't match for /reg-ranges/parent/node
WARNING  devicetree.edtlib:edtlib.py:2577 unit address and first address in 'reg' (0x30000000200000001) don't match for /reg-nested-ranges/grandparent/parent/node
WARNING  devicetree.edtlib:edtlib.py:2640 compatible 'enums' in binding 'test-bindings/enums.yaml' has non-tokenizable enum for property 'string-enum': 'foo bar', 'foo_bar'
WARNING  devicetree.edtlib:edtlib.py:2646 compatible 'enums' in binding 'test-bindings/enums.yaml' has enum for property 'tokenizable-lower-enum' that is only tokenizable in lowercase: 'bar', 'BAR'
================================================================================================================================================================================== short test summary info ==================================================================================================================================================================================
FAILED tests/test_edtlib.py::test_interrupts - devicetree.edtlib.EDTError: component 'node@70000000E' in path '/interrupt-map-bitops-test/node@70000000E' does not exist
=============================================================================================================================================================================== 1 failed, 87 passed in 0.41s ================================================================================================================================================================================
py3: exit 1 (0.56 seconds) /home/pdgendt/zephyrproject/zephyr/scripts/dts/python-devicetree> python -m pytest tests pid=38636
  py3: FAIL code 1 (3.04=setup[2.48]+cmd[0.56] seconds)
  evaluation failed :( (3.06 seconds)

Impact

Functional Limitation – Some features not working as expected, but system usable.

Environment

• OS: Ubuntu 24.04
• Toolchain: Zephyr SDK 0.17.4
• Commit: a8f8f7d
• Python: 3.12.12

Additional Context

No response

[pdgendt]

CC @kylebonnici

[kylebonnici]

The fix done will work around this issue but to me this exposes another issue in the dtlib.py

edt.get_node("/interrupt-map-bitops-test/node@70000000e") is equal to edt.get_node("/interrupt-map-bitops-test/node@70000000E")

Looking at dtlib is seams that is also does not consider this case from the spec https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#path-names as address can also be omitted if path is unambiguous

e.g.

/ {
foo@10 {};
}

both paths -> /foo and /foo@10 should work. looking at scripts/dts/python-devicetree/src/devicetree/dtlib.py the fill name in full with address is always used and this is not correct.

shall we address these limitations in the dtlib.py? and if so should we use this same issue to address the issues in the dtlib.py ?

[pdgendt]

shall we address these limitations in the dtlib.py? and if so should we use this same issue to address the issues in the dtlib.py ?

This issue is for tracking the CI issue, if further changes are required/bugs need to be fixed, please open a new one with more details.