cancel
Showing results for 
Search instead for 
Did you mean: 

STM32MP151 custom board OPTEE issue, one element (tamp@5c00a000) deferred

rgruberski
Associate III

Hi,

I have a custom board with STM32MP151 and have been trying to run it for quite some time. I have been fixing one mistake after another. But now I can't solve the last problem:

 

[13:11:36:338] F/TC:0 0 probe_driver_node:436 Probing stm32-tamp on node tamp@5c00a000
[13:11:36:344] D/TC:0 0 probe_driver_node:449 element: stm32-tamp on node tamp@5c00a000 deferred 2 time(s)
[13:11:36:354] F/TC:0 0 probe_driver_node:436 Probing stm32-cpu-opp on node cpu0-opp-table
[13:11:36:357] D/TC:0 0 probe_driver_node:449 element: stm32-cpu-opp on node cpu0-opp-table deferred 3 time(s)
[13:11:36:368] D/TC:0 0 process_probe_list:590 Unresolved dependencies after 3 rounds, 3 deferred
[13:11:36:377] D/TC:0 0 probe_dt_drivers_early:774 Deferred drivers probing
[13:11:36:377] D/TC:0 0 print_probe_list:397 Probe list: 2 elements
[13:11:36:388] D/TC:0 0 print_probe_list:399 |- Driver stm32-tamp probes on node tamp@5c00a000
[13:11:36:392] D/TC:0 0 print_probe_list:399 |- Driver stm32-cpu-opp probes on node cpu0-opp-table
[13:11:36:396] D/TC:0 0 print_probe_list:403 `- Probe list end

 

The reason for the defer is not explained. I have attached the complete boot log. Please let me know if you see something disturbing in the log file.

Thank you for any support!

1 ACCEPTED SOLUTION

Accepted Solutions

Hi! Sorry, the problem has been solved. I forgot to close the topic. It was a clock configuration problem. Now I am fighting with u-boot. To be honest, I don't know how to close it :)

View solution in original post

2 REPLIES 2
Erwan SZYMANSKI
ST Employee

Hello @rgruberski ,
Can you also attach your device tree used in OP-TEE please ? 

Kind regards,
Erwan.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

Hi! Sorry, the problem has been solved. I forgot to close the topic. It was a clock configuration problem. Now I am fighting with u-boot. To be honest, I don't know how to close it :)