2018-03-12, 17:50
@popcornmix:
Found that starting with build 0307 my overclocked RPI3 also crashes with h264 thvheadend footage.
The crash happens direct when I start a channel. The image stops but the sound continues.
The config I used for testing looks like this:
arm_freq=1300
over_voltage=2
sdram_freq=550
over_voltage_sdram=5
sdram_schmoo=0x02000020
dtoverlay=sdtweak,overclock_50=83
# gpu_freq=500
core_freq=500
isp_freq=500
h264_freq=500
v3d_freq=500
The maximum gpu config that doesn't crash is:
core_freq=500
# isp_freq=500
# h264_freq=500
# v3d_freq=500
Strangest thing is that even though it's h264 data, the PI crashes when I keep h264_freq=500 disabled but with isp_freq and v3d_freq enabled (also separate).
When I replace fixup.dat and start.elf with the ones you've posted earlier the problem is gone with the full overclock config (with build 0307 till 0311).
Found that starting with build 0307 my overclocked RPI3 also crashes with h264 thvheadend footage.
The crash happens direct when I start a channel. The image stops but the sound continues.
The config I used for testing looks like this:
arm_freq=1300
over_voltage=2
sdram_freq=550
over_voltage_sdram=5
sdram_schmoo=0x02000020
dtoverlay=sdtweak,overclock_50=83
# gpu_freq=500
core_freq=500
isp_freq=500
h264_freq=500
v3d_freq=500
The maximum gpu config that doesn't crash is:
core_freq=500
# isp_freq=500
# h264_freq=500
# v3d_freq=500
Strangest thing is that even though it's h264 data, the PI crashes when I keep h264_freq=500 disabled but with isp_freq and v3d_freq enabled (also separate).
When I replace fixup.dat and start.elf with the ones you've posted earlier the problem is gone with the full overclock config (with build 0307 till 0311).