Add initial support for BeagleBoard PocketBeagle2 #7897
+27
−0
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
github-actions
bot
added
size/small
rpardini
requested changes
Mar 1, 2025
| #Texas Instruments AM62 dual core 1GB USB2 DDR4 | ||
|
|
||
| BOARD_NAME="PocketBeagle 2" | ||
| BOARDFAMILY="k3" |
| TIBOOT3_BOOTCONFIG="am6232_pocketbeagle2_r5_defconfig" | ||
| TIBOOT3_FILE="tiboot3-am62x-hs-fs-evm.bin" | ||
| DEFAULT_CONSOLE="serial" | ||
| KERNEL_TARGET="edge" |
Comment on lines
+21
to
+23
| declare -g KERNELSOURCE="https://github.com/beagleboard/linux" # BeagleBoard kernel | ||
| declare -g KERNEL_MAJOR_MINOR="6.12" | ||
| declare -g KERNELBRANCH="branch:v6.12.9-ti-arm64-r21" |
There was a problem hiding this comment.
... changing the k3 edge family, for a specific board.
This can't be; it will cause multiple versions of the same kernel package to be produced.
This is "fine" for image builds, but once deployed to an apt repo it will cause mayhem.
Either:
- take only the exact patches needed for this board and patch the k3 family, making sure they don't impact the other boards
- create a specific branch (eg not
edgeorcurrent) just for this board - set a different
LINUXFAMILY-- egk3-pb2-- in the hook. which will cause a completely separate kernel package. (I would do this for now).
rpardini
reviewed
Mar 1, 2025
Comment on lines
+21
to
+23
| declare -g KERNELSOURCE="https://github.com/beagleboard/linux" # BeagleBoard kernel | ||
| declare -g KERNEL_MAJOR_MINOR="6.12" | ||
| declare -g KERNELBRANCH="branch:v6.12.9-ti-arm64-r21" |
There was a problem hiding this comment.
Suggested change
| declare -g KERNELSOURCE="https://github.com/beagleboard/linux" # BeagleBoard kernel | |
| declare -g KERNEL_MAJOR_MINOR="6.12" | |
| declare -g KERNELBRANCH="branch:v6.12.9-ti-arm64-r21" | |
| declare -g KERNELSOURCE="https://github.com/beagleboard/linux" # BeagleBoard kernel | |
| declare -g KERNEL_MAJOR_MINOR="6.12" | |
| declare -g KERNELBRANCH="branch:v6.12.9-ti-arm64-r21" | |
| declare -g LINUXFAMILY="k3-pb2" # Separate kernel package from the regular `k3` family |
There was a problem hiding this comment.
Thanks! For my own understanding, what's the benefit of declaring a kernel family branch like this? Is it for the CI caching when building for multiple boards?
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.
Hey All,
Let's try this again. Apologies for the last force push, I cleaned it up now so it's a CSC file only.
This PR adds support for the BeagleBoard PocketBeagle 2.
Features, schematics, and purchase links can be found on the board page[0].
Notable features:
Thanks! and especially many thanks to @glneo for his patience.
[0] https://www.beagleboard.org/boards/pocketbeagle-2
How Has This Been Tested?
Build/Boot tested Bookworm CLI/Minimal on Edge(v6.12) kernel
Build/Boot tested Noble CLI/Minimal on Edge(v6.12) kernel
UART works
Checklist:
My code follows the style guidelines of this project
I have performed a self-review of my own code
My changes generate no new warnings
Any dependent changes have been merged and published in downstream modules