WirelessAndroidAutoDongle
WirelessAndroidAutoDongle copied to clipboard
nisargjhaveri
Please Provide Support for Rasperry PI 5 Device
Looks like the upstream buildroot still does not have RPi 5 support. We can try to add support, I believe there have been some proposed patches as well.
Unfortunately, I don't have a RPi 5 yet to experiment on. Need to wait for someone to add support upstream first.
Seems like the the buildroot recently added support for RPi5, but that is still not part of any stable release. I believe it should be part of the 2024.08 release when that is available. Also, I don't currently own a RPi 5, so someone else needs to test the setup once we actually bump the buildroot submodule.
Another thing to consider would be the power requirements of a RPi 5 and would it be able to work well on usb power from the car.
I can help test pi5. Should I install the pi4 image on pi5?
(pi5 is over kill for this application, why not use a pi 0. Also I doubt my cars head unit can deliver 5v @ 5A)
Pi 4 image most likely won't work on Pi 5. To build for Pi 5, we'd essentially need appropriate defconfig file, something similar to raspberrypi4_defconfig.
Upstream buildroot contains one right now. See raspberrypi5_defconfig. Having a defconfig will help build for the board. Next would be to test and see if we need any more customisations for it to work.
any updates?
Nope. It's doesn't make sense for several reasons to port this to pi5. Cost: Pi5 cost significantly more a pi0 w or pi2 w. - why waste money.
Power requirements: Pi5 requires a USB-C power supply that can offer the full 5V 5A at 27 watts - that power requirement exceeds most car USB capability.
Why waste developers time on something more expensive and less practical?
any updates?
Nope. It's doesn't make sense for several reasons to port this to pi5. Cost: Pi5 cost significantly more a pi0 w or pi2 w. - why waste money.
Power requirements: Pi5 requires a USB-C power supply that can offer the full 5V 5A at 27 watts - that power requirement exceeds most car USB capability.
Why waste developers time on something more expensive and less practical?
If you already have a pi 5 it is not really a waste and the 25 watts is only if you use every USB port and the Pcie port
@manio Could you describe me in detail how to build for raspberry pi 5 with buildroot I have tried and I got a sdimage but it is not working after I flashed it to the card . @nisargjhaveri
@sree3333 How you created that SD card image? You created a dedicated defconfig as @nisargjhaveri mentioned above?
Yes I have with the dedicated defconfig. Like I have to load the config on the configmenu and run "make" right? Or am I missing anything? @manio
The config has to be adjusted, but what you mean that it is not working? Can you connect HDMI and see on the console what is the error exactly?
This only proves that the buildroot for pi5 seems to be working fine... This is good. Now try this: https://skyboo.net/temp/aa/raspberrypi5_defconfig Note: this is totally untested...
Could you tell me this , should I have to run the biuld from WirelessAndroidAutoDongle folder. I actually ran it in buildroot
You need to clone WirelessAndroidAutoDongle with:
$ git clone --recurse-submodules https://github.com/nisargjhaveri/WirelessAndroidAutoDongle
Then you need to use this file. As the new platform is not yet configured/prepared, so the easiest would be to overwrite eg raspberrypi4_defconfig and build it all like for pi4.
Build instruction is here.
@manio package/pkg-generic.mk:257: *** BR2_GLOBAL_PATCH_DIR contains nonexistent directory board/raspberrypi/patches. Stop.
You sure you compiling it properly? The directory is there, and rest of the configs have the same value.
I suggest you first try to compile it without any changes to see if you have a proper dongle image as the result of the build process...
Ok, I will try to build with the rpi4 original config first and then change to try to rpi5 @manio
@manio the build is successful for rpi5 , but no visible bluetooth to connect
@manio @nisargjhaveri I think there is some issue with the rpi5 defconfig
"+ mv /home/mark-42/Projects/WirelessAndroidAutoDongle/buildroot/output/rpi5/target/etc/aawgd.conf /home/mark-42/Projects/WirelessAndroidAutoDongle/buildroot/output/rpi5/images/aawgd.conf mv: cannot stat '/home/mark-42/Projects/WirelessAndroidAutoDongle/buildroot/output/rpi5/target/etc/aawgd.conf': No such file or directory"
Its not able to make aawgd.conf file while make -j10, I tried copying the aawgd.conf from raspberry pi 4 build but that does'nt seem to work
aawgd.conf is not "building" - it's just in the repository and it is only copied to destination filesystem during the buildroot process.
Its only creating 2 partions 34 MB and rootfs for rpi5 @manio @nisargjhaveri
The one with AAWireless partion is of rpi4 and the other one is rpi5 @manio
This doesn't make any sense to me as the only change is the raspberrypi5_defconfig file in which there is no partition definitions (moreover it's mainly based on pi4).