2026-04-27 12:43 AM - last edited on 2026-04-27 1:13 AM by Andrew Neil
Hi!
I having some issues with Linux at startup. It seems that it disabling the Bucks/LDOs at startup.
vddio2: disabling
vddio3: disabling
vddio4: disabling
vddcore: disabling
v1v8: disabling
v3v3: disablingWhy does this occur?
Here is the complete output as attached file. As you can see, I have set up my own outputs for error handling.
The device three can be found here:
Good to know:
2026-04-27 8:05 AM
Hi @DMårt
also appear with Starter Package. I agree it is quite confusing (for me as well as I'm more HW expert).
[ 32.085289] vddio3: disabling
[ 32.085371] vddio4: disabling
[ 32.085653] vddcore: disabling
[ 32.088709] v1v8: disabling
I guess it is related on the usage of a particular supplies in the probed peripheral (e.g. some of the 1v8 'request' could says 'disabled' if ADC is not used).
I guess it does not directly mean HW will disable them (if even possible) as STPMIC control is managed by Op-Tee which has also its own view of required supplies.
That might be cleaned by more accurately describing the HW in the DTS (if possible).
It does not hurt to ignore those messages.
Regards.
2026-04-30 3:37 AM
Hi!
If you see in the end of the text file output. You can see that RCC clk ID 2 is not started. It gives and error code -17.
Do you know what clock is ID 2?
NOTICE: clk_get_index: Found at 143
F/TC:? 1 invoke_command:63 rng.pta command 0 ptypes 0x7
[ 6.539643] stm32mp25_rcc 44200000.clock-controller: Can't register clk 2: -17
[ 6.546024] stm32 clock failed to initialize
[ 6.550305] stm32mp25_rcc: probe of 44200000.clock-controller failed with error -17
F/TC:1 1 read_available:236 RNG not ready
*F/TC:? 0 pta_scmi_ocall:207 Posting MSG message on channel 0
F/TC:? 0 pta_scmi_ocall:207 Posting MSG message on channel 0
F/TC:? 0 pta_scmi_ocall:207 Posting MSG message on channel 0
F/TC:? 0 pta_scmi_ocall:207 Posting MSG message on channel 0