-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 initial support for BeagleBoard PocketBeagle2 #7897
base: main
Are you sure you want to change the base?
Conversation
#Texas Instruments AM62 dual core 1GB USB2 DDR4 | ||
|
||
BOARD_NAME="PocketBeagle 2" | ||
BOARDFAMILY="k3" |
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.
k3
family...
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.
Are you saying there's an issue with k3 for board family? Any current TI based device w/ AM6x series would fall under K3 normally.
TIBOOT3_BOOTCONFIG="am6232_pocketbeagle2_r5_defconfig" | ||
TIBOOT3_FILE="tiboot3-am62x-hs-fs-evm.bin" | ||
DEFAULT_CONSOLE="serial" | ||
KERNEL_TARGET="edge" |
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.
edge
branch....
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.
My intention is to keep it only to edge to simplify testing until it gets mainlined into both uboot and kernel and then I'll completely drop the custom beagle stuff in favor of K3. For K3, we're going to probably update it so you can pick either TI stable/edge or upstream stable/edge and leave it at that.
Declare separate LinuxFamily as par rpardini suggestion. Temporary until PB2 reaches mainline. Co-authored-by: Ricardo Pardini <ricardo@pardini.net>
When defining a LINUXFAMILY, it expects a new kernel config so putting it under k3-beagle-edge which is going to be where I keep the source for PB2 and BeagleY (which I'll push next week) instead of calling it k3-pb2. If you think this approach makes sense I'm good to keep it like this for now. This ultimately needs to be cleaned up once J722s and PB2 are upstreamed. |
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