2017-07-30, 00:59
(2017-07-30, 00:20)Pienoet Wrote: I´m trying to play a 8 bit hevc file with these overclock settings
Code:gpu_mem_1024=256
arm_freq=1075
core_freq=530
sdram_freq=600
sdram_schmoo=0x02000020
dtoverlay=sdhost,overclock_50=100
gpu_freq=510
over_voltage_sdram=6
over_voltage=8
force_turbo=1
Have you confirmed your overclock is 100% stable? Judging from the crashes, it probably isn't.
I also don't think you need core_freq AND gpu_freq - gpu_freq will configure the core_freq.
You can use "bcmstat.sh xgpd1" (built-in to these builds, and needs a wide ssh console window!) to monitor temperature, core frequencies and cpu load in real time. This will also confirm what ARM/Core/H264/SDRAM frequencies are being successfully configured from config.txt.
If your temperature is not excessive - the RPi2 CPU will begin to throttle at 80C and cap the ARM frequency at 85C - then it's unlikely to be a temperature issue. Rather, you simply didn't win in the silicon lottery and need to wind back your overclock.
Note that bcmstat.sh will report under-voltage, frequency cap and throttle events in the U, F and T columns. A lower-case value (eg. "u") indicates an event has occurred one or more times in the past since the system booted, while an uppercase value (eg. "U") means the event is ongoing (ie. happening right now). A blank value in the U/F/T columns indicates no event has so far occurred since the system booted.