HOME
  • GM-3568JHF
  • M4-R1
  • M5-R1
  • SC-3568HA
  • M-K1HSE
  • CF-NRS1
  • CF-CRA2
  • 1684XB-32T
  • 1684X-416T
  • C-3568BQ
  • C-3588LQ
  • GC-3568JBAF
  • C-K1BA
Shop
  • English
  • 简体中文
HOME
  • GM-3568JHF
  • M4-R1
  • M5-R1
  • SC-3568HA
  • M-K1HSE
  • CF-NRS1
  • CF-CRA2
  • 1684XB-32T
  • 1684X-416T
  • C-3568BQ
  • C-3588LQ
  • GC-3568JBAF
  • C-K1BA
Shop
  • English
  • 简体中文
  • GM-3568JHF

    • 1. Introduction

      • GM-3568JHF Introduction
    • 2. Quick Start

      • 01 Environment Construction
      • 02 Compilation Instructions
      • 03 Burning Guide
      • 04 Debugging Tools
      • 05 Software Update
      • 06 View information
      • 07 Test Command
      • 08 Application Compilation
      • 09 Source code acquisition
    • 3. Peripherals and Interfaces

      • USB
      • Display and touch
      • Ethernet
      • WIFI
      • Bluetooth
      • TF-Card
      • Audio
      • Serial Port
      • CAN
      • RTC
    • 4. Application Development

      • 01 UART read and write case
      • 02 Key detection case
      • 03 LED light flashing case
      • 04 MIPI screen detection case
      • 05 Read USB device information example
      • 06 FAN Detection Case
      • 07 FPGA FSPI Communication Case
      • 08 FPGA DMA read and write case
      • 09 GPS debugging case
      • 10 Ethernet Test Cases
      • 11 RS485 reading and writing examples
      • 12 FPGA IIC read and write examples
      • 13 PN532 NFC card reader case
      • 14 TF card reading and writing case
    • 5. QT Development

      • 01 ARM64 cross compiler environment construction
      • 02 QT program added automatic startup service
    • 6. Others

      • 01 Modification of the root directory file system
      • 02 System auto-start service

03 Burning Guide

1 Windows Burning Instructions

SDK provides Windows burning tool (tool version needs to be V3.31 or above), the tool is located in the project root directory:

tools/
├── windows/RKDevTool

As shown in the figure below, after compiling and generating the corresponding firmware, the device needs to enter the MASKROM or LOADER burning mode for burning. Prepare a USB cable with two male ends. After connecting the USB cable to the PC end, connect the other end to the USB-OTG port of the development board. Press and hold the "UBOOT" button and power on the development board to enter the burning mode. After loading the corresponding path of the compiled firmware, click "Execute" to burn. The following is the burning file in LOADER mode.

FIRMWARE_3

(Note: Windows PC needs to run the tool with administrator privileges to execute it)

FIRMWARE

Note: Before burning, you need to install the latest USB driver. For details, see:

<SDK>/tools/windows/DriverAssitant_v5.13.zip

2 Linux Burning Instructions

The flashing tool under Linux is located in the tools/linux directory (Linux_Upgrade_Tool tool version needs to be V2.36 or above). Please make sure your board is connected to MASKROM/loader rockusb. For example, the compiled firmware is in the rockdev directory, and the upgrade command is as follows:

sudo ./upgrade_tool ul rockdev/MiniLoaderAll.bin -noreset
sudo ./upgrade_tool di -p rockdev/parameter.txt
sudo ./upgrade_tool di -u rockdev/uboot.img
sudo ./upgrade_tool di -misc rockdev/misc.img
sudo ./upgrade_tool di -b rockdev/boot.img
sudo ./upgrade_tool di -recovery rockdev/recovery.img
sudo ./upgrade_tool di -oem rockdev/oem.img
sudo ./upgrade_tool di -rootfs rocdev/rootfs.img
sudo ./upgrade_tool di -userdata rockdev/userdata.img
sudo ./upgrade_tool rd

Or upgrade the complete firmware after packaging:

sudo ./upgrade_tool uf rockdev/update.img

Or in the root directory, the machine is in MASKROM state and runs the following upgrade:

./rkflash.sh

3 System Partition Description

Default partition description (below is the RK3568 EVB partition reference)

FIRMWARE_2
  • Uboot partition: for uboot.img compiled by uboot.
  • misc partition: for misc.img, used for recovery.
  • Boot partition: for boot.img compiled by kernel.
  • recovery partition: recovery.img compiled by recovery.
  • backup partition: reserved, not used for the time being.
  • rootfs partition: rootfs.img compiled by buildroot, debian or yocto.
  • OEM partition: used by manufacturers to store their apps or data. Mounted in the /oem directory.
  • Userdata partition: used by APP to temporarily generate files or for end users, mounted in the /userdata directory.
Edit this page on GitHub
Last Updated:
Contributors: zsl, zwhuang
Prev
02 Compilation Instructions
Next
04 Debugging Tools