Machine Translated by Google

TCL
MediaTek Confidential Release fo

MediaTek_TV_EMMC mass production method description

TCL
MediaTek Confidential Release for

Version: 5.0
Release date: 2022-09-01

TCL
Use of this document and any information contained therein is subject to the terms and conditions set forth in Exhibit 1. This document
is subject to change without notice.

MediaTek Confidential Release for

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved.
Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited.
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

Version History

Version Date Author (optional)

TCL Description
V1.0 17/10/2013 Initial release

V1.1 24/10/2013 Added ECSD setting for programmer

MediaTek Confidential Release fo

V1.2

V1.3
15/07/2014

02/02/2015
Improve the description of emmcbin.ini rules

Added reliable write and hw reset related ecsd setting instructions

V1.4 22/05/2015 ÿ Added precautions for erasing EMMC settings

Added path descriptions for Generator_mpool and emmcnize_V3

V1.5 20/10/2015 Setting the burner in the Emmcnize image packaging method

V1.6 10/11/2015 Added notes on EMMC reliable write

V1.7 18/01/2016 Added EMMC ECSD description

V1.8 05/09/2016 Modify EMMC ECSD setting instructions

V1.9 28/03/2017 ECSD[155] cannot be written directly

V2.0 28/03/2018 Update ECSD[179]=0x08 to solve the problem of low probability booting
V2.1 02/07/2018 Added notes on dumping user area data from the master slice
V2.2 03/09/2019 Modify the problem of MBOOT fixed at 3M and MPOOL fixed at 2M

V2.3 25/09/2019 Added multioptee adaptation function

V2.4 25/11/2019 Added mbootnize for 5M

V2.5 20/02/2020 Added a method to upgrade mboot before dump to avoid mbootnize

V2.6 22/04/2021
TCL Operation

ÿ Modify the ECSD register setting instructions

Delete and replace the emmc.bin part, and emphasize that mboot must be re-burned

Partition, otherwise there will be ns_uboot_load_RPMBProg failed!

MediaTek Confidential Release for

V2.7

V2.8
22/04/2021

25/05/2021
Modify the ECSD[167] register setting description

Increase experience sharing content

V2.9 Add some important notes for emmcnize to generate emmc.bin; (use

19/06/2021 Must read before use)

Added recommended method for simulating burning master image

V3.0 23/06/2021 Added support for GPT partition table in emmcnize

V4.0 7/5/2022 Support Merak architecture, please see section 2.7 for instructions

V5.0 Support Merak architecture FDE function. Please see the updates of Chapter 2 and 5.

9/1/2022 For a summary of the ECSD register setting requirements for the programmer, see Section 6.

chapter.

TCL
MediaTek Confidential Release for
2
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited.
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

Table of Contents
TCL
Version History ··································································································································································2
Table of Contents·······························································································································································3
Creating an Image by Copying the Master Film· ... Introduction· ... Area· ... Area· ... Master Film Preparation· ... Area

MediaTek Confidential Release fo

1

Data· ...

1.3.3 Using a programmer to program the user area· ...

2 Creating an image using the Emmcnize packaging method · ... Introduction· ... Area· ... Area· ... Generate mpool.bin· ...
Packaging Images· ...

2.3.3 Using a programmer to program the user area· ...

TCL
2.3.4 Upgrading the main program via USB after burning mboot with a burner· ...
2.3.5 Adding multioptee· ... Notes· ... Support for Partition Table (emmcnize_V3)· ...

MediaTek Confidential Release for

2.5.1 emmcnize_V3 debug tip ·························································· ·························································· 15 2.6
emmcnize_V4 for Merak Architecture· ... Function· ... 3.1 Operations under Kernel· ... Operations under · ...

4 Sharing of experience in making Fusion EMMC master· ...

4.1 Making emmc.bin · ...
4.1.1 EMMC Less than 4G· ...

4.1.2 EMMC Greater Than 4G· ...

4.2 Making a Master Film· ... Using a programmer to program · ... Sharing of experience in making EMMC master
chip· ... Creating an Image· ... The following CONFIG needs to be opened· ... 22 5.2 Dump Making an Image from a
Master Film· ... Cannot be recognized· ...
TCL
MediaTek Confidential Release for
3
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited.
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

5.3 Method of Simulating Burning Master Image· ... Operation· ... 6 Summary of ECSD Setting Requirements
for Programmers· ...

7 Sharing of cases of problems encountered:· ...

TCL
7.1 Creating emmc.bin · ...
MediaTek Confidential Release fo
7.2 Making a Master Film· ...

7.3 Using a Programmer to Write · ...

TCL
MediaTek Confidential Release for

TCL
MediaTek Confidential Release for
4
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited.
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

1. Use the master copy method to make a mirror

1.1 Introduction
TCL
MediaTek Confidential Release fo
Master chip duplication means dumping the data in the master chip emmc flash, and then using the burner to burn the dumped data into the empty emmc flash, so as to

achieve emmc flash duplication. We use the boot1 area and

user area in the emmc flash. So when burning the emmc flash, there are two situations:

1. If the writer does not support burning these two partitions at the same time, you need to burn these two partitions separately.

When programming, you need to set the extended CSD register of the

programmer: 1) First, set reliable write, that is, a) set

ecsd[175] = 0x1 b) According to the

SPEC of the chip provided by the emmc manufacturer, there are two cases: if escd[167]bit0 is enabled by default before leaving the factory

WR_DATA_REL_USR, that is, escd[167] has been preset to 0x1f or 0x1, then jump directly to step 2); if escd[167]bit0(WR_DATA_REL_USR) is

preset to 0 before leaving the factory, that is, escd[167] has been preset to 0x0, continue with steps c, dc) Set ecsd[167]=0x1, escd[155]=0x1 d) After the

setting is completed, power off the emmc and then power it on

again

2) When programming the boot1 area, all main chips

except MSD801 need to be set: ECSD[179] = 0x49.

MSD801 or all main chips with SPI-NOR boot: Skip this step 2) (no need to burn boot1 area).

3) When programming the user area, you need to set

TCL
MSD801: ECSD[179] = 0, MSD918: ECSD[179] = 0x48, all other master chips: ECSD[179] = 0x08. All master chips: ECSD[177] = 0x02, ECSD[162]

= 0x01

MediaTek Confidential Release for

2. If the burner supports burning boot and user areas at the same time

When programming, you need to set the extended CSD register of the

programmer: 1) First, set reliable write, that is, a) set

ecsd[175] = 0x1 b) According to the

SPEC of the chip provided by the emmc manufacturer, there are two cases: if escd[167]bit0 is enabled by default before leaving the factory

WR_DATA_REL_USR, that is, escd[167] has been preset to 0x1f or 0x1, then jump directly to step 2); if escd[167] bit0 (WR_DATA_REL_USR) is

preset to 0 before leaving the factory, that is, escd[167] has been preset to 0x0, then continue with steps c and d

c) Set ecsd[167]=0x1, escd[155]=0x1 d) After the setting is

completed, power off the emmc and then power it on again

2) Required settings

MSD801: ECSD[179] = 0, MSD918: ECSD[179] = 0x48, all other master chips: ECSD[179] = 0x08. All master chips: ECSD[177] = 0x02, ECSD[162]

= 0x01

Note: If

you want to erase the EMMC, please erase the entire EMMC before setting the extended CSD register. Remove the erase option when programming boot1 and user

TCL
partitions, otherwise the boot1 partition may be accidentally erased when programming the user partition.

3. ECSD Setting Instructions: 1)

Reliable write must be set. If not set, the data written on the eMMC may be damaged when the power is off.

MediaTek Confidential Release for

Reliable write is enabled by default when the emmc is shipped from the factory. If ecsd[167] is 0x1f, reliable write does not need to be set. If reliable write cannot

be set, please consult the emmc manufacturer. 2) ECSD[179] = 0x48 sets the boot1 partition

of the two boot partitions as the boot partition.

5
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited.
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

3) ECSD[177]=0x2 sets the eMMC bit width to 8 bits and the boot mode to standard Speed 4)
Some eMMCs will not boot if ECSD[162] is not set to 1, so it must be set. ECSD[162]=1 requires the eMMC to check the HW reset
pin. The default value is 0, which means it will not be checked. TCL
MediaTek Confidential Release fo

TCL
MediaTek Confidential Release for

TCL
MediaTek Confidential Release for
6
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited.
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

1.2 Burn boot1 area

TCL
The boot1 area stores rom_emmc_boot.bin. Since hash0 in rom_emmc_boot.bin may be

Unique key encryption, so you need to burn the original rom_emmc_boot.bin directly to the boot1 area.

MediaTek Confidential Release fo

1.3 Burn the user area

1.3.1 Master preparation

1. Use tftp to upgrade all partitions of the mother chip (USB upgrade will not upgrade all partitions by default, but a special USB package for upgrading all partitions is also

acceptable); 2.

After the mother chip is upgraded and started up, no actions can be performed, such as starting the APP (which will generate user encryption behavior or generate a unique ID

for the machine, etc.) or plugging in the USB to upgrade the DRM Key, etc. Otherwise, the dumped data will be unusable; 3.

After the mother chip is started up, power off and restart to enter mboot, and upgrade the mboot partition separately using tftp or USB (both rom_emmc_boot.bin and mboot.bin

files must be re-burned, and only one of them cannot be burned, otherwise there will be a problem of ns_uboot_load_RPMBProg failed! Remember not to use Graffito tool

or ISPtool for upgrading, otherwise the environment variables will be overwritten), and remember not to power off after the upgrade is completed, and directly start the next step

of dumping the user area of the mother chip.

1.3.2 Dump user area data from the master slice TCL
To burn the user area, you need to dump the data in the mother chip emmc flash to the USB disk in the mboot command line. Due to the size limit of FAT 4G files, the generation

MediaTek Confidential Release for

of emmc.bin is introduced in two cases.

1. emmc flash with a total capacity less than 4G Step 1) Determine

the port number used by the USB flash drive. After inserting

the USB flash drive (formatted as FAT32, the capacity should not be less than the total capacity of the EMMC), use the command to determine the

USB port #usb start [port number]. For

example, to confirm whether it is inserted in port 1, enter

#usb start 1

If the device is found during printing, port 1 is currently used. 2)

Use the emmcbin command to copy the data in the EMMC to the USB disk file. #emmcbin [port

number]

For example, using port 1 above, input

#emmcbin 1

After the progress bar is completed and the dump is prompted to be completed, a file named emmc.bin will be generated under the USB flash drive, and the size is consistent with

the EMMC capacity (the emmc capacity can be queried through the mmc size command).

2. emmc flash steps with a total capacity greater than 4G

TCL
1) After inserting the USB disk (formatted as FAT32, the capacity should not be less than the total capacity of EMMC), if you are not sure

Which USB port can be used first?

#usb start [port number] command

MediaTek Confidential Release for

confirmation, for example, to confirm whether it is plugged into port 1, enter
#usb start 1 If
the device is found, port 1 is currently used.

7
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited.
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

2) Use the mmc dd command to copy the EMMC data to the USB flash
drive. #mmc dd mmc2usb [port number] For
example, if port 1 is used above,
enter #mmc dd mmc2usb 1. TCL
After the copy is completed (prompted 100%), remember the total size (block number) dumped, which is actually the total capacity of the
EMMC, and will be given in the last line

MediaTek Confidential Release fo of the printout: Dump Block: XXX

3) Use WinHEX on the PC to copy the data just dumped in the USB drive to a file. Select Tools->Disk tools->Clone disk. Note: In the Merak architecture project, the

partition table uses the GPT format, and Windows PC cannot recognize the USB drive with this GPT partition table. In actual tests, when the USB drive is inserted into the

PC, it will not be recognized, and it is also impossible to select this USB drive using WinHEX. Therefore, for the Merak architecture solution, WinHex cannot be used to create

emmc.bin for the time being.

TCL
MediaTek Confidential Release for
Select the USB flash drive as Source and the newly created target file directory as Destination. Fill in 0 for Start sector, which means reading data from the

beginning of the USB flash drive. Note that the Number of sectors to copy here needs to be filled in with the size after "Dump Block:" in 2), then click OK and wait

for the creation to be completed.

1.3.3 Use the burner to burn the user area

Use a burner to burn the generated new_emmc.bin into the user area.

TCL
MediaTek Confidential Release for
8
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited.
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

2. Create an image using the Emmcnize packaging method

2.1 Introduction
TCL
MediaTek Confidential Release fo
Using Emmcnize to pack the image means generating emmc.bin for burning the user area based on the original partition image file.

The difference between the two methods is that there is no need to dump data from the master slice, and the images can be created entirely based on the original images of each partition.

emmc.binÿ

Similarly, you also need to burn the boot1 area and user

area. We use the boot1 area and user area in the emmc flash. So when burning the emmc flash, there are two situations:

1. If the writer does not support burning these two partitions at the same time, you need to burn these two partitions separately.

When programming, you need to set the extended CSD register of the

programmer: 1) First, set reliable write, that is, a) set

ecsd[175] = 0x1 b) According to the

SPEC of the chip provided by the emmc manufacturer, there are two cases: if escd[167]bit0 is enabled by default before leaving the factory

WR_DATA_REL_USR, that is, escd[167] has been preset to 0x1f or 0x1, then jump directly to step 2); if escd[167]bit0(WR_DATA_REL_USR) is

preset to 0 before leaving the factory, that is, escd[167] has been preset to 0x0, continue with steps c, dc) Set ecsd[167]=0x1, escd[155]=0x1 d) After the

setting is completed, power off the emmc and then power it on

again

2) When programming the boot1 area, all main chips

except MSD801 need to be set: ECSD[179] = 0x49.

TCL
MSD801 or all main chips with SPI-NOR boot: Skip this step 2) (no need to burn boot1 area).

3) When programming the user area, you need to set

MediaTek Confidential Release for

MSD801: ECSD[179] = 0, MSD918: ECSD[179] = 0x48, all other master chips: ECSD[179] = 0x08. All master chips: ECSD[177] = 0x02, ECSD[162]

= 0x01

2. If the burner supports burning boot and user areas at the same time

When programming, you need to set the extended CSD register of the

programmer: 1) First, set reliable write, that is, a) set

ecsd[175] = 0x1 b) According to the

SPEC of the chip provided by the emmc manufacturer, there are two cases: if escd[167]bit0 is enabled by default before leaving the factory

WR_DATA_REL_USR, that is, escd[167] has been preset to 0x1f or 0x1, then jump directly to step 2); if escd[167]bit0(WR_DATA_REL_USR) is

preset to 0 before leaving the factory, that is, escd[167] has been preset to 0x0, continue with steps c, dc) Set ecsd[167]=0x1, escd[155]=0x1 d) After the

setting is completed, power off the emmc and then power it on

again

2) Required settings

MSD801: ECSD[179] = 0, MSD918: ECSD[179] = 0x48, all other master chips: ECSD[179] = 0x08. All master chips: ECSD[177] = 0x02, ECSD[162]

= 0x01

Note: If

TCL
you want to erase the EMMC, please erase the entire EMMC before setting the extended CSD register. Remove the erase option when programming boot1 and user

partitions, otherwise the boot1 partition may be accidentally erased when programming the user partition.

MediaTek Confidential Release for

3. ECSD Setting Instructions: 1)

Reliable write must be set. If not set, the data written on the eMMC may be damaged when the power is off.

Reliable write is enabled by default in eMMC. If ecsd[167] is 0x1f, reliable write does not need to be set.

9
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited.
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

If reliable write cannot be set, please consult the emmc manufacturer. 2) ECSD[179] =

TCL
0x48 sets the boot1 partition of the two boot partitions as the boot partition.

3) ECSD[177]= 0x2 sets the eMMC bit width to 8 bits and the boot mode to standard Speed 4) Some eMMCs will not

boot if ECSD[162] is not set to 1, so it must be set. ECSD[162]=1 requires the eMMC to check the HW reset pin. The default value is 0, which means it will

not be checked.

MediaTek
2.2 Burn boot1 area
Confidential Release fo
Use the burner to burn rom_emmc_boot.bin to the boot1 area directly

2.3 Burn the user area

2.3.1 Generate mpool.bin

Merak architecture projects do not need attention.

ÿ Non-secure boot case (ie AN does not open the BUILD_WITH_SECURE_BOOT option): Skip this step and directly

fill in the blank value for the mpool partition in Section 2.3.2 (Emmcnize will fill in the blank value at the corresponding position of the partition if it cannot

find the image corresponding to the partition).

ÿ secure boot + secure merge case (AN ÿÿ BUILD_WITH_SECURE_BOOT ÿ

TCL
BUILD_WITH_SECURE_MERGE option): Skip this
step and directly fill in the blank value for the mpool partition in Section 2.3.2 (Emmcnize will fill in the blank value for the partition if it cannot find

MediaTek Confidential Release for

the image corresponding to the partition).

ÿ Secure boot + R2 tee + non secure merge caseÿ

Copy secure_info_boot.bin, secure_info_recovery.bin, secure_info_tee.bin and nuttx_config.bin to the image folder.

ÿ Secure boot + op-tee + non secure merge case: Copy

secure_info_boot.bin and secure_info_recovery.bin to the image folder.

ÿ Secure boot + op-tee + secure merge case: generator_mpool.sh

is not applicable, and gen_mpool_bin_v3.sh needs to be used to create mpool.bin.

In the case of secure boot + non-secure merge, the MPOOL partition stores the corresponding secureinfo information such as boot img.

Generate mpool.bin based on the secureinfo information.

Files in the folder generator_mpool: ÿÿÿ image ÿ

TCL
ÿÿÿ nuttx_config.bin

ÿ ÿÿÿ secure_info_boot.bin ÿ ÿÿÿ

secure_info_recovery.bin ÿ ÿÿÿ

secure_info_tee.bin ÿÿÿ generator_mpool.sh ÿÿÿ

MediaTek Confidential Release for

util

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 10
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

ÿÿÿ align ÿÿÿ

TCL
crc ÿÿÿ

MergeBin.exe
ÿÿÿ
SeparateBin.exe

runs the generator_mpool.sh script to generate the mpool.bin file:

MediaTek Confidential Release fo

selic.cheng@tc-002:~/gtv/gtv-produce/generator_mpool $ ./ generator_mpool.sh At this time, mpool.bin

will be generated, and some intermediate files will be generated in the temp directory.

Copy mpool.bin, which will be used when Emmcnize packages the image later.

2.3.2 Use Emmcnize to package the image TCL

Emmcnize is to pack multiple partition images (mboot.bin, mpool.bin, recovery.img, boot.img, system.img, etc.) into one

MediaTek Confidential Release for

A tool that creates a separate image and adds the Emmc partition table to the head of the image. Usage

steps: 1. Put emmcnize_V3 and all the partition images and ini configuration files to be packaged in the same

directory; 2. Execute "./emmcnize_V3 XX.ini XX.bin" and wait for the packaging to be completed. Among them, XX.ini is the name of the configuration file, and XX.bin
is the name of the separate image after packaging. For example, if the configuration
, file name is emmcbin.ini and needs to be packaged into a separate image
emmc.bin, type "./emmcnize_V3

emmcbin.ini emmc.bin". 3. The generated emmc.bin can be directly burned into the

emmc with a burner. 4. If you want to generate a bin containing only the partition table, execute "./emmcnize_V3 XX.ini XX.bin -p", that is, add the -p parameter at the end.

Emmcnize creates a partition table by reading the ini configuration file. The format of the ini configuration file is as follows:

[MBOOT-volume]

image=mboot.bin

vol_id=1

vol_size=0x300000

TCL
vol_name=MBOOT

[MPOOL-volume]

image=mpool.bin

MediaTek Confidential Release for

vol_id=2

vol_size=0x200000

vol_name=MPOOL

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 11
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

TCL
[misc-volume]

image=misc.img

vol_id=3

vol_size=0x80000

MediaTek Confidential Release fo

vol_name=misc

[recovery-volume]

image=recovery.img.aes

vol_id=4

vol_size=0x800000

vol_name=recovery

Note:

ÿ The user sets the order and size of each partition in the Board config. The size of each partition must be aligned to 512 bytes, which means the minimum unit is

0x200.

ÿ After compiling Android, a set_partition file will be generated. The order and size of each partition in set_partition must be consistent with the order and size of each partition in emmcbin.ini.

The order and size of each partition must be consistent, and the size of each partition must be aligned to

512Byte; ÿ [XX-volume] is the header of each partition information, and Emmcnize uses this header information to identify the entire

TCL
partition information; ÿ image=XX.img defines the partition image name, which must be the same as the existing image name. If you need to divide a blank partition,

that is, if there is no corresponding partition image, image can be set to a non-existent image name (empty file will be printed when running emmcnize_V3),

but it must have a value;

ÿ vol_id=X Each partition has a unique vol_id, which cannot be the same. The vol_id number starts from 1 and is arranged in ascending order (+1).

MediaTek Confidential Release for

emmcbin_V2 supports up to 63 partitions, and the partition data starts from the 7M offset; ÿ

vol_size=XX defines the partition size. Vol_size must not be less than the partition image size. It is best to keep it consistent with the value in set_partition and ensure

512Byte alignment; ÿ vol_name=XX

defines the emmc partition name. Each partition name cannot be the same. Try to unify it with the image name burned into the partition for easy distinction.
Each parameter of the above partition must be assigned a value, otherwise an error will occur.

2.3.3 Use the burner to burn the user area

Use the burner to burn emmc.bin to the user area

2.3.4 Use the burner to burn mboot and then USB upgrade the main program
TCL
If mboot is burned together with the main program, just follow the above steps. If you burn

MediaTek Confidential Release for

mboot first and then use USB to upgrade the main program, you need to follow the following steps: 1)

Use the burner to burn rom_emmc_boot.bin to the emmc boot1 area according to step 2.2; 2) Use the

burner to burn mboot.bin to the 0x200000-0x500000 position in the emmc user area; 3) After the chip is

restarted, use the USB flash drive to upgrade and burn the emmc.bin produced in 2.3.2 into the emmc user area.

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 12
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

When using a burner to burn emmc, please refer to 2.1 for ecsd settings.

TCL
2.3.5 Adding multioptee

MediaTek Confidential Release fo

OneBinary publishes a single image that can run on different devices. When there are multiple sets of MMAP, multiple tee.aes (or bl31.aes)
files will be encapsulated into a large tee.aes (or bl31.aes) file. Optee Onebin currently has two versions, V1 and V2. The emmcnize program
will automatically parse the version member in the tee.aes (or bl31.aes) image header and generate emmc.bin based on this version: V1 requires
emmcnize to
separate several separate tee.aes files from a tee.aes file, and each tee.aes generates a corresponding emmc.bin. This process is executed
automatically, and no additional parameters are required when executing the command. The file name of the generated file is added with an ID for

distinction. For example, this SOC has 2 model_ids: 4, 5, and there are two emmc.bin generated, namely emmc4.bin and emmc5.bin. When upgrading
emmc.bin, just upgrade the corresponding emmc.bin according to the target board model_id. For example, if the target platform model_id is 4, then
upgrade emmc4.bin; if the target board model_id is 5, then
burn emmc5.bin; V2 does not need emmcnize to do separation, and will directly pack tee.aes (or bl31.aes) into emmc.bin. Finally, only one
emmc.bin is generated, and this emmc.bin can be upgraded on the target platform.

2.4 Notes
1. Use this emmcnize to generate emmc.bin. If the mboot config does not have CONFIG_LOAD_ENV_FROM_SN turned on, the boot may get stuck in the kernel

TCL
startup phase after burning emmc.bin. This is because the mboot environment variables will not be set during the burning of emmc.bin like upgrading

MstarUpgrade.bin, which leads to such a problem. After turning on this config, the first boot in mboot will read env from /tvconfig/config/set_env

and set the env inside it. /tvconfig/config/set_env is copied from the set_config file under device/, which is basically the same as the set_config

MediaTek Confidential Release for

contained in MstarUpgrade.bin. • (Item 1 is not applicable to projects with Merak software architecture)

2. After opening CONFIG_LOAD_ENV_FROM_SN in 1 above, you need to add the recoverycmd setting in set_config under device

envÿÿÿÿsetenv recoverycmd mmc read.p 0x25000000 recovery 0x2800000\; bootm 0x25000000

a. Otherwise, the mboot env will be reloaded from set_env every time the computer is turned on, which will cause the mboot phase to take a long time.

And the env manually modified under mboot is overwritten by this env load. • (Item

2 is not applicable to projects with Merak software architecture)

3. On the Android platform, super.img (with Android dynamic partiton enabled) or system.img/vendor.img needs to be

Non-sparse format, because emmcnize will not do any processing on the original image, but just write the original image into emmc.bin. Otherwise,

the system startup will be Android init mount system, vendor logical partition fail, causing the system startup to get stuck.

4. Super.img/system.img/vendor.img are not in sparse format, that is, their image size must be equal to the corresponding partition size.

• For example (taking Merak architecture AOSP as an

example): • The size of super.img generated by Full build is 1,620,730,132 bytes. • But the super

TCL
partition size is 0x84A00000, which is 2,225,078,272 bytes. • So it needs to be converted to unsparse

format.

MediaTek Confidential Release for

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 13
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

TCL
MediaTek Confidential Release fo

• The conversion method is

as follows: • First add toolchain under out/host/linux-x86 in the Android root directory. • Then execute simg2img super.img

super.img.raw to convert super.img to super.img.raw. • When the emmcnize tool creates a super partition, the converted super.img.raw must be used.

TCL
•

MediaTek Confidential Release for

5. When executing emmcnize, it fails and prompts "femmcnize: error!: cannot write blank for section "userdata-volume" error".

This is usually because the server's hard disk file system has insufficient space (check with df -u).

6. Although the GPT partition table has a partition name limit of 36, the partition table in the disk_partition_t structure is widely used in mboot;

The limit is 31, so the length limit of the partition name (vol_name) of the emmcnize ini file is 31 bytes. 7. emmcnize supports GPT

partition table, but because we cannot know the size of emmc, we will face two problems:

• (1) Unable to accurately fill last_usable_lba • (2) Unable to fill

the backup partition table

Therefore, we will set the value of last_usable_lba to about 2G (basically there will be no emmc less than 2G), and then the emmc of mboot will automatically

Adapt will help us populate last_usable_lba and backup partition tables accurately.

2.5 Emmcnize adds support for GPT partition table (emmcnize_V3)

1. emmcnize_V3 adds support for GPT partition table (add parameter -g) 2.
TCL
emmcnize_V3 relaxes the restrictions on partition table, the maximum size of partition table can be increased to 128 (of course, this requires synchronous modification

of mboot). 3. emmcnize_V3 supports non-Onebin versions, Onebin V1 and Onebin V2. (See 2.3.5 for details) 4. emmcnize_V3

MediaTek Confidential Release for

fixes the error problem caused by the ini file not containing MBOOTBAK partition. 5. emmcnize_V3 fixes the problem that Onebin

V1 with parameters (eg: -g –p, etc.) will fail to execute and mistakenly delete the ini file.

question.

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 14
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

6. emmcnize_V3 is ultimately statically linked. The advantage is that it avoids dynamic linking problems caused by different server environments. The disadvantage is

TCL
The emmcnize_V3 executable file will be relatively large.

7. Simple usage of emmcnize_V3:

• ./emmcnize_V3 ÿView emmcnize usage

• ./emmcnize_V3 ini_file_name bin_name [optargs]

MediaTek Confidential Release fo

•

•
[-b partition_start]

[-p](only create partition table)

• [-c](compact mode, without padding)

• [-d](open MBOOTBAK partition)

• [-g](general gpt partition table)

• [-v](fill 0xFF to the blank data)

• Usually we only use –p -g

• -p : means only generate the partition table

• -g: Generates a GPT partition table

• -v : Indicates that the padding part is not filled with 0x0, but with 0xff

• ./emmcnize emmcbin.ini ${emmcname} -p –g // Generate only the GPT partition table

• ./emmcnize emmcbin.ini ${emmcname} –g //Generate emmcbin with GPT partition table

• ./emmcnize emmcbin.ini ${emmcname} //Generate emmcbin with custom partition table

2.5.1 emmcnize_V3 debug tip

TCL
MediaTek Confidential Release for
1. Be sure to understand the nature of the emmcnize tool. It does not process the binary (compress/decompress, encrypt/decrypt, etc., pkg package upgrade

The level will do it, which is an important difference between the two), so what the bin is in the emmc is what the emmcnize packs in.

For example, the file that is ultimately burned into the super partition is super.img.raw instead of super.img.

2. emmcnize burn debug method

(1) Confirm that the generated emmcbin format content is what we want. Usually, we only need to confirm the first 2M data.

(2) Confirm that the content of the USB drive is correct and that there will be no errors in the data due to tool problems.

(3) Confirm that the data burned into eMMC is correct.

a) If there is a problem, you can enter the mboot command line:

• mmc read 0x50008000 0x0 0x400

• md.b 0x50008000 0x400

• //Usually read the first 2M data for comparison. If the comparison fails, align it with env

• // Check whether other partition data is abnormal

b) If there is a problem, you can enter the system: use the dd command to dump the partitions for comparison

c) Combine log analysis to further locate the partition that may have problems

2.6 emmcnize_V4 for Merak architecture

TCL
MediaTek Confidential Release for
• In old projects, the emmcnize tool will make special treatment for the partition start and size of MBOOT/MPOOL.

The partition start of other partitions is uniformly placed after the block address 0x3800.

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 15
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

• For Merak project, no longer use partition names such as MBOOT / MPOOL. To make emmcnize more concise, all partitions

TCL
Parse the ini file to get the partition name, and use the [-s] option of the emmcnize tool to specify the starting block of the first partition.

• How to use the Merak project:

• ./emmcnize_v4 emmcbin.ini emmc.bin -a1 -g

MediaTek Confidential Release fo

• ${ini_file_name}: • ${bin_name}:
• [logs] • [logs]
emmcbin.ini is the name of the prepared ini file.
emmc.bin is the name of the generated GAMN image
-a0 refers to the fusion architecture, -a1 refers to the merak architecture

-g means to generate emmcbin with GPT partition table

2.7 emmcnize_V5 for Merak architecture integrates FDE functions

•Based on the emmcnize_V4 version, add the -e option, which means to enable the FDE function and bring it in

FDE keyÿ

• ./emmcnize emmcbin.ini emmc.bin -a1 -g -e key.bin

• ${ini_file_name}: • ${bin_name}: emmcbin.ini is the name of the prepared ini file.

• [uploads] • [uploads] • emmc.bin is the name of the generated GAMN image

TCL
[uploads] -a0 refers to the fusion architecture, -a1 refers to the merak architecture

-g means to generate emmcbin with GPT partition table

-e key.bin, use FDE key to encrypt GANG image

MediaTek Confidential Release for

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 16
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

3 Recommended method for simulating burning master image

3.1 Kernel operations

TCL
MediaTek Confidential Release fo
We don't have a burner here, so we need to consider using the method of simulating the master image burning. Emmc.bin files are generally large, for example, more than 8G. Some USB

file systems do not support such large files, so you can compress emmc.bin and copy it to the USB drive, then connect the USB drive to the TV, decompress it, and then write it to

emmc. This method is relatively easy to operate and feasible, and there is no need to use winhex and other methods to make a USB master image. The specific method is as follows

1. Compress emmc.bin

• gzip emmc.bin # will generate emmc.bin.gz, the compressed file size will be greatly reduced and can be directly copied to the USB flash

drive 2. Unzip on TV and write to emmc

• ac androidboot.selinux permissive
clay

res

reboot recovery (make sure to execute in recovery mode, otherwise it may be interrupted by other IO) mkdir /

tmp/sda mount /dev/

block/sda1 -t vfat -o rw /tmp/sda dd if=/tmp/sda/emmc5.bin.gz

bs=4096 | gunzip -c > /dev/block/mmcblk0 #Unzip and flash to emmc

3. After writing to emmc, manually restart the TV to verify whether the system can start normally

TCL
MediaTek Confidential Release for

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 17
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

3.2 Operations under Mboot

TCL
The Mboot processing method is to first read the emmc bin from USB and store it in DRAM, and then write the corresponding location of

EMMC. However, the DRAM size is usually not enough to cache the entire bin, so the bin needs to be cut into several parts.

MediaTek Confidential Release fo

1. You can now execute the following command on your PC to split bin into several parts in units of

128MB: split -b 128M -d --additional-suffix=.bin ./emmc.bin "./emmc"

2. Then type the following commands in mboot, start bin from address 0, and write the entire bin into EMMC.

usb start 0

fatload usb 0 0x30200000 emmc00.bin $size

mmc write 0x30200000 0x00 0x40000

fatload usb 0 0x30200000 emmc01.bin $size

mmc write 0x30200000 0x40000 0x40000

fatload usb 0 0x30200000 emmc02.bin $size

mmc write 0x30200000 0x80000 0x40000

fatload usb 0 0x30200000 emmc03.bin $size

mmc write 0x30200000 0xC0000 0x40000

fatload usb 0 0x30200000 emmc04.bin $size

mmc write 0x30200000 0x100000 0x40000

fatload usb 0 0x30200000 emmc05.bin $size

TCL
mmc write 0x30200000 0x140000 0x40000

MediaTek Confidential Release for

fatload usb 0 0x30200000 emmc06.bin $size

mmc write 0x30200000 0x180000 0x40000

Notice:

The unit of mmc read/write command is block fat

or partition command, the unit is byte. Since it will be

cut into many parts, you can put these commands in scripts, for example, name it usb_upgrade_emmc.txt, and then pass

The following command executes the instructions contained in the scripts in the USB drive:

usb start

mtkupgrade usb -script usb_upgrade_emmc.txt

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 18
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

4. Experience Sharing on Fusion EMMC Master Production

TCL
Notice:

MediaTek Confidential Release fo

1. Use TFTP to upgrade the master (the reason is: USB upgrade will not completely re-upgrade all partitions

by default). 2. After the master machine is upgraded and started, no actions can be performed, such as: 1. Start the APP (will generate user

encryption behavior or generate a unique ID for the machine, etc.) 2. Plug in the USB to upgrade the DRM Key, etc. This will make the

dumped

data unusable. 3. The master production principle and steps are the same as Mstar. The main difference is the Fusion system. The Mboot

Bin Size has been adjusted, and the corresponding parameters and Tools need to be updated. Others remain unchanged.

4.1 Make emmc.bin

4.1.1 EMMC is less than 4G

1) Determine the port number of the USB flash drive.

TCL
After inserting the USB flash drive (formatted as FAT32, the capacity should not be less than the total capacity of EMMC), use the command to determine the USB port

MediaTek Confidential Release for

#usb start [port number] For example, to confirm whether it is plugged into port 1, enter

#usb start 1

If the device found is printed, port 1 is currently used.

2) Use the emmcbin command to copy the data in the EMMC to the USB disk file.

#emmcbin [port number]

For example, using port 1 above, input

#emmcbin 1

After the progress bar is completed and the dump is prompted to be completed, a file named emmc.bin will be generated under the USB flash drive, and the size is consistent

with the EMMC capacity (the emmc capacity can be queried through the mmc size command).

4.1.2 EMMC greater than 4G TCL

MediaTek Confidential Release for
1) After inserting the USB flash drive (formatted as FAT32, the capacity should not be less than the total capacity of EMMC), if you are not sure

which USB port to insert it into, you can first use

#usb start [port number]

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 19
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

Command confirmation, for example, to confirm whether it is plugged into port 1, enter

#usb start 1

If the device is found, port 1 is currently used.

TCL
MediaTek Confidential Release fo
2) Use the mmc dd command to copy the EMMC data to the USB drive.

dd mmc2usb [port number] #mmc

For example, using port 1 above, input

dd mmc2usb #mmc 1

After the copy is completed (prompted 100%), remember the total size (number of blocks) dumped, which is actually the total capacity of the EMMC,

which will be given in the last line of the printout:

Dump Block: XXX

3) Use winhex on the PC to copy the dumped data in the USB disk to a file. Select Tools->Disk tools->Clone disk.

TCL
MediaTek Confidential Release for
Select the USB flash drive as Source and the newly created target file directory as Destination. Fill in 0 for Start sector, which means reading data from the beginning of the

USB flash drive. Note that the Number of sectors to copy here needs to be filled in with the size after "Dump Block:" in 2), then click OK and wait for the creation

to be completed.

4.2 Making the Master Film

The MBOOT partition data in the emmc.bin dumped from the mother chip is actually mboot.bin. Since the CustomerKeyBank in mboot.bin is

encrypted by the unique key in the efuse corresponding to the mother chip, the data of the MBOOT partition in emmc.bin needs to be restored to the original

mboot.bin.

TCL
In the console, use the program mbootnize to process it: (This step is different from the mstar tool, so you need to pay attention)

#./mbootnize mboot.bin emmc.bin new_emmc.bin

Parameter

description: mboot.bin: original mboot.bin.

MediaTek Confidential Release for

emmc.bin: data dumped from the motherboard.

new_emmc.bin: emmc.bin after replacing the MBOOT partition data.

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 20
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

4.3 Use the burner to burn TCL

Use a burner to burn the generated emmc.bin to the user area.

MediaTek Confidential Release fo

TCL
MediaTek Confidential Release for

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 21
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

5 Merak EMMC Master Production Experience Sharing

5.1 Emmcnize makes images

TCL
MediaTek Confidential Release fo
5.1.1 Mboot needs to open the following CONFIG

The following two CONFIGs need to be opened:

CONFIG_RELOAD_DEFAULT_ENV // The uenv.img generated by full build is empty. After opening this CONFIG, a set of default environment variable values will be reloaded after

uboot starts.

CONFIG_USERDATA_PARTITION_SELF_ADAPTION // userdata partition adaptation

5.1.2 If FDE is enabled, an FDE key is required

Each customer project needs to apply for an FDE key.

When Emmcnize creates a GANG image, you can bring in the FDE key to create an encrypted image.

5.2 Dump master to create image

TCL
MediaTek Confidential Release for
5.2.1 The USB flash drive of the dump master is not recognized by Windows PC

In the Merak architecture project, the partition table uses the GPT format, and Windows PC cannot recognize the USB flash drive with this GPT partition table. In actual

tests, when the USB flash drive is inserted into the PC, it cannot be recognized, and it cannot be selected using WinHEX. Therefore, for the Merak architecture solution, WinHex

cannot be used to create emmc.bin for the time

being. This problem needs to be solved.

5.2.2 Note that the mboot command must first turn off FDE

Before doing a dump operation in Uboot, you must first type the following uboot command to turn off FDE

emmc fde inactive //disable FDE function, the dumped data will be encrypted data

(In moot, you can enter cmd: emmc fde, and the fde status will be returned. If it returns inactive, it can be determined that the fde is currently closed.)

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 22
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

5.3 Simulate burning master image method

5.3.1 Mboot operation after FDE enable TCL

Before doing mmc write operation in Uboot, you must first type the following uboot command to turn off FDE

MediaTek Confidential Release fo

emmc fde inactive //disable FDE function, the data written afterwards will not be encrypted again

(In moot, you can enter cmd: emmc fde, and the fde status will be returned. If it returns inactive, it can be determined that the fde is currently closed.)

Since the kernel does not have a command to disable FDE, you cannot perform simulated burning operations under the kernel.

TCL
MediaTek Confidential Release for

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 23
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

6 Summary of ECSD setting requirements for programmers

TCL
EMMC has several important ECSD registers, which are strongly related to boot and need to be filled in according to the requirements of the SOC solution.

If you are required to fill it in, the startup will fail.

MediaTek Confidential Release fo

ÿ If you use MTK tool (Graffito or ISP tool) to burn, the tool will automatically rewrite the EMMC ECSD key registers

device.

ÿ If it is a factory-made programmer, you need to notify the programmer manufacturer to modify the key registers of MMC ECSD.

The following ECSD register requirements are the same for both Fusion and Merak projects.

ECSD Value describe The impact of incorrect settings

Bit[1:0] ÿÿ 2ÿ x8 bit width boot mode

ECSD[177] 0x02 Startup failed, no log
Bit[4:3] ÿÿ 0ÿ backward compatible speed

ECSD[162] 0x01 Bit[1:0] is set to 1, HW reset enable Startup failed, no log

ECSD[179] 0x08
TCL
Bit[5:3] is set to 1, Boot partition 1 for boot fails to start, no log

MediaTek Confidential Release for

ECSD[167]
0x01
or
Bit[4:0] represents the selection of each partition.
write reliability settingsÿ The mboot startup will fail.
At least BIT[0] needs to be written to 1 to ensure that the User Area is open Need to re-burn
0x1F
write reliability

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 24
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

7. Case sharing of problems encountered:

TCL
Since the operation is divided into three steps, the positioning process is also divided into three steps. You can refer to them one by one.

MediaTek Confidential Release fo

7.1 Make emmc.bin

This step is to dump the data in EMMC to the USB disk. If the problem of MBOOT part not found appears, it may be

This is the problem. How to confirm:

Take the emmc.bin produced by the customer and have a look. Since the image may be too large to open, you can use

dd if=emmc.bin of=emmc_10M.bin count=10000 bs=1024 Get the first 10M of the image, then open the image and find

Go to 2M (200000) and check whether it is mboot data. Figure 1 in the figure below is OK, and Figure 2 is wrong.

Secondly, you can take a general look at the data. Because there is a Windows tool like winhex in the operation process of 1.2, you may see it when an error occurs.

Obvious mistakes, such as del+alt+ctrl, which is an obvious window operation.

Figure 1 (OK):

TCL
MediaTek Confidential Release for

Figure 2 (error):

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 25
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

7.2 Making a Master Film

TCL
MediaTek Confidential Release fo
Although this step only has one sentence:

Question!!! The
#./mbootnize mboot.bin emmc.bin new_emmc.binÿ However, each parameter has a problem

issues that need attention are as follows:

1) Mbootnize Due to

the change of times, there are two versions of this tool. The difference is whether the size of MBOOT is 3M or 5M. Many customers currently only have the 3M version.

So when mboot is larger than 3M, the following error will occur

$ ./mbootnize mboot.bin EMMC.BIN new_emmc.bin

mboot file length:4070839

mboot file size 4070839 too large , can not larger than 3145728

When you encounter this problem, use 5M mbootnize, the link is as follows

The command is changed to ./mbootnzie mboot.bin emmc.bin new_emmc.bin 5

Please contact MediaTek Technical Support.

TCL
2ÿmboot.bin

MediaTek Confidential Release for

The mboot.bin and the image used to make the master must be the same set, otherwise various problems will occur due to mismatch.

For example: after burning, the computer is turned on and stuck at the startup logo, etc.

3ÿ emmc.bin

See the previous section on location records

4ÿ new_emmc.bin

The final master chip cannot be verified because Mediatek does not have a burner. You can use the following method to do a simple verification:

(1). Prepare to make the master chip emmc_new.bin

(2). Write the prepared master software to the USB disk in the server

sudo dd if=emmc_new.bin of=/dev/sdb bs=1M

(3). Burn the master chip software to the mainboard

mmc dd usb2mmc 0 1
TCL
7.3 Using the burner to burn

MediaTek Confidential Release for

Use a burner to burn the generated emmc.bin to the user area.

MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 26
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

TCL
MediaTek Confidential Release fo

TCL
MediaTek Confidential Release for

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 27
Machine Translated by Google

MTXXXX (Product Name)

MediaTek_TV_EMMC mass production method description

Exhibit 1 Terms and Conditions

Your access to and use of this document and the information contained herein (collectively this “Document”) is subject to your (including the corporation or other legal entity

TCL
you represent, collectively “You”) acceptance of the terms and conditions set forth below (“T&C”). By using, accessing or downloading this Document, You are
accepting the T&C and agree to be bound by the T&C. If You don’t agree to the T&C, You may not use this Document and shall immediately destroy any copy
thereof.

MediaTek Confidential Release fo

This Document contains information that is confidential and proprietary to MediaTek Inc. and/or its affiliates (collectively “MediaTek”) or its licensors and is provided solely
for Your internal use with MediaTek’s chipset(s) described in this Document and shall not be used for any other purposes (including but not limited to identifying or providing
evidence to support any potential patent infringement claim against MediaTek or any of MediaTek’s suppliers and/or direct or indirect customers). Unauthorized use or
disclosure of the information contained herein is prohibited. You agree to indemnify
MediaTek for any loss or damages suffered by MediaTek for Your unauthorized use or disclosure of this Document, in whole or in part.

MediaTek and its licensors retain titles and all ownership rights in and to this Document and no license (express or implied, by estoppels or otherwise) to any intellectual
propriety rights is granted hereunder. This Document is subject to change without further notification. MediaTek does not assume any
responsibility arising out of or in connection with any use of, or reliance on, this Document, and specifically disclaims any and all liability, including,
without limitation, consequential or incidental damages.

THIS DOCUMENT AND ANY OTHER MATERIALS OR TECHNICAL SUPPORT PROVIDED BY MEDIATEK IN CONNECTION WITH THIS DOCUMENT, IF ANY, ARE
PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE. MEDIATEK SPECIFICALLY DISCLAIMS
ALL WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, FITNESS FOR A PARTICULAR PURPOSE, COMPLETENESS OR ACCURACY AND ALL
WARRANTIES ARISING OUT OF TRADE USAGE OR OUT OF A COURSE OF DEALING OR COURSE OF PERFORMANCE. MEDIATEK SHALL NOT BE RESPONSIBLE
FOR ANY MEDIATEK DELIVERABLES MADE TO MEET YOUR SPECIFICATIONS OR TO CONFORM TO A PARTICULAR STANDARD OR OPEN FORUM.

Without limiting the generality of the foregoing, MediaTek makes no warranty, representation or guarantee regarding the suitability of its products for
any particular purpose, nor does MediaTek assume any liability arising out of the application or use of any product, circuit or software. You agree that

TCL
You are solely responsible for the designing, validating and testing Your product incorporating MediaTek’s product and ensure such product meets applicable standards
and any safety, security or other requirements.

The above T&C and all acts in connection with the T&C or this Document shall be governed, construed and interpreted in accordance with the laws of

MediaTek Confidential Release for

Taiwan, without giving effect to the principles of conflicts of law.

TCL
MediaTek Confidential Release for
MediaTek Proprietary and Confidential. © 2022 MediaTek Inc. All rights reserved. Unauthorized reproduction or disclosure of this document, in whole or in part, is strictly prohibited. 28