My Pi3 (non plus) is super unstable with this new June 1 firmware. It immediately fails the memtester and sometimes does not boot at all.
My config.txt oc settings:
Code:
over_voltage=8
arm_freq=1280
sdram_schmoo=0x02000020
over_voltage_sdram=4
sdram_freq=570
gpu_freq=470
force_turbo=1
Smp1, I'm not an expert but your over_voltage setting seems a tad exaggerated, is it useful?
(2018-06-02, 04:41)smp1 Wrote: [ -> ]My Pi3 (non plus) is super unstable with this new June 1 firmware. It immediately fails the memtester and sometimes does not boot at all.
My config.txt oc settings:
Code:
over_voltage=8
arm_freq=1280
sdram_schmoo=0x02000020
over_voltage_sdram=4
sdram_freq=570
gpu_freq=470
force_turbo=1
Does adding safe_mode_gpio=16 to config.txt and rebooting make any difference?
(2018-06-02, 01:48)h3yn0w Wrote: [ -> ]What exactly is a “borderline” RPi3+ board?
There are a small percentage of pi3+ boards that have stability issues at arm_freq=1400 and/or sdram_freq=500.
They generally need a slightly higher voltage at certain temperatures to become reliable, so we've been tweaking these rules.
After updating to #601 my Pi3 (not plus) no longer boots I get this
after a reboot
and another reboot
So I downloaded #530 and manually copied the files and everything worked.
I tried #601 again and got this
Went back to #530 the same way
(2018-06-02, 07:16)Duxduk Wrote: [ -> ]Smp1, I'm not an expert but your over_voltage setting seems a tad exaggerated, is it useful?
arm_freq=1280 require that much voltage on my Pi3. Otherwise it does not pass torture tests.
(2018-06-02, 17:02)quig Wrote: [ -> ]After updating to #601 my Pi3 (not plus) no longer boots I get this after a reboot and another reboot
So I downloaded #530 and manually copied the files and everything worked.
I tried #601 again and got this
Went back to #530 the same way
Can you paste the contents of your /flash/config.txt
If you are overclocking your RAM, try removing your RAM overclock and see if that helps.
I have an RPi3 with the following sdram overclock:
text:
sdram_freq=580
over_voltage_sdram=5
sdram_schmoo=0x02000020
and this was 100% stable with older firmware, but
now crashes with #0601. Removing the overclock allows the RPi3 to boot with #0601 firmware.
Maybe this sdram overclock is no longer stable with the new rules in the #0601 firmware and I need to revalidate it, or it's a bug in the new firmware.
It looks like sdram_schmoo setting in config.txt is ignored in new firmware.
Quote:When I turn off the Raspberry PI 3 model B+, the USB ports are not disabled (0530 and earlier). My external USB DAC stopped shutting down automatically. Although with 8.2.5 everything works - DAC will turn off automatically after switching off in the 8.2.5.
But when measuring the voltage on the USB with a multimeter in the off state "0", in the switched on "+5V". Something does not allow the ports to completely shut down. On Raspberry PI 3 also works as it should.
Resolved. I added a string "max_usb_current=1" to the config.txt, now everything works as it should.
Is there anything that can be done to solve the issue with artefacts in livetv when bt audio is activated?
I tried the following settings: deactivate wifi with
Code:
dtoverlay=pi3-disable-wifi
and set audio resample to middle but no improvement so far.
Artefacts are visible when watching 1080i50 and also 720p50 channels.
(2018-06-02, 20:53)polo_joe Wrote: [ -> ]Is there anything that can be done to solve the issue with artefacts in livetv when bt audio is activated?
Does this happen with 8.2.5?
Wifi diable in LibreELEC Settings.
I noticed that the Pi is not Powerfull enough (or whatsoever) to capture and watch Live-TV at the same time. I do use 2 Pi´s nearly no Problems at all. (about 0.5% artifacts)
(2018-06-02, 19:17)smp1 Wrote: [ -> ]It looks like sdram_schmoo setting in config.txt is ignored in new firmware.
Based on testing that sounds plausible - 580Mhz/+5/schmoo=0x02000020 is stable in #0531, but only 510Mhz/+5/schmoo=0x02000020 is stable in #0601. If the 580Mhz overclock were marginal then you'd expect maybe 570Mhz or even 560Mhz to be rock solid, but having to drop down to 510Mhz suggests that maybe schmoo is being ignored.