undefined reference to `__device_dts_ord_98'

RE: undefined reference to `__device_dts_ord_98'

helsing — Wed, 20 Dec 2023 15:31:22 GMT

Hi Ruth, Niklas, sorry for the delay.

The nRF52840 development kit does not have any dedicated Real Time Clock IC.

Here is an unofficial sample(a few years old) showing how to use the Real Time COUNTER in nRF Connect SDK. The sample has not been tested using nRF52840 though it might work: fw-nrfconnect-nrf/samples/nrf9160/nrfx/rtc/src/main.c at nrf9160_samples · Rallare/fw-nrfconnect-nrf · GitHub

Ruth, in case you still need guidance, please create a new ticket and refer to the relevant parts of this ticket.

Best regards,

Håkon

RE: undefined reference to `__device_dts_ord_98'

NicolasK. — Fri, 01 Dec 2023 08:48:56 GMT

Hi Ruth,

I think its like Helsing said. We are confusing real time clock and real time counter. Its not good that they have the same abbreviation rtc (in my opinion it should be more like RTIC (increment counter). The real time counter is similar to the ticks of the MCU [like k_uptime_get()]. The real time clock needs a battery and a quartz which is kept running in order to track time even if the main device is turned off. Usually they are a seperate hardware module like the DS3231. My assumption was that since the nrf52840dk has a battery, its likely it has a real time clock, but I guess I'm wrong.

Helsing please correct me if I misunderstood anything.

Kind regards,

Nicolas

RE: undefined reference to `__device_dts_ord_98'

RuthA — Thu, 30 Nov 2023 17:40:00 GMT

Hi Helsing,

I'm seeing the same behaviour with an nRF52 dev kit.

DEVICE_DT_GET( DT_NODELABEL( XX ) )

works for other node labels and it looks like it expands to the correct "__device_dts_ord_XX" number for the rtc nodes (rtc0, rtc1 and rtc2 on my system) when checked against the "devicetree_generated.h" file. However, the "rtc_set_time" function can't use the device and I see the same "undefined reference" error as Nicolas (with a different number).

This method of setting the device and then using "rtc_set_time" seems to follow the procedure in this zephyr test: https://github.com/zephyrproject-rtos/zephyr/blob/a51bd53cef2b2b6cacb1dc7a366adb45565659f3/tests/drivers/rtc/rtc_api/src/test_time.c

Can you explain why it's not working or let me know which external modules we need for the real time clock?

Best wishes,

Ruth

RE: undefined reference to `__device_dts_ord_98'

helsing — Fri, 17 Nov 2023 12:57:18 GMT

rtc_set_time is a part of the Real Time Clock drivers in Zephyr while nordic,nrf-rtc is Real Time Counter. These are not the same.

For real time clock one often needs an external module. For real time clock, there is a Zephyr test here: https://github.com/nrfconnect/sdk-zephyr/tree/main/drivers/rtc

RE: undefined reference to `__device_dts_ord_98'

helsing — Wed, 15 Nov 2023 15:19:59 GMT

Hi Nicolas, sorry for the delay. I will get back to you tomorrow.

RE: undefined reference to `__device_dts_ord_98'

NicolasK. — Wed, 08 Nov 2023 15:56:10 GMT

That doesn't work (I tried it). rtc0 already exist in the nrf53840.dtsi (not the .dts) aswell as rtc1 and rtc2. Im using the " &rtc0 { " to point to that location and overwrite its parameters. The only important piece in the overlay is the status = "okay" to enable rtc0 because by default its status = "disabled". The timer_dev seems to be set correctly because there is no complie error, but when I add the rtc_set_time function it gives me said error. :(

RE: undefined reference to `__device_dts_ord_98'

helsing — Wed, 08 Nov 2023 15:34:24 GMT

Hi Nicolas,

Does it help to if you try 'rtc' instead of 'rtc0' in the overlay file?