diff --git a/configs/AM62LX/AM62LX_linux_toc.txt b/configs/AM62LX/AM62LX_linux_toc.txt index 9d649724f..6a234401b 100644 --- a/configs/AM62LX/AM62LX_linux_toc.txt +++ b/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 diff --git a/source/debian/Building_Debian_Image.rst b/source/debian/Building_Debian_Image.rst index cc0993306..3bf67a229 100644 --- a/source/debian/Building_Debian_Image.rst +++ b/source/debian/Building_Debian_Image.rst @@ -30,6 +30,17 @@ Therefore, the first step is to fetch TI's fork: git clone https://github.com/TexasInstruments/armbian-build.git +.. ifconfig:: CONFIG_part_variant in ('AM62LX') + + .. note:: + + BeagleBadge is supported in Armbian but is not yet supported on **ti-main** branch, therefore run the following command + before building for BeagleBadge: + + .. code-block:: console + + git checkout 2025.12-beaglebadge + Repository Structure -------------------- @@ -121,8 +132,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. diff --git a/source/linux/How_to_Guides/Target/How_to_BeagleBadge_getting_started.rst b/source/linux/How_to_Guides/Target/How_to_BeagleBadge_getting_started.rst new file mode 100644 index 000000000..2bd84a01f --- /dev/null +++ b/source/linux/How_to_Guides/Target/How_to_BeagleBadge_getting_started.rst @@ -0,0 +1,177 @@ +########################### +BeagleBadge Getting Started +########################### + +******** +Overview +******** + +The BeagleBadge is a compact development platform from `BeagleBoard `__ powered +by the `TI AM62L SoC `__. Designed for portable and low-power applications, +it features a built-in CC33xx chip supporting WI-FI and Bluetooth applications, multiple low power modes, and +an integrated fuel gauge for 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 sources, +the BeagleBadge offers flexible boot options (OSPI, UART, SD, USB-DFU). It supports Zephyr or Linux (with Armbian +or Arago distributions), making it an ideal open source solution for modern IoT and HMI projects. + +********* +Boot Flow +********* + +BeagleBadge has a `TI AM62L SoC `__, refer to :ref:`AM62Lx Boot Flow ` +for more details on AM62L boot flow. + +************ +Applications +************ + +- Deep Sleep Low Power mode as low as 350mW power draw +- RTC only mode with 3-5mW power draw +- E-Paper display support with tinyDRM +- Battery-powered with fuel gauge monitoring + +***************** +Low level sources +***************** + +.. list-table:: + :header-rows: 1 + :widths: 15, 15, 15 + + * - Component + - Branch + - Source File + * - U-Boot + - `ti-u-boot-2025.01 `__ + - :file:`configs/am62lx_beaglebadge_defconfig` + * - Linux Kernel + - `ti-linux-6.12.y `__ + - :file:`arch/arm64/boot/dts/ti/k3-am62l3-beaglebadge.dts` + +*********************** +Supported Distributions +*********************** + +.. list-table:: + :header-rows: 1 + :widths: 15, 15 + + * - Component + - Branch + * - Armbian + - `2025.12-beaglebadge `__ + * - Arago + - `Scarthgap `__ + +************************ +Building for BeagleBadge +************************ + +.. 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 on building Arago for BeagleBadge, go :ref:`here `. + +.. note:: + + Yocto: Due to the 256MB size of LPDDR on BeagleBadge, there may be limited free memory (about 17-20MB) + for developing applications with the **default**, TI-provided Arago distribution image. Switching to + sysVinit for init system instead of systemd can help reduce the memory footprint further. Please go + `here `__ + for a comparison of both init systems. + +To build Armbian for BeagleBadge, refer to **Debian SDK user manual** found `here `__. + +******************* +Booting BeagleBadge +******************* + +BeagleBadge supports four boot modes with the following configuration: + ++-------------------------+-------------------+------------------+ +| Button *Select* Pressed | Primary boot mode | Backup boot mode | ++=========================+===================+==================+ +| Yes | SD boot | USB-DFU boot | ++-------------------------+-------------------+------------------+ +| No | OSPI boot | UART boot | ++-------------------------+-------------------+------------------+ + +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 5 + 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 + + => sf probe + SF: Detected is25wx256 with page size 256 Bytes, erase size 4 KiB, total 32 MiB + => fatload mmc 1 ${loadaddr} tiboot3.bin + 221296 bytes read in 11 ms (19.2 MiB/s) + => sf update ${loadaddr} 0 ${filesize} + 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) + => sf update ${loadaddr} 0x80000 ${filesize} + 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) + => sf update ${loadaddr} 0x280000 ${filesize} + device 0 offset 0x280000, size 0x140fbb + SF: 1314747 bytes @ 0x280000 Written: OK + + 3. Cold reset the board by disconnecting and reconnecting USB C cable. + 4. Reconnect to /dev/ttyUSB0 on host machine + +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 boot loader 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. diff --git a/source/linux/How_to_Guides_Developer_Notes.rst b/source/linux/How_to_Guides_Developer_Notes.rst index db9e6f485..d27abecd5 100644 --- a/source/linux/How_to_Guides_Developer_Notes.rst +++ b/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