Phil Elwell
Phil Elwell
Although the 32- and 64-bit OSes can both be run on the same device they are completely different architectures - you have to start from a fresh image download.
Just to warn you - that update contains probably the largest number of changes for non-Pi 4 devices.
Can you try the second and third firmwares on the rpi-firmware master branch (https://github.com/raspberrypi/rpi-firmware/commits/master)? * 2nd: https://github.com/raspberrypi/rpi-firmware/commit/823dc950389082d13b862d684ffb9b8be98500ea * 3rd: https://github.com/raspberrypi/rpi-firmware/commit/b4145cfaa838049fcc1174d1311a98a854703c29
Hmm - I was fairly certain (based solely on the area of code the commits in the source tree refer to) that the newer of those releases would fail while...
What does `dmesg -l err,warn` return?
Thanks - `[ 5.296197] of_clk_hw_onecell_get: invalid index 4` is interesting.
I think it's a bug in the clk-raspberrypi driver that causes it to read off the end of an array, at which point it is at the mercy of what...
Eventually - there's a much simpler version which just increases the allocation from RPI_FIRMWARE_NUM_CLK_ID slots to RPI_FIRMWARE_NUM_CLK_ID + 1.
Have you tried with `dtoverlay=vc4-kms-v3d` instead? That will bypass the firmware completely and at least reduce the number of places that need to support 24-bit audio. Note that HDMI audio...
> (see first post of forum thread I linked)? And my reply.