parse error: undefined node label 'pwm1' when building for 3.0.1 using nrf5340dk

RE: parse error: undefined node label 'pwm1' when building for 3.0.1 using nrf5340dk

Maria Gilje — Wed, 23 Jul 2025 12:43:34 GMT

Hello,

I tried to reproduce your error to get some more information from my own build log, but I was not able to reproduce your build error with this description. The zephyr/samples/boards/nordic/battery sample only supports thingy52/nrf52832 and particle_xenon out of the box. It did not make a difference if I added your overlay because the build failed after generation, that is: when building the source code.

I also tried to use your overlay when building zephyr/samples/hello_world and I do not get the same error as you, but errors about the mipi_dbi node.

Another thing is an inconsistency regarding that in your latest build log you use v2.9.1 of the SDK while in the original post you used v3.0.2. The build error is also not identical with the first one being about pwm1 and the second being about pwm1_default.

I don't think there is enough information here for us to guide you on how to fix the build error. Please clarify the following

Are you using the same .overlay as in your original post?
What is the full path (within the SDK) to the sample you are using?

When creating a build configuration, you need to select the toolchain and SDK version you are building with. Make sure to choose consistently to avoid confusion from conflicting errors.

Also, for future reference: Lesson 2 in the nRF Connect SDK Intermediate course on DevAcademy covers general troubleshooting tips for the devicetree. It does not have a specific example covering "undefined node label", but it can be a good future reference.

Best regards,

Maria

RE: parse error: undefined node label 'pwm1' when building for 3.0.1 using nrf5340dk

lcj — Sat, 12 Jul 2025 17:32:26 GMT

Sorry. I just tried with the battery sample and am getting the same error:

-- Found BOARD.dts: /opt/nordic/ncs/v2.9.1/zephyr/boards/nordic/nrf5340dk/nrf5340dk_nrf5340_cpuapp.dts
devicetree error: /soc/peripheral@50000000/pwm@22000: undefined node label 'pwm1_default'
CMake Error at /opt/nordic/ncs/v2.9.1/zephyr/cmake/modules/dts.cmake:295 (execute_process):
  execute_process failed command indexes:

    1: "Child return code: 1"

Call Stack (most recent call first):
  /opt/nordic/ncs/v2.9.1/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  /opt/nordic/ncs/v2.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /opt/nordic/ncs/v2.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:5 (find_package)


-- Configuring incomplete, errors occurred!
CMake Error at cmake/modules/sysbuild_extensions.cmake:514 (message):
  CMake configure failed for Zephyr project: battery

  Location: /Users/xxxxxxxxx/Projects/GitHub/xxxxxxxxx/battery
Call Stack (most recent call first):
  cmake/modules/sysbuild_images.cmake:20 (ExternalZephyrProject_Cmake)
  cmake/modules/sysbuild_default.cmake:20 (include)
  /opt/nordic/ncs/v2.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  /opt/nordic/ncs/v2.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  /opt/nordic/ncs/v2.9.1/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)

I simply created a new app using the battery sample as a template, selected nrf5340dk as the board target, and tried to build it.

RE: parse error: undefined node label 'pwm1' when building for 3.0.1 using nrf5340dk

AHaug — Tue, 27 May 2025 12:48:19 GMT

Hello,

Could you attach the full build log? I'm curious if there's anything else there.

Could you compare it with the solution (https://github.com/NordicDeveloperAcademy/ncs-inter/tree/main/l4/l4_e2_sol) in https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-4-pulse-width-modulation-pwm/topic/exercise-2-17/ and see if you've missed any configuration?

Kind regards,
Andreas