Introduction of MTK Tools V2 PDF

Introduction of MTK Tools
Jackson Liang
2006/12/20
Agenda
Introduction of Catcher tool
Basic operation of catcher
Catcher debug usage
AT Command tool bar
Introduction of Meta tool
Brief introduction of Meta
Meta Lab introduction
Meta factory introduction
Introduction of MTK download tools
Brief introduction of brom, brom.dll and DA
Usage of Flash tool
Brief introduction of multiple bin mechanism
Usage of Multi-port download tool
Introduction of ATE tool
Brief introduction of MTK production test solution
How to setup production line test station for RF Calibration and Final test
Usage of ATE
Introduction of SN Station tool
Brief introduction of SN Station tool
Usage of SN Station tool
Q&A
COMPANY CONFIDENTIAL, Page 2
Introduction of Catcher
What is catcher?
Catcher is a PC-side tool for MTK GSM/GPRS Products.
The main purpose of Catcher is for logging primitives and debug
information. Engineers can use Catcher to analyze the behavior of
mobile phones.
N.B: Before using catcher, please remember to set TST UART Port
to UART 1.

Basic operation of catcher (1)
Step1:Set database
Step2:Set logging mode

Basic operation of catcher(2)
Step3: Configure RS232

Basic operation of catcher(3)
Step4: Start connect
Step5:Select the correct filter

Catcher default filter
User can select what type of log they want to catch and select the
type from the List.

Catcher debug usage (1)
Catcher will cache the log according to which filters has been set.

User can cache the assert procedure by catcher.
Assert :
Assert()


AssertIdle
Engineer ModeTST UART
TST UART1

After connecting with the target, Catcher receives notification of
any valid exception records in the NVRAM and shows them in the
Sys Trace window.
When the user press the read button, Catcher receives the
corresponding primitive log messages and decodes the exception
records into their data structures according to their exception type.
Pressing the Reset button deletes all exception records in NVRAM.

AT Command Toolbar
The AT Command toolbar allows the user to send AT commands to
the protocol stack. The AT command may only be sent after the
catcher is on-line and connected to a target mobile phone.

Introduction of Meta
What is Meta?
Meta (Mobile Engineering Testing Architecture) application is composed
of Meta LAB and Meta factory. Both Meta Lab and Meta factory are the
windows application at PC side.
Meta LAB offers versatile testing features in RF TX/RX/AFC control,
NVRAM access testing and editing, audio related functions, BaseBand
related functions, MMI data download, IMEI download, getting hardware
and software version, barcode download, updating parameter, FAT editor
and database change list. All Meta LAB testing procedure should be
operated manually due to no specific equipment control.
Meta factory provides the RF calibration and ADC calibration function
required in factory mass production line and Ag8960, R&S CMU200 and
Power Supply control will be supported.

META Target Tasks
There are only the following five tasks wake up in Meta Mode:
FT task
TST task
MEDIA task
L1 audio task
NVRAM task

Meta Lab introduction (1)
Software architecture

RF Tool
Totally, there are ten RF sections in the RF tool
1. PM: Used to measure the RX power transfer from the Radio Tester
2. GainSweep: Used to measure the RX power in different gains
3. Continous RX: Used to do the target continous RX quality
4. Continous TX: Used to control the target transmit power
5. TX Level and profile: Used to measure the TX power of the target by using
Radio Tester
6. AFC Control: Used to do AFC control
7. AFC DAC Sweep: Used to get the best AFC DAC value
8. Crystal AFC control: Used to do Crystal AFC control
9. Crystal AFC Sweep: Used to do the Crystal AFC calibration
10. Multi Slot TX: Used to control target TX in multi Time slot

NVRAM Testing
User can use this function to access and edit three kinds of NVRAM
Data. There are System related Data , L1 Data and other data.

Audio function
There are many audio functions supported by Meta. They are acoustic
FIR-coefficient, additional output FIR-coefficient, AMR FIR-coefficient,
melody FIR-coefficient, audio testing ,ring composer, play song in FAT,
play song using ID, customer volume setting, acoustic FIR tuning and
Melody FIR tuning.

BaseBand function
There are three following parts in this function.
Auxiliary ADC: Used to do ADC calibration manually
Register Read/Write: Used to read or write the BB register value
Battery Level: Used to modify the battery level value

MMI Data Download
User can use MMI data download window to download full screen ,
associate, EMS , midi and iMelody files to FAT from PC Side.

IMEI download
User can use IMEI download window to write IMEI into target or read
out the IMEI of target .
Barcode download
User can use Barcode download window to write SN into target or read
out the SN of target .

Get Version
User can use Get Version window to get version of BaseBand, ECO,
DSP firmware, DSP patch ,software , Hardware , Melody from target.

Update parameter
User can use update parameter window to upload/download RX path
loss, AFC, APC and ADC calibration parameter or load/save RX path
loss, AFC ,APC and ADC calibration from/to file.

FAT Editor
User can use FAT editor window to read ,write ,delete files in FAT and
get FAT disk information which contains sector per cluster, FAT total
size and FAT free space.

DataBase Change
User can use database change window to get database change list
between two NVRAM database files and FAT free space.

Setting
User can use setting function to get/set target setting.

Meta factory introduction (1)
Software architecture

In Meta factory mode, Meta controls Agilent 8960, R&S CMU200,
Power Supply and target to do calibration procedure. Before using
this mode, user must install driver of GPIB card and Visa.
The Meta factory mode current support:
Agilent 8960 with GSM only mode (E1960A) and GSM/GPRS combine
mode (E1968A)
CMU200
Agilent 663x2 series power supply
Agilent 661x series power supply
Agilent and NI GPIB Card



Introduction of Download Tool
The component of Flash Tool
Flash tool requires four parts, one is Flash tool. exe, the others
are BROM DLL, DA and scatter file.
Flash tool.exe
Flash_tool.exe is only the UI program of Flash tool. It requires BROM DLL to
all the Flash tool operations.
BROM DLL
Brom.dll is the kernel library of Flash_tool.exe, it is in charge of all the main
functions to do BootROM handshake, DA downloading and DA handshake.
DA (Download Agent)
z Flash tool will download DA into targets internal SRAM and execute
z MTK_AllInOne_DA.bin Support all MT6205B, MT621X, MT62XX
BB chip projects.
Scatfile
z The starting address of ROM should be same as the built image.
Flash tool executable file

What is Boot ROM?
Description
z Every MTK base-band chips embed a Boot ROM, which is used to store
a simple boot program. Internal BOOT ROM will be selected if BOOT
pin (GPIO0) is tied to GND once reset.
z The Boot ROM contains a small program for downloading data via
UART, and this feature is applied to download program or factory
testing. Purpose of Boot ROM is to interpret commands received from
UART1.
z The Boot ROM is useful in the absence of off-chip memory or when the
external Flash memories have not been initialized yet.
Configuration
z Boot ROM code is executed in ARM 32 bit mode, and the stack is
allocated at 0x40000000~0x400007ff.

What is BROM_DLL?
The Flash Tool is developed base on the kernel library BROM_DLL.
Flash Tool
( UI Program )
RS232
Binary BROM_DLL
Load Kernel
BROM DLL is multi-thread safe library and it is designed to provide

the functionality of BootROM handshaking and flash download/read
back/format.
BROM DLL provides two target boot modes, one is META mode;
the other is FlashTool mode.
Boot_META will trigger target to boot up to META mode for
META testing; Boot_FlashTool will download the DA into target
and then user can perform flash download/read back/format
operations.
What is DA?
DA is a target side agent
After DA is successfully downloaded and running on target, it will be
standby and passively waiting BROM DLL to issue flash download, read
back or format command via UART.

What is Scat file?
A simple sample of scat file is as follows:
ROM 0x0
{
}
Flash tool will parse the scat file to get the name of the Load and the download
start address of flash.

Flash Tool Feature List
Flash Tool supports the following features.
Support NOR flash download/read back/erase operation.
Support NAND flash download/erase operation.
Support most popular NOR flashes in the world.
Both of AMD family and Intel family flash.
High-Speed download.
Support high-speed baud rate download up to 921600bps.
Support MBA (Multiple-Binary-Architecture) download.

How to download at high-speed baud-rate?
1) Install a general high speed RS232 card
2) Use USB-To-COM bridge cable.

Usage of Flash tool (1)
1) Choose the DA file, Scat file and ROM file 3) Choose COM Port
2) Choose the Bard-rate 4) Choose NOR/NAND Operation mode

Usage of Flash tool -Download
1) Power off target first
2) File/Open download agent file
3) File/Open scatter-loading file
4) Assign load regions you want to download
5) Press download button
6) Power on target

Usage of Flash tool -Read back
3) Assign read back file
4) Select which file you want to read back
5) Press read back button
6) Power on target

Usage of Flash tool Format Type (1)
Format Type
Do Not Format FAT
If select this option, Flash Tool will not erase the FAT area.
Reset to factory default
If select this option, Flash Tool will do the following things:
1) Restore the DataItem with NVRAM_CATEGORY_FACTORY
2) Restore certain byte/short/double value to default value in
NVRAM cache data items.
There are three functions in the nvram_user_config.c:
void nvram_restore_byte_cache(kal_uint8 *buffer){}
void nvram_restore_short_cache(kal_uint16 *buffer){}
void nvram_restore_double_cache(kal_uint32 *buffer){}
3) Delete the folder defined in NVRAM_CLEAN_FOLDER_LIST[] in
nvram_user_config.c:

Usage of Flash tool Format Type (2)
Auto Format FAT
If select this option , Flash Tool will format FAT by the area defined in Flashconf.c.
#define FLASH_BASE_ADDRESS 0x0E00000
#define ALLOCATED_FAT_SPACE 0x200000
Note: Please use the following syntax in flashconf.c

#define ALLOCATED_FAT_SPACE 0x200000
but dont use the following syntax:
#if 0
# defin FLASH_BASE_ADDRESS 0x0x700000
#else
#endif
Manual Format FAT

If select this option , user can define which FAT area he want to format.

Usage of Flash tool -Format
3) Press format button
4) Configure the format range
5) Power on target

Two Mode of Flash tool
1Test Mode: CTRL+ALT+A (only for Nor flash)
2 Debug Mode: CTRL+ALTT

Multiple bin mechanism
MBA V2.0 is an enhanced version of MTK multiple binary architecture
support.
Enabling multiple bin is simple and involves only 3 steps:
- #define MULTIPLE_BINARY_FILES in
\mcu\custom\system\[PROJECT]\custom_jump_table.h
- Add multiple BINs sections in the scatter file
- Clean and remake the following modules: custom, mmiresource and plutommi
There will be 4 BINs in the build folder:

ROM : Code and most data
LangPack_ROM: Strings, Fonts and IMEs
CustPack_ROM: Customized NVRAM settings, audios, images and WAP/MMS
settings
JUMP_TABLE: the system jump table for accessing the BINs

Usage of Multi-port download tool (1)
Multi-port download tool is used in production line for
download Bin file . It supports most 16 COM Port to
download at the same time.
Multi-port download tool is base on flash tool ,so it has the
same function of flash tool.
Support NOR flash download/erase operation.
Support NAND flash download/erase operation.
Support most popular NOR flashes in the world
Both of AMD family and Intel family flash.
High-Speed download.
Support high-speed baud rate download up to 921600bps.
Support MBA (Multiple-Binary-Architecture) download.

Usage of Multi-port download tool (2)
All the setting of Multi-port download tool is set in the file
MultiPortFlashDownloadProject.INI.
1. TheFirstComPortNo=3
Please set the first COM port according to actual status here.
2. Format FAT begin address = 0x00E00000
Format FAT length = 0x00200000
If Format FAT Option is Manual and Operation is NOR, please set
NOR flash format FAT information here.
3. NAND format FAT begin address = 0x02000000
NAND format FAT length = 0x06000000
If Format FAT Option is Manual and Operation is NFB, please set
NAND flash format FAT information here.
Auto polling
If select Auto polling ,after finish downloading one handset , what you
need to do is just pull out the handset and connect another handset
waiting to downloaded. You dont need to click Start button again.

Introduction of ATE
Environment Request
1) PC OS:
MS Windows 2000 or XP
2) Hardware:
Pentium III or above PC
Radio Tester: AG 8960 , CMU200,CMD55, MT8820A,WT4400
. Power Supply: AG663x or AG 663xx, Keithley 230x , NGSM
3) Software:
NI (National Instruments) GPIB driver Ver 2.2.10 or later Version
. NI Visa Ver 3.0 or later version

MTK Production line test solution

UI of ATE
Calibration or Final test setting
Test Setting button
Initial Button

Function of ATE
Calibration test include calibration and check result for
MTK chipset, such as AFC calibration, Pathloss Calibration,
APC calibration, ADC Calibration.
Final test include GSM/GPRS signaling test, such as power
measurement, modulation measurement, spectrum
measurement and BER measurement, and for the GPRS part
include Test Mode B and BLER(CMU200) and Type B and
BLER(Agilent 8960)
Combined calibration(META mode) and final test(Normal
mode) for reducing change test station

RF Calibration and Final test Setup
Support Hardware:
Power Supply
R&S NGSM
Agilent 663xx
Keithley 230x
NGSM
Radiocommunication Tester
R&S CMU200
Agilent 8960
CMD55
WT440
MT8820A

Report & System Setting (1)

Fast Power Measurement (CMU 3.50)
When you use CMU200 to do Cal or Final test, remember to select
this option to speed up the power measure rate.
Wireless test
If you want to do wireless test, remember to select this option.
GSM Default Items
If select this option, ATE will do the default items RF Final test
defined in the MTK_xxxxx_SETUP.ini.
Stop Condition
If select this option, ATE will stop testing immediately while one test
item cant pass . In production line, this option should be pitched on
always.

RF Final Test with Check Bar Code
If select this option, ATE will not continue to do final test while
calibration result is fail
Final Test with IMEI Write
If you want to write IMEI to handset before doing final test, select
this option.
Add Cal Status
If select this option, ATE will add 10 ( calibration pass) or 01
(calibration fail) flag behind barcode after Calibration.

Band
You can select which band need to do calibration here.
RX
Only select AFC Cal and Pathloss Calibration here.
TX
RFMD GSM
If the handset use RFMD series PA ,please select this option
SKY GSM (77328)
If the handset use Sky77328 series PA ,please select this option
RENESAS GSM
If the handset use Renesas series PA ,please select this option
Full PCL GSM
Select this option will do all PCL Apc calibration
APC Cal Check
Select this option will check the power of all PCL after APC calibration
ADC Cal/PSU Ctrl
Select this option will do ADC battery and charger calibration.

Final Test Setting
GPRS Test
Select this option will do GPRS Test
GSM850 FinalGSM900 FinalDCS1800 FinalPCS1900 Final
Please select which band you want to do RF Final test here

Test MODE Select
If want to initialize ATE manually, please Select Manual Initialize
If want ATE initialize Final test automatically, please select GSM Test
If want ATE initialize Calibration test automatically, please select
Calibration Test
If want ATE initialize Cal and Final test automatically, please select
Calibration & GSM Test.
Three Unit Calibration is hold for future use.
Bar Code Get Type When Calibration
If want to get barcode from handset NVRAM, please select Get From
NVRAM and the barcode of all calibrated handset will be the same.
If select Auto Bar Code with Date & Batch, ATE will write the PC date plus
Batch into handset NVRAM as barcode.
Batch is define in MTK_XXXXX_SETUP.ini .
If want to scan Barcode manually, please select Scan Barcode .
Check fixture close is hold for future use.

PowerSupply Type
Please select the Powersupply type used in your production line here.
Radio Communication Tester
Please select Radio Communication Tester type used in your
production line here.
BaseBand Chip Type
ATE V5.0.3 or later version supports all MTK BB Chip type. You may
select AutoDetect except handset use 6205B BB Chip.
If the handset use 6205B BB Chip, please select 6205B in this option.
CMU Measurement Port
Just keep the type as RF2.
PowerSupply GPIB Address
Here shows the power supply GPIB address. The address is set in the
Mtk_XXXXB_setup.ini file.
Cal INP loss and Cal OUP loss
Must select these two options always.
NVRAM Database file
Please select the database file like the following format BPLGUInfoxxxxxx
here . The version of the database file should be the same as the bin file.
Config File location
Please select the CFG file here.
Calibration file Location
Please select the Calibration.ini file here.
Test Setup file Location
Please select the MTK_xxxxx_SETUP.ini file here.
Test Report Location
Please select the location where you want to store the test report here.
Default location is: C:\Program Files\MTK_atedemo. Suggest to change it.
Report DataBase Location
Just keep the file: C :\Program Files\MTK_atedemo\6218B_statistics.xls
here.

Final Test Configuration Panel (1)
2 3

Final test Configuration Panel (2)
There are only three places perhaps need to modified in this
panel according to actual status.
Call Type
MO Call
If select MO call, ATE will control handset to dial 112 connect the
Radio communication tester while doing final test.
MT Call
If select MT call, you should plug a Test SIM card into the handset. And
Radio communication tester will call handset while doing final test.
RX Quality
Please input the RX Meas Level here. The default value is -102.
Cable loss setting
Please input the RF Signaling cable loss of CMU200 here.

Calibration Configuration Panel
Please input the RF Non signaling cable loss of CMU200 here.

Usage of ATE-Related files
There are following three files related to ATE:
.INI File
.CFG File
SETUP.INI File

Usage of ATE Cal.ini File
This file contains all initialized data for calibration test.
At the beginning of calibration, ATE will write the data of this file
into handset NVRAM to be close to the target value.
This file should be modified the Power Ram Table by your RF
engineer.

Usage of ATE - CFG File (1)
This file contains all calibration setting data. There are following
several place perhaps need to be modified in this file:
[8960 Initialization]
8960 GPIB Address = GPIB0::15::INSTR
Please set the Ag8960 GPIB address here.
[RX path loss table]

GSM850_MAX_RX_LOSS = 5.0,5.0,5.0,5.0,5.0,3.0,3.0,3.0,3.0,3.0,3.0,3.0,
GSM850_MIN_RX_LOSS = -5.0,-5.0,-5.0,-5.0,-3.0,-3.0,-3.0,-3.0,-3.0,-3.0,-
3.0,-3.0,

Please set the RX Path Loss limit table here.

Usage of ATE - CFG File (2)
[TX PCL table]
The red circle section perhaps need to be modified according to

actual status.
[ADC table]
CHARGER_CHANNEL = 1
If handset BB chip is 6205B, please set the : CHARGER_CHANNEL = 3
else CHARGER_CHANNEL = 1
ADC_RESISTANCE = 0.33
Please set the ADC_RESISTANCE as 0.33 or 0.4 according to the
handset schematic
Usage of ATE - setup.ini File (1)
There are following place perhaps need to be modified in this file:
[System Setting]
CMU Base GPIB Address = 20
Power Supply Address = GPIB0::5::INSTR
Please set the CMU200 and Power Supply GPIB Address here.
[Call Setup Configuration]
Setup Network = 1
If Setup Network= 1 final test begins from GSM900
else if Setup Network= 4 , final test begins from GSM850
Triband Test Type = b
If b=0, ATE will do GSM900/1800/1900 triple band final test

Usage of ATE setup.ini File (2)
[Final Test TX Check]
Please set the RF Final Test Power Limit here.
Please set the Ag8960 RF cable loss here.

Introduction of SN-Station tool
What is the feature of SN-Station tool?
SN Station tool supports the following features:
1. Write Barcode/IMEI/BD Address
2. Do the BT Loopback1 ,Loopback2 test
3. Write audio parameters

Two modes of SN-Station
One is Meta Mode and the other is Normal Mode.
1. While writing Barcode or IMEI number, both two modes are support.
2. While writing BD Address , Only meta mode is support.
3. While doing BT Loopback1 or Loopback2 test, Only Normal mode is
support.
4. While writing audio parameters, Only Meta mode is support.

Usage of SN Station Tool -Meta Mode
Lets use writing IMEI number in Meta Mode as an example:
1. Select IMEI in the Write Select list
2. Select the right COM port and Baud-Rate.
3. Select Meta Mode in the MODE Select List
4. Select the NVRAM Database file and Initialize it
5. Press the Start button and scan into the IMEI number
6. Power on to let the handset into Meta mode
7. If write success, the write Bar code/IMEI done LED will change to
blue, else change to red

Usage of SN Station Tool -Normal Mode
Lets use writing IMEI number in Normal Mode as an example:
1. Select IMEI in the Write Select list
2. Select the right COM port and Baud-Rate.
3. Select Normal Mode in the MODE Select List
4. Press the Start button and Scan into the IMEI number
(Dont need to initialize NVRAM)
5. Power on the handset to enter Normal mode
6. If write success, the write Bar code/IMEI done LED will change to
blue, else change to red

Q&A

Thats All
Thank you!

Introduction of MTK Tools V2 PDF

Uploaded by

Copyright:

Available Formats

Introduction of MTK Tools V2 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Introduction of MTK Tools V2 PDF

Uploaded by

Copyright:

Available Formats

Introduction of MTK Tools

COMPANY CONFIDENTIAL, Page 4

Step2:Set logging mode

COMPANY CONFIDENTIAL, Page 5

COMPANY CONFIDENTIAL, Page 6

Step5:Select the correct filter

COMPANY CONFIDENTIAL, Page 7

COMPANY CONFIDENTIAL, Page 8

COMPANY CONFIDENTIAL, Page 9

COMPANY CONFIDENTIAL, Page 10

COMPANY CONFIDENTIAL, Page 11

COMPANY CONFIDENTIAL, Page 12

COMPANY CONFIDENTIAL, Page 13

COMPANY CONFIDENTIAL, Page 14

COMPANY CONFIDENTIAL, Page 16

COMPANY CONFIDENTIAL, Page 17

COMPANY CONFIDENTIAL, Page 18

COMPANY CONFIDENTIAL, Page 19

COMPANY CONFIDENTIAL, Page 20

COMPANY CONFIDENTIAL, Page 21

COMPANY CONFIDENTIAL, Page 22

COMPANY CONFIDENTIAL, Page 23

COMPANY CONFIDENTIAL, Page 24

COMPANY CONFIDENTIAL, Page 25

COMPANY CONFIDENTIAL, Page 26

COMPANY CONFIDENTIAL, Page 27

COMPANY CONFIDENTIAL, Page 28

COMPANY CONFIDENTIAL, Page 29

COMPANY CONFIDENTIAL, Page 30

COMPANY CONFIDENTIAL, Page 31

COMPANY CONFIDENTIAL, Page 32

COMPANY CONFIDENTIAL, Page 35

COMPANY CONFIDENTIAL, Page 36

BROM DLL is multi-thread safe library and it is designed to provide

COMPANY CONFIDENTIAL, Page 38

COMPANY CONFIDENTIAL, Page 39

COMPANY CONFIDENTIAL, Page 40

COMPANY CONFIDENTIAL, Page 41

2) Choose the Bard-rate 4) Choose NOR/NAND Operation mode

COMPANY CONFIDENTIAL, Page 42

COMPANY CONFIDENTIAL, Page 43

COMPANY CONFIDENTIAL, Page 44

COMPANY CONFIDENTIAL, Page 45

Note: Please use the following syntax in flashconf.c

Manual Format FAT

COMPANY CONFIDENTIAL, Page 46

COMPANY CONFIDENTIAL, Page 47

COMPANY CONFIDENTIAL, Page 48

There will be 4 BINs in the build folder:

COMPANY CONFIDENTIAL, Page 49

COMPANY CONFIDENTIAL, Page 50

COMPANY CONFIDENTIAL, Page 51

COMPANY CONFIDENTIAL, Page 53

COMPANY CONFIDENTIAL, Page 54

Calibration or Final test setting

Test Setting button

COMPANY CONFIDENTIAL, Page 55

COMPANY CONFIDENTIAL, Page 56

COMPANY CONFIDENTIAL, Page 57