Raspberry Pi 5 (rpi5) Support

[Swivelgames]

Wanted to revive this discussion:

• Raspberry pi 5 support #652
• Raspberry pi 5 issues? “Update the OS or set os_check=0 in config. txt to skip this check” #671

It would be great to see Raspberry Pi 5 support added! I'd be interested in helping to contribute, but would love some assistance in direction.

Are there any plans to add Pi 5 support?

[matt2005]

Yes I'm working on a build

[matt2005]

This sticky point is I'm updating to bookworm, and applying various aasdk and openauto fixes/improvements at the same time.

[ryantiger658]

I am considering doing a new build and would love to build off of the Pi5. How far out are we looking for Pi5 support?

[matt2005]

I'm working on a Trixie build on a pi5 on 64bit.
I've got aasdk building and openauto running.

I'm in the process of going through all the scripts and services and updating the build.

It's slow going but I'm making progress.

[Swivelgames]

@matt2005 That's fantastic news, especially given that it seems like all other Pi Android Auto projects are effectively dead at the moment.

Thanks so much for the hard work! 🎉

[FabianRaidt]

@matt2005 I did not want to wait for your implementation and tried it myself for the PI5 on Bookworm. I build the binaries for the prebuilts on the PI5 with normal Bookworm, except the additions like Ilclient and the rearcam software, i just wanted openauto on the PI5 working. I also did a little change in the fullscreen behavior of the projection, because it did not want to get to fullscreen, maybe it just was a result in changing all the files from 32bit to 64bit. Most of the changes I just told Copilot to fix it, so the project of mine is not really clean.
To get to the point, at the end it worked on the PI5 after some days, but there are some significant performance issues when using the projection in 1080p60 or even on 720p30 you can see some latency when scrolling on the map. I also used the project initially on the PI4 32bit just to try it and in difference to this one its a lot slower on the PI5.

In conclusion, I think its you can not really use the PI5 for projection because you are missing the VideoCore hw decoder for H.254, I also tried the PI4 with the 64bit project but the performance for this is incredibly bad, it does not come out of the lag it just stutters around.

I ordered myself a debix model a with a H.254 decoder, I want to implement AGL in 64bit version with OpenAuto building with BitBake on YOCTO base, but I do not have a lot of time for things like this, so this will take some time.

Did you already try out the OpenAuto on your PI5? Is it also not as fast as the 32bit version on the PI4?

[matt2005]

So I've managed to get openauto with aasdk on trixie. however its all the support scritp sthat are causing me issues so I'm trying a different route. The main branches of openauto and aasdk build on bookworm and trixie amd64, armhf and arm64.
I could do with some help as its currently just me working on it.

[FabianRaidt]

As I am understanding you correctly, you are having problems with the stages to build the image? This one was also one of my biggest problems for me, I just told Copilot to fix the issues and iterate as long as its not building completely, copilot deleted packages and did some changes to the scripts. The main thing it did from the beginning was to change the docker-build.sh. Copilot also implemented the new Kernel and other things different to the PI5.
I forked your main-branches and uploaded all the changes to it, maybe you can compare it with your branches to see differences, or you just ask Copilot to do the fixes for you, but I think the 32bit would not work anymore for it. I just advise you to use Claude Sonnet, not the free ones, its a big difference between these ones.
I hope the BitBake-build will be more clean, if I have time some day to try it out...

[github-actions]

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 60 days.