dtc complains about peripherals sharing the same address space.

Hi.

We are using nrf52840 with nrf connect 2.7.0.

When compiling my app the DTC complains like so:

-- Generated zephyr.dts: /develop/scms/west_ws/nrf-connect-tondo/app/build/app/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /develop/scms/west_ws/nrf-connect-tondo/app/build/app/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /develop/scms/west_ws/nrf-connect-tondo/app/build/app/zephyr/dts.cmake
/develop/scms/west_ws/nrf-connect-tondo/app/build/app/zephyr/zephyr.dts:58.25-63.5: Warning (unique_unit_address_if_enabled): /soc/clock@40000000: duplicate unit-address (also used in node /soc/power@40000000)
/develop/scms/west_ws/nrf-connect-tondo/app/build/app/zephyr/zephyr.dts:350.21-354.5: Warning (unique_unit_address_if_enabled): /soc/acl@4001e000: duplicate unit-address (also used in node /soc/flash-controller@4001e000)

naturally dtc is right as flash controller + acl are sharing space and power + clock are sharing space.

It's a hardware design so i can't do anything about it, also for clock + power some offsets inside the memory space like interrupts are also shared (at least according to the product spec).

So the real question is, is there anything i can do so silence the warnings ? is there a better way to define the device tree so the peripheral is still well defined ? maybe define the base address different to start from the minimal offset that is not shared ?

Parents Reply
  • disabling the warning might be ok for the power + clock warnings, as they really o share memory areas of interrupts and i don't rememmber what else, but the rest can be solved by changing the device tree to avoid the memory area collision, after all if you add the offset it's NOT the same address. Why take the approach of silent the thing that troubles the dtc ?

Children
No Data
Related