Time become incorrect when enable bluetooth of board nucleo_wba52cg.

[2024markLuo]

Is your feature request related to a problem? Please describe.
I use board nucleo_wba52cg, When I call bt_enable(), then all k_msleep() become not correct.
for example: k_msleep(2000), it was supposed to delay for 2 seconds, but in fact it delayed for 12 seconds.

Describe the solution you'd like
After enabling bluetooth on board nucleo_wba52cg, k_msleep can be accurate and systick can also be accurate.

Describe alternatives you've considered

Additional context

[github-actions]

Hi @2024markLuo! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

[carlescufi]

@erwango any ideas?

[asm5878]

Dear @2024markLuo,
Just for info I have made a test with nucleo_wba55cg board and peripheral_hr.
I have used a GPIO to test a k_sleep behavior and it was as expected.

Here a snippet of while loop:

	while (1) {
		k_sleep(K_SECONDS(1));
		gpio_pin_configure_dt(&tp1, GPIO_OUTPUT_ACTIVE);
		/* Heartrate measurements simulation */
		hrs_notify();
		/* Battery level simulation */
		bas_notify();
		gpio_pin_set_dt(&tp1, 0);
		gpio_pin_configure_dt(&tp1, GPIO_DISCONNECTED);
	}

Right now I haven't in my hands any nucleo_wba52cg to do the same test.
Maybe a mismatch between nucleo_wba52cg and nucleo_wba55cg clock configuration?

Thanks,
Alex

[erwango]

@2024markLuo Did you try to use clock configuration from nucleo_wba55 to nucleo_wba52?

[erwango]

Note that currently BLE support on nucleo_wba52 is not enabled in tree, so this is not technically a "bug".

Moving to discussion.