Upgrade instructions

LQ3328 has a flexible starting method. Under normal circumstances, unless the hardware is damaged, the LQ3328 development board will not be bricked.

If an accident occurs during the upgrade process and the bootloader is damaged, making it impossible to upgrade again, you can still enter the MaskRom mode to repair it.

Loading method

LQ3328 has 20KB BootRom and 36KB internal SRAM, and supports loading the system from the following devices:

SPI interface

eMMC interface

SDMMC interface

LQ3328 downloads the system code from the Type-C interface.

Start sequence

The startup sequence is as follows:

Main control power-on initialization

The BootRom code runs on SRAM to verify the bootloader in the storage device

After the verification is passed, load and run the bootloader boot code

The bootloader boot code is responsible for initializing the DDR memory, loading the complete bootloader code into the DDR memory and running

The bootloader loads the Linux kernel on the storage device and gives the execution rights to the Linux kernel

Start mode

LQ3328 has three startup modes:

Normal mode

Loader mode

MaskRom mode

Normal mode

Normal mode is the normal startup process. Each component is loaded in turn and enters the system normally.

Loader mode

In Loader mode, the bootloader will enter the upgrade state, waiting for host commands for firmware upgrades, etc. To enter the Loader mode, the bootloader must detect that the RECOVERY button is pressed during startup and the USB is connected. There are two ways to make the device enter the upgrade mode:

One way is to disconnect the power adapter

The Type-C cable connects the device and the host.

Press and hold the RECOVERY button on the device.

Plug in

After about two seconds, release the RECOVERY button.

Another way is to connect the power adapter

The Type-C data cable connects the device and the host.

Press and hold the RECOVERY button on the device.

Briefly press the RESET button.

After about two seconds, release the RECOVERY button.

MaskRom mode

MaskRom mode is used to repair the system when the bootloader is damaged.

Generally, it is not necessary to enter the MaskRom mode. Only when the bootloader verification fails (the IDR block cannot be read, or the bootloader is damaged), the BootRom code will enter the MaskRom mode. At this time, the BootRom code waits for the host to transmit the bootloader code through the USB interface, load and run it.

Detailed description of software upgrade

This article introduces how to burn the firmware file on the host into the flash memory of the development board through the Type-C data cable. When upgrading, you need to select an appropriate upgrade method according to the host operating system and firmware type.

Ready to work

Equipment and environment

AIO-RK3328-JD4 development board

firmware

Host

Good Type-C data cable

Note: There are generally two types of firmware files:

A single unified firmware update.img packs the boot loader, parameters and all partition images together for firmware release.

Multiple partition images, Linux system has uboot.img, boot.img, rootfs.img; Android system has kernel.img.system.img, etc., which are all generated during the development phase

Note: The host operating system supports:

Firmware download

Firmware download page

Burning tool download

Under Windows: AndroidTool_v2.58

Under Linux: Upgrade_Tool_v1.34

Windows upgrade

After downloading the AndroidTool tool, unzip it and run the AndroidTool.exe inside (note that if it is Windows 7/8, you need to press the right mouse button and choose to run as administrator)

Burn unified firmware update.img

The steps to flash the unified firmware update.img are as follows:

Switch to the 'Upgrade Firmware' page.

Press the 'Firmware' button to open the firmware file to be upgraded. The upgrade tool will display detailed firmware information.

Press the 'Upgrade' button to start the upgrade.

Linux upgrade

There is no need to install the device driver under Linux, just refer to the Windows chapter to connect the device.

After downloading the Linux tool Upgrade_Tool, install it to the system as follows for easy calling:

unzip Linux_Upgrade_Tool_xxxx.zipcd Linux_UpgradeTool_xxxxsudo mv upgrade_tool /usr/local/binsudo chown root:root /usr/local/bin/upgrade_toolsudo chmod a+x /usr/local/bin/upgrade_tool

sudo upgrade_tool uf update.img

# Erase flash Use the ef parameter to specify the loader file or the corresponding update.img sudo upgrade_tool ef update.img # Re-program sudo upgrade_tool uf update.img 

sudo upgrade_tool ul bootloader.bin # Burn bootloadersudo upgrade_tool di -p paramater   #Burn parametersudo upgrade_tool di -uboot /path/to/uboot.imgsudo upgrade_tool di -trust /path/to/trust.imgsudo upgrade_tool di -m /path/to/misc.imgsudo upgrade_tool di -baseparameter /path/to/baseparameter.imgsudo upgrade_tool di -b /path/to/boot.imgsudo upgrade_tool di -k /path/to/kernel.imgsudo upgrade_tool di -resource /path/to/resource.imgsudo upgrade_tool di -r /path/to/recovery.imgsudo upgrade_tool di -s /path/to/system.imgsudo upgrade_tool di -vendor /path/to/vendor.imgsudo upgrade_tool di -oem /path/to/oem.img

sudo upgrade_tool ul $LOADER
sudo upgrade_tool di -p $PARAMETER
sudo upgrade_tool di -uboot $UBOOT
sudo upgrade_tool di -trust $TRUST
sudo upgrade_tool di -b $BOOT
sudo upgrade_tool di -r $RECOVERY
sudo upgrade_tool di -m $MISC
sudo upgrade_tool di -oem $OEM
sudo upgrade_tool di -userdata $USERDATA
sudo upgrade_tool di -rootfs $ROOTFS

sudo upgrade_tool lf update.img # low-level format sudo upgrade_tool ef update.img # erase