|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
HiLoader User Guide
|
||
|
Issue |
10 |
|
|
Date |
2018-09-30 |
|
|
|
||
|
Copyright © HiSilicon (Shanghai) Technologies Co., Ltd. 2018. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of HiSilicon (Shanghai) Technologies Co., Ltd.
Trademarks and Permissions
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice The purchased products, services and features are stipulated by the contract made between HiSilicon and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. |
|
HiSilicon (Shanghai) Technologies Co., Ltd. |
|
|
Address: |
New R&D Center, 49 Wuhe Road, Bantian, Longgang District, Shenzhen 518129 P. R. China |
|
Website: |
|
|
Email: |
|
Purpose
This document describes how to use the loader package tool HiLoader.
Related Versions
The following table lists the product versions related to this document.
|
Product Name |
Version |
|
Hi3716M |
V4XX |
|
Hi3716M |
V31X |
|
Hi3716M |
V32X |
|
Hi3716M |
V33X |
|
Hi3796M |
V1XX |
|
Hi3798M |
V1XX |
|
Hi3110E |
V5XX |
|
Hi3798C |
V2XX |
|
Hi3798M |
V2XX |
|
Hi3796M |
V2XX |
|
Hi3798M |
V3XX(H) |
Intended Audience
This document is intended for:
l Technical support engineers
l Software R&D engineers
Change History
Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made in previous issues.
Issue 10 (2018-09-30)
This issue is the tenth official release, which incorporates the following changes:
Hi3716M V430, Hi3716M V450, and Hi3798M V300H are supported.
Issue 09 (2017-08-31)
This issue is the ninth official release, which incorporates the following changes:
Hi3798M V300 is supported.
Issue 08 (2017-06-01)
This issue is the eightth official release, which incorporates the following changes:
Step 4 of section 2.1, Step 4 of section 2.2.1, Step 3 of section 2.2.2 are modified.
Issue 07 (2017-03-14)
This issue is the seventh official release, which incorporates the following changes:
Step 1 of section 1.2 is modified.
Issue 06 (2017-02-13)
This issue is the sixth official release, which incorporates the following changes:
Hi3796M V200 is supported.
Section 1.1 is modified.
Section 1.2 is added.
Issue 05 (2016-11-04)
This issue is the fifth official release, which incorporates the following change:
Hi3798M V200 is supported.
Issue 04 (2015-04-30)
This issue is the fourth official release, which incorporates the following changes:
Hi3798C V200, Hi3716M V420, and Hi3716M V410 are supported.
Issue 03 (2015-03-10)
This issue is the third official release, which incorporates the following change:
Hi3110E V500 is supported.
Issue 02 (2015-01-15)
This issue is the second official release, which incorporates the following changes:
Chapter 2 GUI and Function Description
Sections 2.2.2 and 2.2.3 are added.
This issue is the first official release, which incorporates the following changes:
Hi3716M V310, Hi3796M V100, and Hi3798M V100 are supported.
Issue 00B01 (2013-12-16)
This issue is the first draft release.
1.1 Introduction to the HiLoader
2 GUI and Function Description
2.1 Packaging Images as an Upgrade File Complying with the HiSilicon Protocol
2.2 Packaging Images as an Upgrade File Complying with the SSU Protocol
2.2.1 Packaging Images as an Upgrade File Complying with the SSU Protocol (with Nothing Inserted)
2.2.2 Inserting Resource Linked Descriptors.
Figures
Figure 1-1 Main GUI of the HiLoader
Figure 2-1 HISI protocol packaging
Figure 2-3 Upgrade information
Figure 2-4 Generating the upgrade file
Figure 2-5 SSU protocol packaging
Figure 2-7 Upgrade information
Figure 2-8 Generating the upgrade file
Figure 2-9 Setting Transfer Mode to Cable
Figure 2-10 Setting Transfer Mode to Terrestrial
Figure 2-11 Generating the upgrade file
Figure 2-12 Configuring the file parameters
Figure 2-13 Generating the upgrade file
The HiLoader is a loader packaging tool provided by HiSilicon. It is used to package original images as an upgrade file complying with either of the following protocols:
l HiSilicon protocol (including the HISI OTA and HISI FILE protocols)
l System Software Updates (SSU) protocol
Before you use the HiLoader, do as follows:
Step 1 Copy HiTool-XXX-X.X.X.zip (in $SDK_DIR _HiTool\HiTool\windows) to a local hard disk drive on a PC that runs Windows 7 or Windows XP.
For HiTool-XXX-4.0.15 and later versions, JRE is integrated and therefore no installation is required.
For versions earlier than HiTool-XXX-4.0.15, preinstall 32-bit JRE 1.6 (such as jre-6u1-windows-i586-p); otherwise, the HiTool may fail to run properly. You can download JRE 1.6 from http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase6-419409.html.
Step 2 Decompress HiTool-XXX-X.X.X.zip, and double-click HiTool.exe.
Step 3 Select a chip (for example, Hi3798M V100), and click HiLoader, as shown in Figure 1-1.
Figure 1-1 Main GUI of the HiLoader

----End
Step 1 Start the HiLoader, select HISI on the main GUI, as shown in Figure 2-1.
Figure 2-1 HISI protocol packaging
Step 2
Click
in
the upgrade file option group to add a partition row. You can select the
component type, component CS (four CSs are supported), specify whether the file
system is required, select the file system type, and change the start address
of the partition, the partition size, and the partition image. You can also add
partition rows in batches by loading the configuration file. To delete a
partition row, click
. See
Figure 2-2.

l File name: name of the image corresponding to the partition
l Flash Type: type of the component where the partition is located. The value can be nand (corresponding to the NAND flash), spi (corresponding to the SPI flash), and emmc (corresponding to the eMMC flash).
l File System: file system of the partition. You can select none, yaffs, or ubi for the NAND/SPI flash, none or ext3/4 for the eMMC flash, and none for the boot and kernel partitions.
l Chip Select: ID of the chip to be selected among chips of the same type
l Start Address: start address of the partition in the component
l File Length: length of the partition
Step 3 Add other upgrade files by repeating step 2.
Step 4 Configure file parameters in the Upgrade Information area, as shown in Figure 2-3.
Figure 2-3 Upgrade information
l Download PID: upgrade stream PID, 16-bit width (0x20–0x1FFE)
l Download Table ID: table ID of the download sequence, 8-bit width (0x40–0xFF)
l Manufacturer ID: code of the manufacturer (0x0000–0xFFFF)
l Hardware Version: version of the hardware suited for the downloaded software, 32-bit width (0x00000000–0xFFFFFFFFF)
l Software Version: version of the downloaded software, 32-bit width (0x00000000–0xFFFFFFFF)
l Start sequence number: start SN of the STB whose software needs to be upgraded, 32-bit width (0x00000000–0xFFFFFFFF)
l End sequence number: end SN of the STB whose software needs to be upgraded, 32-bit width (0x00000000–0xFFFFFFFF)
Step 5 Click Browse in the target upgrade file generation area, specify the name and path for the upgrade file to be generated, and then click the corresponding package button.
The HiSilicon protocol supports the following package modes:
l TS package: Click TS Package to generate the upgrade file complying with the HISI OTA protocol.
l USB package: Click USB Package to generate the upgrade file complying with the HISI FILE protocol.
![]()
Only the HISI protocol supports the USB upgrade. The HiLoader uses the HISI protocol forcibly for the USB upgrade.
See Figure 2-4.
Figure 2-4 Generating the upgrade file

----End
Perform the following steps:
Step 1 Start the HiLoader, select SSU on the main GUI, as shown in Figure 2-5.
Figure 2-5 SSU protocol packaging

Step 2
Click
in
the upgrade file option group to add a partition row. You can select the
component type, component CS (only one CS is supported), specify whether the
file system is required, select the file system type, and change the start
address of the partition, the partition size, and the partition image. You can
also add partition rows in batches by loading the configuration file. To delete
a partition row, click
. See Figure 2-6.

l File name: name of the image corresponding to the partition
l Flash Type: type of the component where the partition is located. The value can be nand (corresponding to the NAND flash), spi (corresponding to the SPI flash), and emmc (corresponding to the eMMC flash).
l File System: file system of the partition. You can select none, yaffs, or ubi for the NAND/SPI flash, none or ext3/4 for the eMMC flash, and none for the boot and kernel partitions.
l Chip Select: ID of the chip to be selected among chips of the same type
l Start Address: start address of the partition in the component
l File Length: length of the partition
Step 3 Add other upgrade files by repeating step 2.
Step 4 Configure file parameters in the Upgrade Information area, as shown in Figure 2-7.
Figure 2-7 Upgrade information

l Download Group ID: code of the group, 16-bit width (0x20–0xFFFF)
l Download PID: upgrade stream PID, 16-bit width (0x20–0x1FFE)
l Manufacturer ID: code of the manufacturer (0x0000–0xFFFF)
l Hardware Version: version of the hardware suited for the downloaded software, 32-bit width (0x00000000–0xFFFFFFFFF)
l Software Version: version of the downloaded software, 32-bit width (0x00000000–0xFFFFFFFF)
l Start sequence number: start SN of the STB whose software needs to be upgraded, 32-bit width (0x00000000–0xFFFFFFFF)
l End sequence number: end SN of the STB whose software needs to be upgraded, 32-bit width (0x00000000–0xFFFFFFFF)
Step 5 Click Browse in the target upgrade file generation area, specify the name and path for the upgrade file to be generated, and then click TS Package to generate the upgrade file complying with the SSU protocol. See Figure 2-8.
Figure 2-8 Generating the upgrade file

----End
Perform the following steps:
Step 1 Perform steps 1 to 4 in section 2.2.1 "Packaging Images as an Upgrade File Complying with the SSU Protocol (with Nothing Inserted)."
Step 2 Select Insert Linked Descriptor.
Step 3 Select a transfer mode.
− Upgrade Type: Undefined, Forcible upgrade, or Non-forcible upgrade
− Symbol Rate: 1000−99999 KS/s
− Modulation: Undefined, 16 QAM, 32 QAM, 64 QAM, 128 QAM, or 256 QAM
− Frequency: 1−9999 MHz
Figure 2-9 Setting Transfer Mode to Cable

l If you select Terrestrial from the Transfer Mode drop-down list, configure the parameters in the Package Options pane shown in Figure 2-10.
− Bandwidth: 6 MHz, 7 MHz, or 8 MHz
− Center Frequency: 10 Hz (0x00000001)−42,949,672,950 Hz (0xFFFFFFFF) (32-bit width)
− Constellation: QPSK, 16-QAM, or 64-QAM
Figure 2-10 Setting Transfer Mode to Terrestrial

Step 4 Click Browse in the target upgrade file generation area, specify the name and path for the upgrade file to be generated, and then click TS Package to generate the upgrade file complying with the SSU protocol. See Figure 2-11.
Figure 2-11 Generating the upgrade file

----End
Perform the following steps:
Step 1 Perform steps 1 to 4 in section 2.2.1 "Packaging Images as an Upgrade File Complying with the SSU Protocol (with Nothing Inserted)."
Step 2 Configure the file parameters in the Package Options pane, as shown in Figure 2-12.
Figure 2-12 Configuring the file parameters

l Symbol Rate: 1000−99999 KS/s, 28-bit width
l Valid Symbol Rate: 1000−99999 KS/s, 28-bit width
Step 3 Click Browse in the target upgrade file generation area, specify the name and path for the upgrade file to be generated, and then click TS Package to generate the upgrade file complying with the SSU protocol. See Figure 2-13.
Figure 2-13 Generating the upgrade file

![]()
If the network packet loss rate is high, inserting empty packets reduces the loss of valid data.
----End
Note the following when you use the HiLoader:
l When adding a partition, note that:
− The unit K or M (not case-sensitive) must be attached when the partition length is entered.
− The entered partition length must be greater than the length of the selected file.
− The addresses occupied by partitions cannot overlap.
l If an error occurs when you use the HiLoader, save the screenshot that shows the symptom, and deliver the screenshot along with the issue to facilitate problem location.
l Wait patiently during the TS packaging process. Packaging TSs may take a long time because there are many partitions or the partition files are large.
l If the partition file exceeds a specific size (490 MB in the HISI protocol and 250 MB in the SSU protocol), the tool automatically divides the partition into small partition files. This is because certain field length is limited in the protocol.
l For the eMMC EXT4 file system, the tool supports files in the sparse or non-sparse formats, and it identifies the format automatically based on the file header.
l If the HISI protocol is used, you can view the NAND CS in the displayed information during boot. For example, Nand (Hardware):
− Block: 128 KB
− Page: 2 KB
− OOB: 64 B
− ECC: 4 bits
− Chip: 128 MB*1
|
E |
|
|
|
eMMC |
embedded multimedia card |
The standard specifications of an embedded memory include an MMC interface, a flash memory, and a master controller, all in a small ball grid array (BGA) package. The eMMC is fast and upgradable. |
|
|
|
|
|
H |
|
|
|
HISI OTA |
|
A protocol defined by HiSilicon. This protocol applies to OTA upgrade. |
|
HISI FILE |
|
A protocol defined by HiSilicon. This protocol is also called USB/IP protocol and applies to USB and IP upgrade. |
|
|
|
|
|
N |
|
|
|
NAND |
|
The NAND flash is a better storage solution than the hard disk drive. |
|
|
|
|
|
S |
|
|
|
SPI |
serial peripheral interface |
Synchronous serial communication mode |
|
system software updates |
||
|
|
|
|