WIP: Raspberry Pi 5 support #2506
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jens-maus
added
💡 enhancement-ideas
This commit implements a first basicly working Raspberry Pi 5 support which is able to boot into the main RaspberryMatic system and seems to work as expected with the following exceptions/todo: 1. No U-boot bootloader: due to no bcm2712/pi5 support in the upstream U-Boot sources, there is currently also no u-boot support like with the other rpi platforms/boards. That means, there is currently no possibility to boot into the recovery system, thus no way to update this system via standard update packages/procedures. 2. No framebuffer console: due to the missing u-boot support and also potentially due to the stripped down kernel configs there is currently no framebuffer console available for direct login via a HDMI connected monitor. 3. High carrier sense with RPI-RF-MOD@GPIO: Unfortunately, it seems that a RPI-RF-MOD rf module directly connected to the GPIO of a Raspberry Pi 5 does exhibit quite a high CarrierSense (> 80%) due to massive RF interferences. More analyses and work seems to be required to try to reduce this, thought.
This commit implements a first basicly working Raspberry Pi 5 support which is able to boot into the main RaspberryMatic system and seems to work as expected with the following exceptions/todo: 1. No U-boot bootloader: due to no bcm2712/pi5 support in the upstream U-Boot sources, there is currently also no u-boot support like with the other rpi platforms/boards. That means, there is currently no possibility to boot into the recovery system, thus no way to update this system via standard update packages/procedures. 2. No framebuffer console: due to the missing u-boot support and also potentially due to the stripped down kernel configs there is currently no framebuffer console available for direct login via a HDMI connected monitor. 3. High carrier sense with RPI-RF-MOD@GPIO: Unfortunately, it seems that a RPI-RF-MOD rf module directly connected to the GPIO of a Raspberry Pi 5 does exhibit quite a high CarrierSense (> 80%) due to massive RF interferences. More analyses and work seems to be required to try to reduce this, thought.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a first basicely working Raspberry Pi 5 support which is able to boot into the main RaspberryMatic system and seems to work as expected with the following exceptions/todo: