12-Hardware function instructions
Last updated
Last updated
Development board expansion pin capabilities
Can be used to connect external devices (temperature sensors, humidity sensors, etc.)
Communicate with other boards or modules (I2C, SPI, UART, etc.)
Customize GPIO functions
See the pin list for specific function expansion details.
The list of pins is marked with the default configuration of each pin (marked with an *), and an optional configuration corresponding to that pin is given.
The development board is equipped with 2 LEDs, the green LED is the power indicator, and it is always on by default when powered on.
The blue LED is the system working heartbeat light. If the heartbeat light continues to flash, it indicates that the core is running normally.
In addition, the system working heartbeat light can refer to the following aspects to control LED as other functions.
User layer control LED status
Command line control LED status
The default LED trigger mode is heartbeat, and the LED state cannot be controlled by humans in this mode.
If you want to control the LED state by command, you can set it to none by the following command, and then set the brightness of the LED
Restore heartbeat mode
Multi-channel controllable GPIO is configured by default in the expansion pins of the development board.
First, through the [Expansion Pin] (#ExpansionPin) section, confirm the GPIO pin position and number, and refer to the following steps to control the state of the specified GPIO.
Default software extension pins configured as GPIO are generally registered for this mode of control
This method can control the pin output high or low
View GPIO registration list
Command Line Control GPIO
When there is a need to configure the extension pin as an input, the default software's GPIO-LED does not meet the requirement.
You need to modify the software and re-burn it. Details
View DEBUG pin
The Kickpi development board debugging serial port is generally embedded in the extension pin, and the corresponding DEBUG pin position can be viewed through the [Extension Pin] (#ExpansionPin) chapter, which is generally arranged in order as UART_RX_DEBUG, UART_TX_DEBUG, and GND.
Debugging serial cable instructions
The debugging serial cable currently provided has four wires, the red one is'VCC ', the green one is'TX', the white one is'RX ', and the black one is'GND'. Generally, it is not necessary to connect to'VCC '.
The same is true for other debugging Creative Tools, just connect TX RX GND
Development board debugging serial port wiring
Debugging serial port location wiring instructions
The debugging line "TX" is connected to "RX" on the main board, "RX" is connected to "TX" on the main board, and "GND" is connected to "GND" on the main board. There is no need to connect "VCC".
PIN on main board：RX TX GND
PIN of the debugging line：TX RX GND
Download Serial Port Assistant Software
Serial assistant software can be downloaded by yourself. The following is an example of Mobaxterm
Mobaxterm software address download: https://mobaxterm.mobatek.net/
Mobaxterm operation steps
Create a new session window
Select the session window type as serial
Select the COM number of the serial port (open the Windows System Facility Management - > Port interface to view the COM number)
Select the serial port baud rate 1500000
Start the session window
Confirm the string slogan used
Check if the corresponding node exists
Use microcom for communication testing
If the serial port 4 found node is /dev/ttyS4
-S Set baud rate to 115200
Android 13.0 system USB supports OTG mode by default, and can automatically switch leader/follower functions
Linux system USB defaults to HOST mode, does not support OTG for the time being
Android supports adb debugging (type-c interface to connect to the host)
The main commands of adb are as follows:
adb devices
Description: To view the currently connected devices, the devices connected to the computer or the emulator will be listed and displayed
adb start-server
Description: Start adb
Description: Close adb
Description: This command will log into the shell of the device, followed by the command to run the device directly, which is equivalent to executing a remote command
Description: This command can copy files from the computer to the development board -Example: adb push hello.c /tmp/This copies the hello.c file on the computer to the/tmp directory on the development board
Description: This command can copy the files on the development board to the computer
Example: adb pull /tmp/hello.c./Copy the file hello.c in the/tmp directory on the development board to the current directory
Description: Check the version of adb
Description: adb help, for more command details, please use the adb help command to view
RK3568 has 4 PWM modules, each PWM module has 4 channels of PWM, a total of 16 channels of PWM.
Extend 40Pin interface, including multi-channel PWM, take PWM3 channel as an example, enter the PWM configuration according to the following command
After the configuration parameters are successfully set according to the example, the PWM3 pin can be measured with a multimeter, and the correct voltage should be about 1.6V
Example: Set PWM3 channel, period 10000ns, duty cycle 5000ns, polarity is normal
The PWM path is/sys/class/pwm, and pwmchip* is sorted from 0 in your enable order. Set pwmchip0 as follows:
How to confirm the pwm corresponding to the pwmchip
fd8b0010.pwm For the node corresponding to dts
K1 development board with RTL8822CS high-performance WIFI module
Support 2.4G/5G dual band, WIFI5, 2T2R
Check if AP mode is supported
AP/VLAN can indicate hardware support
Note: After restarting the computer, the virtual network interface card created here will be invalid
Download the installation tool create_ap
Use create_ap to create hotspots
< wirelessname > is the name of your wireless network interface card, < virtualwlanname > virtual network interface card name, < SSID > < password > is the hotspot wifi name and password created respectively
for example
If the created hotspot gets stuck
You can stop the hotspot created before, and then restart the hotspot as follows.
< virtualwlanname > virtual network interface card name
The K1 development board is equipped with an RTL8822CS high-performance Bluetooth module.
K1 development board, equipped with a SATA3.0 hard disk interface
SATA hard disk wiring is divided into hard disk power supply interface and hard disk data interface
Special attention: The SATA hard disk power supply interface is a PH2.0 terminal, you need to buy another PH2.0 terminal to SATA power cord.
The power supply part contains 5V and 12V. You must confirm that the wiring sequence is correct before connecting to the hard disk, otherwise the hard disk will be burned out.
Keep the development board powered off, power on after connecting to the hard disk, Android/Linux will automatically mount the hard disk partition
Special attention: try to partition the hard disk in advance, and the partition format
K1 development board, equipped with one PCIE3.0 M.2 SSD hard disk interface
Android system, only supports'NTFS 'or'Fat32' format partitions
It is recommended to format the SSD in advance and create a partition that supports the format
If the SSD partition is not in a format supported by the system, you can also follow the system prompts to format the partition, and the default format is Fat32.
The M.2 interface supports the current mainstream 2280 specification hard disk and is equipped with fixed studs
Make sure that the development board is powered off, and power it on after connecting to the hard disk.
Test SSD Model: Samsung PM981 256G
Test results:
K1 Android13.0
243 MB/s
604 MB/s
K1 Debian11
If there are no special requirements, it is recommended to use Fat32 format partitions
The K1 development board is equipped with HYM8563 RTC chip, which can realize the function of saving time after power failure
To test the RTC function, an external button battery must be connected, and confirm that the battery is fully charged.
Power down save time test
Test steps:
The development board is connected to the network and automatically synchronizes the correct network time
Disconnect the network connection and disconnect the power supply of the development board.
After waiting for a few hours, reconnect the development board power supply.
If the system time is the same as the current time, the RTC function is normal
K1 development board, equipped with three LCD interfaces, namely two LVDS/MIPI interfaces (reusable) and one eDP interface
Three-way LCD interface supports three-screen display/touch
The default factory firmware is a multi-screen compatible image, which has been adapted to three screens
A firmware can be compatible with any LCD + HDMI output. If you need more than two LCD displays, you need to re-compilation mirroring.
**Cable requirements **
The number of pins is 30Pin, and the direction of the cable is the same direction.
It is recommended to use the cable that comes with the screen, otherwise it may cause damage to the screen.
Wiring example diagram
Note: Before plugging in or unplugging any FPC interface peripherals, ensure that the board is completely powered off
Cable requirements
The number of pins is 30Pin, and the direction of the cable is the same direction.
It is recommended to use the cable that comes with the screen, otherwise it may cause damage to the screen.
Wiring example diagram
Note: Before plugging in or unplugging any FPC interface peripherals, ensure that the board is completely powered off
KICKPI K3 supports one Dual LVDS screen, and uses CS5518 chip to realize MIPI to Dual LVDS function
PS: Dual LVDS screen, and MIPI/LVDS screen, multiplexed with each other, can only choose one of the two
**K3 Dual LVDS Interface Description **
LVDS power supply voltage can be selected from 3.3V, 5V, 12V. The corresponding voltage must be selected according to the specification, otherwise it will not light up or burn the screen.
**Cable requirements **
The number of pins is 30Pin, and the direction of the cable is the same direction.
It is recommended to use the cable that comes with the screen, otherwise it may cause damage to the screen.
**Wiring example diagram **
Note: Before plugging in or unplugging any FPC interface peripherals, ensure that the board is completely powered off
EDP screen, an additional 12V power supply must be connected at the screen end
The K1 development board supports a single MIPI CSI 4Lane camera interface, which can be connected to up to two cameras
The K3 development board supports dual MIPI CSI 4Lane camera interface, which can be connected to up to four cameras
**Cable requirements **
The number of pins is 40Pin, and the direction of the cable is reversed.
It is recommended to use the cable that comes with the screen, otherwise it may cause damage to the screen.
Before plugging in or unplugging any FPC interface peripherals, ensure that the board is completely powered off
Command line execution After starting the cheese program, directly display the camera image
Debian file system with built-in gst-launch-1.0 test script
Depending on the number of connected cameras, it will cause the/dev/video node number to be offset, so that the script cannot open the correct camera.
At this point, you can modify the script to specify the correct video number, device =/dev/video-camera0
K8 supports one HDMI input. The resolutions supported by EDID in the current driver code include:
Supported input formats include:
**GPU Usage Rate **
Move the mouse or window or run a GPU test to see if hard acceleration is working
RK Linux file system built-in glmark2-es performance testing tool
Connect the board to the display device, open the virtual end point or debug the serial end point, and execute the following command to start the GPU performance test
The external display can view the GPU rendering graphics (score about 49), and the debugging serial port can view the GPU rendering log (score about 203).
According to the GPU performance difference, it will take about 10 minutes to complete the performance test.
**K8 test results **
Access HDMI_OUT0, test result is 676
RK3568 is equipped with 0.8T computing power NPU unit
**Check NPU usage **
Open the virtual end point or debug the serial end point, and execute the following command to start the NPU function test
The content after "Begin perf..." shows the performance data of the model running multiple times:
The sequence number of each run is recorded, along with the corresponding elapse time ('Elapse Time') and frame number per second ('FPS'). For example, '0: Elapse Time = 2.85ms, FPS = 351.12' means that the first run of model inference took a total of 2.85 milliseconds, from which 351.12 frames per second can be processed (FPS is calculated by dividing 1000 by the time taken each time, and the unit is converted to get the frame number per second).
---- Top5 ----section presents the top 5 probability categories in the model inference output and their corresponding probability values and category numbers:
'0.935059 - 156' indicates that the model believes that the input data (such as an image) is most likely to belong to the category numbered 156, and its corresponding probability is as high as 0.935059. This probability value is relatively high, indicating that the model has a relatively high confidence level in this judgment. The following "0.057037-155", "0.003881-205", "0.003119-284", and "0.000172-285" list the category numbers and their probability values from the 2nd to the 5th, respectively. These probability values decrease in turn, indicating that the model's confidence in their belonging to the corresponding category judgment is also gradually decreasing.
**K8 NPU stress testing results **
Access HDMI_OUT0
From the print information, it can be seen that an average of 450 frames of data are processed per second
Detect data streams, available from cameras or video files
The test results are directly output to the display screen, so you need to connect the display screen to see the results.
Rockchip MPP provides mpi_enc_test, mpi_dec_test and other testing tools
MPI can be called directly from the command line for hardware codec testing
Encoding H.264 4096x2160 100 frames test
Encoding H.265 4096x2160 100 frames test
Parameter analysis:
mpi_enc_test MPP coding test tool
-W 4096 -h 2160 Specifies the encoded video resolution as 4096x2160
-T 16777220 Specifies the encoding type as H.265
-o./test.h265 Specify the encoded content output file
-N 100 Specify the frame number
Decode H.264 video 100 frames test
Decode H.265 video 100 frames test
**K8 codec test results **
Connect the board to the display device, open the virtual end point or debug the serial port end point, and execute the following command to start the chromium video test
RK3568 with 8-way ADC, K1 development board leads ADC3 channel to expansion pin holder
RK3568 is equipped with a guard dog all the way. The door dog is turned on by default when powered on, and the kernel thread automatically feeds the dog.
The following command can be modified to manually feed the dog at the user level, and the following command must be repeated every 44 seconds to feed the dog, otherwise the system will restart
The power supply voltage of the fan is 5V, and the connection method is shown in the figure below.
Currently compatible with Quecte EC20, Quecte EC200M-CN model modules
**alsa tool **
Linux system can generally control the sound card configuration and audio playback through the alsa tool. At present, Linux system software has built-in related tools.
If there are no relevant tools, you can execute the following command to install
After installation, aplay, arecord, amixer and other commands can be used
**Tool Instructions **
Use the command -h to view the instructions for the corresponding command
**List to view sound cards **
The speaker sound card is es8388, that is, the sound card 1.
**View sound card control configuration list **
**Get the specified configuration of the sound card **
**Set the specified configuration of the sound card **
**Speaker playback test **
amixer configuration for es8388 sound card
**Headphone playback test **
amixer configuration for es8388 sound card
**mic recording test **
amixer configuration for es8388 sound card
**Headset MIC recording test **
amixer configuration for es8388 sound card
Applicable platform: RK3568/RK3576/RK3588
The RK part of the chip supports the native CAN interface, which is usually led out to the expansion pin. For the specific location, please check the extension pin part.
The chip's native CAN interface cannot be used directly, and an external level switching circuit needs to be added.
**Query the current network device **
**CAN configuration **
Disable CAN
Set bit rate 500KHz
Print can0 information
Start CAN
**CAN FD send **
Sent (standard frame, dataframe, ID: 123, date: DEADBEEF):
Send (standard frame, remote frame, ID: 123)
**CAN receive **
Start printing and wait for receiving.
**Loop mode test **
After starting can, enter the io command to start the loop auto-test (the base address is configured according to the can started by the actual dts)
0xfea60000 DTS node for K8 CAN0
In loop mode, candump can be received after cansend.
**Example **
end point 1
Turn on the loop mode test and listen can
end point 2
Send command
**Tool Location **
**Compile **
Select the kernel CROSS_COMPILE
**Loop mode test **
Master as Master
MISO, MOSI for short connection
Example
Applicable platform: KICKPI-K8 RK3588 Android/Linux
At present, only RK3588 supports one 4Lane PCIE3.0 interface, and the theoretical transmission rate can reach 3.938GB/s.
Standard PCI-E expansion port can be connected to common PCIE USB expansion card, PCIE Ethernet expansion card, PCIE SSD expansion card on the market
PCIE to USB 3.0 Testing
Hardware wiring (PCIE X1 module)
software testing
Hardware wiring (PCIE X4 module)
Software testing
Applicable platforms: present on all major platforms
To be perfected
Android tests using the command getevent:
Linux test using evtest:
