Kickpi-Book
  • KICKPI Document
  • K5/K5C(A133)
    • A133中文文档
      • 01-主板介绍
        • 01-KICKPI-K5硬件介绍
        • 02-KICKPI-K5C硬件介绍
      • 02-入门必读
        • 01-网盘目录说明
        • 02-快速使用
        • 03-功能测试
        • 04-扩展引脚
      • 03-镜像烧录
        • 01-获取镜像文件
        • 02-SD卡烧录
        • 02-USB线烧录
      • 04-SDK编译
        • 01-编译环境搭建
        • 02-LINUX_SDK源码编译
        • 03-ANDROID_SDK源码编译
      • 05-外设驱动
        • LCD功能调试
        • LRADC按键配置
      • 06-ANDROID系统定制
        • 01-Android常用系统定制
      • 07-LINUX系统定制
        • 02-Linux常用系统定制
      • 08-进阶
        • K5C主板供电
        • 安卓休眠唤醒
        • 13-硬件工厂测试
    • en
      • 01-Development_board_Introduction
        • 01-KICKPI-K5_Hardware_Introduction
        • 02-KICKPI-K5C_Hardware_Introduction
      • 02-Getting_Started_Guide
        • 01-KICKPI_Cloud_Storage_Introduction
        • 02-Quick_Start_Guide
        • 03-Functional_Testing
        • 04-Expansion_Pins_Testing
      • 03-Image_Flashing_Guide
        • 01-How_to_Get_Image_File
        • 02-SD Card Burning
        • 03-USB_Cable_Flashing
      • 04-SDK_Compilation_Guide
        • 01-Compilation_Environment_Setup
        • 02-Linux_SDK_Compilation
        • 03-Android_SDK_Compilation
      • 06-Android_System_Customization
        • 01-Android_Common_System_Customization
      • 07-Linux_System_Customization
        • ADB_Tutorial
  • K2B/K2C(H618)
    • en
      • 01-Development_board_Introduction
        • 01-KICKPI-K2B_Hardware_Introduction
        • 02-KICKPI-K2B_Hardware_Introduction
      • 02-Getting_Started_Guide
        • 01-KICKPI_Cloud_Storage_Introduction
        • 02-Quick_Start_Guide
        • 03-Functional_Testing
        • 04-Expansion_Pins_Testing
      • 03-Image_Flashing_Guide
        • 01-SD_Card_Flashing
        • 02-USB_Cable_Flashing
      • 04-SDK_Compilation_Guide
        • 01-Compilation_Environment_Setup
        • 02-Linux_SDK_Compilation
        • 03-Android_SDK_Compilation
      • 05-Drivers_Development
        • RTC
      • 06-Android_System_Customization
        • 01-Android_Common_System_Customization
      • 07-Linux_System_Customization
        • 01-Linux_Common_System_Customization
      • 08-Advanced_Topics
        • Hardware_Factory_Testing
        • Keybox
    • zh
      • 01-主板介绍
        • 01-KICKPI-K2B硬件介绍
        • 02-KICKPI-K2C硬件介绍
      • 02-入门必读
        • 01-网盘目录说明
        • 02-快速使用
        • 03-功能测试
        • 04-扩展引脚
      • 03-镜像烧录
        • 01-SD卡烧录
        • 02-USB线烧录
      • 04-SDK编译
        • 01-编译环境搭建
        • 02-LINUX_SDK源码编译
        • 2. Android SDK编译
      • 05-外设驱动
        • RTC
      • 06-Android系统定制
        • Android常用系统定制
      • 07-Linux系统定制
        • 01-Linux常用系统定制
        • 02-Linux_QT开发环境搭建
      • 08-进阶
        • Keybox
        • Secure Boot
        • Windows_QT开发环境搭建
        • 扩展引脚功能定制
        • 硬件工厂测试
  • K1/K1B/K3/K8(RK356x-RK3588)
    • en
      • 01-Development_board_Introduction
        • 01-RK_Chip_Comparison_Introduction
        • 02-KICKPI-K1_Hardware_Introduction
        • 03-KICKPI-K1B_Hardware_Introduction
        • 04-KICKPI-K3_Hardware_Introduction
        • 05-KICKPI-K8_Hardware_Introduction
      • 02-Getting_Started_Guide
        • 01-Cloud_Storage_Directory_Description
        • 02-K1-Quick_Start_Guide
        • 02-K1B-Quick_Start_Guide
        • 02-K3-Quick_Start_Guide
        • 02-K8-Quick_Start_Guide
        • 03-Functional_Testing
        • 04-Expansion_Pins
      • 03-Image_Flashing_Guide
        • 01-USB_Cable_Flashing
      • 04-SDK_Compilation_Guide
        • 01-Compilation_Environment_Setup
        • 02-LINUX_SDK_Compilation
        • 03-ANDROID_SDK_Compilation
      • 05-Drivers_Development
        • GPIO
        • Kernel
        • LCD
        • PWM
        • RTC
      • 06-Android_System_Customization
        • 01-Common_Android_System_Customizations
        • 01-Common_Android_System_Customizations
      • 07-Linux_System_Customization
        • 01-Common_Linux_System_Customization
        • 02-Installing_VNC_on_Linux
        • 03-Linux_Docker
        • 04-Linux_QT_Environment_Setup
        • 05-Linux_NPU_YOLOV5S_object_detection
      • 08-Advanced_Topics
        • 01-Hardware_Factory_Test
        • 02-Hardware_Aging_Test
        • 03-Firmware_Unpacking_and_Packing
    • zh
      • 01-主板介绍
        • 01-RK芯片对比介绍
        • 02-KICKPI-K1硬件介绍
        • 03-KICKPI-K1B硬件介绍
        • 04-KICKPI-K3硬件介绍
        • 05-KICKPI-K8硬件介绍
      • 02-入门必读
        • 01-网盘目录说明
        • 02-K1-快速使用
        • 02-K1B-快速使用
        • 02-K3-快速使用
        • 02-K8-快速使用
        • 03-功能测试
        • 04-拓展引脚
      • 03-镜像烧录
        • 01-获取镜像文件
        • 02-USB线烧录
      • 04-SDK编译
        • 01-编译环境搭建
        • 02-LINUX_SDK编译
        • 03-ANDROID_SDK编译
      • 05-外设驱动
        • GPIO
        • Kernel
        • LCD
        • PWM
        • RTC
      • 06-ANDROID系统定制
        • 01-Android常用系统定制
        • 07-Android NPU YOLOV5 目标检测
      • 07-LINUX系统定制
        • 01-Linux常用系统定制
        • 02-Linux安装VNC
        • 03-Linux Docker环境搭建
        • 04-Linux QT环境搭建
        • 05-Linux NPU YOLOV5S 目标检测
      • 08-进阶
        • 01-硬件工厂测试
        • 02-硬件老化测试
        • 03-固件解包和打包
  • K7(RK3576)
    • en
      • 01-Development_board_Introduction
        • 01-KICKPI-K7_Hardware_Introduction
      • 02-Getting_Started_Guide
        • 01-KICKPI_Cloud_Storage_Introduction
        • 02-Quick_Start_Guide
        • 03-Functional_Testing
        • 04-Expansion_Pins_Testing
      • 03-Image_Flashing_Guide
        • 01-How_to_Get_Image_File
        • 02-USB_Cable_Flashing
      • 04-SDK_Compilation_Guide
        • 01-Compilation_Environment_Setup
        • 02-Linux_SDK_Compilation
        • 03-Android_SDK_Compilation
      • 05-Drivers_Development
        • ADC
        • PWM
      • 06-Android_System_Customization
        • 01-Android_Common_System_Customization
      • 07-Linux_System_Customization
        • 01-Linux_Common_System_Customization
        • 02-Linux_Docker_Environment_Setup
        • 03-Linux_NPU_YOLOv5s_Object_Detection
        • 04-Linux_DeepSeek_Large_Model
        • 05-Linux_VNC_Remote_Control
      • 08-Advanced_Topics
        • Advanced_Testing
    • zh
      • 01-主板介绍
        • 01-KICKPI-K7硬件介绍
      • 02-入门必读
        • 01-网盘目录说明
        • 02-快速使用
        • 03-功能测试
        • 04-拓展引脚
      • 03-镜像烧录
        • 01-获取镜像文件
        • 02-USB线烧录
      • 04-SDK编译
        • 01-编译环境搭建
        • 02-Linux_SDK编译
        • 03-Android_SDK编译
      • 05-外设驱动
        • ADC
        • PWM
      • 06-ANDROID系统定制
        • 01-Android常用系统定制
      • 07-LINUX系统定制
        • 01-Linux常用系统定制
        • 02-Linux Docker环境搭建
        • 03-Linux NPU YOLOV5S 目标检测
        • 04-Linux_Deepseek大模型
        • 05-Linux_VNC远程控制
      • 08-进阶
        • 进阶测试
  • K4B(T113-S3)
    • T113-S3中文文档
      • 01-KICKPI-K4B硬件介绍
      • 10-系统镜像烧录
      • 11-SDK源码编译
      • 12-硬件功能测试
      • 13-硬件工厂测试
      • LCD功能调试
      • 20-Ubuntu20.04系统定制
      • Buildroot_QT5配置
      • Buildroot系统定制
  • common
    • en
      • adb
        • ADB_Tutorial
      • allwinner_burnning
        • SD_Card_Flashing
        • USB_Cable_Flashing
      • debug
        • 01 - Log Collection
      • display
        • FPC_Interface_Introduction
      • linux
        • SSH
    • zh
      • adb
        • ADB教程
      • android
        • qt
      • debug
        • 01-日志抓取
        • 常见问题
      • display
        • FPC接口介绍
      • linux
        • SSH
        • VNC
        • qt
      • 全志烧录
        • SD卡烧录
        • USB线烧录
Powered by GitBook
On this page
  • Symbol Explanation
  • Powering on the Board
  • Power Supply
  • LED Indicators
  • Power-On Steps
  • Display
  • LVDS/MIPI
  • HDMI
  • User and Password
  • User Information
  • Changing the User Password
  • Debug Serial Port
  • ADB
  • SSH
  • Common Issues
  • Power Supply Issues
  • MIPI Screen Display Issues
  • Debug Serial Port Usage Issues
  • Username and Password Errors
  • What is the Motherboard Command-Line Console?
  1. K1/K1B/K3/K8(RK356x-RK3588)
  2. en
  3. 02-Getting_Started_Guide

02-K1B-Quick_Start_Guide

Last updated 2 days ago

This guide aims to assist users in quickly getting started with the motherboard, covering topics such as powering on the board, connecting the display, using the debug serial port, ADB, and SSH connections.

Symbol Explanation

  • SDK$: Represents the source code path.

  • console$: Generally refers to the motherboard's command-line console.

  • ADB$: Android Debug Bridge command-line tool, generally refers to an environment where ADB can be run.

Powering on the Board

Currently, all series of boards are set to boot automatically upon power-on by default. The following introduces the power supply methods for each board and the signs indicating the normal startup of the board.

Power Supply

The K1B board operates at a supply voltage of 5V and supports two power supply methods: TYPE-C and expansion pins.

  • TYPE-C Port (Recommended)

image-20250417191511204
  • Expansion Pin Power Supply

In special cases where the TYPE-C port cannot supply power to the board, you can use the 1st 5V pin in the expansion pins, paired with the 6th GND pin for power supply.

With this power supply method, the maximum supply current is approximately 0.5A.

Connect an external 5V power supply to Pin 1 (VCC) and Pin 6 (GND) of the 20-pin expansion header.

LED Indicators

The development board is equipped with two LEDs:

The green LED serves as the power indicator, which remains lit by default when powered on. The blue LED acts as the system heartbeat indicator. If the heartbeat LED keeps blinking, it indicates that the kernel is running normally. Additionally, the system heartbeat LED can be controlled for other functions as described below.

Power-On Steps

  1. Plug in the DC12V power supply to board..

  2. checking the status of the two LEDs:

    • The power indicator should remain lit as soon as power is applied. If it does not light up, check the power supply section for any abnormalities.

    • The heartbeat LED should keep blinking after the kernel starts. If not, the system may be running abnormally.

Display

All display interfaces on the KICKPI development board are used with corresponding display adapter boards. The purchased displays will be shipped with the adapter boards already connected.

LVDS/MIPI

The K1B is default compatible with LVDS 7-inch screens, MIPI 5-inch, 8-inch, and 10.1-inch screens sold by KICKPI.

HDMI

The motherboard is equipped with an HDMI OUT display interface. The interface type is HDMI Type-A and supports hot-plugging.

User and Password

User Information

The default usernames and passwords for different systems are as follows:

System
Username
Password

Debian

linaro

linaro

Debian

root

Ubuntu

kickpi

kickpi

Ubuntu

root

The root password is not set and needs to be set manually.

Changing the User Password

console$ passwd $username

Example:

root@kickpi:/# passwd kickpi
New password:
Retype new password:
passwd: password updated successfully

Debug Serial Port

The debug serial port is a UART port on the motherboard, mainly used during the development and debugging phases to help developers understand the internal working status of the system. The debug serial port is sometimes also referred to as the console port or debug terminal.

Baud Rate: 1500000

The USB-to-UART cable connected to the socket also needs to support a baud rate of 1500000 for normal communication.

Debug Serial Cable Description

The currently provided debug serial cable has four wires. The red wire is VCC, the green wire is TX, the white wire is RX, and the black wire is GND. Generally, there is no need to connect VCC.

The same applies to other debug tool cables. Only connect TX, RX, and GND.

Viewing the DEBUG Pins

Each model of the motherboard is equipped with a DEBUG serial port, which is located among the 20-pin/40-pin headers. You can check the location of the DEBUG port in the Expansion Pins section of the hardware introduction for each model of the motherboard in the motherboard introduction. Additionally, the location is marked with silk screen on the front and back of the board.

Connecting the Debug Serial Port of the Development Board

Connect the TX of the debug cable to the RX of the motherboard, the RX of the debug cable to the TX of the motherboard, and the GND of the debug cable to the GND of the motherboard. There is no need to connect VCC.

Motherboard Expansion Pins
Debug Cable Pins

UART_RX_DEBUG

TX

UART_TX_DEBUG

RX

GND

GND

Downloading the Serial Assistant Software

There are many free/commercial serial assistant tools, no need to use a special one, you can choose the one you preferred. Here we use Mobaxterm as an example.

Mobaxterm software download address: https://mobaxterm.mobatek.net/

Mobaxterm Operation Steps

  1. Open Mobaxterm and click the "Session" button to create a new session window.

  2. In the session type list, select "Serial".

  3. Select the serial port COM index, which can be retrieved by checking the Windows Device Manager -> COM and LPT.

  4. Set the serial port baud rate to 1500000.

  5. Click "OK" to start the session window.

ADB

SSH

Common Issues

Power Supply Issues

When the motherboard is connected to multiple peripherals, resulting in high power consumption, after connecting the power supply, the power-on green light may be dim or not stay lit constantly, and the system startup may also encounter issues.

Solution: This is generally a power supply issue. Check whether the power supply can provide sufficient power to support the connected peripheral modules.

MIPI Screen Display Issues

If the MIPI screen fails to display, check the wiring and whether the backlight is lit properly.

Solution:

Debug Serial Port Usage Issues

When using Mobaxterm or other serial port tools to connect to the serial port, you may encounter issues such as garbled characters or being able to only view but not input data.

Solution: This is generally because the debug serial port tool does not support a baud rate of 1500000. It is recommended to use a debug serial port tool that supports a baud rate of 1500000.

Username and Password Errors

When logging in via ssh, the password may be incorrect.

Solution: Please confirm whether the relevant account exists and whether the password is correct. You can use the following command to change the user password:

console$ passwd $username

Example:

root@kickpi:/# passwd kickpi
New password:
Retype new password:
passwd: password updated successfully

What is the Motherboard Command-Line Console?

The command-line console, as referred to in this document, generally means an interface where users can interact with the computer system through text commands. Users execute operations (such as file management, program execution, system configuration, etc.) by entering specific instructions, rather than relying on graphical user interface (GUI) operations like mouse clicks.

Examples of command-line consoles:

For the Android system, you can use the serial port or adb shell to access the command-line console.

console$

For the Debian system, you can use the serial port, adb shell, ssh, etc., to access the command-line console.

root@linaro$

For the Ubuntu system, you can use the serial port, adb shell, ssh, etc., to access the command-line console.

kickpi@kickpi$
image-20250417191801337
image-20250421103741365

The K1B motherboard has display interfaces. You can check the number of interfaces and the types of default compatible displays in the section. You can connect display peripherals as needed.

LVDS/MIPI 0 Interface:

image-20250512140834526
image-20250512141342753
image-20241231145656021
image-20250422094320253
image-20250418175523261

The K1B Android/Debian system supports the use of ADB. For details, refer to the .

The K1B supports the use of SSH. For details, refer to .

If the backlight is not lit, check the wiring. If the backlight is lit, check the software. (K7 V1.2 does not support automatic MIPI screen recognition yet. Different screens require different software to be flashed.)

ADB Tutorial
SSH
MIPI_DSI Wiring
Motherboard Command-Line Console
Flip-down FPC Interface
K1B Hardware Introduction