docs(linux): Add initial documentation for BeagleBadge

Add an initial 'How to guide' for BeagleBadge board supported
in Debian in Arago distributions.

Signed-off-by: Judith Mendez <[email protected]>

Author: jmenti

configs/AM62LX/AM62LX_linux_toc.txt

@@ -123,6 +123,7 @@ linux/How_to_Guides/Target/How_to_emmc_boot
 linux/How_to_Guides/Target/How_to_mmcsd_boot_emmc_uda
 linux/How_to_Guides/Target/How_To_Enable_M2CC3301_in_linux
 linux/How_to_Guides/Target/Runtime_debug_unlock_on_secure_device
+linux/How_to_Guides/Target/How_to_BeagleBadge_getting_started
 linux/How_to_Guides/FAQ/How_to_Check_Device_Tree_Info
 linux/How_to_Guides/FAQ/How_to_Integrate_Open_Source_Software
 linux/How_to_Guides_Hardware_Setup_with_CCS

source/debian/Building_Debian_Image.rst

@@ -121,8 +121,8 @@ For a list of boards and branches supported by each SoC, refer:
       AM62-LP,sk-am62-lp,``config/boards/sk-am62-lp.conf``,"vendor, vendor-rt, vendor-edge, edge"
       AM62SIP,sk-am62-sip,``config/boards/sk-am62-sip.conf``,"vendor, vendor-rt, vendor-edge, edge"
       AM62Lx,tmds62levm,``config/boards/tmds62levm.conf``,"vendor, vendor-rt, vendor-edge"
+      AM62Lx,beaglebadge,``config/boards/beaglebadge.conf``,"vendor-edge"
       AM62Px,sk-am62p,``config/boards/sk-am62p.conf``,"vendor, vendor-rt, vendor-edge, edge"
       AM64x,sk-am64b,``config/boards/sk-am64b.conf``,"vendor, vendor-rt, vendor-edge, edge"
 
-
 ``output/images/`` stores the built images. These images have a ``.img`` extension.

source/linux/How_to_Guides/Target/How_to_BeagleBadge_getting_started.rst

@@ -0,0 +1,156 @@
+===========================
+BeagleBadge Getting Started
+===========================
+
+Overview
+========
+
+The BeagleBadge is a compact development platform from BeagleBoard.org powered by the TI AM62L SoC.
+Designed for portable and low-power applications, it features built-in Wi-Fi and Bluetooth, multiple
+low power modes, and an integrated fuel gauge for precise battery power monitoring.
+
+The board provides a rich interface including an e-paper connector, DSI connector, Grove expansion,
+seven-segment displays, and an RGB LED. Fully supported in TI releases, the BeagleBadge offers flexible
+boot options (OSPI, UART, SD, USB-DFU) and runs Zephyr OS or Linux via Debian or Arago, making it an
+ideal open source solution for modern IoT and HMI projects.
+
+Supported Operating System
+==========================
+
+- Linux : https://github.com/TexasInstruments/ti-linux-kernel branch: ti-linux-6.12.y
+- Zephyr : https://github.com/glneo/zephyr branch: openamp-am62x-sk-m4
+
+Supported Distributions
+=======================
+
+- Debian: https://github.com/TexasInstruments/armbian-build.git branch: 2025.12-beaglebadge
+- Arago: https://github.com/TexasInstruments/meta-tisdk branch: scarthgap
+
+Low level sources
+=================
+
+- TI Linux: :file:`arch/arm64/boot/dts/til3-am62l3-beaglebadge.dts`
+- TI U-boot: :file:`configs/am62lx_beaglebadge_defconfig`
+
+Building for BeagleBadge
+========================
+
+Debian:
+
+.. code-block:: console
+
+   $ sudo apt-get install docker.io qemu-user-static binfmt-support
+   $ git clone https://github.com/TexasInstruments/armbian-build.git
+   $ cd armbian-build
+   $ git checkout 2025.12-beaglebadge
+   $ ./compile.sh build BOARD=beaglebadge BRANCH=vendor-edge BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie GIT_SKIP_SUBMODULES=yes SKIP_ARMBIAN_REPO=yes
+
+For more information go Debian Building Images documentation.
+
+.. note::
+
+   Armbian: Due to the limited 128MB size of LPDDR on BeagleBadge, SystemD services have
+   been trimmed down to reduce memory footprint.
+
+Arago:
+
+.. code-block:: console
+
+   $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk
+   $ cd tisdk
+   $ ./oe-layertool-setup.sh -f configs/arago-scarthgap-config.txt
+   $ cd build
+   $ . conf/setenv
+   $ export MACHINE=beaglebadge-ti
+   $ ARAGO_SYSVINIT=1 bitbake -k tisdk-tiny-image
+
+For more information go :ref:`here <building-the-sdk-with-yocto>`
+
+.. note::
+
+   Yocto: Due to the limited 128MB size of LPDDR on BeagleBadge, only the *tisdk-tiny-image*
+   can boot on BeagleBadge. Switching to SystemV for init system instead of SystemD will reduce
+   the memory footprint since more system services will be enabled by default with SystemD.
+
+Booting BeagleBadge
+===================
+
+In the following instructions, assume /dev/ttyUSB0 is the serial port enumerated
+on host machine from BeagleBadge USB C connection.
+
+SD boot:
+   1. Flash SD card with Debian or Arago image
+   2. Insert Micro SD card
+   3. Press & hold Select until step 4
+   4. Connect USB C cable
+   5. Connect to /dev/ttyUSB0 on host machine
+
+OSPI boot:
+   1. Boot via SD boot and stop at u-boot prompt
+   2. Flash OSPI
+
+      .. code-block:: console
+
+         => fatload mmc 1 ${loadaddr} tiboot3.bin
+         221296 bytes read in 11 ms (19.2 MiB/s)
+         => print filesize
+         filesize=36070
+         => sf probe
+         SF: Detected is25wx256 with page size 256 Bytes, erase size 4 KiB, total 32 MiB
+         => sf erase 0 40000
+         SF: 262144 bytes @ 0x0 Erased: OK
+         => sf write ${loadaddr} 0 36070
+         device 0 offset 0x0, size 0x36070
+         SF: 221296 bytes @ 0x0 Written: OK
+         => fatload mmc 1 ${loadaddr} tispl.bin
+         1464080 bytes read in 62 ms (22.5 MiB/s)
+         => print filesize
+         filesize=165710
+         => sf probe
+         SF: Detected is25wx256 with page size 256 Bytes, erase size 4 KiB, total 32 MiB
+         => sf erase 0x80000 180000
+         SF: 1572864 bytes @ 0x80000 Erased: OK
+         => sf write ${loadaddr} 0x80000 165710
+         device 0 offset 0x80000, size 0x165710
+         SF: 1464080 bytes @ 0x80000 Written: OK
+         => fatload mmc 1 ${loadaddr} u-boot.img
+         1314747 bytes read in 57 ms (22 MiB/s)
+         => print filesize
+         filesize=140fbb
+         =>  sf probe
+         SF: Detected is25wx256 with page size 256 Bytes, erase size 4 KiB, total 32 MiB
+         => sf erase 0x280000 180000
+         SF: 1572864 bytes @ 0x280000 Erased: OK
+         => sf write ${loadaddr} 0x280000 140fbb
+         device 0 offset 0x280000, size 0x140fbb
+         SF: 1314747 bytes @ 0x280000 Written: OK
+
+   3. Reset the board (S1 RST)
+
+UART boot:
+   1. Connect USB C cable
+   2. Connect to /dev/ttyUSB0 on host machine
+   3. Run the following instructions on host machine:
+
+      .. code-block:: console
+
+         $ sb --xmodem tiboot3.bin > /dev/ttyUSB0 < /dev/ttyUSB0
+         $ sb --xmodem tispl.bin > /dev/ttyUSB0 < /dev/ttyUSB0
+         $ sb --ymodem u-boot.img > /dev/ttyUSB0 < /dev/ttyUSB0
+
+USB-DFU boot:
+   1. Press & hold Select until step 4
+   2. Connect USB C cable
+   3. Connect to /dev/ttyUSB0 on host machine
+   4. Send bootloader binaries from host MACHINE
+
+      .. code-block:: console
+
+         $ sudo -E -S dfu-util -R -a bootloader -D  tiboot3.bin
+         $ sudo -E -S dfu-util -R -a bootloader -D  tispl.bin
+         $ sudo -E -S dfu-util -R -a u-boot.img -D u-boot.img
+
+Any of the above boot methods can be used to boot to u-boot prompt,
+from here, loading the rootfs is generic and can be loaded from SD
+card, OSPI flash, or USB DFU as is discussed in other sections of this
+documentation.

source/linux/How_to_Guides_Developer_Notes.rst

@@ -35,6 +35,7 @@ Developer Notes
    How_to_Guides/Target/How_to_enable_SSC_for_DSS
    How_to_Guides/Target/How_to_boot_quickly
    How_to_Guides/Target/Runtime_debug_unlock_on_secure_device
+   How_to_Guides/Target/How_to_BeagleBadge_getting_started
    How_to_Guides/FAQ/How_to_Verify_Ipc_Linux_R5
    How_to_Guides/FAQ/How_to_Configure_MSMC_memory
    How_to_Guides/FAQ/How_to_Check_Device_Tree_Info