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.

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 3 commits into
base: main
Choose a base branch
from

Conversation

Grippy98
Copy link

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:

  • 2x 64-bit Arm-Cortex A53 microprocessor
  • 512MB RAM
  • On-board ADC via a TI MSPM0L1105 Cortex-M0+ MCU
  • Onboard LiPo Battery charger
  • JST-SH 1.00mm UART debug port compatible with Pi Debug probe
  • Pre-soldered headers compatible with original PocketBeagle

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

@github-actions github-actions bot added size/small PR with less then 50 lines Needs review Seeking for review Hardware Hardware related like kernel, U-Boot, ... labels Feb 28, 2025
Grippy98

This comment was marked as outdated.

@Grippy98 Grippy98 requested a review from glneo as a code owner March 2, 2025 03:34
@github-actions github-actions bot added size/large PR with 250 lines or more and removed size/small PR with less then 50 lines labels Mar 2, 2025
@Grippy98 Grippy98 requested a review from rpardini March 2, 2025 03:35
@Grippy98
Copy link
Author

Grippy98 commented Mar 2, 2025

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.

@rpardini
Copy link
Member

rpardini commented Mar 5, 2025

defining a LINUXFAMILY, it expects a new kernel config

Yes, indeed, as it sets a whole new kernel package (as intended), and that ofc needs a .config. You could alternatively set LINUXCONFIG to point to the regular k3 config instead of duplicating, if they're the same.

Grippy98 and others added 3 commits March 5, 2025 06:57
Declare separate LinuxFamily as par rpardini suggestion. Temporary until PB2 reaches mainline.

Co-authored-by: Ricardo Pardini <ricardo@pardini.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Hardware Hardware related like kernel, U-Boot, ... Needs review Seeking for review size/large PR with 250 lines or more
Development

Successfully merging this pull request may close these issues.

2 participants