-
Notifications
You must be signed in to change notification settings - Fork 421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Raspberry Pi 5 #1237
Add Raspberry Pi 5 #1237
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
Would you mind adding the relevant machines in the CI too? https://github.com/agherzan/meta-raspberrypi/blob/master/.github/workflows/yocto-builds.yml#L17 It will help us validate in one go. |
4a0bc52
to
26308f9
Compare
Done @agherzan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@floion, it looks like the builds fail. Could it be that we missed the kernel bump? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rPI 5 builds fail with missing dts
There is also a kernel recipe version bump that landed in master today, so we will need to rebase this PR. |
Hi, I received a Raspberry Pi 5 kit with the official power supply today. The first thing that I tried was this GitHub pull request. Here are my test results:
I will continue investigation the issues tomorrow. Best regards, |
@leon-anavi can you try with the commits @floion just pushed? |
For Raspberry Pi 5 64-bit we also need to set I'm investigating further but some changes are also needed it in |
My previous comment related to |
@leon-anavi yeah iirc it's related to config.txt size somehow |
Do you experience the same issue with I am having other issues with machine |
Based on my further debugging today on Raspberry Pi 5 I am proposing some minor and some temporary changes floion#2
|
Hi @leon-anavi for the u-boot change I think it's enough you make sure you don't have |
I want to make sure an error will appear during building images if |
On the proposed change about the u-boot skipping floion@60b9be8 I'll let @agherzan @kraj have a say |
@leon-anavi what size if the config.txt that fails for you? Can you attach it here? Thinking about opening an issue upstream about the size problem |
@leon-anavi @floion I like the idea of erroring out on uboot to avoid known limitations constantly reported. The vc4 dtb is required too, yes. |
Without the change to remove the comments As a result my Raspberry Pi 5 doesn't boot with. It shows the screen as if Raspberry Pi 5 has been booted without a microSD card at all. |
Ok @agherzan I'll add Leon's commits to the PR |
Hi, I did a test of this branch (including the latest changes from floion#4), but I do get a fully reproducible bootup hang at
after that no further boot output. Has anybody an idea what might go wrong? I am on nanbield with meta-raspberrypi put to this patchset. |
Try all master for best results |
Thanks for the hint! Together with poky master I got core-image-weston running. |
I can also confirm that I was able to boot an image derived from core-image-base. UART & HDMI output seem to work fine. I didn't test any further since my sample camera app is built on top of legacy python3-picamera, which needs some Commits used:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@agherzan I think its ready for merge.
Signed-off-by: Florin Sarbu <florin@balena.io>
Add overlays/vc4-kms-v3d-pi5.dtbo to use vc4-kms-v3d driver on Raspberry Pi 5. This work was sponsored by GOVCERT.LU. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Temporary avoid Raspberry Pi 5 machines because U-Boot has not been ported to it yet. This work was sponsored by GOVCERT.LU. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Remove some comments to reduce config.txt file size to avoid file corruption and make sure Raspberry Pi 5 will boot successfully. The issue with large config.txt has been reported to related projects: raspberrypi/firmware#1848 Evilpaul/RPi-config#9 This work was sponsored by GOVCERT.LU. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Use bcm2711_defconfig instead of bcm2712_defconfig for Raspberry Pi 5 as per the instructions in the documentation: https://www.raspberrypi.com/documentation/computers/linux_kernel.html#kernel-configuration This work was sponsored by GOVCERT.LU. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Set SDIMG_KERNELIMAGE to kernel_2712.img instead of kernel8.img. Raspberry Pi 5 firmware defaults to loading kernel_2712.img because this image contains optimisations specific to Raspberry Pi 5 (e.g. 16K page-size). For more details: https://www.raspberrypi.com/documentation/computers/config_txt.html#kernel This work was sponsored by GOVCERT.LU. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Set SERIAL_CONSOLES to ttyAMA10. This fixes login on the UART no matter if systemd is used. This work was sponsored by GOVCERT.LU. Suggested-by: Gael PORTAY <gael.portay@rtone.fr> Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
@kraj I think we still need this patch for |
I would suggest that we retarget that as an incremental patch directly as a fresh pull after the merge. |
@kraj CI won't pass without, and it is going to complain in all the PR later. @floion do you have a timeline for including @leon-anavi 's patch? |
if we can do a new combined PR ? where this PR and added patches are put together ? |
Ok, yes, I will give it a try tomorrow and provide a combined PR. |
"zImage" not supported on arm64 so set KERNEL_IMAGETYPE_DIRECT to "Image" for Raspberry Pi 5 and avoid the following errors: | make: *** No rule to make target 'zImage'. Stop. | ERROR: oe_runmake failed This work was sponsored by GOVCERT.LU. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Head branch was pushed to by a user without write access
@kraj @agherzan @leon-anavi I added the requested commit to this PR |
Thank you. Today I updated and I tested again this PR on Raspberry Pi 5. I was able to successfully build |
Looks good. I've triggered CI, and it will merge if it succeeds. |
- What I did
- How I did it