|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
HiBurn User Guide
|
||
Issue |
07 |
|
Date |
2015-03-10 |
|
|
||
Copyright © HiSilicon Technologies Co., Ltd. 2015. 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 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 Technologies Co., Ltd. |
|
Address: |
Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China |
Website: |
|
Email: |
Purpose
This document describes how to use the HiBurn. By using the HiBurn, you can burn all program images to the flash memory of a board in one-click mode, burn images to the flash memory of a board with boot by the flash address, or burn only the boot image to the flash memory of a board.
Related Versions
The following table lists the product versions related to this document.
Product Name |
Version |
Hi3798M |
V1XX |
Hi3796M |
V1XX |
Hi3798C |
V1XX |
Hi3798C |
V2XX |
Hi3796C |
V1XX |
Hi3716C |
V1XX |
Hi3716M |
V1XX |
Hi3716C |
V2XX |
Hi3719C |
V1XX |
Hi3718C |
V1XX |
Hi3719M |
V1XX |
Hi3718M |
V1XX |
Hi3716M |
V4XX |
Hi3716M |
V31X |
Hi3716M |
V32X |
Hi3798C |
V1XX |
Hi3712 |
V1XX |
Hi3110E |
V2XX |
Hi3110E |
V4XX |
Hi3110E |
V5XX |
Hi3110E |
V3XX (CA) |
Hi3716C |
V11X (CA) |
Hi3716M |
V2XX (CA) |
Hi3716M |
V3XX (CA) |
Hi3716C |
V2XX (CA) |
Hi3719M |
V100 (CA) |
Hi3521 |
V1XX |
Hi3531 |
V1XX |
Hi3520D |
V1XX |
Hi3535 |
V1XX |
Hi3536 |
V1XX |
Hi3521A |
V1XX |
Hi3751 |
V8XX |
Hi3751 |
V6XX |
V5XX |
Intended Audience
This document is intended for:
l Technical support engineers
l Hardware development engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol |
Description |
|
Alerts you to a high risk hazard that could, if not avoided, result in serious injury or death. |
|
Alerts you to a medium or low risk hazard that could, if not avoided, result in moderate or minor injury. |
|
Alerts you to a potentially hazardous situation that could, if not avoided, result in equipment damage, data loss, performance deterioration, or unanticipated results. |
|
Provides a tip that may help you solve a problem or save time. |
|
Provides additional information to emphasize or supplement important points in the main text. |
Change History
Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made in previous issues.
Issue 07 (2015-03-10)
This issue is the seventh official release, which incorporates the following changes:
Hi3716M V320 and Hi3110E V500 are supported.
Section 10.19 is added.
Issue 06 (2014-12-31)
This issue is the six official release, which incorporates the following change:
The Hi3536 and Hi3521A series are supported.
Issue 05 (2014-11-06)
This issue is the fifth official release, which incorporates the following change:
The Hi3751 series are supported.
Issue 04 (2014-10-31)
This issue is the fourth official release, which incorporates the following changes:
Hi3796M V100 is supported.
Issue 03 (2014-09-19)
This issue is the third official release, which incorporates the following changes:
Hi3716M V310 is supported.
Issue 02 (2014-09-05)
This issue is the second official release, which incorporates the following changes:
Chapters 6 and 8 and section 9.4 are added.
Issue 01 (2014-05-20)
This issue is the first official release, which incorporates the following changes:
Chapter 8 FAQs
Sections 8.1 to 8.6, sections 8.11 to 8.13, and sections 8.15 to 8.18 are added.
This issue is the first draft release.
Contents
1.1 Introduction to the HiBurn
1.2 Supported Components and Functions
2.3 Creating Images for the NAND Burner
2.4 Creating Images for the HiPro
2.5 Redirecting to the Burn by Address Page
3 Burning Images by the Flash Address
5.3 Creating Images for the Burner
5.5 Creating Images for the HiPro
6 Burning Images to the Advanced CA Boards
9.3 Setting Invalid Data to Be Filled into Images
9.4.1 Setting the HiBurn-Debug Console
9.4.3 Automatically Updating mtdparts/blkdevparts in the Bootargs Partition
10.1 What Do I Do If the TFTP Timeout Error Occurs?
10.2 How Do I Download Images by Using the External tftpd32?
10.7 What Are the Advantages and Disadvantages of File Transmission over the Serial Port?
10.8 What Are the Requirements on the File Length On the Burnt by Address Page?
10.12 What Should I Pay Attention to When Images Are Burnt to the eMMC?
10.15 What Should I Pay Attention to When Creating the Image to Be Burnt by Using the eMMC Burner?
10.17 What Does the HiBurn Display When the DDR Training Fails?
10.18 What Information Should I Provide When Submitting Feedback on the HiBurn?
10.19 How Do I Check Whether Port 69 of the TFTP Is Occupied?
Figures
Figure 1-1 Bootstrap jumper cap for the Hi3716M board
Figure 1-2 Bootstrap jumper cap for the Hi3716C/Hi3716H board
Figure 2-1 Starting the HiTool
Figure 2-2 Selecting the chip model
Figure 2-4 Clicking Burn by Partition
Figure 2-6 Configuring partition information
Figure 2-7 Modifying partition information
Figure 2-8 Asking you whether to save the partition information
Figure 2-10 Setting Length to -
Figure 2-13 Creating images for the NAND burner
Figure 2-14 Selecting the HiPro image type
Figure 2-15 Creating images for the HiPro
Figure 2-17 Redirecting to the Burn by Address tab page
Figure 3-1 Clicking Burn by Address
Figure 3-6 Selecting the data type
Figure 4-1 Clicking Burn Fastboot
Figure 4-2 Selecting a serial port
Figure 4-3 Setting the boot burning information
Figure 5-1 Burning images to the eMMC
Figure 5-2 Setting the partition information about the board
Figure 5-3 Modifying the partition information
Figure 5-4 Asking you whether to save the partition information
Figure 5-8 Creating an image for the burner
Figure 5-10 Selecting HiPro image type
Figure 5-11 Creating images for the HiPro
Figure 6-1 Burning images to the advanced CA boards
Figure 7-2 Detecting bad blocks
Figure 7-3 Information about bad blocks
Figure 8-1 Merge Image tab page
Figure 8-2 Loading the partition table
Figure 9-3 Setting invalid data to be filled into images
Figure 9-4 Selecting Open Debug Mode
Figure 9-5 Switching to the HiBurn-Debug console
Figure 9-7 Automatically updating the bootargs partition parameter
Figure 10-1 TFTP timeout error
Figure 10-2 Checking the network configuration
Figure 10-3 Modifying TFTP parameters
Figure 10-4 Configuring the tftpd32
Figure 10-5 Information indicating TFTP startup failure
Figure 10-6 Downloading images by using the tftpd32
Figure 10-7 "Failed to send start frame" error
Figure 10-8 Checking the serial port ID
Figure 10-9 "Failed to send head frame" error
Figure 10-10 Checking the chip model over the serial port
Figure 10-11 "Failed to send data frame" error
Figure 10-12 "Failed to execute command" error
Figure 10-13 Checking Boot Media
Figure 10-14 Length of burnt data displayed in the console
Figure 10-15 Changing the mmc write command execution speed
Figure 10-16 Entering the length of the component
Figure 10-17 Information displayed in the console when the partition image is a sparse image
Figure 10-19 Setting the stuffed value of invalid data
Figure 10-20 DDR training failure information
Figure 10-21 Checking whether the port is occupied by a process
Figure 10-22 Checking the name of a process with a specific PID
The HiBurn is mainly used to burn and upload images and create burner images.
The functions and components supported by the HiBurn vary according to the chip. For details, see Table 1-1.
Table 1-1 Components and functions supported by the HiBurn based on the chip model
Chip Model |
Flash Type |
File System |
Advanced Function |
||||||
SPI |
NAND |
eMMC |
Yaffs |
SquashFS |
UBI |
EXT3/4 |
CA |
Bad Block Check |
|
Hi3521 Hi3531 Hi3520D Hi3535 |
● |
● |
○ |
● |
○ |
○ |
○ |
○ |
○ |
Hi3712 |
● |
● |
○ |
● |
○ |
● |
○ |
○ |
○ |
Hi3110E V200 Hi3110E V400 |
● |
○ |
○ |
○ |
● |
● |
○ |
○ |
○ |
Hi3798M Hi3798C Hi3796C Hi3716C Hi3716H Hi3798C Hi3751V Hi3716M V100 Hi3716M V200 Hi3716M V300 Hi3716M V400 Hi3716C V200 Hi3718C V100 Hi3719C V100 Hi3719M V100 Hi3719M V100_A |
● |
● |
● |
● |
○ |
● |
● |
○ |
● |
Hi3110E V300 (CA) |
● |
○ |
○ |
● |
○ |
● |
○ |
● |
○ |
Hi3716C V110 (CA) Hi3716M V200 (CA) Hi3716M V300 (CA) Hi3716C V200 (CA) Hi3719M V100 (CA) Hi3719C V100 (CA) |
● |
● |
● |
● |
○ |
● |
● |
● |
○ |
S40 V100 |
● |
● |
○ |
○ |
● |
○ |
○ |
○ |
○ |
Note that ● indicates supported and ○ indicates not supported.
Connect the serial port, Ethernet port, and bootstrap jumper cap of the board. See Figure 1-1 and Figure 1-2. For some chips, the bootstrap jumper cap does not need to be connected, such as the Hi3521, Hi3531, Hi3520D, and Hi3535.
Figure 1-1 Bootstrap jumper cap for the Hi3716M board
Figure 1-2 Bootstrap jumper cap for the Hi3716C/Hi3716H board
The function of burning images by partition applies to all boards. No matter whether boot exists on the board, images can be burnt by partition.
To burn images by partition, perform the following steps:
Step 1 Double click HiTool.exe to start the HiTool, as shown in Figure 2-1.
Figure 2-1 Starting the HiTool
Step 2 Select the model of the chip on the board in the displayed Chip Selection dialog box, as shown in Figure 2-2.
Figure 2-2 Selecting the chip model
Step 3 Click HiBurn in the Welcome To HiTool UI, as shown in Figure 2-3.
Step 4 Click the Burn by Partition tab, as shown in Figure 2-4.
Figure 2-4 Clicking Burn by Partition
Step 5 Select a serial port for connecting the board, select the IP address of the PC, and set the MAC address, IP address, subnet mask, and gateway of the board. See Figure 2-5.
The IP addresses of the PC and the board must be on the same network segment. Otherwise, images cannot be burnt.
l When the HiBurn is started for the first time, it automatically generates default parameters. If the parameter configuration is changed, the HiBurn automatically records the modified parameter values, saves the values when it is exited normally, and uses the saved parameter values during the next startup. However, if the HiBurn is exited abnormally, the modified parameters may not be saved. In this case, the latest modifications are invalid.
l Clicking the Save button saves the current network configurations for the board; clicking the Load button allows you to select a group of saved configurations as the current configuration.
l If Use XML's parent path as default is selected, the HiBurn searches for the partition image in the directory where the .xml partition table file locates in priority. Otherwise, the HiBurn searches for the partition image in the absolute path specified in the .xml partition table in priority. If no image is found in the absolute path, the HiBurn then searches for the image in the directory where the .xml file locates.
Step 6 Click Browse to select a partition table to load it to the HiBurn, as shown in Figure 2-6.
Figure 2-6 Configuring partition information
l The partition information here is used only for burning images. The allocation of actual partitions of the board depends on the bootargs parameter of the board. The partition information here must be consistent with that specified by the bootargs parameter. Otherwise, errors may occur.
l The HiBurn allows the paths of partitions to be different, and it can burn remote images.
l If a partition is selected but no image is burnt, the HiBurn erases the partition.
l If you need to package all partition files as an image for burning, the image must contain fastboot and must be loaded to the fastboot partition for burning. (For the NAND flash, if the file system has the read and write properties, the partition files cannot be packaged together.) This burning method is not recommended because the fastboot partition is burnt over the serial port and the burning speed is slow.
Figure 2-7 Modifying partition information
To add a partition row, click .
After clicking each partition row, you can rename the partition, select the
flash memory type, select the file system type, and change the start address of
the partition and partition size.
The start address of a partition and partition size are in the unit of KB or MB and must be an integral multiple of the flash memory size. Otherwise, an error may occur.
l
To select or change the file to be burnt to a
partition, click .
l
To delete a partition, click .
The fastboot partition cannot be deleted and its name cannot be changed. Otherwise, images cannot be burnt in one-click mode.
l
To select all partitions to be burnt in
one-click mode, click ; to deselect all partitions,
click
again. To select a
specific partition, select the corresponding check box
.
l To save the edited partition table as a file, click Save.
There is no .xml partition information file when the HiBurn is started for the first time. When you close the HiBurn after setting or modifying the partition information, a dialog box shown in Figure 2-8 is displayed, asking you whether to save the partition information. Click OK. The Save As dialog box shown in Figure 2-9 is displayed. Select a save path, enter a file name, and click Save. An .xml partition information file is generated. If you click Cancel, the information is not saved and the HiBurn is not exited.
After the partition table is created, the dialog box shown in Figure 2-8 is displayed when you switch the chip. Click OK. Select a save path, enter a file name, and click Save in the displayed Save As dialog box. The partition information is saved as an .xml file. If you click Cancel, the chip is switched but the partition information is not saved. The file must be in .xml format. Otherwise, the partition information cannot be loaded during next startup.
Figure 2-8 Asking you whether to save the partition information
Select the last row, and click . A new last row is generated.
Enter - in the Length column, and specify the partition
name, file system, and file path. The length of this partition can be
calculated during burning, which is the available space of the component. See Figure 2-10.
Figure 2-10 Setting Length to -
If you do not select the current last partition row when creating a partition row, the created partition may not be the last partition, and you cannot set Length to - in this case.
Step 7 Prepare the board environment. Connect the serial port and Ethernet port of the board. If the board is powered on, power it off and short-circuit the bootstrap jumper cap of the board. For details, see section 1.3 "Environment Preparation."
Step 8 Click Burn to start to burn files, see Figure 2-11.
Step 9 Power on the board to burn the files. Figure 2-12 shows the burning process.
The information about the burning process is displayed in the Console. If an error occurs:
l Check whether the correct serial port is selected.
l Check whether the IP address is correct and whether it is occupied.
l Check whether the bootstrap jumper on the board is short-circuited.
Step 10 Connect the terminal tool and restart the board.
----End
The HiBurn allows you to create images for the NAND burner. After the partition information is configured, click Make Nand Programmer Image. The dialog box shown in Figure 2-13 is displayed.
Figure 2-13 Creating images for the NAND burner
Specify the parameters in the dialog box, and click Make to generate images for the NAND burner. Note that the Randomization can be selected if the page size of the NAND flash is 8 KB or larger.
l The specified parameter values must be consistent with those in the boot information of the board (you can view the boot information by using HyperTerminal).
l For the image of the non-Yaffs partition, File System in the partition table cannot be set to yaffs. For the image of the Yaffs partition, File System in the partition table must be set to yaffs. Otherwise, the created image is incorrect.
The HiBurn also allows you to create images for the HiPro. However, this function is not supported for the Hi3521, Hi3531, Hi3520D, and Hi3535.
After the partition table is configured, click Create HiPro image, and select the type of images to be created (HiPro-Serial or HiPro-Usb), as shown in Figure 2-14.
Figure 2-14 Selecting the HiPro image type
Specify the file path in the displayed dialog box. Then images for the HiPro can be created. See Figure 2-15.
Figure 2-15 Creating images for the HiPro
If a partition is not selected, or the file to be burnt for a selected partition is not specified, the partition image is not created.
The Burn by Partition tab page allows
you to redirect the information of a partition (including the partition name,
file system, file path, start address, and partition length) to the Burn by Address tab page. After
redirection, the information is directly loaded on the Burn by Address tab page. You only need
to select a row in the partition table on the Burn
by Partition tab page and click . Then
the Burn by Address page
is displayed. See Figure 2-16
and Figure 2-17.
Figure 2-17 Redirecting to the Burn by Address tab page
To burn images by address, perform the following steps:
Step 1 Click the Burn by Address tab, as shown in Figure 3-1.
Figure 3-1 Clicking Burn by Address
Step 2 Set the flash memory type, set the start address and length of the file to be burnt, and click Browse to select the file to be burnt, as shown in Figure 3-2.
Step 3 Prepare the board environment. Connect the serial port and Ethernet port of the board. If the board is powered on, power it off and short-circuit the bootstrap jumper cap of the board. For details, see section 1.3 "Environment Preparation."
Step 4 Click Burn to start to burn the images, as shown in Figure 3-3.
When images are burnt by address, you need to select only the files to be burnt but not the file system type. The format of the Yaffs file (with OOB data) is different from that of other files (with no OOB data). The HiBurn automatically distinguishes the file type (yaffs or none) at the background based on the selected file and burns the file based on the type. When images are burnt by address, you need to power on the board again only when the Burn button is clicked for the first time.
Step 5 Power on the board to burn the files. Figure 3-4 shows the burning process.
The information about the burning process is displayed in the Console. If an error occurs:
l Check whether the correct serial port is selected.
l Check whether the IP address is correct and whether it is occupied.
l Check whether the bootstrap jumper on the board is short-circuited.
The process of the erase operation is similar to that of the burn operation.
Step 6 Connect the terminal tool and restart the board.
----End
Step 1 Click the Burn by Address tab.
Step 2 Set the flash memory type, set the start address and length for the data to be uploaded, and click Browse to select the file that is used to store the uploaded data. See Figure 3-5.
Step 3 Prepare the board environment. Connect the serial port and Ethernet port of the board. If the board is powered on, power it off and short-circuit the bootstrap jumper cap of the board. For details, see section 1.3 "Environment Preparation."
Step 4 Click Upload. If images to be uploaded are fastboot, kernel, and ubifs images, select Data without OOB. If the images are yaffs files, select Data with OOB. See Figure 3-6.
Figure 3-6 Selecting the data type
If data is uploaded by address, specify the type of the data to be uploaded in the dialog box that is displayed after you click Upload. If you select an incorrect data type, the uploaded data is inconsistent with the original file. If a Yaffs file system image is to be uploaded, the length must be an integral multiple of (page size + OOB size).
----End
The erase function allows you to erase data of specific length from the specific start address from the board. The erasing process is similar to the burning process.
Step 1 Click the Burn by Address tab.
Step 2 Set the flash memory type, set the start address and length for the data to be erased in the flash memory. See Figure 3-7.
Step 3 Prepare the board environment. Connect the serial port and Ethernet port of the board. If the board is powered on, power it off and short-circuit the bootstrap jumper cap of the board. For details, see section 1.3 "Environment Preparation."
Step 4 Click Erase and power on the board. See Figure 3-8.
The length of data to be erased must be an integral multiple of the block size.
----End
There is no fastboot program running on the board and all images can be burnt by address.
To burn the fastboot, perform the following steps:
Step 1 Click the Burn Fastboot tab, as shown in Figure 4-1.
Figure 4-1 Clicking Burn Fastboot
Step 2 Select a serial port for connecting to the board, as shown in Figure 4-2.
Figure 4-2 Selecting a serial port
Step 3 Select the flash memory type and the fastboot image, as shown in Figure 4-3.
Figure 4-3 Setting the boot burning information
Step 4 Prepare the board environment. If the board is powered on, short-circuit the jumper, and power off the board; if the board is not powered on, short-circuit the board jumper. For details about the jumper position, see section 1.3 "Environment Preparation."
Step 5 Click Burn to start to burn the fastboot, as shown in Figure 4-4.
Step 6 Power on the board to burn the fastboot. Figure 4-5 shows the burning process.
The information about the burning process is displayed in the Console. If an error occurs, do as follows:
l Check whether the correct serial port is selected.
l Check whether the bootstrap jumper on the board is short-circuited.
Step 7 Connect the terminal tool and restart the board.
----End
This burning mode applies only to the embedded multimedia card (eMMC). No matter whether the fastboot program exists on a board, all images can be burnt in one-click mode.
However, this function is not supported for the following chips: Hi3521, Hi3531, Hi3520D, Hi3535, Hi3712, Hi3110E V200, Hi3110E V400, Hi3110E V300 (CA), and S40 V100.
To burn images to the eMMC, perform the following steps:
Step 1 Click the Burn eMMC tab, as shown in Figure 5-1.
Figure 5-1 Burning images to the eMMC
l If Use XML's parent path as default is selected, the HiBurn searches for the partition image in the directory where the .xml partition table file locates in priority. Otherwise, the HiBurn searches for the partition image in the absolute path specified in the partition table in priority. If no file is found in the absolute path, the HiBurn then searches for the file in the directory where the .xml file locates. This option is selected by default.
l If Create eMMC Partition Table is selected, an eMMC partition table is created for the EXT3/4 file system partition. This option is selected by default. This option is available for only the Hi3716, Hi3716_CA series chips (except Hi3716C V200, Hi3716C V200_CA, and Hi3716C V200ES), Hi3712, and Hi3712_CA series chips.
Step 2 Click Browse to select a partition table to load it to the HiBurn, as shown in Figure 5-2.
Figure 5-2 Setting the partition information about the board
l If the images of all partitions are packaged as an image file, the image file must be placed in the fastboot partition and must contain the fastboot. In this case, the image file is burnt over a serial port, which takes a long time. Note that because a partition table must be created for the eMMC file system partition, the images of other file system partitions cannot be packaged. There is no such issue for the Android version.
l As the eMMC uses the DOS partition format, the kernel can identify the EXT3/4 file system partition only when a partition table is created for the EXT3/4 file system partition.
l If the partitions of the eMMC change, you must select Create eMMC partition table to create an eMMC partition table again. Otherwise, the kernel cannot identify the EXT3/4 partition.
To modify the information about a partition, modify the .xml partition information file or click the corresponding partition row in the HiBurn, as shown in Figure 5-3.
Figure 5-3 Modifying the partition information
The start position of a partition and partition size are in the unit of KB or MB and must be an integral multiple of the eMMC sector size. Otherwise, an error may occur.
l
To add a partition row, click . After
clicking a partition row, you can rename the partition, select the required
file system, select the file system type, and change the start position of the
partition and partition size.
l
To select the file to be burnt to a partition,
click .
l
To delete a partition, click . Note
that the fastboot partition cannot be deleted and its name cannot be changed.
Otherwise, one-click burning cannot be implemented.
l
To select all partitions to be burnt in
one-click mode, click ; to deselect all partitions,
click
again. To select a
specific partition, select the corresponding check box
.
l To save the edited partition table as a file, click Save.
After the partition table is created, the dialog box shown in Figure 2-8 is displayed when you switch the chip. Click OK. Select a save path, enter a file name, and click Save in the displayed Save As dialog box. The partition information is saved as an .xml file. If you click Cancel, the chip is switched but the partition information is not saved. The file must be in .xml format. Otherwise, the partition information cannot be loaded during next startup.
Figure 5-4 Asking you whether to save the partition information
Step 3 Prepare the board environment. Connect the serial port and Ethernet port of the board. If the board is powered on, power it off and short-circuit the bootstrap jumper cap of the board. For details, see section 1.3 "Environment Preparation."
Step 4 Click Burn to start to burn files, see Figure 5-6.
Step 5 Power on the board to burn the files. Figure 5-7 shows the burning process.
The information about the burning process is displayed in the Console.
l Check whether the correct serial port is selected.
l Check whether the IP address is correct and whether it is occupied.
l Check whether the bootstrap jumper on the board is short-circuited.
Step 6 Connect the terminal tool and restart the board.
----End
You can select a file from the current partition list to create an image for the burner. After the partition information is configured, click Create Programmer Image and specify the file path in the displayed dialog box, as shown in Figure 5-8.
Figure 5-8 Creating an image for the burner
Uploading data from the eMMC to the PC based on the start address and length is the reverse process of burning images to the eMMC. The uploading process is similar to the burning process.
Step 1 Click the Burn eMMC tab
Step 2 Configure the information for uploading. Set the start address in Start and length in Length, and specify a file path to save the content in a certain file on the PC.
Step 3 Connect the serial port and Ethernet port of the board. If the board is powered on, power it off and short-circuit the bootstrap jumper cap of the board. For details, see section 1.3 "Environment Preparation."
Step 4 Click Upload to save the data to the specific file. See Figure 5-9.
----End
The HiBurn allows you to create images for the HiPro. After the partition table is configured, click Create HiPro image, and select the type of images to be created (HiPro-Serial or HiPro-Usb), as shown in Figure 5-10.
Figure 5-10 Selecting HiPro image type
Specify the file path in the displayed dialog box. Then images for the HiPro can be created. See Figure 5-11.
Figure 5-11 Creating images for the HiPro
l If a partition is not selected, or the file to be burnt for none file system partition is not specified, the partition image is not created.
l If the file to be burnt for the EXT3/4 file system partition is not specified, the HiBurn writes an empty partition to the image.
l The length of the last EXT3/4 file system partition must be specified.
l Because a partition table is attached to the eMMC, the actual addresses for the fastboot partition and all EXT3/4 partitions are shifted backwards slightly relative to the configured burning addresses.
Before burning images to the advanced CA board, you need to specify a file that contains the commands and issue the file to the board because the fastboot may not contain the commands required for burning the images. This file is called the programmer file in the HiBurn.
If all the required commands are included, images can be burnt after you specify the programmer file or fastboot.
The following chips do not support this function: Hi3521, Hi3531, Hi3520D, Hi3535, Hi3712, Hi3110E V200, Hi3110E V400, Hi3716C, Hi3716H, Hi3716M V100, Hi3716M V200, Hi3716M V300, Hi3716C V200, Hi3718C V100, Hi3719C V100, Hi3719M V100, Hi3719M V100_A, and S40 V100.
Click Browse next to the Programmer File textbox, and select a programmer file. See Figure 6-1. (This section uses burning by partition as an example. The operations for other burners are similar.)
Figure 6-1 Burning images to the advanced CA boards
For details about the subsequent procedures, see chapters 2 to 5.
The bad block detection function applies to the board that supports the NAND flash and runs the boot.
This function is not supported for the following chips: Hi3521, Hi3531, Hi3520D, Hi3535, Hi3712, Hi3110E V200, Hi3110E V400, Hi3110E V300 (CA), Hi3716C V110, Hi3716M V200 (CA), Hi3716M V300 (CA), Hi3716C V200 (CA), Hi3719M V100 (CA), and S40 V100.
To detect bad blocks, perform the following steps:
Step 1 Click the Bad Block Checker tab, as shown in Figure 7-1.
Step 2 Click Check Bad. The dialog box shown in Figure 7-2 is displayed.
Figure 7-2 Detecting bad blocks
When a bad block is detected, a red line is displayed on the green bar, corresponding to the address on the board. Detailed information about the bad block is displayed in the pane below the green bar. See Figure 7-3.
Figure 7-3 Information about bad blocks
——End
When the SPI flash is used, multiple images can be merged into one to use blocks more efficiently as the storage space of the SPI flash is small. You can also use this function to merge images for other flash memories.
To merge images, perform the following steps:
Step 1 Click the Merge Image tab, as shown in Figure 8-1.
Figure 8-1 Merge Image tab page
Step 2
Click Browse to load a partition table or click to
create a partition table, as shown in Figure 8-2.
Figure 8-2 Loading the partition table
Step 3 Click Merge Image. See Figure 8-3.
----End
To set the Trivial File Transfer Protocol (TFTP) of the HiBurn, choose Window > Preferences, and choose HiBurn > TFTP Setting, as shown in Figure 9-1.
The setting options are described as follows:
l TFTP speed (Unit: KB/s): The timeout period can be calculated based on the configured TFTP speed and length of the transmitted file.
l Deal with losing packages: If this option is selected, the maximum number of lost consecutive packets can be configured. The transmission fails if the maximum number of lost consecutive packets is reached. If this option is not selected, the maximum number of lost consecutive packets cannot be configured, and packet loss during transmission is ignored.
l The number of consecutive packet loss: Sets the maximum number of lost consecutive packets allowed.
l TFTP retry count: Sets the times of TFTP retry attempts allowed. If the transmission fails, the tool retries for the configured times and then stops.
l TFTP no response timeout (Unit: s): Sets the timeout period for no response. If there is no response during transmission in the configured timeout period, the transmission is considered failed.
To set the commands of the HiBurn, choose Window > Preferences, and choose HiBurn > Command Setting, as shown in Figure 9-2.
Speed: The timeout period can be calculated based on the configured speed and length of data to be written. The unit is byte/s.
The setenv ethact command is used to set the current network port.
To set the invalid data to be filled in to the images for the eMMC burner and HiPro, choose Window > Preferences, and choose HiBurn > Invalid Data Setting, as shown in Figure 9-3.
Figure 9-3 Setting invalid data to be filled into images
To set the HiBurn-Debug console, perform the following steps:
Step 1 Choose Window > Preferences, click HiBurn, and select Open Debug Mode, as shown in Figure 9-4.
Figure 9-4 Selecting Open Debug Mode
Step 2
After the burning starts, the HiBurn
automatically creates the Debug console. Click in the upper right corner
of the console and choose HiBurn-Debug. Then the Debug console is displayed, as shown in Figure 9-5.
Figure 9-5 Switching to the HiBurn-Debug console
----End
Choose Window > Preferences, click HiBurn, and select Check whether the PC and board IP addresses are in the same network segment, as shown in Figure 9-6. If this option is selected, the HiBurn checks whether the IP address for the PC and that for the board are in the same network segment before burning.
Figure 9-6 Checking whether the IP address for the PC and that for the board are in the same network segment
The HiBurn can automatically updates the mtdparts or blkdevparts parameter in the bootargs partition. Choose Window > Preferences, click HiBurn, and select Auto-set mtdparts/blkdevparts, as shown in Figure 9-7. Then the HiBurn generates a temporary bootargs file during burning based on the current partition table and burns it to the board.
Figure 9-7 Automatically updating the bootargs partition parameter
l The parameters mtdparts and blkdevparts have the same function in the bootargs partition. A bootargs file contains only one of the two parameters. For example, the parameter for the bootargs partition of Hi3716C V200 is blkdevparts.
l After Auto-set mtdparts/blkdevparts is selected, the HiBurn does not modify the original bootargs file. If the current partition information is inconsistent with that specified in the original bootargs file, the HiBurn creates a temporary file bootargs.temp to replace the original bootargs file and burns the temporary file to the bootargs partition of the board.
Problem Description
The TFTP timeout error occurs, as shown in Figure 10-1.
Figure 10-1 TFTP timeout error
Solution
Do as follows:
l Check whether the network configuration of the HiBurn is correct, as shown in Figure 10-2.
Check whether the server IP address is correct. If not, select the correct IP address for the PC. Then check whether the subnet mask and network gateway are correct. If yes, check whether the board IP address is occupied (Run the ping command to check whether the current board IP address can be pinged. If no, the network is disconnected.) Ensure that all parameters are correctly configured and try to burn an image again.
Figure 10-2 Checking the network configuration
l Use the external tftpd32 tool instead of the embedded TFTP to download images. If a timeout error also occurs, check whether the current network environment is normal. For details about how to use the external tftpd32 tool, see section 10.2 "How Do I Download Images by Using the External tftpd32?"
l Modify the TFTP parameters in the HiBurn to match the current network environment. Choose Window > Preferences > HiBurn > TFTP Setting, and set The number of consecutive packet loss and TFTP no response timeout to larger values, as shown in Figure 10-3. Then burn an image to check whether the tool is normal.
l Check whether the firewall is disabled. If not, disable the firewall.
Figure 10-3 Modifying TFTP parameters
Problem Description
How do I download images by using the external tftpd32?
Solution
Perform the following steps:
Step 1 Open the tftpd32, and select the correct PC IP address and the directory for storing the image to be burnt, as shown in Figure 10-4.
Figure 10-4 Configuring the tftpd32
Step 2 Click the burn button in the HiBurn. The dialog box shown in Figure 10-5 is displayed. Click OK. Then the external tftpd32 is used to download the image, as shown in Figure 10-6.
Figure 10-5 Information indicating TFTP startup failure
Figure 10-6 Downloading images by using the tftpd32
----End
Problem Description
The system displays "Failed to send start frame" when the fastboot partition is being burnt, as shown in Figure 10-7.
Figure 10-7 "Failed to send start frame" error
Solution
Check whether the board is restarted within 15 seconds after the burn button is clicked. If yes, check whether the serial port is properly connected to the board. If yes, check whether the serial port ID is correctly selected in the HiBurn, as shown in Figure 10-8. Then burn the image again.
Figure 10-8 Checking the serial port ID
Problem Description
When the fastboot partition is being burnt, the console stops displaying information after "#########" is displayed, and the error message "Failed to send head frame" is displayed, as shown in Figure 10-9.
Figure 10-9 "Failed to send head frame" error
Solution
This issue may be caused due to the following reasons:
l There is a mismatch between the fastboot image being burnt and the current chip model. Check the chip model directly or over the serial port, as shown in Figure 10-10. The value of CPU is the chip model. Then select and burn the SDK image that matches the chip model.
l The board DDR is faulty. It cannot be initialized properly.
Figure 10-10 Checking the chip model over the serial port
Problem Description
The system displays "Failed to send data frame" when the fastboot partition is being burnt, as shown in Figure 10-11.
Figure 10-11 "Failed to send data frame" error
Solution
This issue may occur because the serial port is not connected properly when the fastboot image is being burnt, which results in a data transmission failure during interaction between the HiBurn and the board. Therefore, check whether the serial port is properly connected.
Problem Description
The system displays "Failed to execute command" when the fastboot partition is being burnt, as shown in Figure 10-12.
Figure 10-12 "Failed to execute command" error
Solution
This issue occurs because the selected flash type of the fastboot partition is incorrect, as shown in Figure 10-13. Restart the board to check the Boot Media attribute of the board. If it is eMMC, the flash type of the fastboot partition must be eMMC, and the partition must be burnt in eMMC mode.
Figure 10-13 Checking Boot Media
Problem Description
What are the advantages and disadvantages of file transmission over the serial port?
Solution
If images are burnt over the serial port, the efficiency is low because a large amount of data needs to be transmitted to the board during burning and the transmission rate of the serial port is low. Therefore, you are advised to burn images over the Ethernet port. However, if your network environment is unstable, you are advised to use the serial port because burning images over the serial port is stable.
Problem Description
What are the requirements on the file length on the Burn by Address page?
Solution
The length of data to be erased must be an integral multiple of the block size, and the length of the Yaffs file system to be uploaded must be an integral multiple of (page size+OOB size).
Problem Description
After the Burn button is clicked and the board is restarted, the HiBurn does not start to burn images.
Solution
This issue occurs if the selected serial port is incorrect or the serial port is not connected properly (view the serial port information by using the terminal tool). Wait for the console to display the related information.
Problem Description
Solution
This issue occurs if you do not log in to the board as the root user, because only the root user has the permission to enable the TFTP service or use the serial port. If a message indicating that the TFTP port is occupied is reported, another software may be using the port.
Problem Description
The console displays pure data length and len_incl_bad when images are being burnt to the NAND flash. What do they mean?
Solution
As shown in Figure 10-14, pure data length indicates the length of the actually burnt data, and len_incl_bad indicates the length of burnt data including bad blocks. Both pure data length and len_incl_bad do not include the length of the OOB.
Figure 10-14 Length of burnt data displayed in the console
Problem Description
There are two methods of burning images to the eMMC based on the chip model. The difference lies in whether a partition table needs to be created. What should I pay attention to when burning images by using the two methods?
Solution
A partition table must be created for the following chips: Hi3716H V100, Hi3716M V100, Hi3716M V200, Hi3716M V300, Hi3716C V110 (CA), Hi3716M V200 (CA), and Hi3716M V300 (CA). If the preceding chips are burnt for the first time or after partitions are adjusted, you must select Create eMMC Partition Table and burn the table to the board. Otherwise, the board cannot start properly.
Problem Description
"Time out while receiving command execute result!" is displayed when images are being burnt to the eMMC.
Solution
This issue occurs because after the mmc write command is executed, a timeout occurs when the HiBurn is waiting for the response from the board. Choose Window > Preferences > HiBurn > Command Setting, as shown in Figure 10-15, set the speed to a smaller value, and burn the image again.
Figure 10-15 Changing the mmc write command execution speed
Problem Description
What should I pay attention to when burning large files or burning files to the eMMC (with Create eMMC Partition Table selected)?
Solution
You must have the write permission on the directory for the file to be burnt or the directory for the first selected file so that you can create temporary files in the directory.
Problem Description
What should I pay attention to when creating the image to be burnt by using the eMMC burner?
Solution
l When an image to be burnt is being created by using the eMMC burner, if the length of the last partition in the partition table is -, you need to enter the available length of the component on the board for calculating the length of the last partition. See Figure 10-16.
Figure 10-16 Entering the length of the component
l If the file system of the partition is EXT3 or EXT4, the partition image may be a sparse image. In this case, the console displays information similar to that shown in Figure 10-17. If the size of the sparse image after parsing exceeds the partition size, the console displays information similar to that shown in Figure 10-18, and the created image may be abnormal.
Figure 10-17 Information displayed in the console when the partition image is a sparse image
Figure 10-18 Information displayed in the console when the size of the sparse image after parsing exceeds the partition size
Problem Description
When creating images to be burnt by using the eMMC burner, how do I change the stuffed value of invalid data to 0x00 or 0xFF?
Solution
Choose Window > Preferences > HiBurn > Invalid Data Setting, and select 0x00 or 0xFF, as shown in Figure 10-19. After that, invalid data bits are stuffed with the specified value when you create images to be burnt by using the eMMC burner again.
Figure 10-19 Setting the stuffed value of invalid data
Problem Description
What does the HiBurn display when the DDR training fails?
Solution
If the DDR training fails, information shown in Figure 10-20 is displayed when the fastboot partition is being burnt.
Figure 10-20 DDR training failure information
Problem Description
What information should I provide when submitting feedback on the HiBurn?
If an error occurs when you use the HiBurn, click the Export button on the console toolbar to export the displayed information in the console and provide the exported information when you submit feedback on the HiBurn. This helps locate and solve the problem.
Problem Description
Running the tftp command always returns a message indicating that the file cannot be found. However, all the configurations are correct. How do I check whether port 69 of the TFTP is occupied by a process?
Solution
Port 69 may be occupied by a background process. You can check whether it is occupied by a process by using the following method:
Enter netstat -ano -p udp in the command-line interface. The information similar to that shown in Figure 10-21 is displayed.
Figure 10-21 Checking whether the port is occupied by a process
As shown in Figure 10-21, port 69 is occupied by the process with the PID 7696. Then run tasklist|findstr "7696" to check the name of the process. The information similar to that shown in Figure 10-22 is displayed.
Figure 10-22 Checking the name of a process with a specific PID
You can kill the process in the process manager.
A |
|
AXI |
advanced eXtensible interface |
|
|
C |
|
CRC |
cyclic redundancy check |
|
|
D |
|
DDR |
double data rate |
|
|
E |
|
eMMC |
embedded multimedia card |
|
|
G |
|
GPIO |
general purpose input output |
|
|
H |
|
HDMI |
high-definition multimedia interface |
|
|