diff --git a/configs/AM62LX/AM62LX_debian_config.txt b/configs/AM62LX/AM62LX_debian_config.txt index e2aa25440..795409724 100644 --- a/configs/AM62LX/AM62LX_debian_config.txt +++ b/configs/AM62LX/AM62LX_debian_config.txt @@ -13,15 +13,16 @@ Replacement Variables --------------------- -'__PART_FAMILY_NAME__' : 'AM62LX' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62LX' +'__PART_FAMILY_NAME__' : 'AM62Lx' +'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Lx' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62lxx-evm' -'__SDK_FULL_NAME__' : 'Debian for AM62L' +'__SDK_FULL_NAME__' : 'Debian for AM62Lx' '__SDK_SHORT_NAME__' : 'Debian' -'__SDK_DOWNLOAD_URL__' : '`AM62L-SDK-Download-page `__' +'__SDK_DOWNLOAD_URL__' : '`AM62Lx-SDK-Download-page `__' '__LINUX_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__LINUX_UBUNTU_VERSION_SHORT__' : '22.04' +'__OPTEE_PLATFORM_FLAVOR__' : 'k3-am62lx' Configuration Values -------------------- diff --git a/configs/AM62LX/AM62LX_debian_tags.py b/configs/AM62LX/AM62LX_debian_tags.py index 7fcbbb13e..fcc508839 100644 --- a/configs/AM62LX/AM62LX_debian_tags.py +++ b/configs/AM62LX/AM62LX_debian_tags.py @@ -2,8 +2,8 @@ fam_name = 'AM62LX' # Project name and HTML title -project = u'Debian for AM62LX' -html_title = 'Debian AM62LX Documentation' +project = u'Debian for AM62Lx' +html_title = 'Debian AM62Lx Documentation' # The master toctree document. master_doc = 'devices/AM62LX/debian/index' diff --git a/configs/AM62LX/AM62LX_debian_toc.txt b/configs/AM62LX/AM62LX_debian_toc.txt index e483a1929..9db082ef5 100644 --- a/configs/AM62LX/AM62LX_debian_toc.txt +++ b/configs/AM62LX/AM62LX_debian_toc.txt @@ -1,6 +1,8 @@ devices/AM62LX/debian/index debian/Overview +devices/AM62LX/linux/Release_Specific +devices/AM62LX/linux/Release_Specific_Release_Notes devices/AM62LX/debian/Getting_Started_Guide debian/Building_Debian_Image debian/Building_Debian_Packages diff --git a/configs/AM62PX/AM62PX_debian_config.txt b/configs/AM62PX/AM62PX_debian_config.txt index 4692c1038..20e08d647 100644 --- a/configs/AM62PX/AM62PX_debian_config.txt +++ b/configs/AM62PX/AM62PX_debian_config.txt @@ -16,12 +16,13 @@ Replacement Variables '__PART_FAMILY_NAME__' : 'AM62Px' '__PART_FAMILY_DEVICE_NAMES__' : 'AM62Px' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' -'__SDK_BUILD_MACHINE__' : 'am62xx-evm' +'__SDK_BUILD_MACHINE__' : 'am62pxx-evm' '__SDK_FULL_NAME__' : 'Debian for AM62Px' '__SDK_SHORT_NAME__' : 'Debian' '__SDK_DOWNLOAD_URL__' : '`AM62Px-SDK-Download-page `__' '__LINUX_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__LINUX_UBUNTU_VERSION_SHORT__' : '22.04' +'__OPTEE_PLATFORM_FLAVOR__' : 'k3-am62px' Configuration Values -------------------- diff --git a/configs/AM62PX/AM62PX_debian_toc.txt b/configs/AM62PX/AM62PX_debian_toc.txt index 658b6d727..05dabf235 100644 --- a/configs/AM62PX/AM62PX_debian_toc.txt +++ b/configs/AM62PX/AM62PX_debian_toc.txt @@ -1,6 +1,8 @@ devices/AM62PX/debian/index debian/Overview +devices/AM62PX/linux/Release_Specific +devices/AM62PX/linux/Release_Specific_Release_Notes devices/AM62PX/debian/Getting_Started_Guide debian/Building_Debian_Image debian/Building_Debian_Packages diff --git a/configs/AM62X/AM62X_debian_toc.txt b/configs/AM62X/AM62X_debian_toc.txt index b71dc9cc2..604873e8c 100644 --- a/configs/AM62X/AM62X_debian_toc.txt +++ b/configs/AM62X/AM62X_debian_toc.txt @@ -1,6 +1,8 @@ devices/AM62X/debian/index debian/Overview +devices/AM62X/linux/Release_Specific +devices/AM62X/linux/Release_Specific_Release_Notes devices/AM62X/debian/Getting_Started_Guide debian/Building_Debian_Image debian/Building_Debian_Packages diff --git a/configs/AM64X/AM64X_debian_toc.txt b/configs/AM64X/AM64X_debian_toc.txt index 386f8ebde..5fc6cb57a 100644 --- a/configs/AM64X/AM64X_debian_toc.txt +++ b/configs/AM64X/AM64X_debian_toc.txt @@ -1,6 +1,8 @@ devices/AM64X/debian/index debian/Overview +devices/AM64X/linux/Release_Specific +devices/AM64X/linux/Release_Specific_Release_Notes devices/AM64X/debian/Getting_Started_Guide debian/Building_Debian_Image debian/Building_Debian_Packages diff --git a/source/debian/Building_Debian_Image.rst b/source/debian/Building_Debian_Image.rst index 94546a028..f90ab104c 100644 --- a/source/debian/Building_Debian_Image.rst +++ b/source/debian/Building_Debian_Image.rst @@ -6,7 +6,7 @@ Introduction ============ Texas Instruments uses the **Armbian** build framework to generate Debian images for its platforms. -*Armbian* describes itself to be a "base operating system"; that is, a build framework used to build +Armbian describes itself to be a "base operating system"; that is, a build framework used to build Linux images optimized for Single-Board Computers. |__SDK_DOWNLOAD_URL__| provides Debian images, but users can also build these, especially if users @@ -22,8 +22,9 @@ time, see `Armbian Documentation `__. Get Armbian ----------- -For the time being, TI's fork of Armbian maintains support for TI platforms. Therefore, the first -step is to fetch TI's fork: +For the time being, `TI's fork `__ of +`Armbian/build `__ maintains support for TI platforms. +Therefore, the first step is to fetch TI's fork: .. code-block:: console @@ -32,75 +33,91 @@ step is to fetch TI's fork: Repository Structure -------------------- -There are 4 files and directories of relevance to this high-level overview: +The following files and directories are relevant to this high-level overview: -- :file:`configs/`: This directory has configurations for boards, families, kernel configurations, - desktop or CLI environments and so on. To find configuration files relevant to TI, see: +- :file:`config/`: This directory has configurations for boards, families, kernel configurations, + desktop or CLI environments and so on. To find configuration files relevant to TI, see: - - :file:`configs/sources/families/k3.conf` - - :file:`configs/kernel/linux-k3-current.conf` - - :file:`configs/kernel/linux-k3-rt-current.conf` + - :file:`config/boards/.conf` + - :file:`config/sources/families/k3.conf` + - :file:`config/kernel/linux-k3-current.conf` + - :file:`config/kernel/linux-k3-rt-current.conf` -- :file:`compile.sh`: This is the script that the user should run for building Armbian images. +- :file:`compile.sh`: This is the script that the user should run for building Armbian images. -- :file:`lib/`: This directory stores the scripts that do most of the work in building Armbian images. +- :file:`lib/`: This directory stores the scripts that do most of the work in building Armbian images. -- :file:`extensions/`: This directory has files that define **extension hooks**. In Armbian, *extension - hooks* are function signatures, which the build framework calls in the process of building an - image. However, the build framework does not define these in ``lib/``. Users can define these - functions and integrate custom steps in the build process. TI has ``extensions/ti-debpkgs.sh`` - extension file. To customize the build process, create a new file in this directory, and define - your extension hooks there. Once the file is created, be sure to add the following line to - board/family config file: +- :file:`extensions/`: This directory has files that define **extension hooks**. In Armbian, extension + hooks are function signatures, which the build framework calls in the process of building an + image. However, the build framework does not define these in ``lib/``. Users can define these + functions and integrate custom steps in the build process. TI has ``extensions/ti-debpkgs.sh`` + extension file. To customize the build process, create a new file in this directory, and define + your extension hooks there. Once the file is created, be sure to add the following line to + board/family config file: .. code-block:: console enable_extension -- :file:`userpatches/`: This directory stores files that define build parameters, user patches and so on. +- :file:`userpatches/`: This directory stores files that define build parameters, user patches and so on. Building Images --------------- -Armbian supports an interactive build process. To build interactively, go to TI's Armbian fork you -cloned, and use the following command: +Armbian supports both an interactive UI and a noninteractive build process. -.. code-block:: console +.. note:: - ./compile.sh + This build guide has been tested on an x86 host machine running Ubuntu 22.04. The Armbian :file:`compile.sh` script + builds in an ARM64 docker container. Ensure the following packages are installed: -The build framework will then display dialog boxes. The user can use this to select the board, CLI -or desktop environment, kernel configurations and so on. + .. code-block:: console -To build the image non-interactively, specify all required **Build Switches** in the command: + sudo apt update + sudo apt install docker.io qemu qemu-user-static binfmt-support -.. code-block:: console +- To build interactively: - ./compile.sh [command] [switch...] [command...] + .. code-block:: console -A full list of build switches is available at `Build Switches `__. + ./compile.sh -For example, the following command builds the minimal non-RT Trixie image: + The build framework will then display dialog boxes. The user can use this to select the board, CLI + or desktop environment, kernel configurations and so on. -.. code-block:: console +- To build non-interactively: + + .. code-block:: console + + ./compile.sh [command] [switch...] [command...] + + A full list of build switches is available at `Build Switches `__. + + .. warning:: + + If build issues arise, try adding these build switches to the end of the build command: + + .. code-block:: console + + GIT_SKIP_SUBMODULES=yes SKIP_ARMBIAN_REPO=yes + + For example, the following command builds the minimal non-RT Trixie image: + + .. code-block:: console + + ./compile.sh build BOARD= BRANCH=current BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie GIT_SKIP_SUBMODULES=yes SKIP_ARMBIAN_REPO=yes + +For a list of boards and branches supported by each SoC, refer: + + .. csv-table:: + :header: "SoC", "Board", "Board Config File", "Branch" - ./compile.sh build BOARD= BRANCH=current BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie SKIP_ARMBIAN_REPO=yes - -For a list of targets corresponding to each board, refer: - - +------------------------------+--------------+ - | Board | Target | - +==============================+==============+ - | AM62P | sk-am62p | - +------------------------------+--------------+ - | AM62x | sk-am62b | - +------------------------------+--------------+ - | AM62-LP | sk-am62-lp | - +------------------------------+--------------+ - | AM62SIP | sk-am62-sip | - +------------------------------+--------------+ - | AM64x | sk-am64b | - +------------------------------+--------------+ + AM62Lx,am62lxx-evm,``config/boards/am62lxx-evm.conf``,"current, current-rt, edge" + AM62Px,am62pxx-evm,``config/boards/am62pxx-evm.conf``,"current, current-rt, edge" + AM62x,sk-am62b,``config/boards/sk-am62b.conf``,"current, edge" + AM62-LP,sk-am62-lp,``config/boards/sk-am62-lp.conf``,"current, current-rt, edge" + AM62SIP,sk-am62-sip,``config/boards/sk-am62-sip.conf``,"current, current-rt, edge" + AM64x,sk-am64b,``config/boards/sk-am64b.conf``,"current, edge" ``output/images/`` stores the built images. These images have a ``.img`` extension. diff --git a/source/debian/Building_Debian_Packages.rst b/source/debian/Building_Debian_Packages.rst index 746505cfe..8182bec45 100644 --- a/source/debian/Building_Debian_Packages.rst +++ b/source/debian/Building_Debian_Packages.rst @@ -2,92 +2,94 @@ Building Debian Packages ======================== -`Debian-Repos `__ is a set of scripts to build TI's Debian packages with a single command. +`debian-repos `__ is a set of scripts to build TI's Debian packages with a single command. The generation of a Debian package from a binary or source involves many steps such as, obtaining the source code in tar (compressed) format, generating template files, modifying template file. The host build system and host build environment variables should also be configured. -The `run.sh` script handles these steps, thus the building of a deb package for TI's packages is as simple as running `run.sh` with the desired package's name. +The :file:`run.sh` script handles these steps. Therefore, the building of a deb package for TI's packages is as simple as running :file:`run.sh` with the package's name as a command line argument. This repository is useful to the following audience: -1. Potential package contributors who want to fix bugs or add enhancements to TI packages. -2. Users who want to create a new package with the latest changes or customizations. -3. Anyone who wants to study Debian packaging. +- Potential package contributors who want to fix bugs or add enhancements to TI packages. +- Users who want to create a new package with the latest changes or customizations. +- Anyone who wants to study Debian packaging. Structure ========= -The `run.sh` file is the "main" script that should be run. It takes as argument the name of the package to be built. +The :file:`run.sh` file is the "main" script. It takes as argument the name of the package to build. -Each TI package has a corresponding directory, named after its source package. Within this directory exists the `suite//debian/` path. All Debian related files (`control`, `rules`, man pages etc) for the package are located here. +Each TI package has a corresponding directory, named after its source package. Within this directory exists the :file:`suite//debian/` path. All Debian related files (:file:`control`, :file:`rules`, man pages etc) for the package are located here. -There also exists a `/version.sh` file. This file is sourced by `run.sh`. +There also exists a :file:`/version.sh` file. This file is sourced by :file:`run.sh`. Setting Up Host for the build ============================= -The `debian-repos` only support native compilation of packages. Hence, the build has to be done either on the ARM64 Target or ARM64 Docker Container or ARM64 Chroot Environment. +`debian-repos `__ only supports native compilation of packages. Therefore, the build has to be done either on the ARM64 target or an ARM64 Docker Container. When running on native ARM64 target, no additional setup is required. Proceed with Building the Package. -To setup and run an ARM64 Docker, run the following commands: +To setup and run an ARM64 Docker Container, run the following commands: .. code-block:: - # Setup Qemu multiarch support - sudo apt-get install qemu binfmt-support qemu-user-static - docker run --rm --privileged multiarch/qemu-user-static --reset -p yes + # Setup Qemu multiarch support + sudo apt install qemu binfmt-support qemu-user-static + docker run --rm --privileged multiarch/qemu-user-static --reset -p yes - # Run ARM64 Container - docker pull ghcr.io/texasinstruments/debian-arm64:latest - docker run --rm -it ghcr.io/texasinstruments/debian-arm64:latest + # Run ARM64 Container + docker pull ghcr.io/texasinstruments/debian-arm64:latest + docker run --rm -it ghcr.io/texasinstruments/debian-arm64:latest bash Building the Package ==================== -Clone `debian-repos `__ +#. Clone `debian-repos `__: -.. code-block:: + .. code-block:: - git clone https://github.com/TexasInstruments/debian-repos.git - cd debian-repos + git clone https://github.com/TexasInstruments/debian-repos.git + cd debian-repos -To build a package, the syntax is: +#. Build package: -.. code-block:: + .. code-block:: - ./run.sh + ./run.sh -This command carries out all the necessary steps to build the package including installation of package-specific dependencies. The package and all related files are then stored in `build/`. + .. note:: -For example: to build `ti-linux-kernel`, the command is: + This command carries out all the necessary steps to build the package including installation of package-specific dependencies. + The package and all related files are then stored in :file:`build/`. -.. code-block:: + For example: to build :file:`ti-linux-kernel`, the command is: + + .. code-block:: - ./run.sh ti-linux-kernel + ./run.sh ti-linux-kernel -The output is then found in `build/ti-linux-kernel/`. + The output is then found in :file:`build/ti-linux-kernel/`. Adding Packages =============== To add a package, follow the following steps: -1. Create nested directories as follows: +#. Create directory structure: -.. code-block:: - - mkdir -p /suite//debian/ + .. code-block:: -2. Copy all ``debian/`` specific files that are relevant to building the package: + mkdir -p /suite//debian/ -.. code-block:: +#. Copy all :file:`debian/` specific files that are relevant to building the package: - cp /path/to/debian/* -r /suite//debian/ + .. code-block:: -3. In ``/``, create the ``version.sh`` file. The file must export the following variables: + cp /path/to/debian/* -r /suite//debian/ -.. code-block:: +#. In :file:`/`, create the :file:`version.sh` file. The file must export the following variables: - git_repo # link from which to clone + .. code-block:: + git_repo # link from which to clone diff --git a/source/debian/Overview.rst b/source/debian/Overview.rst index 2a9f1116c..bec5b58b1 100644 --- a/source/debian/Overview.rst +++ b/source/debian/Overview.rst @@ -11,19 +11,18 @@ TI creates Debian images by using the popular project called **Armbian**. Armbia Single-Board Computers. Unlike other tools, such as mmdebstrap and bdebstrap, which are often used for creating Debian images, Armbian focuses on creating images for Single-Board Computers. -TI's AM62LX, AM62Px, AM62x and AM64x platforms offer the Debian distribution. Few key highlights of -this project are: +A few key highlights of this project are: -- The Debian filesystem image requires standard packages from debian.org and TI's customizations as - ``.deb`` packages. TI's package build infrastructure uses public sources of git repositories to build - deb packages. TI's official repository maintained on `Github/TexasInstruments/ti-debpkgs - `__ hosts these packages. +- The Debian filesystem image requires standard packages from debian.org and TI's additional packages as + ``.deb`` packages. TI's package build infrastructure uses public sources of git repositories to build + deb packages. TI's official repository maintained on `Github/TexasInstruments/ti-debpkgs + `__ hosts these packages. -- This document also provides the required steps and instructions to customize the TI's components - for AM62Lx, AM62Px, AM62x and AM64x Systems-on-Chip and create the corresponding deb packages. +- This document also provides the required steps and instructions to customize the TI's components + for |__PART_FAMILY_DEVICE_NAMES__| System-on-a-Chip (SoC) and create the corresponding deb packages. -- The entire project is public and we accept community contributions as pull requests to GitHub - repositories. +- The entire project is public and we accept community contributions as pull requests to GitHub + repositories. Debian vs Yocto =============== @@ -37,8 +36,8 @@ Comparison +-------------------+--------------------------------------+---------------------------------------+ | **File System** | **Debian** | **OpenEmbedded/Yocto (Arago)** | +-------------------+--------------------------------------+---------------------------------------+ -| Build Time | Faster since all the packages are | All the packages are built from | -| | downloaded as deb packages and | source. so build time is too high. | +| Build Time | Fast since all the packages are | All the packages are built from | +| | downloaded as deb packages and | source. so build time is high. | | | installed. | | +-------------------+--------------------------------------+---------------------------------------+ | Patching SW Stack | Difficult because all components are | Since all the components are built | @@ -59,8 +58,9 @@ Comparison Acknowledgements ================ - - `armbian/build `__ - - `beagleboard/repos-arm64 `__ +- `armbian/build `__ +- `TI/armbian-build `__ +- `beagleboard/repos-arm64 `__ .. _technical-support: @@ -74,13 +74,10 @@ path for developing a product based on the Linux/Debian/RTOS/Android SDKs. However, we know we'll never cover everything that can be done, and occasionally we even make mistakes . So, when you can't seem to find what you need, there's a good place to search through previously -answered questions and ask a new one - The E2E Support Forums. - -There is an active community of TIers and other customers like you -already using a TI Processor, on these forums. You may find your -question has already been answered with a quick Search of the Forums. If -not, a quick post will likely provide you the answers you need. - -- `E2E Processor Support - `__ +answered questions or ask a new one: +the `E2E Support Forums `__. +The E2E Support Forums is an active community of TIers and other customers +like you already using a TI Processor. You may find your question has already +been answered with a quick Search of the Forums. If not, a quick post will +likely provide you the answers you need. diff --git a/source/debian/_Debian_Developers_Guide.rst b/source/debian/_Debian_Developers_Guide.rst index 876af67b4..950f10006 100644 --- a/source/debian/_Debian_Developers_Guide.rst +++ b/source/debian/_Debian_Developers_Guide.rst @@ -3,5 +3,5 @@ Thank you for choosing to evaluate one of our `TI Processors of the Box experience is designed to quickly provide the information you need most while evaluating a TI microprocessor, specifically running one of the Software Architectures -available, Embedded Linux. +available: Embedded Linux. diff --git a/source/devices/AM62LX/debian/Getting_Started_Guide.rst b/source/devices/AM62LX/debian/Getting_Started_Guide.rst index de22be5ae..857f8dfc9 100644 --- a/source/devices/AM62LX/debian/Getting_Started_Guide.rst +++ b/source/devices/AM62LX/debian/Getting_Started_Guide.rst @@ -4,83 +4,83 @@ Getting Started with Debian *************************** -The SD card Image ti_debian_trixie_-.img provided on the |__SDK_DOWNLOAD_URL__| is all you need to get started and explore Debian on TI microprocessors. +The SD card Debian Image provided on the |__SDK_DOWNLOAD_URL__| is all you need to get started and explore +Debian on TI microprocessors. -The Debian Image provided has all the basic packages required to boot with weston as default window manager. The user can install any new package using inbuilt 'apt' utility -and customize the filesystem as required. +The Debian Image provided has all the basic packages required to boot with weston as default window manager. +The user can install any new package using Debian's default ``apt`` package manager and customize the +filesystem as desired. -Follow the steps mentioned in this page to create an SD Card. +Follow the steps mentioned in this page to flash an SD Card. Hardware Setup -------------- -In addition to the EVM itself, the following hardware is needed: +In addition to the Evaluation Module (EVM) itself, the following hardware is needed: -1. USB Type-C 5V - 15V and 3A power supply -2. Micro-SD card reader -3. Micro-SD card (16GB or larger recommended) -4. USB Micro-B cable for UART serial communication -5. HDMI display and HDMI cable -6. USB mouse and Keyboard (For controlling the UI) -7. Ethernet cable (For network access) +- USB Type-C 5V - 15V and 3A power supply +- Micro-SD card reader +- Micro-SD card (16GB or larger recommended) +- USB Micro-B cable for UART serial communication +- HDMI display and HDMI cable +- USB mouse and Keyboard (For controlling the UI) +- Ethernet cable or CC33xx M.2 WiFi card (For network access) .. _processor-sdk-debian-create-sd-card: -Create SD Card using balenaEtcher ---------------------------------- - -1. Download the default bootable SD card image (WIC file) available on the release page as - tisdk-debian-trixie--.wic.xz - -| +Flash SD Card using balenaEtcher +-------------------------------- -2. Download and install the balenaEtcher tool: +#. Download the default bootable SD card image (IMG file) available on the release page: - Balena Etcher is an open-source utility that can be installed on both Linux and Windows. - Download the tool from `this link `__ and install it. + ``tisdk-debian----Armbian-.img`` -| +#. Download and install the balenaEtcher tool: -3. Flash the WIC image to the SD card: + Balena Etcher is an open-source utility that can be installed on both Linux and Windows. + Download the tool from `this link `__ and install it. - Insert a micro SD card into the USB SD card reader and start Etcher. Choose the debian wic - image to be flashed, choose the USB SD card reader as the target, and then click "Flash". - Etcher will decompress the image and write it to the SD card, as shown below: +#. Flash the IMG image to the SD card: - .. Image:: /images/balena_etcher.png + Insert a micro SD card into the USB SD card reader and start Etcher. Choose the debian img + image to be flashed, choose the USB SD card reader as the target, and then click "Flash". + Etcher will decompress the image and write it to the SD card, as shown below: -| + .. image:: /images/balena_etcher.png Set the EVM to SD card Boot mode -------------------------------- -The simplest way to run Linux on the EVM is through an SD card. For that, the EVM will need to be configured for SD card boot. Refer to `AM62L EVM User's Guide `__ for detailed information about boot mode configurations. For quick reference, the figure below shows the boot mode switch setting for SD card boot. +The simplest way to run Linux on the EVM is through an SD card. For that, configure the EVM for SD card boot mode. Refer to +`AM62Lx EVM User's Guide `__ for detailed information about boot mode configurations. +For quick reference, the figure below shows the boot mode switch setting for SD card boot. -.. Image:: /images/AM62LX_SD_boot.jpg +.. image:: /images/AM62LX_SD_boot.jpg Boot and Validate Debian ------------------------ -Make sure to connect the Ethernet cable, HDMI Display, Mouse and Keyboard to the EVM. Insert the SD Card in the board and Power ON the EVM. +Make sure to connect the Ethernet cable or CC33xx M.2 WiFi card, HDMI Display, Mouse and Keyboard to the EVM. Insert the SD Card in the board and Power ON the EVM. -After a few seconds, a setup script will run. This script guides the user through setting up user account, root password, date and so on. Once the setup ends, reboot the board. Weston screen will appear on the display. +During first bootup, a setup script will run. This script guides the user through setting up user account, root password, date and so on. +Once the setup ends, reboot the board. Weston screen will appear on the display. -.. Image:: /images/debian_homescreen.png +.. image:: /images/debian_homescreen.png -You've successfully booted Debian on AM62L. +You've successfully booted Debian on |__PART_FAMILY_DEVICE_NAMES__|. If the board is connected to a private network, setup the proxy to be able to access the Internet. -For more info, refer to `apt.conf(5) man page `__ +For more info, refer to `apt.conf(5) man page `__ Also export ``http_proxy``, ``https_proxy``, ``ftp_proxy`` and ``no_proxy`` with appropriate values if needed. Do an ``apt update`` to make sure that the proxy is properly set and apt recognizes it. The sample output of the command is as shown below:. -.. Image:: /images/debian_am62l_apt_update.png +.. image:: /images/debian_am62l_apt_update.png To install any package available on Debian Standard Package Archive and TI Package Archive use ``apt install``. As an example to install and run ``fortune`` package. -.. Image:: /images/debian_am62l_apt_install.png +.. image:: /images/debian_am62l_apt_install.png More packages can be installed at runtime following the instructions provided to help with the development work flow. diff --git a/source/devices/AM62LX/debian/index.rst b/source/devices/AM62LX/debian/index.rst index f31a45c32..012e0f229 100644 --- a/source/devices/AM62LX/debian/index.rst +++ b/source/devices/AM62LX/debian/index.rst @@ -15,6 +15,7 @@ Debian Developer's Guide :numbered: /debian/Overview + /devices/AM62LX/linux/Release_Specific Getting_Started_Guide /debian/Building_Debian_Image /debian/Building_Debian_Packages diff --git a/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst index 72b653cd8..decbcf87b 100644 --- a/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst @@ -34,6 +34,8 @@ status for all packages included in this release. The manifest can be found on the SDK download page or in the installed directory as indicated below. - Linux Manifest: :file:`/manifest/software_manifest.htm` +- Debian Manifest: `TI debian software manifest 11.01.16.13 + `__ Release 11.01.16.13 =================== @@ -77,6 +79,9 @@ What's new Build Information ================= +Arago (Yocto/OE) +---------------- + .. list-table:: :header-rows: 1 :widths: 15, 30, 30, 30 @@ -118,6 +123,42 @@ Build Information - `11.01.16.13 `__ - +Debian (Armbian) +---------------- + +.. list-table:: + :header-rows: 1 + :widths: 15, 30, 30, 30 + + * - Component + - Branch Info + - Tag Info + - Config Info + * - U-Boot + - `ti-u-boot-2025.01 `__ + - `11.01.16 `__ + - `Build `__ + * - ATF + - `ti-master `__ + - `v2.12+ `__ + - `Build `__ + * - OPTEE + - `master `__ + - `4.7.0+ `__ + - `Build `__ + * - Linux Firmware + - `ti-linux-firmware `__ + - `11.01.16 `__ + - `Git Clone `__ + * - Linux Kernel + - `ti-linux-6.12.y `__ + - `11.01.16 `__ + - `non-RT `__, `RT `__ + * - Armbian Build + - `2025.10-release `__ + - `11.01.16.13 `__ + - `Build `__, `Board `__ + Issues Tracker ============== diff --git a/source/devices/AM62PX/debian/Getting_Started_Guide.rst b/source/devices/AM62PX/debian/Getting_Started_Guide.rst index a3ab46981..bf37b0f1b 100644 --- a/source/devices/AM62PX/debian/Getting_Started_Guide.rst +++ b/source/devices/AM62PX/debian/Getting_Started_Guide.rst @@ -4,84 +4,83 @@ Getting Started with Debian *************************** -The SD card Image tisdk-debian-bookworm- provided on the |__SDK_DOWNLOAD_URL__| is all you need to get started and explore Debian on TI microprocessors. +The SD card Debian Image provided on the |__SDK_DOWNLOAD_URL__| is all you need to get started and explore +Debian on TI microprocessors. -The Debian Image provided has all the basic packages required to boot with weston as default window manager. The user can install any new package by using inbuilt 'apt' utility -and customize the filesystem as required. +The Debian Image provided has all the basic packages required to boot with weston as default window manager. +The user can install any new package using Debian's default ``apt`` package manager and customize the +filesystem as desired. -Follow the steps mentioned in this page to create an SD Card. +Follow the steps mentioned in this page to flash an SD Card. Hardware Setup -------------- -In addition to the SK Evaluation Module (EVM) itself, use the following hardware: +In addition to the SK Evaluation Module (EVM) itself, the following hardware is needed: -1. USB Type-C 5V - 15V and 3A power supply -2. Micro-SD card reader -3. Micro-SD card (16GB or larger recommended) -4. USB Micro-B cable for UART serial communication -5. HDMI display and HDMI cable -6. USB mouse and Keyboard (For controlling the UI) -7. Ethernet cable (For network access) +- USB Type-C 5V - 15V and 3A power supply +- Micro-SD card reader +- Micro-SD card (16GB or larger recommended) +- USB Micro-B cable for UART serial communication +- HDMI display and HDMI cable +- USB mouse and Keyboard (For controlling the UI) +- Ethernet cable or CC33xx M.2 WiFi card (For network access) -Create SD Card using balenaEtcher ---------------------------------- +.. _processor-sdk-debian-create-sd-card: -1. Download the default bootable SD card image (WIC file) available on the release page as - tisdk-debian-bookworm-.wic.xz - -| +Flash SD Card using balenaEtcher +-------------------------------- -2. Download and install the balenaEtcher tool: +#. Download the default bootable SD card image (IMG file) available on the release page: - Balena Etcher is an open-source utility that can be installed on both Linux and Windows. - Download the tool from `this link `__ and install it. + ``tisdk-debian----Armbian-.img`` -| +#. Download and install the balenaEtcher tool: -3. Flash the WIC image to the SD card: + Balena Etcher is an open-source utility that can be installed on both Linux and Windows. + Download the tool from `this link `__ and install it. - Insert a micro SD card into the USB SD card reader and start Etcher. Choose the debian wic - image to be flashed, choose the USB SD card reader as the target, and then click "Flash". - Etcher will decompress the image and write it to the SD card, as shown in the following: +#. Flash the IMG image to the SD card: - .. Image:: /images/balena_etcher.png + Insert a micro SD card into the USB SD card reader and start Etcher. Choose the debian img + image to be flashed, choose the USB SD card reader as the target, and then click "Flash". + Etcher will decompress the image and write it to the SD card, as shown below: -| + .. image:: /images/balena_etcher.png Set the EVM to SD card Boot mode -------------------------------- -The simplest way to run Linux on the SK EVM is through an SD card. For that, configure the EVM in SD card boot mode. Refer to `AM62Px SK EVM User's Guide `__ for detailed information about boot mode configurations. For quick reference, the following figure shows the boot mode switch setting for SD card boot. +The simplest way to run Linux on the SK EVM is through an SD card. For that, configure the EVM for SD card boot mode. Refer to +`AM62Px SK EVM User's Guide `__ for detailed information about boot mode configurations. +For quick reference, the figure below shows the boot mode switch setting for SD card boot. -.. Image:: /images/AM62x_SD_boot.jpg +.. image:: /images/AM62x_SD_boot.jpg Boot and Validate Debian ------------------------ -Make sure to connect the Ethernet cable, HDMI Display, Mouse and Keyboard to the EVM. Insert the SD Card in the board and Power ON the EVM. +Make sure to connect the Ethernet cable or CC33xx M.2 WiFi card, HDMI Display, Mouse and Keyboard to the EVM. Insert the SD Card in the board and Power ON the EVM. -After a few moments, a configuration script will start running. This script will walk you through creating -a user account, setting a root password, configuring the date and other initial setup options. When -the setup finishes, restart the board. Upon reboot, the weston wallpaper should appear on your -display. +During first bootup, a setup script will run. This script guides the user through setting up user account, root password, date and so on. +Once the setup ends, reboot the board. Weston screen will appear on the display. -.. Image:: /images/debian_homescreen.png +.. image:: /images/debian_homescreen.png -You've successfully booted Debian on AM62x. +You've successfully booted Debian on |__PART_FAMILY_DEVICE_NAMES__|. If the board is connected to a private network, setup the proxy to be able to access the Internet. -For more info, refer to `apt.conf(5) man page `__ +For more info, refer to `apt.conf(5) man page `__ Also export ``http_proxy``, ``https_proxy``, ``ftp_proxy`` and ``no_proxy`` with appropriate values if needed. Do an ``apt update`` to make sure that the proxy is properly set and apt recognizes it. The sample output of the command is as shown below:. -.. Image:: /images/debian_apt_update.png +.. image:: /images/debian_apt_update.png To install any package available on Debian Standard Package Archive and TI Package Archive use ``apt install``. As an example to install and run ``fortune`` package. -.. Image:: /images/debian_apt_install.png +.. image:: /images/debian_apt_install.png More packages can be installed at runtime following the instructions provided to help with the development work flow. diff --git a/source/devices/AM62PX/debian/index.rst b/source/devices/AM62PX/debian/index.rst index f31a45c32..4a2fa83bc 100644 --- a/source/devices/AM62PX/debian/index.rst +++ b/source/devices/AM62PX/debian/index.rst @@ -15,6 +15,7 @@ Debian Developer's Guide :numbered: /debian/Overview + /devices/AM62PX/linux/Release_Specific Getting_Started_Guide /debian/Building_Debian_Image /debian/Building_Debian_Packages diff --git a/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst index a2ae6944a..5d108bda4 100644 --- a/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62PX/linux/Release_Specific_Release_Notes.rst @@ -34,6 +34,8 @@ status for all packages included in this release. The manifest can be found on the SDK download page or in the installed directory as indicated below. - Linux Manifest: :file:`/manifest/software_manifest.htm` +- Debian Manifest: `TI debian software manifest 11.01.16.13 + `__ Release 11.01.16.13 @@ -80,6 +82,9 @@ What's new Build Information ================= +Arago (Yocto/OE) +---------------- + .. list-table:: :header-rows: 1 :widths: 15, 30, 30, 30 @@ -121,6 +126,42 @@ Build Information - `11.01.16.13 `__ - +Debian (Armbian) +---------------- + +.. list-table:: + :header-rows: 1 + :widths: 15, 30, 30, 30 + + * - Component + - Branch Info + - Tag Info + - Config Info + * - U-Boot + - `ti-u-boot-2025.01 `__ + - `11.01.16 `__ + - `Build `__ + * - ATF + - `master `__ + - `v2.13+ `__ + - `Build `__ + * - OPTEE + - `master `__ + - `4.7.0+ `__ + - `Build `__ + * - Linux Firmware + - `ti-linux-firmware `__ + - `11.01.16 `__ + - `Git Clone `__ + * - Linux Kernel + - `ti-linux-6.12.y `__ + - `11.01.16 `__ + - `non-RT `__, `RT `__ + * - Armbian Build + - `2025.10-release `__ + - `11.01.16.13 `__ + - `Build `__, `Board `__ + Issues Tracker ============== diff --git a/source/devices/AM62X/debian/Getting_Started_Guide.rst b/source/devices/AM62X/debian/Getting_Started_Guide.rst index 1f4e370f0..dee5da5aa 100644 --- a/source/devices/AM62X/debian/Getting_Started_Guide.rst +++ b/source/devices/AM62X/debian/Getting_Started_Guide.rst @@ -4,84 +4,83 @@ Getting Started with Debian *************************** -The SD card Image tisdk-debian-bookworm- provided on the |__SDK_DOWNLOAD_URL__| is all you need to get started and explore Debian on TI microprocessors. +The SD card Debian Image provided on the |__SDK_DOWNLOAD_URL__| is all you need to get started and explore +Debian on TI microprocessors. -The Debian Image provided has all the basic packages required to boot with weston as default window manager. The user can install any new package by using inbuilt 'apt' utility -and customize the filesystem as required. +The Debian Image provided has all the basic packages required to boot with weston as default window manager. +The user can install any new package using Debian's default ``apt`` package manager and customize the +filesystem as desired. -Follow the steps mentioned in this page to create an SD Card. +Follow the steps mentioned in this page to flash an SD Card. Hardware Setup -------------- -In addition to the SK Evaluation Module (EVM) itself, use the following hardware: +In addition to the SK Evaluation Module (EVM) itself, the following hardware is needed: -1. USB Type-C 5V - 15V and 3A power supply -2. Micro-SD card reader -3. Micro-SD card (16GB or larger recommended) -4. USB Micro-B cable for UART serial communication -5. HDMI display and HDMI cable -6. USB mouse and Keyboard (For controlling the UI) -7. Ethernet cable (For network access) +- USB Type-C 5V - 15V and 3A power supply +- Micro-SD card reader +- Micro-SD card (16GB or larger recommended) +- USB Micro-B cable for UART serial communication +- HDMI display and HDMI cable +- USB mouse and Keyboard (For controlling the UI) +- Ethernet cable or CC33xx M.2 WiFi card (For network access) -Create SD Card using balenaEtcher ---------------------------------- +.. _processor-sdk-debian-create-sd-card: -1. Download the default bootable SD card image (WIC file) available on the release page as - tisdk-debian-bookworm-.wic.xz - -| +Flash SD Card using balenaEtcher +-------------------------------- -2. Download and install the balenaEtcher tool: +#. Download the default bootable SD card image (IMG file) available on the release page: - Balena Etcher is an open-source utility that can be installed on both Linux and Windows. - Download the tool from `this link `__ and install it. + ``tisdk-debian----Armbian-.img`` -| +#. Download and install the balenaEtcher tool: -3. Flash the WIC image to the SD card: + Balena Etcher is an open-source utility that can be installed on both Linux and Windows. + Download the tool from `this link `__ and install it. - Insert a micro SD card into the USB SD card reader and start Etcher. Choose the debian wic - image to be flashed, choose the USB SD card reader as the target, and then click "Flash". - Etcher will decompress the image and write it to the SD card, as shown in the following: +#. Flash the IMG image to the SD card: - .. Image:: /images/balena_etcher.png + Insert a micro SD card into the USB SD card reader and start Etcher. Choose the debian img + image to be flashed, choose the USB SD card reader as the target, and then click "Flash". + Etcher will decompress the image and write it to the SD card, as shown below: -| + .. image:: /images/balena_etcher.png Set the EVM to SD card Boot mode -------------------------------- -The simplest way to run Linux on the SK EVM is through an SD card. For that, configure the EVM in SD card boot mode. Refer to `AM62x SK EVM User's Guide `__ for detailed information about boot mode configurations. For quick reference, the following figure shows the boot mode switch setting for SD card boot. +The simplest way to run Linux on the SK EVM is through an SD card. For that, configure the EVM for SD card boot mode. Refer to +`AM62x SK EVM User's Guide `__ for detailed information about boot mode configurations. +For quick reference, the figure below shows the boot mode switch setting for SD card boot. -.. Image:: /images/AM62x_SD_boot.jpg +.. image:: /images/AM62x_SD_boot.jpg Boot and Validate Debian ------------------------ -Make sure to connect the Ethernet cable, HDMI Display, Mouse and Keyboard to the EVM. Insert the SD Card in the board and Power ON the EVM. +Make sure to connect the Ethernet cable or CC33xx M.2 WiFi card, HDMI Display, Mouse and Keyboard to the EVM. Insert the SD Card in the board and Power ON the EVM. -After a few moments, a configuration script will start running. This script will walk you through creating -a user account, setting a root password, configuring the date and other initial setup options. When -the setup finishes, restart the board. Upon reboot, the weston wallpaper should appear on your -display. +During first bootup, a setup script will run. This script guides the user through setting up user account, root password, date and so on. +Once the setup ends, reboot the board. Weston screen will appear on the display. -.. Image:: /images/debian_homescreen.png +.. image:: /images/debian_homescreen.png -You've successfully booted Debian on AM62x. +You've successfully booted Debian on |__PART_FAMILY_DEVICE_NAMES__|. If the board is connected to a private network, setup the proxy to be able to access the Internet. -For more info, refer to `apt.conf(5) man page `__ +For more info, refer to `apt.conf(5) man page `__ Also export ``http_proxy``, ``https_proxy``, ``ftp_proxy`` and ``no_proxy`` with appropriate values if needed. Do an ``apt update`` to make sure that the proxy is properly set and apt recognizes it. The sample output of the command is as shown below:. -.. Image:: /images/debian_apt_update.png +.. image:: /images/debian_apt_update.png To install any package available on Debian Standard Package Archive and TI Package Archive use ``apt install``. As an example to install and run ``fortune`` package. -.. Image:: /images/debian_apt_install.png +.. image:: /images/debian_apt_install.png More packages can be installed at runtime following the instructions provided to help with the development work flow. diff --git a/source/devices/AM62X/debian/index.rst b/source/devices/AM62X/debian/index.rst index f31a45c32..ad1bffc5c 100644 --- a/source/devices/AM62X/debian/index.rst +++ b/source/devices/AM62X/debian/index.rst @@ -15,6 +15,7 @@ Debian Developer's Guide :numbered: /debian/Overview + /devices/AM62X/linux/Release_Specific Getting_Started_Guide /debian/Building_Debian_Image /debian/Building_Debian_Packages diff --git a/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst index c23eb0653..fab6f4eef 100644 --- a/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM62X/linux/Release_Specific_Release_Notes.rst @@ -77,6 +77,9 @@ What's new Build Information ================= +Arago (Yocto/OE) +---------------- + .. _u-boot-release-notes: U-Boot @@ -167,6 +170,42 @@ Yocto | Release Tag: 11.01.05.03 | +Debian (Armbian) +---------------- + +.. list-table:: + :header-rows: 1 + :widths: 15, 30, 30, 30 + + * - Component + - Branch Info + - Tag Info + - Config Info + * - U-Boot + - `ti-u-boot-2025.01 `__ + - `11.01.05 `__ + - `Build `__ + * - ATF + - `master `__ + - `v2.13+ `__ + - `Build `__ + * - OPTEE + - `master `__ + - `4.6.0 `__ + - `Build `__ + * - Linux Firmware + - `ti-linux-firmware `__ + - `11.01.05 `__ + - `Git Clone `__ + * - Linux Kernel + - `ti-linux-6.12.y `__ + - `11.01.05 `__ + - `non-RT `__, `RT `__ + * - Armbian Build + - `2025.07-release `__ + - `11.01.05.03 `__ + - `Build `__, `Board `__ + Issues Tracker ============== diff --git a/source/devices/AM64X/debian/Getting_Started_Guide.rst b/source/devices/AM64X/debian/Getting_Started_Guide.rst index 239d5821e..3b3714ba5 100644 --- a/source/devices/AM64X/debian/Getting_Started_Guide.rst +++ b/source/devices/AM64X/debian/Getting_Started_Guide.rst @@ -4,53 +4,55 @@ Getting Started with Debian *************************** -The SD card Image tisdk-debian-bookworm- provided on the |__SDK_DOWNLOAD_URL__| is all you need to get started and explore Debian on TI microprocessors. +The SD card Debian Image provided on the |__SDK_DOWNLOAD_URL__| is all you need to get started and explore +Debian on TI microprocessors. -The user can install any new package by using inbuilt 'apt' utility and customize the filesystem as required. +The Debian Image provided has all the basic packages required to boot with weston as default window manager. +The user can install any new package using Debian's default ``apt`` package manager and customize the +filesystem as desired. -Follow the steps mentioned in this page to create an SD Card. +Follow the steps mentioned in this page to flash an SD Card. Hardware Setup -------------- -In addition to the Evaluation Module (EVM) or the Starter Kit itself, use the following hardware: +In addition to the Evaluation Module (EVM) or the Starter Kit (SK) itself, the following hardware is needed: -1. Barrel jack power supply -2. Micro-SD card reader -3. Micro-SD card (16GB or larger recommended) -4. USB Micro-B cable for UART serial communication -5. Ethernet cable (For network access) +- Barrel jack power supply +- Micro-SD card reader +- Micro-SD card (16GB or larger recommended) +- USB Micro-B cable for UART serial communication +- Ethernet cable (For network access) -Create SD Card using balenaEtcher ---------------------------------- +.. _processor-sdk-debian-create-sd-card: -1. Download the default bootable SD card image (WIC file) available on the release page as - tisdk-debian-bookworm-.wic.xz - -| +Flash SD Card using balenaEtcher +-------------------------------- -2. Download and install the balenaEtcher tool: +#. Download the default bootable SD card image (IMG file) available on the release page: - Balena Etcher is an open-source utility that can be installed on both Linux and Windows. - Download the tool from `this link `__ and install it. + ``tisdk-debian----Armbian-.img`` -| +#. Download and install the balenaEtcher tool: -3. Flash the WIC image to the SD card: + Balena Etcher is an open-source utility that can be installed on both Linux and Windows. + Download the tool from `this link `__ and install it. - Insert a micro SD card into the USB SD card reader and start Etcher. Choose the debian wic - image to be flashed, choose the USB SD card reader as the target, and then click "Flash". - Etcher will decompress the image and write it to the SD card, as shown in the following: +#. Flash the IMG image to the SD card: - .. Image:: /images/balena_etcher.png + Insert a micro SD card into the USB SD card reader and start Etcher. Choose the debian img + image to be flashed, choose the USB SD card reader as the target, and then click "Flash". + Etcher will decompress the image and write it to the SD card, as shown below: -| + .. image:: /images/balena_etcher.png Set the EVM to SD card Boot mode -------------------------------- -The simplest way to run Linux on the SK EVM is through an SD card. For that, configure the EVM in SD card boot mode. Refer to `AM64x SK EVM User's Guide `__ or the `TMDS64EVM User's Guide `__ (depending on the device) for detailed information about boot mode configurations. For quick reference, the following figure shows the boot mode switch setting for SD card boot. +The simplest way to run Linux on the EVM or SK is through an SD card. For that, configure the EVM or SK for SD card boot mode. Refer to +`AM64x EVM User's Guide `__ or `AM64x SK User's Guide `__ (depending on the device) +for detailed information about boot mode configurations. For quick reference, the figure below shows the boot mode switch setting for SD card boot. -.. Image:: /images/AM64x_SD_boot.jpg +.. image:: /images/AM64x_SD_boot.jpg Boot and Validate Debian ------------------------ @@ -58,26 +60,29 @@ Make sure to connect the UART and Ethernet cable to the EVM. Insert the SD Card After approximately 20 seconds, the board should boot and you should see the on-board LED glowing. -You've successfully booted Debian on AM64x. +During first bootup, a setup script will run. This script guides the user through setting up user account, root password, date and so on. +Once the setup ends, reboot the board. To verify the distro, connect via the UART console and try running ``neofetch`` on the terminal. The output of the command can be observed on the screen as shown below. -.. Image:: /images/debian_neofetch.png +.. image:: /images/debian_neofetch.png + +You've successfully booted Debian on |__PART_FAMILY_DEVICE_NAMES__|. If the board is connected to a private network, setup the proxy to be able to access the Internet. -For more info, refer to `apt.conf(5) man page `__ +For more info, refer to `apt.conf(5) man page `__ Also export ``http_proxy``, ``https_proxy``, ``ftp_proxy`` and ``no_proxy`` with appropriate values if needed. Do an ``apt update`` to make sure that the proxy is properly set and apt recognizes it. The sample output of the command is as shown below:. -.. Image:: /images/debian_apt_update.png +.. image:: /images/debian_apt_update.png To install any package available on Debian Standard Package Archive and TI Package Archive use ``apt install``. As an example to install and run ``fortune`` package. -.. Image:: /images/debian_apt_install.png +.. image:: /images/debian_apt_install.png More packages can be installed at runtime following the instructions provided to help with the development work flow. diff --git a/source/devices/AM64X/debian/index.rst b/source/devices/AM64X/debian/index.rst index 0df9c59c6..6277dc3cd 100644 --- a/source/devices/AM64X/debian/index.rst +++ b/source/devices/AM64X/debian/index.rst @@ -15,6 +15,7 @@ Debian Developer's Guide :numbered: /debian/Overview + /devices/AM64X/linux/Release_Specific Getting_Started_Guide /debian/Building_Debian_Image /debian/Building_Debian_Packages diff --git a/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst index 538c33afb..e20721d4e 100644 --- a/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM64X/linux/Release_Specific_Release_Notes.rst @@ -169,6 +169,42 @@ Yocto | Release Tag: 11.01.05.03 | +Debian (Armbian) +---------------- + +.. list-table:: + :header-rows: 1 + :widths: 15, 30, 30, 30 + + * - Component + - Branch Info + - Tag Info + - Config Info + * - U-Boot + - `ti-u-boot-2025.01 `__ + - `11.01.05 `__ + - `Build `__ + * - ATF + - `master `__ + - `v2.13+ `__ + - `Build `__ + * - OPTEE + - `master `__ + - `4.6.0 `__ + - `Build `__ + * - Linux Firmware + - `ti-linux-firmware `__ + - `11.01.05 `__ + - `Git Clone `__ + * - Linux Kernel + - `ti-linux-6.12.y `__ + - `11.01.05 `__ + - `non-RT `__, `RT `__ + * - Armbian Build + - `2025.07-release `__ + - `11.01.05.03 `__ + - `Build `__, `Board `__ + Issues Tracker ============== diff --git a/source/linux/How_to_Guides/Target/How_To_Enable_M2CC3301_in_linux.rst b/source/linux/How_to_Guides/Target/How_To_Enable_M2CC3301_in_linux.rst index b5bf13def..23e57e89d 100644 --- a/source/linux/How_to_Guides/Target/How_To_Enable_M2CC3301_in_linux.rst +++ b/source/linux/How_to_Guides/Target/How_To_Enable_M2CC3301_in_linux.rst @@ -114,7 +114,16 @@ Connect to Wi-Fi .. code-block:: console + nmcli device wifi list nmcli device wifi connect "" password "" + .. note:: + + The following command also works and will prompt for a password: + + .. code-block:: console + + nmcli device wifi connect --ask "" + For more information on the Wi-Fi capabilities of the CC33xx devices, please see the documentation that can be found in the `CC33xx SDK `_.