SPRADU1 September   2026 AM62A3 , AM62A7

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Boot Process
    1. 2.1 SPL Boot Process
      1. 2.1.1 R5 SPL
      2. 2.1.2 TF-A+OPTEE+A53 SPL
      3. 2.1.3 U-Boot
      4. 2.1.4 Linux and User Mode
    2. 2.2 SPL Falcon Mode
      1. 2.2.1 Steps
        1. 2.2.1.1 Installing Linux SDK
        2. 2.2.1.2 Adding Falcon Script
        3. 2.2.1.3 Compiling Linux Device Tree
        4. 2.2.1.4 Creating tispl.bin
        5. 2.2.1.5 Creating a Bootable Card
    3. 2.3 Replacing SPL With SBL
      1. 2.3.1 Falcon Boot in SBL
  6. 3Boot Media
  7. 4Operating System Boot Optimization
    1. 4.1 Trimming Operating System
      1. 4.1.1 Using Preset Trimming Configuration
      2. 4.1.2 Custom Trimming
    2. 4.2 Reducing Log Output
  8. 5Userspace Optimization
    1. 5.1 Customizing Boot Services Using Systemd
  9. 6Minimizing Boot Services Using init Script
  10. 7Conclusion
  11. 8References

Custom Trimming

Custom trimming requires modifying the configuration in arch/arm64/configs/defconfig. For example, set CONFIG_PPS to y to compile the code associated with that configuration into the kernel and start it at kernel startup; set the parameter to m to make it a dynamically loaded module, which is loaded when the file system boots after kernel startup is complete; or set the parameter to n to disable it. However, it is important to note that many modules are interdependent, so simply modifying defconfig may not work. The specific effect can be checked after the build by accessing .config under the board-support/ti-linux-xxxx directory under the Linux SDK directory to check the configuration that finally takes effect. For example, although module A is disabled, when module B, which is dependent on module A, is enabled, module A will still be active in .config after the build.

Custom trimming can also be configured using the Linux configuration tool menuconfig, which checks dependencies during configuration to help with efficient configuration.

For example, as the following figure shows, Bluetooth and the associated protocol stack may not be required in the target application. In this case, use menuconfig to open a graphical interface and make a selection with the arrow keys.

 Menuconfig InterfaceFigure 4-1 Menuconfig Interface

Selecting the Networking support item, you can see a Bluetooth-related option. Select the Bluetooth-related option, and press m to configure the module to be dynamically loaded, press n to disable it, or press y to configure it as a kernel module, which starts with the kernel.

 Configuring Bluetooth in Menuconfig InterfaceFigure 4-2 Configuring Bluetooth in Menuconfig Interface

When the modifications are complete, select Save.

 Saving MenuconfigFigure 4-3 Saving Menuconfig