TIMER20 driver instance missing dependency

RE: TIMER20 driver instance missing dependency

Hieu — Mon, 08 Sep 2025 18:48:44 GMT

[quote user="Nick_RA"]OK, so I started afresh with a new hello_world project and copied the code over and it works. So something screwy with that particular project I guess. [/quote]

Right... it unfortunately seems so. Usually this happens when custom board files are being used, and a mistake was made where the timer20 definition isn't correctly included or recreated.

However, the fact that you could refer to it by using &timer20 suggests that the node is indeed available, in which case, it should satisfy the only dependency for CONFIG_NRFX_TIMER20.

[quote user="Nick_RA"]

Hieu said:
CONFIG_NRFX_TIMER20 only depends on the existence of the node timer20 in DeviceTree, with the appropriate compatible property. Whether the node is disabled or enabled doesn't matter, because the nrfx drivers configure the registers directly, unlike Zephyr drivers, which are designed to work with DeviceTree.
That means you don't have to do anything to use CONFIG_NRFX_TIMER20.

Well, it's needed for sure. I haven't delved into the macros but the line

nrfx_timer_t timer_inst = NRFX_TIMER_INSTANCE(TIMER_INST_IDX);

doesn't compile without CONFIG_NRFX_TIMER20

[/quote]

Could this be a hint towards what is wrong? Refer to the dependency definition I linked above, NRFX_TIMER20 only needs the node to be presented. It doesn't need it enabled.
The project I attached in my last reply should also be able to prove that.

RE: TIMER20 driver instance missing dependency

Nick_RA — Fri, 05 Sep 2025 09:54:52 GMT

[quote userid="9456" url="~/f/nordic-q-a/124165/timer20-driver-instance-missing-dependency/547778"]For reference, here is the hello_world sample where I just put CONFIG_NRFX_TIMER20=y in, and it works.[/quote]

OK, so I started afresh with a new hello_world project and copied the code over and it works. So something screwy with that particular project I guess.

This isn't my actual project; because this ecosystem is new to me when starting something new I just start with hello_world to get it going then write it into my code when I'm happy with it, but rather than create loads of mini test projects I normally just CTRL-A / DELETE and start again so something has obviously gone a bit awry.

[quote userid="9456" url="~/f/nordic-q-a/124165/timer20-driver-instance-missing-dependency/547778"]CONFIG_NRFX_TIMER20 only depends on the existence of the node timer20 in DeviceTree, with the appropriate compatible property. Whether the node is disabled or enabled doesn't matter, because the nrfx drivers configure the registers directly, unlike Zephyr drivers, which are designed to work with DeviceTree.
That means you don't have to do anything to use CONFIG_NRFX_TIMER20.[/quote]

Well, it's needed for sure. I haven't delved into the macros but the line

 nrfx_timer_t timer_inst = NRFX_TIMER_INSTANCE(TIMER_INST_IDX);

doesn't compile without CONFIG_NRFX_TIMER20

[quote userid="9456" url="~/f/nordic-q-a/124165/timer20-driver-instance-missing-dependency/547778"]How did you build your project? You mentioned wanting to keep cross compatibility with a nRF52 project. Could you be compiling for a nRF52 target?[/quote]

This was using 54L15DK/54L15/CPUAPP. Yes, I do need to maintain compatibility with another board using nRF52832 so I have separate builds and configs where I'll be storing the timer instances.

[quote userid="9456" url="~/f/nordic-q-a/124165/timer20-driver-instance-missing-dependency/547778"]I also would like to note that, by default, TIMER20 is used by the Multiprotocol Service Layer (MPSL) in projects with wireless functionality like BLE or Matter. Therefore, you should choose another TIMER instance, like TIMER21.[/quote]

Noted, thanks (I hadn't got that far yet!), but please note I was starting from an earlier support article linked in my original post. Maybe someone needs to look at and amend that post & github code...

RE: TIMER20 driver instance missing dependency

Hieu — Thu, 04 Sep 2025 14:33:55 GMT

Hi Nick_RA,

CONFIG_NRFX_TIMER20 only depends on the existence of the node timer20 in DeviceTree, with the appropriate compatible property. Whether the node is disabled or enabled doesn't matter, because the nrfx drivers configure the registers directly, unlike Zephyr drivers, which are designed to work with DeviceTree.
That means you don't have to do anything to use CONFIG_NRFX_TIMER20.

How did you build your project? You mentioned wanting to keep cross compatibility with a nRF52 project. Could you be compiling for a nRF52 target?

It is possible to maintain one code base for both nRF52 and nRF54L, but you will need to have some separate board overlay files.

I also would like to note that, by default, TIMER20 is used by the Multiprotocol Service Layer (MPSL) in projects with wireless functionality like BLE or Matter. Therefore, you should choose another TIMER instance, like TIMER21.

For reference, here is the hello_world sample where I just put CONFIG_NRFX_TIMER20=y in, and it works.

devzone.nordicsemi.com/.../c350910_2D00_250904_5F00_01.zip

Hieu