Hi,
okay, thanks to the fixed DRAM, I can now successfully boot a Pyra prototype with 1,5GHz enabled. However, before anyone rejoices: I can only boot it. It freezes when the CPU really is used.
Here is a cpufreq-info after booting:
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: 380 us. hardware limits: 500 MHz - 1.50 GHz available frequency steps: 500 MHz, 750 MHz, 1000 MHz, 1.10 GHz, 1.15 GHz, 1.17 GHz, 1.19 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.27 GHz, 1.29 GHz, 1.30 GHz, 1.37 GHz, 1.39 GHz, 1.41 GHz, 1.43 GHz, 1.45 GHz, 1.47 GHz, 1.49 GHz, 1.50 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance current policy: frequency should be within 500 MHz and 1.50 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 500 MHz (asserted by call to hardware). cpufreq stats: 500 MHz:50.15%, 750 MHz:27.33%, 1000 MHz:7.50%, 1.10 GHz:2.90%, 1.15 GHz:3.46%, 1.17 GHz:1.40%, 1.19 GHz:0.00%, 1.20 GHz:0.00%, 1.22 GHz:0.69%, 1.25 GHz:0.71%, 1.27 GHz:0.98%, 1.29 GHz:0.00%, 1.30 GHz:1.38%, 1.37 GHz:0.69%, 1.39 GHz:0.00%, 1.41 GHz:0.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: 380 us. hardware limits: 500 MHz - 1.50 GHz available frequency steps: 500 MHz, 750 MHz, 1000 MHz, 1.10 GHz, 1.15 GHz, 1.17 GHz, 1.19 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.27 GHz, 1.29 GHz, 1.30 GHz, 1.37 GHz, 1.39 GHz, 1.41 GHz, 1.43 GHz, 1.45 GHz, 1.47 GHz, 1.49 GHz, 1.50 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance current policy: frequency should be within 500 MHz and 1.50 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU[ 60.001689] ata1: SATA link down (SStatus 1 SControl 310) frequency is 500 MHz (asserted by call to hardw[ 60.011036] ata1: EH complete are). cpufreq stats: 500 MHz:50.15%, 750 MHz:27.33%, 1000 MHz:7.50%, 1.10 GHz:2.89%, 1.15 GHz:3.46%, 1.17 GHz:1.40%, 1.19 GHz:0.00%, 1.20 GHz:0.00%, 1.22 GHz:0.69%, 1.25 GHz:0.71%, 1.27 GHz:0.98%, 1.29 GHz:0.00%, 1.30 GHz:1.38%, 1.37 GHz:0.69%, 1.39 GHz:0.00%, 1.41 GHz:0.00)
As you can see, I added multiple frequencies into the board file. And it seems it nevr went higher than 1,37GHz during boot, which explains why it didn't crash.
As soon as I ran the high-load script, it froze after a few seconds.
However, my unit still has the wrong SMPS3-trace. I've attached my board file, so Nikolaus can try it on the corrected SMPS3-board (after all, it seems to run a lot better than mine, as mine never reached more than 1,18GHz before).
I got the feeling we really have a capacitor issue, but we're not THAT far off. So maybe a slight change in the used capacitors can give us that last improvement we need.