[fsm]

U-Boot 2020.10-stm32mp-r1-CSD (Mar 02 2022 – 13:59:09 +0000)

CPU: STM32MP157F?? Rev.Z
Model: Trophy CJ984 board
HW ID: 00
Boot: trusted – stm32image
DRAM: 512 MiB
Clocks:
– MPU : 800 MHz
…
#cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 69.0 us.
hardware limits: 10.0 MHz – 800 MHz
available frequency steps: 10.0 MHz, 800 MHz
available cpufreq governors: userspace
current policy: frequency should be within 10.0 MHz and 800 MHz.
The governor “userspace” may decide which speed to use
within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).
cpufreq stats: 10.0 MHz:28.14%, 800 MHz:71.86% (11)
analyzing CPU 1:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 69.0 us.
hardware limits: 10.0 MHz – 800 MHz
available frequency steps: 10.0 MHz, 800 MHz
available cpufreq governors: userspace
current policy: frequency should be within 10.0 MHz and 800 MHz.
The governor “userspace” may decide which speed to use
within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).
cpufreq stats: 10.0 MHz:28.14%, 800 MHz:71.86% (13)

———————————————————————–

U-Boot 2020.10-stm32mp-r1-CSD (Mar 02 2022 – 13:59:09 +0000)

CPU: STM32MP157C?? Rev.Z
Model: Trophy CJ984 board
HW ID: 00
Boot: trusted – stm32image
DRAM: 512 MiB
Clocks:
– MPU : 650 MHz
…
# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 0.00 ms.
hardware limits: 10.0 MHz – 650 MHz
available frequency steps: 10.0 MHz, 650 MHz
available cpufreq governors: userspace
current policy: frequency should be within 10.0 MHz and 650 MHz.
The governor “userspace” may decide which speed to use
within this range.
current CPU frequency is 650 MHz (asserted by call to hardware).
cpufreq stats: 10.0 MHz:0.00%, 650 MHz:100.00%
analyzing CPU 1:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 0.00 ms.
hardware limits: 10.0 MHz – 650 MHz
available frequency steps: 10.0 MHz, 650 MHz
available cpufreq governors: userspace
current policy: frequency should be within 10.0 MHz and 650 MHz.
The governor “userspace” may decide which speed to use
within this range.
current CPU frequency is 650 MHz (asserted by call to hardware).
cpufreq stats: 10.0 MHz:0.00%, 650 MHz:100.00%

[fsm]

Neeraj,
In my tf-a.dts & u-boot.dts, i replace #include “stm32mp15xc.dtsi” by #include “stm32mp15xf.dtsi” -> no effects, running at 650MHz

Then, I replace my tf-a.dts with your stm32mp157f-dk2.dts ( no changes on u-boot.dts ) and stm32mp157f boots in 800MHz but the sdcard is not running on stm157c version.

I modify tf-a.dts to include stm32mp15xf.dtsi AND stm32mp15xc.dtsi -> I have now an image booting both stm32mp157f at 800MHz and stm32mp157c

Why did you ask me to remove “stm32mp15xc.dtsi” from all my device trees?
if this is not the right way to get the same image for both platforms, how should we do it ?

A big thank you for your help and your great reactivity.
Fred

[Author]

Posts