Skip to content
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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+27 −0
Open

Add initial support for BeagleBoard PocketBeagle2 #7897

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions config/boards/pocketbeagle2.csc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
#Texas Instruments AM62 dual core 1GB USB2 DDR4

BOARD_NAME="PocketBeagle 2"
BOARDFAMILY="k3"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

k3 family...

BOARD_MAINTAINER="grippy98"
BOOTCONFIG="am6232_pocketbeagle2_a53_defconfig"
BOOTFS_TYPE="fat"
BOOT_FDT_FILE="k3-am6232-pocketbeagle2.dts"
TIBOOT3_BOOTCONFIG="am6232_pocketbeagle2_r5_defconfig"
TIBOOT3_FILE="tiboot3-am62x-hs-fs-evm.bin"
DEFAULT_CONSOLE="serial"
KERNEL_TARGET="edge"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

edge branch....

KERNEL_TEST_TARGET="edge"
SERIALCON="ttyS2"
ATF_BOARD="lite"

#Until PB2 goes upstream, use this branch
function post_family_config_branch_edge__pocketbeagle2_use_beagle_kernel_uboot() {
display_alert "$BOARD" " beagleboard (next branch) u-boot and kernel overrides for $BOARD / $BRANCH" "info"

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"
Comment on lines +21 to +23
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... 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:

  1. take only the exact patches needed for this board and patch the k3 family, making sure they don't impact the other boards
  2. create a specific branch (eg not edge or current) just for this board
  3. set a different LINUXFAMILY -- eg k3-pb2 -- in the hook. which will cause a completely separate kernel package. (I would do this for now).

Comment on lines +21 to +23
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?


declare -g BOOTSOURCE="https://github.com/beagleboard/u-boot" # BeagleBoard u-boot
declare -g BOOTBRANCH="branch:v2025.01-pocketbeagle2"
}
Loading