nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

Jared — Fri, 30 Sep 2022 09:18:50 GMT

Hi,

Did you change the RTC ID parameter of NRF_LIBUARTE_ASYNC_DEFINE() to 2 as well?

regards

Jared

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

kai19960504 — Thu, 29 Sep 2022 09:49:47 GMT

Hi Jared,

Here have two status.

One :

In sdk_config.h I set NRFX_RTC0_ENABLED to 0 and NRFX_RTC1_ENABLED to 1,and change the 3th and 4th parameters of NRF_LIBUARTE_ASYNC_DEFINE() to 1,you can see below picture.

but when i build the project it gives below error

So I change RTC1 to RTC2.

Two :

Change RTC1 to RTC2.

It can build but when I run the project it show ERROR 17 [NRF_ERROR_BUSY]

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

Jared — Thu, 29 Sep 2022 09:11:35 GMT

Hi,

In your sdk_config.h file, can you set NRFX_RTC0_ENABLED to 0 and NRFX_RTC1_ENABLED to 1?

You also have to change the 3th and 4th parameters of NRF_LIBUARTE_ASYNC_DEFINE() to 1 so that it use RTC 1 and TIMER 1 instead of RTC 0 and TIMER 0.

regards

Jared

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

kai19960504 — Thu, 29 Sep 2022 07:31:06 GMT

Hi Jared,

The error occurs when executing nrf_libuarte_async_init.

I continue to track down the nrf_rtc_prescaler_set in nrfx_rtc_init have error.

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

Jared — Thu, 29 Sep 2022 07:05:06 GMT

Hi,

Can you use breakpoints and the debugger and check how far the program reach before it asserts? Does it assert before or after uart_init()?

regards

Jared

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

kai19960504 — Thu, 29 Sep 2022 06:37:25 GMT

Hi Jared,

I always using debug mode,and the error about Invalid memory access do not have more information.

It have not tell me where happening.

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

Jared — Thu, 29 Sep 2022 06:26:18 GMT

Hi,

Does the error message specify where the Invalid memory access happens? Can you re-build your project in debug mode, flash it to your board and then see if the error log is more verbose?

Can you share the entire error log?

If you're using SES, then you can rebuild your project in debug mode by:

regards
Jared

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

kai19960504 — Thu, 29 Sep 2022 01:22:57 GMT

Hi Jared,

Sorry,I'm not sure which instance is using.

Can you download my project and check it?

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

Jared — Wed, 28 Sep 2022 10:26:12 GMT

Hi Kai,

Good, now it's reporting a different error for something else. Softdevice: INVALID MEMORY ACCESS means that the program is accessing a peripheral that has been blocked by the Softdevice. When enabled the Softdevice restricts access to certain peripheral such as the radio and CLOCK 0 and RTC0. Which instance is the app timer module using?

regards

Jared

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

kai19960504 — Wed, 28 Sep 2022 09:17:13 GMT

Hi Jared,

I have already try it,and that time it return me this image.

RE: nrf_drv_clock_init() return ERROR 133 [NRF_ERROR_MODULE_ALREADY_INITIALIZED]

Jared — Wed, 28 Sep 2022 09:14:40 GMT

Hi there,

The error means that clock driver has already been initialized somewhere else in your code before you call UART_Init(), try removing line 1101 and see if the error is still reported.

regards

Jared