Installing Operating System¶
Obtaining Image¶
Obtain Kickpi K4B image files from OneDrive.
Note
Example: update-t113-kickpi-k4b-buildroot-lvds-lcd-sdboot-2026040117.img
update: Full image package
t113-kickpi-k4b: Main controller model T113-S3, hardware board Kickpi-K4b
buildroot / ubuntu: File system (Buildroot or Ubuntu)
lvds-lcd / mipi-lcd: Display interface (LVDS LCD or MIPI LCD)
sdboot / 256MB / 512MB: sdboot: Only supports booting from SD card for debugging, and cannot be flashed. 256MB / 512MB: Corresponding to NAND flash of 256MB and 512MB respectively
2026040117.img: Image build date and time
| Image | System | Description |
|---|---|---|
| update-t113-kickpi-k4b-buildroot-lvds-lcd-256MB-*.img | Buildroot 2019.02 | Single display, LVDS LCD, compatible with 256MB NAND boards |
| update-t113-kickpi-k4b-buildroot-lvds-lcd-512MB-*.img | Buildroot 2019.02 | Single display, LVDS LCD, compatible with 512MB NAND boards |
| update-t113-kickpi-k4b-buildroot-lvds-lcd-sdboot-*.img | Buildroot 2019.02 | Single display, LVDS LCD, for SD card boot debugging |
| update-t113-kickpi-k4b-buildroot-mipi-lcd-256MB-*.img | Buildroot 2019.02 | Single display, automatically detects multiple MIPI screens, compatible with 256MB NAND boards |
| update-t113-kickpi-k4b-buildroot-mipi-lcd-512MB-*.img | Buildroot 2019.02 | Single display, automatically detects multiple MIPI screens, compatible with 512MB NAND boards |
| update-t113-kickpi-k4b-buildroot-mipi-lcd-sdboot-*.img | Buildroot 2019.02 | Single display, automatically detects multiple MIPI screens, for SD card boot debugging |
| update-t113-kickpi-k4b-ubuntu-lvds-lcd-256MB-*.img | Ubuntu 20.04 | Single display, LVDS LCD, compatible with 256MB NAND boards |
| update-t113-kickpi-k4b-ubuntu-lvds-lcd-512MB-*.img | Ubuntu 20.04 | Single display, LVDS LCD, compatible with 512MB NAND boards |
| update-t113-kickpi-k4b-ubuntu-lvds-lcd-sdboot-*.img | Ubuntu 20.04 | Single display, LVDS LCD, for SD card boot debugging |
| update-t113-kickpi-k4b-ubuntu-mipi-lcd-256MB-*.img | Ubuntu 20.04 | Single display, automatically detects multiple MIPI screens, compatible with 256MB NAND boards |
| update-t113-kickpi-k4b-ubuntu-mipi-lcd-512MB-*.img | Ubuntu 20.04 | Single display, automatically detects multiple MIPI screens, compatible with 512MB NAND boards |
| update-t113-kickpi-k4b-ubuntu-mipi-lcd-sdboot-*.img | Ubuntu 20.04 | Single display, automatically detects multiple MIPI screens, for SD card boot debugging |
SD Card Installation¶
K4B has a SD card slot ( microSD aka. TransFlash or TF ) which can also serves as a bootable device. In K4B's boot sequence, SD card has higher priority, so K4B always try to boot from SD card first, when no one mounted, K4B then boot from on-board eMMC / NAND. Since SoC vendor's official Tools use terminology SD(microSD) instead of TF, so we use SD card in this context, TF and SD means the same thing.
With SoC vendor's tool, we can make 2 types of booting card. SD Boot Card works like a portable edition OS, e.g. windows PE. We use SD Boot Card to power device for some maintain and fix purpose. also can be used to verify your own customization. the second type is SD installation card. you create this kind of booting card when you try to use it to install new Image into on-board eMMC / NAND. it contains a specific script to create partition, format FS, copy files to eMMC / NAND. Make sure you understand what you need and create the right SD card.
Preparation¶
Note
Supported SD card filesystem formats: exfat, NTFS
SD Boot Card (SD Boot): Contains bootloader and complete system image, supports device booting directly from microSD card, used in scenarios like eMMC, dev debugging.
SD Installation Card (Upgrade Firmware): Stores firmware image and installation script, used to install or upgrade firmware to the device's on-board storage (e.g., eMMC).
-
Hardware: Windows PC/laptop, USB TYPE-C cable(some cheap TYPE-C cable only provide current, make sure use the one capable of data exchange). some users reported when using double male TYPE-C to TYPE-C cable, installation failed sometimes, when switch to double male USB TYPE-A to TYPE-C, it's ok.
-
Software: Installing tool PhoenixCard, image.
SD Boot Card¶
1. Navigate to the PhoenixCard extracted folder and launch PhoenixCard.

2. Follow the steps shown in the diagram to flash the downloaded image onto the SD card.
Note
During the operation, if PhoenixCard prompts to format the SD card, confirm the formatting.
Select the image with the suffix sdboot.

3. The SD boot card is created successfully.

4. Power off the board, insert the SD Boot Card into the TF card slot of the board, and reconnect the power supply. Since K4B runs a headless system, the startup is successful if the monitor displays the LOGO normally.
Success
The green LED remains lit, and the blue LED blinks continuously (the blue LED will not light up immediately, please wait patiently).
SD Installation Card¶
Note
Select the corresponding image according to the board's storage specifications when installing the OS via SD card.
1. Navigate to the PhoenixCard extracted folder and launch PhoenixCard.

2. Follow the steps shown in the diagram to flash the downloaded image onto the SD card.
Note
During the operation, if PhoenixCard prompts to format the SD card, confirm the formatting.
Select the corresponding image according to the board's storage specifications when installing the OS via SD card.

3. The SD installation card is created successfully.

4. Power off the board, insert the SD Installation Card into the TF card slot of the board, and power on the device again. Wait for the installation to complete. Since K4B runs a headless system, only the LOGO will be displayed on the monitor.
Success
A progress bar will be displayed on the monitor during installation. When the installation is complete, the green LED and blue LED will remain steady on. Power off the board, remove the SD card, power on the board again, and wait for the system to restart.
USB Installation¶
Preparation¶
-
Hardware: USB A-to-C cable.
-
Software: Installing tool PhoenixSuit, AW_Driver_V2.0.2, image.
Steps¶
1. Navigate to the extracted directory of AW_Driver_V2.0.2, and click to run InstallUSBDrv.bat to install the driver.

2. Open Device Manager; the driver installation is successful as shown below.

3. Open PhoenixSuit from the extracted folder in Administrator mode.

4. In the installing software, click "firmware" to select the image to be install.
Note
Select the image based on storage specifications.


5.connect the board to your computer via a USB A-to-C flashing cable, enter installation mode on the development board, Once the software detects the device, the driver will be installed automatically, and the following screen will be displayed. Wait for the installation to complete.
Note
Installation Mode:
When the motherboard is powered off, press and hold the FEL button on the back of the motherboard, then insert the USB flashing cable to connect to the computer. Once the flashing tool detects the device (indicating entry into installation mode), release the FEL button.
When the motherboard is powered on, insert the USB flashing cable, press and hold the FEL button on the back of the motherboard, then press the RST button briefly. Once the flashing tool detects the device (indicating entry into installation mode), release the FEL button.

6. Once the image is installed successfully, the board will restart automatically.
Success
The green LED is steady on, and the blue LED is flashing continuously. (Note: The blue LED will not light up immediately; please wait patiently.)

Q&A¶
- Image Boot Priority?
When systems exist simultaneously on both the mainboard's eMMC and the SD card, upon power-up, the development board will prioritize booting from the system on the SD card.