cancel
Showing results for 
Search instead for 
Did you mean: 

OP-TEE: set_voltage_then_clock:134 Failed to set clock

HLee.21
Associate III

Trying to merge a custom stm32mp153c board to the new BSP (6.1-yocto-mickledore), OP-TEE panics:

 

F/TC:0 0 probe_driver_node:391 Probing stm32mp1-cpu-opp on node cpu0-opp-table
F/TC:0 0 get_supply_phandle:114 cpu: supplied by 4
F/TC:0 0 __clk_enable:1174 Clock 140 has been enabled
F/TC:0 0 __clk_disable:1187 Clock 140 has been disabled
F/TC:0 0 pmic_get_voltage:220 buck1: get volt
F/TC:0 0 __clk_enable:1174 Clock 140 has been enabled
F/TC:0 0 __clk_disable:1187 Clock 140 has been disabled
F/TC:0 0 __clk_enable:1174 Clock 140 has been enabled
F/TC:0 0 __clk_disable:1187 Clock 140 has been disabled
D/TC:0 0 stm32_bsec_find_otp_in_nvmem_layout:644 nvmem part_number_otp = 1: 1 bit offset: 0, length: 8
D/TC:0 0 stm32mp1_cpu_opp_get_dt_subnode:291 Found OPP 0 (650000kHz/1200mV) from DT
F/TC:0 0 regulator_set_voltage:299 buck1 1200mV
F/TC:0 0 __clk_enable:1174 Clock 140 has been enabled
F/TC:0 0 __clk_disable:1187 Clock 140 has been disabled
F/TC:0 0 pmic_set_voltage:233 buck1: set volt
F/TC:0 0 __clk_enable:1174 Clock 140 has been enabled
F/TC:0 0 __clk_disable:1187 Clock 140 has been disabled
F/TC:0 0 __clk_enable:1174 Clock 140 has been enabled
F/TC:0 0 __clk_disable:1187 Clock 140 has been disabled
F/TC:0 0 __clk_enable:1174 Clock 140 has been enabled
F/TC:0 0 __clk_disable:1187 Clock 140 has been disabled
F/TC:0 0 regulator_set_voltage:327 buck1 0uS
E/TC:0 0 set_voltage_then_clock:134 Failed to set clock
E/TC:0 0 Panic at core/arch/arm/plat-stm32mp1/cpu_opp.c:137 <set_voltage_then_clock>

Please see the full bootlog attached.

Any ideas how to fix this?

1 ACCEPTED SOLUTION

Accepted Solutions
HLee.21
Associate III

Quick update: This issue with my custom STM32MP153C board has been resolved. The solution was to use the clock settings from the ST development kits instead of CubeMX's.

View solution in original post

1 REPLY 1
HLee.21
Associate III

Quick update: This issue with my custom STM32MP153C board has been resolved. The solution was to use the clock settings from the ST development kits instead of CubeMX's.