PL Feature - Boot Flash Loader - Um PDF

BU Feature
Boot & Flash Loader Software

Rev. 01.29 — 8 June 2010 User Manual
Document information
Info Content
Title BU Feature
Short title (1 line) BU Feature
Subtitle Boot & Flash Loader Software
Short subtitle (1 line) Boot & Flash Loader Software
Author(s) Michel Zamaron, Céline Finet, Martine Da Silva, Julien Beal, Frédéric
Craisson, Alexander Ulitskiy, Laurent Satta
Department BUMP - BLC - PL Feature, Sophia-Antipolis
Document ID PL-FEATURE_BOOT-FLASH-LOADER_UM
Document type User Manual
d
Revision number 01.29
Status Released
se
Security status For internal and customer use only
Keywords Flash, Memory, Download, Loader, Installer
Abstract
ea
Distribution information
el
Name Department Address

Laurent CONSEIL PL Feature LMS laurent.conseil@stericsson.com
Stéphane VAILLAND PL Feature LMS stephane.vailland@stericsson.com
R
Christophe MONTAUD PL Feature LMS christophe.montaud@stericsson.com

Miguel CASTRO PL Feature LMS miguel.castro@stericsson.com
Tristan BOYER PL Entry Rennes tristan.boyer@stericsson.com
Pascal LE GUENNEC PL Entry Rennes pascal.leguennec@stericsson.com
Additional information: This document explains how to install/uninstall and use the
Flash Loader software that allows to download a code in a memory device embedded
on a platform based on ST-Ericsson baseband families. Refer to Section 1.2
“Flashloader versions and applicable devices”.
For internal and customer use

ST-Ericsson BU Feature
For internal and customer use Boot & Flash Loader Software
only
Revision history
Rev Date Description Authors
01.29 08 Jun 10 Add precisions on upload command L. Satta
01.28 06 Apr 10 PL_ENTRY OTP: Reading OTP values from file L. Satta
01.27 19 Mar 10 Update PL_ENTRY OTP feature. Add burn/read OTP precedure for L. Satta
PL_ENTRY
01.26 09 Mar 10 Add PL_ENTRY OTP feature L. Satta
01.25 06 Jan 10 Update error codes description J. Beal
01.24 09 Dec 09 Applicable devices section updated and moved to document beginning F. Craisson
Sw backddor added
Target settings section updated (addresses both 7.2 and 7.3)
UART limitations: selection up to COM32
BootNand and SWboot versions section updated
Download in Onenand added
d
Section warning on exec in UART renamed
Main window screenshots updated
se
01.23 28 Oct 09 Security features section updated (explanation on USB dongles) F. Craisson
01.22 27 Oct 09 Add new target PNX4910. L. Satta
ea
01.21 8 Sep 09 Update after review. P. Mondoloni

01.20 19 Aug 09 Added new target PNX4908. Alexander Ulitskiy
01.19 15 jul 09 Add DDRAM memory target M. Zamaron
el
01.18 30 Jun 09 Corrections and updates in User Interface section F. Craisson

R
01.17 25 May 09 Add chapters for .msi use to un/install Flash Loader Martine Da Silva
01.16 02 Apr 09 Update on upload command F. Craisson
Screenshots updated (taken from 7.2.0)
CS0...CS3 replaced by EBI_CS0... EBI_CS3
01.15 27 Mar 09 Add chapter for Nandflash bad block management M. Zamaron
01.14 17 Mar 09 Update Flash database editor, add Flash parameter in-line help J. Beal
documentation description
01.13 06 Fev 09 Update for signature offset in NOR flash Michel Zamaron
01.12 05 Fev 09 Update for new security protocol between baseband and host for Michel Zamaron
PNX6529
Contact information
For more information, please visit URL: http://www.stericsson.com
or send an email to: michel.zamaron@stericsson.com
PL-FEATURE_BOOT-FLASH-LOADER_UM © NXP B.V. 2010. All rights reserved.
User Manual Rev. 01.29 — 8 June 2010 2 of 89

only
Revision history …continued

Rev Date Description Authors
01.11 08 Jan 09 Update cover page and contact information F. Craisson / J. Beal
Update references to “Applicable devices” chapter 5
Update devices part number and Bootrom location in figures n. 2 to 7
Update Scenario for consecutive download chapter 4.5
Update Limitations according to Multiple Download feature chapter 6
Update References chapter 7
01.10 11 Dec 08 Update jump delay specification Michel Zamaron
01.09 13 Nov 08 Change FlashLoader MMI, Add flash database description Michel Zamaron
01.08 23 October 08 Change FlashLoader MMI, Add CRC description for Nandflash Michel Zamaron
01.07 20 October 08 Add new field for partition table Michel Zamaron
01.06 07 October 08 Add USB Msg error handling Michel Zamaron
01.05 09 June 08 Add support PNX4901 (obsolete) Michel Zamaron
d
01.04 26 May 08 Add support PNX6516 Michel Zamaron
se
01.03 6 May 08 Update after doc review Julien Beal
01.02 10 Apr 08 1/Adding single and multiple download MMI latest functionnalities. Julien Beal
2/Update NAND Custom erase for First block specific case
ea
01.01 10 Apr 08 Creation from single download documentation Julien Beal

“mstbb_pcf5213_boot-flash-loader_um“ rev 06.07
el
R
Contact information

only
1. Introduction
1.1 Purpose and scope

This document describes how to install/uninstall and use the Boot & Flash Loader
software revision 7.2 and higher.
This document is intended to the customers of this software.
1.2 Flashloader versions and applicable devices

• Flashloader 7.2 - Applicable devices
– PNX65-09/11
– PNX65-08/13/15/16/17
– PNX52-20/22/25
– PNX5217
d
– PNX67-07/08/09/10/15
se
– PNX6715_Linux
• Flashloader 7.3 is obsolete
ea
• Flashloader 7.4 - Applicable devices

– All of the above
– PNX4908
el
– PNX4910
– PNX6529/6718
R
– PNX6729
1.3 Glossary
Acronym Definition
AES Advanced Encryption Standard
AUXPAR Auxiliary Parallel Interface
BB Baseband
BBM Bad Block Management
CS Chip Select
DLL Dynamic Link Library
EEPROM Electrically Erasable Programmable Read-Only Memory
FB First Block
MSI MicroSoft Installer
Contact information

only
1
Acronym Definition
2
NFI NAND Flash Interface 3
OTP One Time Programmable 4
5
RAM Random Access Memory 6
RCB Reservoir Control Block 7
SCRAM System Controller RAM 8
9
UART Universal Asynchronous Receiver Transmitter 10
USB Universal Serial Bus 11
12
13
1.4 Definitions 14
15
16
Name Description 17
Bad Block A process to manage Bad Block in a Nand Flash : if a Block is marked as 18
d
Management BAD, it should be re-mapped to a block in the Reservoir Control Block 19
(RCB). A structure in the RCB is duplicated and holds remapping 20
21
se
information: which bad block is remapped to which good block in the RCB.
22
Boot ROM Software launched after hardware Reset or Power-on
23
Boot NAND A small SW programmed in NAND memory (usually in the first 24
ea
pages of NAND) necessary to support the process of executing 25

other SW from NAND. The Boot NAND is loaded and executed in 26
SCRAM by the Boot ROM.Since execution in place is not possible 27
with NAND Flashes, the Boot Nand copies the code from NAND to 28
el
RAM either all or by pages (Page-On-Demand). 29

CTO/LIPP Former RTG internal supplier 30
31
R
Dongle Hardware device used to allow code downloading on protected IC

32
supporting a symmetric key security scheme. Flashloader provide interface
33
with such dongle and so Flashloader along with proper dongle connected to
34
PC host allows the user to download a protected device.
35
First Block The first 16 or 64 kBytes of NAND memory holding 36
Boot NAND SW and partition table and recopied by the Bootrom in SCRAM. 37
The size of a block depends on the flash memory (if it has small or lage 38
pages). 39
Flash High-speed block erasable EEPROM 40
41
Flash signature Used to guarantee flash contents integrity 42
Loader Software downloaded in RAM for flash programming 43
NOR flash Linear addressed device with individually addressed words of data, like 44
RAM, that allows execution in place 45
46
NAND flash Non-linear addressed device where the data and commands are 47
multiplexed on 8 I/O lines into the flash chip 48
NOR flash Binary This is the application file in “.bin“ file format 49
NAND flash “Binary” This is a group of files : The partition table file in “.ptt“ format, and partition 50
binary files pointed by the partition table. 51
52
Partition A logical part of NAND flash storage space that is used for a particular 53
purpose and treated as a whole. Partitions are defined in a Partition Table 54
Partition Table Contains partitions descritption and all parameters used to program or 55
erase partitions in a NAND flash 56
57

only
1
Name Description
2
Protected device Device with the security features enabled 3
Reservoir Control It is a special area at the end of the NAND flash address that contains 4
Block several blocks to be used in case of Bad Blocks in the normal area space. 5
6
RTG Re Use Technology Group, internal NXP supplier 7
Signature offset Address where to write the flash signature 8
Software reset e.g. a watchdog reset 9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
2. Description 1
2
The Flash Loader is a PC tool that allows to download code into a memory device (flash, 3
RAM, SCRAM, ...) embedded on a platform based on STE PNX baseband families. Refer 4
to Section 1.2 “Flashloader versions and applicable devices”. 5
6
7
8
2.1 Environment 9
In order to use the Flash Loader, the following equipment is required: 10
11
12
13
14
PC Dongle
15
L 16
L
D 17
r 18
e
d
d
a Baseband devices 19
Flash Loader o 20
L PNX…
Software h 21
s
se
la 22
F
23
24
RS232 / USB
ea
25
26
Application files User 27
Loader file 28
el
Config. File 29
Uploaded files 30
31
R
32
33
34
35
36
37
38
Fig 1. Flash Loader environment 39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
2.1.1 Software components

1
• PC with Windows 2000 or Windows XP Operating System 2
3
• Flash Loader application 4
• Flash Loader DLLs 5
6
• Binary file to download 7
• External Loader binary file (optional) 8
9
2.1.2 Hardware components 10
11
• HW platform including Baseband processor and memory 12
13
• Power supply for the Platform 14
• USB Dongle (optional, for secure ICs only) 15
16
• Serial cable and/or USB cable 17
• PC USB host controllers USB 1.1, USB 2.0(UHCI, OHCI, EHCI) 18
d
19
20
2.2 General principle of downloading 21
se
After hardware reset, the application part of baseband processor (CPU) starts executing 22
23
code from the on-chip Boot ROM (SCROM). This code initializes baseband processor and
24
checks if there is an external connection from the host PC to the baseband via the UART
ea
25
and/or USB ports. 26
27
If a connection has been detected, the baseband starts communication with the host PC 28
el
according to the protocol embedded in the SCROM. Typically the communication protocol 29
allows the host to ask baseband’s HW and SW versions, make SCROM to execute some 30
simple commands and load arbitrary data (code) to the available not-protected RAM. The 31
R
host PC may use this protocol to upload and pass the control to special embedded SW 32
which will then assist flash programming and other complex operations under the host 33
control. 34
35
If no connection has been detected, the SCROM finishes initialization and jumps to CS0 in 36
case of NOR boot, or copies the first pages of NAND to SCRAM and jumps to SCRAM in 37
38
case of NAND boot.
39
The software uploading process has some minor differences depending on the family of 40
41
chipsets and type of target memory device (NOR flash, NAND flash or RAM) and will be
42
described below. 43
44
2.2.1 PL Feature and PL Entry ICs: UART downloading process differences 45
While PL_FEATURE family of chipsets uploads data in binary format, the SCROM of 46
47
PL_ENTRY family (PNX4908, PNX4910) uploads data in the Intel Hex32 format only. But
48
the same amount of data in the Intel Hex32 format requires ~3 times more time to transfer 49
than in the binary form. Due to this reason and also because of historically taken 50
approach, in case of PL_ENTRY chipsets, the host PC uploads the embedded flash 51
loaders in SCRAM in two steps. First it uploads and runs a small auxiliary loader in the 52
Intel Hex32 format. Then the auxiliary loader makes the necessary CPU initialization and 53
RAM remapping and uses its own protocol to load the embedded flash loader in binary 54
format. 55
56
57

only
1
There is no principal difference in the host-target communication protocol between 2
PL_FEATURE and PL_ENTRY families. 3
4
However, for PL_Entry, all the downloads described in the following sections happen only 5
after an auxiliary loader has been loaded. 6
7
8
2.2.2 USB Back Door (for PL Feature basebands) 9
10
2.2.2.1 Hardware backdoor
11
On PL_FEATURE family, in order to make a host to target connection over USB when the 12
flash is not erased, the customer must use a backdoor.This backdoor consists in 13
pressing at the same time any three keys1 on the keyboard during the reset or power 14
ON sequence of the target. When the STOP button, on the Flash Loader MMI appears the 15
16
customer can release the keys. 17
18
2.2.2.2 Software backdoor
d
19
As the hardware backdoor can not be used on final products without keyboards, we have 20
21
se
introduced a software backdoor allowing to update a non-empty flash without pressing at
the same time different keys. That solution is based on an AT-command sent to the device 22
23
by the flashloader. A checkbox button has been added in the main FL window to enable
24
the software backdoor use. It can only work if the program already in flash is compatible
ea
25
with that AT-command: when the board connected to the PC boots, COM ports are 26
created waiting for a given AT-command to come. 27
28
el
29
30
31
R
32
33
34
Fig 2. Software backdoor checkbox 35
36
Note: the current implementation is only compatible with T3G boards and software. 37
38
39
40
2.2.3 Download into external RAM 41
42
The Boot ROM code receives data on the selected link (UART or USB) and copies them 43
directly into the external RAM memory. 44
45
The download of the data in RAM is made in several steps (see Figure 3 “Download in 46
RAM”). 47
48
• Step 0: After hardware Reset or Power-on, execution of the Boot ROM (BB & USB / 49
UART init) 50
51
• Step 1: The Boot ROM code checks an eventual connection with a host (PC tool) 52
53
54
55
56
1. For some ICs, two key press may be sufficient, to be confirmed. 57

only
• Step 2: The Boot ROM code downloads the binary file into RAM memory
1
2
3
4
5
Platform environment PC environment 6
Boot ROM mapped in 7
0x00000000 for PNX6511/PNX6515/PNX6516/4908/4910 8
0xFFFF0000 for PNX5222/PNX5217/PNX67xx/PRISM
9
10
0 Boot 1 PC tool 11
ROM 12
(Flashloader)
13
14
15
2 16
SCRAM Loader
17
18
d
19
RAM binary file
20
21
(e.g. CS1) binary file
se
22
23
24
ea
25
26
27
28
el
Fig 3. Download in RAM 29

30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
2.2.4 Download into SCRAM
3
The download into SCRAM is the same principle as with RAM memory. It is just a different 4
5
base address. The Boot ROM code gets data on the selected link (UART or USB) and
6
copies them directly into SCRAM. 7
8
The download of the data into SCRAM is made in several steps (see Figure 4 “Download
9
into SCRAM”). 10
11
• Step 0: After hardware Reset or Power-on, execution of the Boot ROM (BB, USB / 12
UART init) 13
15
• Step 2: The Boot ROM code downloads the binary file into SCRAM memory 16
17
18
d
19
21
se
Boot ROM mapped in
0x00000000 for PNX6511/PNX6515/PNX6516 22
0xFFFF0000 for PNX5222/PNX5217/PNX67xx/PRISM 23
24
ea
0 Boot 1
PC tool
25
ROM 26
(Flashloader)
27
28
el
29
30
2 Loader
SCRAM binary file 31
R
32
33
binary file 34
35
36
37
38
39
40
41
42
Fig 4. Download into SCRAM 43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
2.2.5 Download into NOR flash (single file and multiple file programming)
3
NOR Flashes can be programmed in the following ways: 4
5
• with a single file for execution in place (.cla file) 6
7
• starting with Flashloader 7.3 and 6529 ICs, with multiple files including a boot section 8
and partitions (.ptt selected as entry file in Flashloader MMI). The boot section will be 9
shadowed in SCRAM by the bootrom and executed. This is the same concept as 10
used for Nand programming described in Section 2.2.7. 11
12
To download into NOR flash, the principle is more complex and requires first to erase the 13
NOR flash contents (if the NOR flash is not virgin), then to send some write commands to 14
the flash. To do so a special software is needed: the Loader that is first loaded into 15
SCRAM then executed by the system controller. 16
17
18
The Loader allows to:
d
19
20
• Communicate with the host (PC tool) 21
se
• Detect the type of flash memory used 22
23
• Get the flash parameters from the flash database
24
ea
• Set the flash parameters into the embedded generic driver 25

26
• Erase the flash
27
• Program the flash 28
el
29
Remark: If the device used is a protected device the process is more complex. For more 30
details about this process see Section 2.3.5 “Download into NOR flash with a protected 31
R
device (PL_FEATURE family)”. 32

33
As characteristics (length, block, ...), commands and scenario programming are different 34
between different flash memories, it is necessary to have parameters set for the generic 35
Flash driver. This parameters are available through the Flash database. 36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
The download of the binary file is made in several steps (see Figure 5 “Download into 1
2
NOR flash”).
3
4
Note that for PL_ENTRY Step 2 is not relevant in UART mode and is replaced with a more
5
complex sequence as described in Section 2.2.1 “PL Feature and PL Entry ICs: UART 6
downloading process differences”. Thus Step 2 becomes “The Boot ROM code 7
downloads a first loader into SCRAM” and a Step 2.1 “The first loader downloads the 8
main Loader in SCRAM“ must be added. Then, from Step 3, the sequence is the same as 9
the one describes below. 10
11
• Step 0: After a hardware Reset or Power-on, execution of the Boot ROM (BB, 12
UART/USB init) 13
14
• Step 2: The Boot ROM code downloads the Loader into internal SCRAM 16
17
• Step 3: Execution of the Loader into SCRAM ( detects NOR flash type, Erase NOR 18
flash, ...)
d
19
• Step 4: The loader downloads either one binary file from the host and program the 20
21
se
NOR Flash (.cla file), or multiple files and program the different binaries in NOR
partitions (.ptt as entry file with a SWboot major version set to 5 and a SWboot minor 22
23
version set to 2)
24
ea
25
26
el
0x00000000 for PNX6511/PNX6515/PNX6516

29
0xFFFF0000 for PNX5222/PNX5217/PNX67xx/PRISM
30
31
R
0 Boot 1
PC tool 32
ROM 33
(Flashloader)
34
35
2 36
SCRAM 3
Loader 37
38
Loader
39
4 40
binary file
41
42
43
44
Ext. Flash 45
(e.g. CS0) binary file 46
47
48
49
Fig 5. Download into NOR flash
50
51
52
53
54
55
56
57

only
1
2
2.2.6 Download into DDRAM memory
3
To download into DDRAM memory, the principle is more complex and requires first to 4
5
initialize the SDI_SDRAM IP, then to write the data into the DDRAM memory.To do so a
6
special software is needed: the Loader that is first loaded into SCRAM then executed by 7
the system controller. 8
9
The Loader allows to: 10
11
• Communicate with the host (PC tool) 12
• Detect the type and the size of DDRAM memory used 13
14
• Erase or Reset the DDRAM memory (set DDRAM memory to 0xFF) 15
• Write the DDRAM memory 16
17
The download of the binary file is made in several steps (see Figure 6 “Download into 18
d
DDRAM memory”). 19
20
21
se
• Step 0: After a hardware Reset or Power-on, execution of the Boot ROM (BB,
UART/USB init) 22
23
ea
26
• Step 3: Execution of the Loader into SCRAM ( detects DDRAM memory and size, 27
Erase/Reset DDRAM memory, ...) 28
el
29
• Step 4: The Loader downloads the binary file from the host and write DDRAM memory
30
31
R
32
33
0x00000000 for PNX6511/PNX6515/PNX6516 36
38
0 Boot 1
PC tool 39
ROM 40
(Flashloader)
41
42
2 43
SCRAM 3
Loader
44
45
Loader
46
4 47
binary file
48
49
50
51
Ext. DDRAM
52
(SDI IP) 53
binary file 54
55
56
Fig 6. Download into DDRAM memory 57

only
2.2.7 Download into NAND flash

1
To download into NAND flash, the principle is similar to NOR flash except that different 2
binaries are downloaded into different NAND partitions instead of a unique binary file.The 3
input file is a partition file (.ptt). Nand flash device storage is divided into blocks and 4
pages. Each device consists of a large number of blocks, with each block divided into 5
pages. When the Nand Flash is shipped, it contains bad blocks (i.e. blocks that contain 6
7
one or more invalid bits, whose reliability is not guaranteed). Additional Bad Blocks may
8
develop during the lifetime of the device. Consequently, the Flash Loader had to support a 9
Bad Block Management (BBM) process. 10
A detailed description of the BBM is given in the Software Interface Specification for 11
NANDFLASH (Ref. 12 “NANDFLASH for Nexperia TM System Solution - Software 12
Interface Specification”) . The default Loader is used. 13
14
15
Remark: If the used device is a protected device, the process is more complex. For more 16
details about this process see Section 2.3.7 “Download into NAND flash with a protected 17
device (PL_FEATURE family)”. 18
d
19
Since characteristics (length, block, ...), commands and scenario programming are 20
21
se
different between different NAND flash memories, it is necessary to have parameters set
22
for the generic Flash driver.This parameters are available through the Flash database. 23
24
ea
25
The download of different NAND flash partitions is made in several steps (see Figure 7 26
“Download into NAND flash”). Step 0 to Step 4 are made at Power-ON 27
28
el
Note that for PL_ENTRY Step 2 is not relevant in UART mode and is replaced with a more 29
complex sequence as described in Section 2.2.1 “PL Feature and PL Entry ICs: UART 30
31
R
downloading process differences”. Thus Step 2 becomes “The Boot ROM code
downloads a first loader into SCRAM” and a Step 2.1 “The first loader downloads the 32
main Loader in SCRAM“ must be added. Then, from Step 3, the sequence is the same as 33
34
the one describes below. 35
36
• Step 0: After a hardware Reset or Power-on, execution of the Boot ROM (BB, 37
UART/USB init) 38
40
• Step 2: The Boot ROM code downloads the Loader into SCRAM 41
• Step 3: Execution of the Loader in SCRAM: 42
43
– Detect Flash type
44
– Get Flash parameters from flash database 45
46
– Set Flash parameters into embedded generic driver
47
– Initialize NAND Flash and get Reservoir Control Block 48
– Get the First Block data (contains BootNand, Partition Table, ..) 49
50
– Test Flash access and driver parameters 51
• Step 4...n: The PC sends sequentially to the Loader all the binaries to be programmed 52
53
into the appropriate partition. If the partition is protected, the header (the first 2 kbytes
54
of a partition first block) is AES encrypted by the Loader and written into the NAND 55
flash. 56
57

only
• Step n+1: When the Nand Flash is re-programmed, it is not always necessary to
reprogram its First block (FB). This first block is the block shadowed in SCRAM by the 1
2
Boot ROM and executed to mount the partitions. If an update of the FB is needed
3
(change in BootNand or signature or partition table has been detected), the PC sends 4
to the Loader the FB containing the partition table and the Boot NAND (see Ref. 12 5
“NANDFLASH for Nexperia TM System Solution - Software Interface Specification”) 6
7
8
9
11
14
0 Boot 1
15
PC tool 16
ROM
(Flashloader)
17
18
d
19
2
20
SCRAM 3
Loader 21
se
Loader 22
4 23
Partition x 24
ea
25
n
26
27
Partition y
28
el
NAND Flash n+1 29

onNFI or 30
First Block First block
AUXPAR 31
R
32
Fig 7. Download into NAND flash 33
34
2.2.8 Download into OneNand flash 35
36
Since 7.3 releases the Flashloader supports OneNand flash programming.The principle is 37
the same than the NAND one described in Section 2.2.7. 38
39
In that case, the input file is a partition file (.ptt) with a SWboot major version set to 5 and 40
a SWboot minor version set to 2. 41
42
43
2.3 Security features 44
45
2.3.1 Equipment 46
47
In order to use the security features, some additional equipments are required: 48
49
• USB Dongle supporting AES algorithm and programmed with appropriate key: 50
– customer key kc1 (128-bit constant) for development dongle 51
52
– customer key kc2 (128-bit constant) for production dongle 53
• Customer ID 54
55
• Binary file 56
57

only
Only one dongle is required per PC when performing multi-target downloads.

1
The flashloader code implements the interface with MARX dongles. Dongles from other 2
suppliers could be used, however it would require an update of the Flashloader code 3
4
(dongle dll code).
5
For security test purposes, the need of an hardware dongle has been removed and 6
7
replaced with a software only solution: test keys are read from a file (SecretKey.txt located
8
in the same folder than bfloader.exe) and used for AES computation by dongle dll code. 9
10
NOTE on Marx dongles: a “user password” is required when using MARX dongles. That
11
password is stored in the ini file (bfloader.ini) in the “user_passwd” field. Each section in 12
bfloader.ini dedicated to a target type has its own “user_passwd” field. The default ini file 13
sets “user_passwd” to “es” for all sections. It is up to the user to set “user_passwd” to the 14
value delivered by Marx with the purchased dongles. Internal program and documentation 15
to program dongles w/ keys and user password are available upon request. 16
17
2.3.2 Boot with a protected device 18
d
19
During the boot process, the Flash Loader requests from the protected device a string of 20
21
se
16 (109 for PNX6529) random bytes. This string is decrypted with the Dongle, completed
22
with the Customer ID and returned to the target (Ref. Section 5.2 “Advanced settings
23
window”.) 24
ea
25
The target checks if this is the correct response of either a development or a production 26
Dongle. In case of a development Dongle, Debug is allowed on the target. 27
28
el
2.3.3 Flash signature 29

30
Flash signature is used to guarantee flash contents integrity. 31
R
32
During flash programming, the Flash Loader requests from the protected device the flash 33
signature in encrypted form. This signature is decrypted by the Dongle and written into the 34
flash. 35
36
The Flash Loader only supports to write the signature at an address (signature offset) 37
38
included between the beginning and the end of the downloaded binary file. For more
39
details about the flash contents see Ref. 1 for PNX6511, Ref. 2 for PNX5220, Ref. 3 for 40
PRISM / PNX67xx and Ref. 4 for PNX6515 / PNX6516. 41
42
NOTE: 43
44
The signature offset is in the flash parameter section (see the relevant Security, Boot & 45
Download User Manual). The signature offset is automatically computed by the Flash 46
Loader and written into the flash parameters section. 47
48
• For NAND Flash, signature offset is hard-coded in the Flash Loader but can also be 49
found in BootNAND flash parameter section 50
51
• For NOR Flash, signature offset is taken from application binary. The Flash Loader 52
erase the block, corresponding to the signature offset, and rewrite it with the 53
decrypted signature. 54
55
56
57

only
2.3.4 OTP fuse

1
The Flash Loader allows to burn bits of the OTP fuse for PNX5xxx/6xxx ICs and starting 2
3
from release FL 7.3.x to program OTP of 4908/4910 ICs.
4
For PNX4908/10 ICs OTP programming is done word by word (32-bit word) and an ECC 5
6
is programmed for each 32 bit word. This mechanism prevents to program the same word 7
several times. 8
9
For other supported ICs (PNX5xxx/6xxx families), the OTP can be programmed bit wise 10
and so words can be programmed several times (setting to 1 bits that are still set to zero). 11
12
13
For PNX5xxx/6xxx ICfamilies, The OTP programming is done by sending a command to 14
the Boot ROM for each OTP row (OTP data x) specified in the Advanced Window of the 15
Flash Loader.Only the bits set to 1 are programmed. Setting a bit to 1 for a bit already 16
burnt in the fuse has no effect. 17
18
d
The OTP burning is done prior to processing the other commands selected in the main 19
20
window’s ‘Command’ section.
21
se
22
In case of a protected device, the customer id must be first authentified using a properly 23
programmed Dongle (see 2.3.2) in order to put the target in Debug mode. 24
ea
25
For more details about the OTP contents see Ref. 1 for PNX6511, Ref. 2 for PNX5220, 26
Ref. 3 for PRISM / PNX67xx and Ref. 4 for PNX6515 / PNX6516. 27
28
el
2.3.5 Download into NOR flash with a protected device (PL_FEATURE family) 29
30
31
R
To download into NOR flash with a protected device, the principle is the same as with a
non protected device, only that the binary file is split over 2 consecutive downloads and 32
33
that a signature is programmed in Flash. This procedure can also be executed with an
34
unprotected device, by checking the CalcSign check box (see Figure 14 “Flash Loader 35
main window”). 36
37
38
The download of the binary file consists of the following steps (see Figure 8 “Download 39
into NOR flash with a protected device”). 40
41
• Step 0: After hardware Reset or Power-on, execution of the Boot ROM (BB & UART or 42
USB init) 43
45
• Step 3: Execution of the Loader in SCRAM (flash type detection, flash erase, ...) 47
48
• Step 4: The Loader downloads and writes into the flash the first part of the binary file 49
from the beginning of the file to the signature offset 50
51
• Step 5: The Loader downloads and writes into the flash the second part of the binary 52
file from the signature offset + the signature length to the end of the file 53
• Step 6: The Boot ROM is reinitialized by a software reset 54
55
57

only
• Step 8: Flash Loader requests flash signature to SCROM. Signature is received

encrypted and Flash Loader decrypts it using a dongle. 1
2
• Step 9: The Loader is executed in SCRAM 3
• Step 10: The Loader erases and rewrites the block containing the decrypted flash 4
5
signature at the signature offset
6
7
8
9
0x00000000 for PNX6511/PNX6515/PNX6516
12
0xFFFF0000 for PNX5222 13
14
Boot 1 7
PC tool 15
0 6
ROM 8 16
(Flashloader)
17
18
d
2 19
SCRAM 3 20
9 Loader
21
se
Loader 22
23
binary file 24
ea
25
5 26
10 27
binary filePart II
28
el
Ext. Flash
(e.g. CS0) Flash Signature 29
binary filePart I 30
4
31
R
32
Fig 8. Download into NOR flash with a protected device 33
34
35
36
2.3.6 Download into NOR flash with a protected device (PL_ENTRY family) 37
38
Not yet supported. 39
40
41
42
2.3.7 Download into NAND flash with a protected device (PL_FEATURE family) 43
44
To download in a NAND flash with a protected device, the principle is the same as with an 45
unprotected device but the FB must be signed. This procedure can also be called with an 46
unprotected device, by checking the CalcSign check box. 47
48
49
The download of the binary file consists of the following steps (see Figure 9 “Download 50
into NAND flash with a protected device”). 51
52
• Step 0: After hardware Reset or Power-on, execution of the Boot ROM (BB & UART 53
54
or USB init)
55
57

only
• Step 2: The Boot ROM code downloads the Loader into internal SCRAM
1
• Step 3: Execution of the Loader in SCRAM (NAND flash type detection, NAND flash 2
partitions erase, ...) 3
• Step 4: The PC uploads and stores the FB 4
5
• Step 5...n: The Loader downloads and programs all the partitions into NAND flash 6
• Step n+1: The PC sends to the Loader the FB (if it changed) containing partition table 7
8
and Boot NAND. The last page of the FB is not programmed
9
• Step n+2: The Boot ROM is reinitialized by a software reset 10
• Step n+3: Flash Loader requests NAND flash signature to SCROM. Signature is 11
12
received encrypted and Flash Loader decrypts it using a dongle.
13
• Step n+4: The Loader is downloaded in SCRAM 14
15
• Step n+5: The Loader is executed in SCRAM 16
• Step n+6: The Loader writes the decrypted NAND flash signature in the last page of 17
the FB at the signature offset (defined by the FB mapping see Ref. 12 ). 18
d
19
20
21
se
23
ea

26
0 27
Boot 1
PC tool 28
el
n+2 ROM
n+3 (Flashloader) 29
30
31
R
2 32
3 n+5 n+4
SCRAM Loader 33
Loader 34
35
n
Partition x 36
37
NAND Flash 38
5
on NFI 39
Partition y 40
n+6 41
42
Flash Signature 4
43
First Block First block 44
n+1 45
46
Fig 9. Download into NAND flash with a protected device 47
48
49
50
2.3.8 Download into NAND flash with a protected device (PL_ENTRY family) 51
52
Not yet supported. 53
54
55
56
57

only
3. Installation 1
2
3
3.1 Flash Loader installation procedures 4
Follow the instructions below in order to install the Flash Loader 5
There are two ways to install the Flash Loader: 6
7
• Launching the .msi Microsoft Installer (refer to Section 3.1.1 on page 21) 8
9
• or unzipping the .zip package (refer to Section 3.1.2 on page 25) 10
11
Administration rights are required on the host PC to install the USB driver. The person 12
who performs the installation has to be familiar with the general principle of installing a 13
Windows driver to be able to solve unexpected Windows behaviour. 14
15
16
3.1.1 Msi Installer 17
18
d
1. Launch the “FlashLoader_vX.Y.Z.msi“ file to install Flash Loader application and the 19
corresponding USB driver. 20
21
se
This msi file is composed of: 22
23
– “bfloader.exe”: Main executable file of the Flash Loader 24
ea
– “bfluart.dll, bflusb.dll, bfldongle.dll, bfldb.dll“: DLLs used by the Flash Loader to 25

26
provide respectively UART communication, USB communication, security and
27
Flash database services. These DLLs shall be in the same directory as the 28
el
executable. 29
– “52xdfu.inf, 52xdfu.sys”: DFU driver based on CTO/LIPP USB stack 30
31
R
– “bfldb.csv”: default Flash Database file which stores flash configurations: name, 32
manufacturer id, device id, timing, size,..... 33
– “bfloader.ini, bfloader.log”: dummy log and ini files that will be overwritten by default 34
ones when launching the Flash Loader application. The bfloader.ini file stores 35
36
application configuration settings.
37
NOTE: Upon closing the Flash Loader application, “bfloader.exe” terminates and 38
overwrites two files: the default “bfloader.ini” file to reflect configuration last used by 39
application and the default “bfldb.csv” file with bfldb.csv used by application (.csv 40
possibly updated to add a new memory model). 41
42
2. The following Setup Wizard will be displayed: 43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
Fig 10. Flash Loader Setup Wizard start

29
30
• Click ‘Next’, then read and accept the terms of the End-User License Agreement 31
R
• Click ‘Next’, then read carefully the text on the USB driver 32
• Click ‘Next’, then select the folder where to install the Flash Loader application. You 33
34
can keep default path or browse for a custom path 35
• Click ‘Next’, then click ‘Install’ to install the Flash Loader or click ‘Back’ to change 36
settings 37
38
• Once you click ‘Install’, installation will start. If you are running the Setup Wizard on 39
Windows XP, the following popup may appear since the USB driver is not Windows 40
certified. Press ‘Continue Anyway’ to continue installation 41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
Fig 11. Flash Loader Setup Wizard Driver certification warning 28
el
29
• A popup will appear to warn you that the USB device can be attached to the PC later 30
31
R
to complete USB driver installation:

32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
Fig 12. Flash Loader Setup Wizard installation

29
30
• Click ‘OK’ to finish installation, then click ‘Finish’ to exit the Flash Loader Setup 31
R
Wizard 32
• Shortcuts to the Flash Loader application will be automatically created on desktop 33
and in programs list: 34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Fig 13. Flash Loader application shortcuts 52
53
54
55
56
57

only
3.1.2 Zip package

1
1. Unzip the “bfloader_exe_vX.Y.Z.zip“ file in an empty directory (without spaces in the 2
complete path!) 3
4
5
This zip file is composed of: 6
– “bfloader.exe”: main executable file of the Flash Loader 7
8
– “bfluart.dll, bflusb.dll, bfldongle.dll, bfldb.dll“: DLLs used by the Flash Loader to 9
provide respectively UART communication, USB communication, security and 10
Flash database services. These DLLs shall be in the same directory as the 11
executable. 12
– “52xdfu.inf, 52xdfu.sys”: DFU driver based on CTO/LIPP USB stack 13
14
– “bfldb.csv”: default Flash Database file which stores flash configurations: name, 15
manufacturer id, device id, timing, size,.... 16
17
18
2. Launch “bfloader.exe“, the Main Flash Loader Window is displayed (see Figure 14
d
19
“Flash Loader main window”). Only download via UART is possible at the moment if 20
21
se
no USB driver has been installed yet (see next chapter).
22
23
24
ea
3.2 USB driver installation procedures 25

26
There are two cases to distinguish:
27
• Only the CTO/LIPP USB stack will be installed. 28
el
29
In this case the CTO/LIPP USB stack is used by the boot ROM to download loader
30
and by the loader to download application in Flash. 31
R
• An external USB stack may be installed. 32

In this case the CTO/LIPP stack is used for the Boot downloading process (Boot 33
ROM) and the external USB stack is used by the external loader to download 34
35
application in Flash. The external loader shall of course be compatible with external
36
USB stack. 37
38
39
The next sections describe the Flash Loader settings and the USB drivers installation 40
once the Flash Loader tool is started. 41
42
3.2.1 Flash Loader setting for USB download 43
44
To perform a download over USB, the user must select a target supporting a USB stack in
45
the Boot ROM and select USB in “Communication settings“. For targets not supporting 46
USB, the USB option is disabled. 47
48
The USB driver will be requested by the Windows Install Wizard when Windows discovers 49
a new USB Hardware. 50
51
NOTE: For more details on the Flash Loader MMI, refer to Section 5 “User interface”. 52
53
54
55
56
57

only
3.2.1.1 Internal loader setting

1
• Check the USB box as displayed (see Figure 14 “Flash Loader main window”) 2
3
• ‘Internal Loader’ is selected as default in the ‘Advanced...’ window. The internal loader 4
is provided with the Flash Loader and uses CTO/LIPP USB stack. 5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
Fig 14. Flash Loader main window 50
51
52
53
3.2.1.2 External Loader setting 54
55
• Check the USB box in the main Flash Loader window (see Figure 14 “Flash Loader 56
main window”) 57

only
• In the Advanced configuration window (‘Advanced...’ button in main window), select

‘External Loader’ 1
2
• Enter the Loader file path/name and where to load/execute the Loader code by the 3
Boot ROM code (‘Location’) 4
With the ComboBox “Capability”, you must select the link capability of the external 5
loader. 6
By default, the capability is set to “USB” link. 7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
Fig 15. External Loader 53
54
55
56
57

only
3.2.2 USB driver (CTO/LIPP and external user) install / uninstall / update
1
procedure 2
The installation is only requested once by Windows. 3
4
These two drivers are installed using the “Plug&Play” application from Windows for each 5
USB port: 6
7
• Plug an USB cable into the target and the PC USB port 8
9
• When all the settings are correctly set (Target, USB, command, Application binary 10
file....), press the ’START’ button and switch ON the target 11
12
13
3.2.2.1 USB CTO/LIPP driver (52xdfu) installation 14
15
Upon the target reset, when the “Found New HW Wizard” pops up, select “Search for 16
suitable driver for my device”, then “Specify a location”, then browse and select the file 17
“52xdfu.inf”. 18
d
19
Windows installs the driver “52xdfu.sys” in the Windows environment. In the Windows 20
21
se
device manager (Control Panel -> System -> Hardware -> Device Manager), the following
Properties appears when the Device is connected: 22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
Fig 16. USB CTO/LIPP install driver details 57

only
Now USB can work with the CTO/LIPP USB stack only. Start again the Flash Loader 1
2
(bfloader.exe).
3
4
If you choose the same settings, you can download and flash a binary file on the target 5
board. In MMI, select an “Application binary file” e.g “application.bin” or your own binary 6
file and press ‘START’. Reset the target. See Section 5.6 for the scenario description. 7
8
9
For a “52xdfu.sys” driver already installed on PC, update is required only if version does 10
not match version of DFU driver included in Flash Loader delivery (driver version is 11
specified in Flash Loader delivery notes and in driver property menu once installed on 12
PC). See Section 3.2.2.2 for driver update procedure. 13
14
15
16
17
18
3.2.2.2 USB CTO/LIPP driver (52xdfu) update and uninstall procedures
d
19
20
How to check the version of 52xdfu drivers files: 21
se
Open the 52xdfu.inf file in text mode and read the “DriverVer” parameter: 22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
Fig 17. Check the 52xdfu driver files version 44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
Check 52xdfu device driver instantiation, update or uninstall it (WinXP and Win2K): 2
3
1. Show Hidden devices in Windows Device Manager: 4
5
a. Set “devmgr_show_nonpresent_devices” registry variable using shell command: 6
> set devmgr_show_nonpresent_devices=1 7
b. Start MS Device Manager using shell command: 8
> start devmgmt.msc 9
10
c. In the Device Manager, select “Show Hidden Devices” in “View” menu 11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
Fig 18. Show Hidden devices in MS Windows (XP/2K) Device Manager 40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2. Show one device driver instantiation properties: 2
a. Expand “Universal Serial Bus Controller”, and go to the list of “USB Device with 3
DFU capabilities” 4
5
b. Right-Click on the device driver instantiation to be checked and updated, and 6
select “Properties“. 7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Fig 19. Show driver instantiation properties 47
48
3. Update or Uninstall the Driver instantiation 49
50
To update the driver : the “Driver Version “ is not correct, click on “Update Driver” 51
To uninstall it, select uninstall and then confirm. 52
4. Update the device driver instantiation: 53
54
a. First, in the Update wizard windows, does not select automatic web update 55
b. Then select “Install from a specific location (Advanced)” and click Next. 56
57

only
c. Specify the location of the new driver files version and click Next
1
d. The driver is not signed by Microsoft, Select “Continue Anyway” in the popup 2
warning window. 3
e. At the end, click “Finish”, and the Driver Version is updated 4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Fig 20. Update a device driver instantiation 51
52
3.2.2.3 USB CTO/LIPP and external USB drivers install procedure 53
When the customer wants to use an external Loader which uses a different USB stack, 54
55
a second USB driver must be installed.
56
57

only
Upon target reset, the USB CTO/LIPP driver is installed (refer to Section 3.2.2.1).
1
2
Upon installation completion (till Windows Properties window appears), close, launch and
3
start again the Flash Loader. The communication is done via USB CTO/LIPP stack with 4
the Boot ROM code to download the user external Loader binary. 5
6
When the external Loader is executed, installation of the associated driver is requested. 7
Follow same USB CTO/LIPP installation instructions but select “<user>.inf” for the INF 8
file. 9
10
11
In the Windows device manager (Control Panel -> System -> Hardware -> Device
12
Manager), the user USB Loader Properties must appear: 13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Fig 21. Example : USB install driver details 47
48
49
50
Now USB can also work with the user USB stack. Start again the Flash Loader 51
(bfloader.exe). 52
53
If you choose the same settings, you can download and flash a binary file on the target 54
55
56
57

only
board. Select an “Application binary file” e.g “application.bin” or your own binary file and
press ‘START’. Reset the target. See Section 5.5 for the scenario description. 1
2
3
4
3.3 File interface 5
6
When the Flash Loader is launched, the following actions are performed: 7
8
• The current configuration is updated from the “bfloader.ini“ file. Target, link, memory... 9
configurations are saved in this file. The user can add a target, a memory or change a 10
link by modifying this file. For example in order to change the parity and/or the number 11
of stop bit, you must change, for the selected target, the parity and/or stopbit value in 12
the #xx_link_BR_USER section. The parity value could be 1 (odd) or 2 (even). The 13
stopbit value could be 0 (1 stopbit) or 2 (2 stopbit). 14
15
• If this ini file is not present or is corrupted when the software is initialized, a default 16
configuration file is created. 17
• The current flash database filename is updated from the “bfloader.ini”. If the file exists, 18
d
a flash database is built from this csv file. 19
20
• If this csv file is not present or is corrupted when the software is initialized, a default 21
se
flash database is created. 22
23
When NAND Flashs are programmed, the following actions are performed: 24
ea
25
• The Reservoir Control Block (RCB) is read during initialisation and is saved under 26
C:\Temp\, with the partition name and the product id. Its extension is :“*.before.rcb“ 27
and “*.after.rcb“ respectively for rcb used before erase/write action and after 28
el
erase/write action.The user can check if some invalid blocks have been found while 29
processing commands on the nand flash. 30
31
R
• The Nand First Block is read during initialisation and is saved to a file, in the same 32
folder than the Partition Table (.ptt) file, with the same filename but the extension 33
“.ptt.fb“. The folder contains .bootnand and all the partitions to be programmed in 34
Flash. 35
36
When the Flash Loader exits, the following actions are performed: 37
38
• The current configuration is saved into the “bfloader.ini“ file. 39
40
• The current trace information is saved into the “bfloader.log“ file. 41
• The current Flash database information is saved into the “bfldb.csv” file. 42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
4. Uninstallation 1
2
3
4.1 Uninstall procedures 4
Follow the instructions below in order to uninstall the Flash Loader from your PC. 5
There are two ways to uninstall the Flash Loader: manually and automatically via .msi file. 6
7
4.1.1 Manual uninstall 8
9
• If you used the zip package to install the Flash Loader, remove manually the installed 10
files listed in Section 3.1.2 11
12
• To remove drivers, use uninstall driver procedure described in Section 3.2.2.2. 13
14
15
16
4.1.2 Automatic uninstall 17
If you previously used the .msi to install the Flash Loader, you can uninstall the Flash 18
d
Loader by launching the same .msi Microsoft Installer. It will also uninstall the USB driver. 19
20
21
se
• Launch the “FlashLoader_vX.Y.Z.msi“ file to uninstall Flash Loader application and
the corresponding USB driver. 22
23
• The following Setup Wizard will be displayed: 24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
Fig 22. Flash Loader Setup Wizard restart 54
55
• Click ‘Next’, following action list is displayed: 56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
Fig 23. Flash Loader Setup Wizard to uninstall

29
30
• Click ‘Back’ to change previous settings or ‘Cancel’ to exit the Setup Wizard without 31
R
performing any action or ‘Remove’ to start uninstalling the Flash Loader from your PC. 32
33
• Once you have pressed ‘Remove’, The Flash Loader application, the shortcuts and 34
the USB driver are removed from your PC. 35
• Press ‘Finish’ to exit the Setup Wizard. 36
37
38
5. User interface 39
40
41
5.1 Main window 42
This window (see Figure 24 “Flashloader main window”) allows to: 43
44
• Set the type of baseband processor embedded in the platform 45
46
• Set the area in memory space where to download the binary file 47
• Set the binary file to download for NOR Flash 48
49
• Access the Partition Table for NAND flash 50
• Select UART or USB communication link 51
52
• Set the PC’s UART communication port and its speed in case of UART selected. 53
• Choose the scenario to execute (set of Erase / Write / Execute commands....) 54
55
• Select the number of devices to execute the scenario on 56
• Start and Stop the download 57

only
• Display events about download progress and errors for each device
1
• Access to the advanced settings 2
• Access to the flash database editor 3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Fig 24. Flashloader main window 47
48
49
50
51
52
53
54
55
56
57

only
5.1.1 Target settings

1
Location: This list allows to choose the location in memory space where to download the 2
binary file. Here are the different choices: 3
4
• ExtBus_CS0 to ExtBus_CS3 (7.3) or EBI_CS0 to EBI_CS3 (7.2) (if not applicable, will 5
not appear in the combo list): The binary file will be downloaded at the address 6
specified in the field “Address” (read only). The memory device shall be a flash or a 7
RAM. In case of flash device the Loader is downloaded into SCRAM and run in order 8
to download the binary file. 9
10
• NAND Interface (7.3) or NFI_NAND (7.2) (if not applicable, will not appear in the 11
combo list): The binary files corresponding to the partitions will be downloaded at 12
partition specific addresses using NFI or AUXPAR depending the chipset family. The 13
Loader is downloaded into SCRAM and run in order to download the binary files. 14
15
• Internal RAM (7.3) or SCRAM (7.2): The binary file will be downloaded at the SCRAM 16
address. The memory device is a RAM. With this selection the Loader will not be 17
downloaded 18
d
19
• User defined : The binary file will be downloaded at the address specified by the 20
customer in the “Address“ field (read/write). The memory device shall be a flash or a 21
se
RAM. In case of flash device the Loader is downloaded into SCRAM and run in order 22
to download the binary file 23
24
ea
25
NOTE: The Loader is normally downloaded into SCRAM as it is always available and “at 26
the same location” whatever the customer memory organization. If the user Loader is too 27
big, it will copied into external RAM, usually in ExtBus_CS1 / EBI_CS1. 28
el
29
30
31
R
Table 1. Address base of the memory location

Memory area PNX65-09/11 PNx6529 PNX52-20/22/ PNX67xx PNX4908
32
PNX65-08/13/ 25 PNX5217
33
PNX4910 34
15/16/17
35
36
ExtBus_CS0 (7.3) / 0x2000 0000 0x8000 0000 0x8000 0000 - 0x8000 0000 37
EBI_CS0 (7.2) 38
ExtBus_CS1 (7.3) / 0x3000 0000 0x9000 0000 0x9000 0000 - 0x9000 0000 39
EBI_CS1 (7.2) 40
41
ExtBus_CS2 (7.3) / 0x4000 0000 0xA000 0000 0xA000 0000 - 0xA000 0000 42
EBI_CS2 (7.2) 43
ExtBus_CS3 (7.3) / 0x4400 0000 0xA400 0000 0xB000 0000 - - 44
EBI_CS3 (7.2) 45
46
NAND Interface (7.3) / - N/A[1] N/A[1] N/A[1] N/A[1] 47
NFI_NAND (7.2) 48
Internal RAM (7.3) / 0x1C00 0000 0x0000 0000 0x0000 0000 0x0000 0000 0x2FFE 1000 49
SCRAM (7.2) 50
51
S/D-DRAM (7.3) / - 0x2000 0000 0x2000 0000 0x2000 0000 0xC000 0000 52
SDI_DRAM (7.2) 53
User Defined user address user address user address user address user address 54
55
[1] NAND flash does not directly address through address base but only through NFI or AUXPAR 56
57

only
Specific location type: enabled when the Location is not NAND Interface / NFI_NAND
and not Internal RAM / SCRAM. Three possible choices: “Static RAM”, “Nor Flash” or 1
2
“OneNand Flash”. It gives an indication on the location type. This information can be
3
different from a design to another, thus it has to be checked and modified if necessary. 4
5
Address (Hex): enabled when the Location is “User Defined”, and allows to specify the 6
address where the binary file will be downloaded. 7
8
5.1.2 Scenario settings 9
Each command can be selected separately even if this command has no sense (e.g. 10
11
programming a none blank flash).
12
13
Erase command: This command is only executed if the selected memory device is a 14
NOR flash, DDRAM memory or a NAND flash. The flash is erased with the length 15
specified by the erase option. 16
The NAND flash partitions are erased if ‘Erase’ command is selected in the main window 17
and if the ‘Erase’ and/or ‘Program’ check-boxes are checked in the partition table window. 18
d
19
20
Write command: This command is executed if the selected memory device is a flash or a
21
se
RAM. The memory device is programmed with the binary file. 22
For NAND flash, a partition is programmed if the associated check-box ‘Program’ is 23
selected in the partition table window. 24
ea
25
Execute command: This command is applicable to NOR flash, NAND flash or RAM 26
memory devices. The code downloaded in Flash is executed after a delay (see Section 27
28
el
5.2 “Advanced settings window”). Note for Nand Flash:after the download process ends, a
29
watchdog reset is done and the code is executed via the BootROM.
30
31
R
Upload command: This command is applicable to both flash or RAM memory devices. 32
The number of bytes read at a location specified below the Upload Option (in “Offset Hex” 33
field) is copied in a file whose name and path can be given by the customer in Section 5.2 34
“Advanced settings window”. The flashloader adapts the upload speed to be the fastest 35
according to the memory available on the target and the link protocol (UART/USB). Yet 36
variations in upload time can be noticed depending on the configuration. 37
38
39
Erase option / Upload option: only available if the ‘Erase’ command is selected (then
40
named “Erase option”) or if the ‘Upload’ command is selected (then named ‘Upload 41
option’). Only an erase or upload of the selected area is done: 42
43
• Application size: The flash is erased/uploaded with the length of the selected 44
application (in main window for NOR) or partitions (in partition table window for NAND, 45
in this case all the blocks including the partitions are erased/uploaded and not 46
exactely the partitions binary files). 47
48
• Complete (for Erase only): The flash is completely erased. 49
For NAND flash, only the valid blocks are erased. 50
• Custom: The flash is erased/uploaded from “Address” + “Offset” to “Address” + 51
“Offset” + “Length”. 52
In reality, the granularity is the sector size of the flash and the length is rounded to the 53
54
start address of the next sector.
55
56
57

only
This option is available for a NAND flash device, but not functionnal for the First Block
custom address, because the normal process is to rewrite the First Block after 1
2
program or erase. Refer to the note below.
3
4
NOTES for NAND Flash: The FB is stored in the PC side prior to do any action on the
5
NAND flash. 6
In case of ‘Complete ‘option selected, the FB is erased first before the other blocks and is 7
not rewritten at the end of the process 8
In case of ‘Application size’ selected, the FB is erased only if it changed, after the 9
partitions programming or erasing, to be overwritten. 10
11
CalcSign command: This command allows to order and to get the signature computed 12
by the Boot ROM for an uprotected IC. The returned signature is in unencrypted (plain) 13
14
format.
15
For a protected IC, the signature is automatically requested to the Boot ROM by the tool. 16
In addition, selecting the command triggers the signature display in the trace information 17
window (both in encrypted/plain format for protected IC, plain format only for unprotected 18
d
IC) 19
20
21
se
Verify command (Nand Flash Only): This command allows to verify the data
programmed (page by page verification) or erased in the NAND flash (FFF everywhere). 22
23
Note that it is not available for PNX4910.
24
ea
Crc command (Nand Flash Only): This command allows to compute the Crc on a whole 25
26
partition. This Crc is checked when the partition is programmed into the NandFlash. If the
27
check fails, the download is stopped. This command is applied for all partitions. 28
el
29
BurnOtp command: This command allows to burn the chip One Time Programmable 30
register, using OTP data from the advanced window. 31
R
32
A pop-up window is displayed when the customer presses the ’START’ button in order to 33
confirm the action. 34
35
ReadOtp command: This command, available for PNX4908/10 ICs only, allows to read 36
the One Time Programmable register of the chip. The read values are displayed in the 37
advanced window. Restriction: the BurnOtp and ReadOtp boxes must not be 38
selected together in the same scenario. 39
40
41
42
5.1.3 Communication settings 43
RS232C / USB : This radio button allows to choose the communication link.When USB is 44
selected the COM port and Speed list are disabled. 45
46
47
COM port: This list allows to choose the PC’s UART COM port to use (COM1 to COM32).
48
49
Speed: This list allows to choose the UART communication speed (with Boot ROM and 50
Loader). The maximum speed depends on the software running on the target (Boot ROM 51
or Loader). If the selected speed is not supported by the software running on the target, 52
the previous speed is used. 53
54
55
56
57

only
Table 2. Maximum UART speed

1
Bits per second Boot ROM Loader 2
9600 X X 3
4
19200 X X 5
38400 X X 6
7
57600 X X
8
115200 X X 9
230400 X X 10
11
460800 X X 12
921600 X X 13
14
15
These speeds are the ‘user’ speeds (saved in the ‘bfloader.ini’ file under the 16
[target#xx_link_BR_user] and [target#xx_link_LD_user] sections). The ‘default’ speeds 17
([target#xx_link_BR_dflt] and [target#xx_link_LD_dflt]) must be compliant with the Boot 18
d
19
ROM and Loader softwares i.e. 115200 bauds for all devices.
20
21
Table 3.
se
Additional UART speeds for PNX4908 / 4910 chipsets:
22
Bits per second Boot ROM Loader 23
1152000 X 24
ea
25
1498000 X
26
2996000 X 27
28
el
29
Note that the Boot ROM of PNX4908 and PNX4910 does not support these speeds and 30
always uploads data at 115200 kbps. The other data rates are enabled by means of the 31
R
embedded flash loader after it is uploaded on the target by the host PC. 32
33
Most PCs support all the standard data rates for UART up to 115200 kbps. The speeds 34
above are not necessarily available with standard COM ports but can be easily achieved 35
with USB to UART convertors. This should be considered when setting UART 36
communication speed in the flash loader on the host PC. 37
38
To change the parity and number of stop bits to communicate with the Boot ROM, the 39
values are hereafter: 40
41
• parity = 0 for no parity, 1 for odd parity, 2 for even parity 42
43
• stopbit = 0, 1 for 1 stop bit and 2 for 2 stop bits 44
45
5.1.4 Buttons 46
47
Application binary file: Sets the path of the binary file to download (NOR flash only).
48
49
Start/Stop: This button allows to start the download.
50
Advanced: This button allows to set advanced settings (see Section 5.2 “Advanced 51
52
settings window”).
53
54
FlashDatabase viewer: This button allows to display/edit or modify the flash database
55
settings (see ). 56
57

only
5.1.5 Download status and Multiple device frame (USB / UART)

1
Max Nb of Devices: when USB is selected, the current flashloader version allows to flash 2
up to 8 devices (4 devices in UART mode). In UART mode, the serial port com available 3
4
on the PC, appears, automatically, on the port com combo box.
5
Device status color box: After a “Start“ and before a “Stop”, it shows the status of each 6
7
Device thread: 8
9
• Yellow: Device thread is executing scenario 10
• Blue: Device thread is ready to execute the choosen scenario and no errors have 11
been detected during the previous execution (in case of multi loop scenario 12
execution). 13
14
• Light Blue: Device thread is ready to execute the choosen scenario and an error has 15
been detected during previous execution (in case of multi loop scenario execution). 16
17
Progress bar: One progress bar per device that shows the progression of the scenario 18
being executed.
d
19
20
Device N: Tab view to display events about download progress and errors 21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
Fig 25. Download status frame 43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
Fig 26. Download status frame - Yellow during process
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
Fig 27. Download status frame - Light blue after process 43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
Fig 28. Download status frame - Blue after process
20
21
se
22
5.2 Advanced settings window 23
24
This window allows to set the advanced settings of the Flash Loader.
ea
25
26
Jump delay (BootROM test purpose only): Specify the time the Boot ROM or Loader
27
must wait before executing the application. 28
el
This delay to jump to the application is only applicable in case of ‘Exec’ only or ‘Write’ and 29
‘Exec’ in RAM memory. In case of flash, the delay is applied after the ‘Write’ with the 30
Loader. By default the Jump delay value is zero. 31
R
32
Specify Customer ID (used for secure chipsets only): check this box in order to enter a 33
customer ID (used by security protocol). 34
35
If this option is checked (by default for devices supporting OTP), the customer ID must be
36
specified by the field “Customer ID“ otherwise the customer ID is taken from the binary 37
file. 38
For more details about security features (see Section 2.3 “Security features”). 39
40
Upload settings: Before executing the code in flash or RAM, the boot code can return to 41
the PC a number of bytes specified by the ‘Upload Length’ field. The bytes are copied 42
from the base address until the length specified in the ‘Upload Length’ field. Below select 43
the file in which the bytes will be saved. The base address is derived by the tool from the 44
45
address associated to the ‘Location’ selected in the main window. 46
These fields are active only if the ‘Upload’ command check-box in the main window is 47
enabled. 48
49
Loader binary file: An internal Loader binary file is embedded in the Flash Loader to 50
support the different flash devices. 51
For debug purpose, it is possible to use an external Loader binary file. This is to support a 52
new flash device or update a Loader version. This Loader could be downloaded into 53
54
SCRAM or into external RAM.
55
This choice could be made under control of the ComboBox “Location”. 56
With the ComboBox “Capability”, you must select the link capability of the external loader. 57

only
By default, the capability is set to “USB” link.

1
2
OTP data settings: This feature is available only if the target selected in the Main window
3
supports OTP features. A text box field is defined for each OTP register to program. This 4
text box content is different for a PL_FEATURE target or a PL_ENTRY target. 5
For PL_FEATURE, the selected target supports 16 or 32 OTP fuses, then one or two tabs 6
“OTP data 0 .. 15” and “OTP data 16 .. 31” appear to allow burning up to 16 or 32 OTP 7
registers. 8
Setting a bit to 1 burns the corresponding bit of the OTP fuse at the address specified by 9
the row (0 for OTP data 0 field, ...,15 for OTP data 15 field and 31 for OTP data 31 field) 10
11
and the column (position of bit set in the row 32-bit value).
12
For PL_ENTRY 4908/10 ICs, there are five tabs, four to enter OTP register values and 13
one to enter lock bits. Each of the first four tabs contains sixteen registers entries 14
identified with their register address. The registers can be burnt only one time. To burn a 15
register the value has to be written in the edit field and the check box next to the register 16
must be selected (checked). If this box is not checked the corresponding register will not 17
be burnt. 18
d
19
OTP data reading: This feature is available only for PL_ENTRY 4908/4910 ICs. 20
21
se
In order to read the OTP registers and lock bits, the ReadOtp box must be selected as a
scenario in the Main window. Then START button shall be pressed to launch the scenario. 22
23
Values are accessible in the advanced window, once “read OTP done” message is
24
displayed in MMI and user has pressed the STOP button (then can access the advanced
ea
25
window). 26
27
FormatBBM (Debug purposes only): It is not recommended for Flash Loader users 28
el
to use this option. This option allows the Flash Loader to re-format the RCB for the BBM. 29
Manufacturer Bad block information (BBI) shall never be re-formatted. To avoid the 30
31
R
manufacturer BBI being reformatted, the user shall ensure that the Flash record in the
32
Flash database contains the manufacturer BBI location information (BBI1 and BBI2 fields
33
to fill in). 34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Fig 29. Advanced window settings for PL_FEATURE 46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Fig 30. Advanced window settings for PL_ENTRY when burn OTP 47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Fig 31. Advanced window settings for PL_ENTRY when read OTP 47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Fig 32. Advanced window settings for PL_ENTRY when read or burn OTP Lock bits 46
47
48
49
50
5.3 Partition Table window 51
52
This window allows to set the partition table of the Flash Loader. The customer can select
53
up to 16 partitions. All the fields are read-only. They are filled from the partition file .ptt set 54
in browser window. 55
56
Name : The name of the partition. 57

only
Path: The path where the PC application can find the binary for this partition. 1
2
3
Size: Total size of the partition in bytes, including bytes within invalid blocks and unused 4
(margin) blocks. 5
6
Content: 32-bit total content size, not including bytes within invalid blocks or margin 7
blocks. Data starts at the first byte of the first valid block of the partition and extends in 8
contiguous bytes and blocks for content size bytes. The contiguous arrangement is 9
broken when an invalid block occurs; invalid blocks are re-mapped inside the Reservoir 10
11
Block.
12
13
Margin: The difference between the size and the content size. 14
15
Selected : When this check-box is selected, the partition is erased (if ‘Erase’ selected in 16
the main window) and programmed (if Programm is selected in the main window). The 17
partition table in the first block will then reflect modification if ‘Erase’ only is selected in the 18
d
main window. 19
20
21
se
22
Browse: This button is used to select the .ptt file path/name for the partition table. 23
24
ea
When the user wants to re-program only one partition, it is under the user responsability to 25
check if this new partition could be fit in the old partition in term of size and offset. 26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
Fig 33. Partition Table window settings 37
38
5.3.1 Partition Table File Syntax 39
40
The .ptt file could be built using STE PBuilder tool or using a WordPad editor. The syntax 41
is as follows: 42
up to 16 partitions. All the fields are read-only. They are filled from the partition file .ptt set 43
in browser window. 44
[partition table config start] 45
number_of_partition = “number of partitions defined in this file” 46
BootNand = “path of the BootNand File” 47
bootnand_major_version = ”major bootnand version see Section 5.3.2” 48
49
bootnand_minor_version = “minor bootnand version related to BBM (RCB) used by the
50
bootnand.bin see Section 5.3.3” 51
[partition#01] “description for the partition number 1” 52
partition_id = “id of the partition” 53
partition_name = “name of the partition” 54
partition_path = “path of the binary for this partition” 55
partition_offset = “offset in bytes, in the NandFlash, for this partition” 56
57

only
partition_size=”size in bytes for this partition”

partition_protected=”boolean 0 or 1 to determine if the partition is protected or not” 1
2
partition_load=”boolean 0 or 1 to determine if the partition could be loaded or not”
3
partition_exec=”boolean 0 or 1 to determine if the partition could be executable or not” 4
partition_header=”boolean 0 or 1 to determine if the partition has a header or not” 5
field beloew defines some flag value used for File System Volume 6
partition_parameter_volume=”boolean 0 or 1 to determine if partition contains SySol 7
parameter volume 8
partition_system_volume=”boolean 0 or 1 to determine if partition contains SySol system 9
volume 10
11
partition_application_volume=”boolean 0 or 1 to determine if partition contains SySol
12
application volume 13
partition_mandatory_volume=”boolean 0 or 1 to determine if partition contains SySol 14
mandatory volume and its mounting is mandatory 15
partition_read_only_volume=”boolean 0 or 1 to determine if partition contains SySol read 16
only volume 17
partition_format_if_not_mounted_volume=”boolean 0 or 1 to determine if partition 18
d
contains SySol volume and it will be formatted if mounts failed 19
20
partition_garbage_collector_enabled_volume=”boolean 0 or 1 to determine if partition
21
se
contains SySol volume and the background garbage collections is enabled for this volume 22
partition_usb_access_volume=”boolean 0 or 1 to determine if partition contains SySol 23
volume and it can be accessed over USB from PC. 24
ea
;”to insert a comment” 25

[partition table config end] 26
27
That format is supported by both 7.2 and 7.3 versions. 28
el
29
Note: since PNX6529 target has been added to 7.3, we also support in 7.3 a variant 30
version using SWboot instead of Bootnand (all other .ptt lines are the same). 31
R
32
[partition table config start] 33
number_of_partition = “number of partitions defined in this file” 34
SWboot = “path of the SWboot File” 35
SWboot_layout_major_version = ”major SWboot version see Section 5.3.2” 36
SWboot_layout_minor_version = “minor SWboot version related to BBM (RCB) used by 37
38
the swboot.bin see Section 5.3.3”
39
[partition#01] “description for the partition number 1” 40
41
42
43
44
5.3.2 BootNand Major and SWboot Major versions 45
The boornand_major_version can be one of the following values: 2, 3 or 4 46
47
The SWboot_layout_major_version can be of the following values: 5 48
49
Please refer to Ref. 12 for more information 50
51
52
5.3.3 BootNand or SWboot Minor Version
53
The bootnand_minor_version or the SWboot_layout_minor_version must be set as 54
described in following table: 55
56
57

only
Table 4. BootNand or SWBoot Minor Version Number

1
BootNand minor Version / Description 2
Software Boot minor Version
3
0 use IBT for BBM obsolete 4
1 use RCB for BBM (BBM supports only 1024 5
6
v1) blocks Large page
7
NANDs, and (FL 7.2.2 8
and onwards only), 2048 9
blocks Large Page Nands 10
2 use RCB for BBM (BBM supports SMALL/LARGE 11
v2) Page Nands with any 12
number of blocks (max: 13
8192) 14
15
3 BBM v3, used by 6710 Linux supports only 2048 16
blocks Large page 17
NANDs 18
d
19
5.3.4 Bad Block Management 20
21
se
Over the lifetime of the device additional Bad Blocks may develop and are identified 22
through: 23
24
ea
• Attempt to program or erase them reports errors in the Nand Flash Status Register. 25
26
• Verify option reports errors: ECC uncorrectable error or read/write comparison 27
mismatch. 28
el
29
A bad block has to be remapped to a valid block in the Reservoir Control Block. The 30
Reservoir Control Block is an area at the end of the Nand Flash that stores the “bad block 31
R
re-mapping to valid block” information and valid blocks used to remap the bad blocks (and 32
so store blocks data). 33
34
The mapping of bad blocks to reservoir blocks is stored in one (BBM v1, v2) or two tables 35
(BBM v3). The table must fit into one block and a copy of it is also available in the RCB. 36
When programming a block, the BBM is used to translate the block logical address (virtual 37
38
block number) into a block physical address (physical block number). The BBM checks if
39
virtual block number corresponds to a bad block, if it does, it will translate it into a mapped 40
physical block number (in reservoir control block), if it does not (block is valid), it will not 41
remap it and only match it to the corresponding physical block number. 42
43
44
45
46
5.4 Flash Database Editor window 47
48
This window allows to display, edit, modify or add a flash device record in the database. 49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
Fig 34. Flash database editor
28
el
29
By expanding the tree view, the user can display, for a selected flash, the Manufacturer ID 30
and the flash device ID0,1,2,3. 31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
Fig 35. Flash database editor : Edit menu 56
57

only
The Edit menu allows to :

1
• Copy/Paste flash parameters : can be used to create a new flash record by taking 2
an existing one. For copy the focus must be on the flash selected, the new flash is 3
4
created in the same flash tree.
5
• Display/Edit: when the user has selected a flash, the user can display or edit the 6
flash parameters. 7
8
• Add NAND,NOR,ONENAND manufacturer: the user can create a new flash device 9
manufacturer. That new flash device manufacturer is added in their respective tree. 10
No new flash device is created. 11
• Add new flash device here: the user can create a new flash device on the selected 12
manufacturer.The user must set all the flash parameters: they are checked and if 13
14
there is no parameter error, the flash record is created.
15
The Flash parameters window is accessed by selecting Display/Edit from Edit Menu 16
17
and allows to :
18
d
19
• Modify the flash parameters in Edit mode.
20
• Display the flash parameters in Display mode. 21
se
• Flash Identification, Capacity, Timings are dedicated for the generic flash parameters 22
23
• Nor Flash Parameters, Nor Flash Command Type, “External Memory 24
ea
Interface”Timings are dedicated for the nor flash parameters 25

26
• OneNand Flash Parameters, “External Memory Interface” Timings are dedicated for 27
the one nand flash parameters 28
el
• Nand Flash Parameters, “External Parallel Interface” Timings are dedicated for the 29
nand flash parameters 30
31
R
• All the parameters must be found into the flash device datasheet. 32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

only
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
Fig 36. Flash database display/edit window 50
51
When the user press OK, the flash database check all the parameters, if an error occurs, 52
the specified parameter is colored with a specific color 53
54
• RED : the error is : “PARAM_NOT_SUPPORTED” 55
• ORANGE : the error is : “PARAM_TOOSMALL” 56
57

only
• VIOLET : the error is : “PARAM_TOOBIG”

1
• PINK : the error is not : “PARAM_COMPATIBILITY” 2
• YELLOW : the error is : “PARAM_WRONGRANGE” 3
4
• BROWN : the error is : “PARAM_IS_0XFF” 5
• BLUE : the error is : “PARAM_IS_NULL” 6
7
• WHITE : the error is : “PARAM_NO_ERROR” 8
9
In-line documentation is available to help the user fill correctly the flash parameters. For 10
that purpose the “help“ button is available in the upper-right corner of the dialog windows. 11
12
First the user click on the “?” button to modify the mouse pointer, then the user shall click 13
on the parameter field for which help is needed. 14
15
16
17
18
d
19
20
21
se
22
23
24
ea
25
26
27
28
el
29
30
31
R
32
33
34
35
36
37
38
39
40
41
42
43
Fig 37. Flash database editor 44
45
46
5.5 Scenario for consecutive dowload execution 47
48
5.5.1 Single & Multiple download over UART or USB 49
1. Select actions to be executed on the Target and number of targets to Flash 50
(multi-download case). 51
52
2. Press the Start Button. 53
54
3. Connect on power on the board(s) device(s). 55
56
57

only
4. Wait for end of scenario execution : “Slot freed for new download“ in the Download
status frame(s). 1
2
5. Disconnect the board(s) device(s) 3
4
6. Repeat 3/, 4/ and 5/ several times if needed. Be careful to connect the same device 5
family. 6
7
7. Then press Stop Button to finish scenario execution several times per slot. 8
9
10
5.5.2 Power on Sequence
11
In the Flash Loader MMI, press the START button then follow next steps on boards: 12
13
• 651x boards: 14
– Plug USB Cable from PC host to board 15
16
– Force backdoor (if flash is not virgin) by pressing 3 keys 17
– And finally power on the board 18
d
19
• 522x / 67xx boards: 20
21
se
– Force backdoor (if flash is not virgin) by pressing 3 keys
22
– Then, power on the board 23
– And finally, plug USB cable from host to board. 24
ea
25
• 4908, 4910 boards/mobile phones: 26
– Unplug the power from the board/device, connect it to the host PC. 27
28
el
– Start flash loader application on the host PC, select required actions (Erase / 29
Program / Execute etc.), set communication parameters (UART+speed / USB), 30
press “Start” button. 31
R
32
– Insert the battery or connect the device to its external power supply unit.
33
– In case you program mobile phone, you may need to press its power key and hold 34
it until the flash loader application on the host PC displays in the trace window that 35
the “1st loader has been loaded” or an error (if it happens). 36
37
– Release the power key. The rest of the process goes autonomously. 38
39
5.5.3 WARNING for Multiple download over USB 40
IMPORTANT: During download, a device slot number (Tabs “Device N“ in the download 41
42
status frame) corresponds to a USB physical link and the target plugged on it.
43
For next download, the device slot number may not correspond to the previously used 44
45
USB physical link:
46
47
For next download (new detected device), the Flash Loader application uses the
48
first free slot. 49
50
5.5.4 WARNING for a scenario over UART with “EXEC” command 51
IMPORTANT: Consecutive scenario executions without pressing STOP and START 52
buttons are not allowed. 53
54
1. Select actions to be executed on the Target. 55
56
57

only
2. Press the Start Button.

1
3. Connect on power on the board(s) device(s). 2
3
4. Wait for end of scenario execution : “Slot freed for new download“ in the Download 4
status frame(s). As “exec” is selected in UART mode, there is also the following warning: 5
“After exec on UART, thread waiting for STOP/START to restart” in the status frame(s) 6
7
5. Disconnect the board(s) device(s) 8
9
6. Then press Stop Button to finish 1 time scenario execution. Repeat from 1/ if needed. 10
11
12
5.6 Scenario for RAM and NOR flash 13
14
1. Power on the platform. 15
2. Start the Flash Loader software by running the bfloader.exe file. 16
17
3. When all the parameters are set (see Section 5.1 “Main window” and Section 5.2 18
“Advanced settings window”), begin the download by clicking on the ’START’ button.
d
19
Follow events and indications in the trace (see Figure 25 “Download status frame”). 20
21
se
4. The Flash Loader waits for a connection request from the target: reset the platform to
22
establish the connection. 23
5. The Flash Loader displays the Product ID, SCROM and Chipset versions. 24
ea
25
6. If the device is RAM see step 9, if the device is flash see step 7.
26
7. The Loader is loaded and then run. 27
28
el
8. The flash type is detected and the flash is erased.

29
9. The binary file is now being downloaded. A “progress bar” indicates the progression. 30
31
R
32
33
5.7 Scenario for NAND flash 34
35
1. Power on the platform. 36
2. Start the Flash Loader software by running the bfloader.exe file. 37
38
3. When all the parameters are set (see Section 5.1 “Main window” , Section 5.2
39
“Advanced settings window” and Section 5.3 “Partition Table window”), begin the 40
download by clicking on the ’START’ button. Follow events and indications in the trace 41
(see Figure 25 “Download status frame”). 42
4. The Flash Loader waits for a connection request from the target: Reset the platform to 43
44
establish the connection.
45
5. The Flash Loader displays the Product ID, SCROM and Chipset versions. 46
47
6. The Loader is loaded and then run.
48
7. The NAND flash type is detected. 49
8. The FB is downloaded into the PC. 50
51
9. All the partitions with check box ‘Selected’ checked are programmed. 52
A “progress bar” indicates the progression. 53
54
10. If the FB needs an update, it is programmed.
55
56
57

only
6. Burning and reading OTP
6.1 Burning OTP on PL_ENTRY targets

To burn OTP registers select BurnOtp in the command If there are many devices connected, the same OTP
section of the main window . Burning OTP can be values will be burnt in the same registers of all the
done in a complex scenario (for example devices. But when you go back in the advanced
Erase/Write/BurnOtp) or alone. window after the run, you will see the registers
content of the device selected in the main window.
In a complex scenario it will be done after erase, write
or upload but before execution. Some more precisions:
Once BurnOtp is selected go into the advanced When the advanced window has been opened
window by clicking on the “Advanced...” button. The after a burning run and is closed by pressing the
advance window displays an OTP section with many “Cancel” button, if a new run is started by
tabs that allow to program selected registers or lock pressing the “START” button in the main window,
bit. Each register is identified by its address. Write the the flashloader will try to burn the same registers
d
value to be burnt in the input box near the as in the previous run.
corresponding address and check the box next to the
If you close the advanced window by pressing the
se
input box. If the box is not checked, the corresponding
register will not be burnt. In the example the register “OK” button without having done any modification, the
@227 will not be burnt. It is possible to burn many flasloader will do nothing on a new run because no
registers in the same run. The “OTP lock bits” tab check box are selected.
ea
allows to select which lock bit to burn. To validate your

If you do modifications and close the advanced
selection you have to close the advanced window by
window by pressing the “OK” button they will be taken
clicking on the “OK” button.
el
into account by the flashloader.

Once back in the main window press the “START”
Note that a value of 0 in a register does not mean
button. A warning window will appear to make sure
R
necessarily that the register is writable. It is

you want to burn OTP registers. Press “Yes” to
possible that the register has been previously burnt
continue. During burning status are displayed in the
with the value of 0.If a register contains a value that is
message window. If some registers are already
not 0, it is for sure not writable.
written a message indicates it .
You can now press the “STOP” button. The advanced

window displays the content of all registers read after Burning from file
the burn. It does not display the values you wanted
to burn. That is, if a register was already written you It is possible to read the burning values from a file.
will see their content value and not the one you The “Advanced” window proposes a browse widget to
wanted to burn. You will be able to check if the content choose the file. When read, the values are displayed
reflect what you expect to. in the tab dialog and can be modified by user if
necessary.
The file must have the following structure:
Each line beginning with ‘#’ or a blank is a comment.
© ST-Ericsson. 2010. All rights reserved.

For more information, please visit: http://www.nxp.com
For sales office addresses, email to: sales.addresses@www.nxp.com
Document date: 8 June 2010
Document identifier: PL-FEATURE_BOOT-FLASH-LOADER_UM
For internal and customer use only
only
A section for the selected target must exist. A section

begin with the keyword target_name followed by the
target name. For example target_name PNX4910
will begin the PNX4910 section. The section ends with
a new section or the end of file.
In a section each line can have a register value or a

lock bit value.
If register value, the format is: address value

ctrl where address is the register address, value
is the value to burn and the ctrl is 1 if the value must
be burnt, 0 if not. All the OTP registers must have an
entry in the section. They not need to be in the
crescent order but it will be easier to maintains the
section if they are.
If lock bit value the line format is: lock_keyword
d
ctrl where lock_keyword is a keyword that
identifies the lock bit and ctrl is 1 if the value must
se
be burnt, 0 if not. The lock keywords are: rtc_lock,
otp_lock, trim_lock, charger_lock,
anti_rollback_lock, arm_jtag_lock,
ea
sec_boot_lock, sec_keys_lock.
A short example can be

el
target_name PNX4910
0x100 0x12345678 1
R
rtc_lock 1

only
d
se
ea
el
R
Fig 38. Burn OTP selection in main window

only
d
se
ea
el
R
Fig 39. Advanced windows: Entering values to be burnt

only
d
se
ea
el
R
Fig 40. Example of OTP burning status messages when no error

only
d
se
ea
el
R
Fig 41. OTP burning status messages: some registers were already written

only
d
se
ea
el
R
Fig 42. The advanced window will reflect the Device2 registers content

only
d
se
ea
el
R
Fig 43. Advanced window display Device2 OTP registers content

only
d
se
ea
el
R
Fig 44. The advanced window when loading OTP values from a file

only
6.2 Reading OTP on PL_ENTRY targets

To read OTP registers select ReadOtp in the
command section of the main window. Reading OTP
can be done in a complex scenario (for example
Erase/Write/BurnOtp) or alone.
In a complex scenario it will be done after erase, write

or upload but before execution.
In the main window press the “START” button.

Reading status are displayed in the message window.
After the run press the “STOP” button and go to the

advanced window. It displays the content of all
registers. If there are many devices the advanced
window is displaying the registers content of the
device selected in the main window. To display the
registers content of another device, close the
d
advanced window, select the other device in the main
window and re-open the advanced window.
se
ea
el
R

only
d
se
ea
el
R
Fig 45. Read OTP selection in main window

only
d
se
ea
el
R
Fig 46. Read OTP messages

only
d
se
ea
el
R
Fig 47. Advanced window display Device2 OTP registers content

only
7. Restrictions for Multiple Download feature
7.1 USB Limitations

• Multiple Download is available over USB link: * UHCI external Hub (ports support USB Full
– Configuration recommended: Speed/Universal Host Controller Interface
* Windows XP (UHCI) standard (slower))
* OHCI/EHCI PC Cards (USB ports support *OHCI/EHCI external Hub (USB ports support
High Speed/Enhanced Host Controller High Speed/Enhanced Host Controller
Interface (EHCI) and Full Speed /Open Host Interface (EHCI) and Full Speed/Open Host
Controller Interface (OHCI) standards). Controller Interface (OHCI) standards).
– Configuration allowed: – Configuration that shall not be used:

* Windows 2K (slower). *Any USB external Hub without its own Power
* UHCI PC Cards (USB ports support Full Supply or from Laptop “Docking Station”.
Speed/ Universal Host Controller Interface • Up to 8 devices max
(UHCI) standard (slower))
7.2 UART Limitations

d
se
• Supported configurations: UART COM port or • Speed limitation: all connected devices should
USB-to-UART convertors with up to 921,6 kbps support the selected UART Speed on Main frame
ea
(up to 2,996 Mbps for PNX4908 / 4910 chipsets) dialog box

• Selection from COM1 to COM32 • Flash loader supports parallel loading of up to 4
devices connected over UART links
el
8. References
R
[1] PNX5230/PNX5231 - GSM/GPRS/EDGE/UMTS [4] PNX6515 - GSM/GPRS/EDGE Baseband

Baseband Processor - Security, Boot and Processor - Security, Boot and Download -
Download - User Manual — Version 04., NXP User Manual — Version 01., NXP
Semiconductors MST-BB, 12 May 2006 Semiconductors PL Feature, 07 December 2007
[2] PNX5220/PNX5221 - GSM/GPRS/EDGE/UMTS [5] PNX6511 - Nexperia TM 2.5G Multimedia
Baseband Processor - Security, Boot and Baseband Processor - Objective
Download - User Manual — Version 05., NXP Specification — Version 01., NXP
Semiconductors MST-BB, 10 October 2006 Semiconductors MSTBB, 22 February 2007
[3] PNX6712 - PRISM Nexperia TM 2.5G/3G [6] PNX5220/PNX5221 - Nexperia TM 2.5G/3G
Multimedia Baseband Processor - Security, Multimedia Baseband Processor - Objective
Boot and Download - User Manual — Version Specification — Version 05.02, NXP
01.01, NXP Semiconductors PL Feature, Semiconductors MSTBB, 27 July 2006
07August 2007

only
[7] Nexperia TM 2.5G/3G Multimedia Baseband

Processor PNX6712 - Objective
Specification — Version 02.01, NXP
Semiconductors PL Feature, 21 December 2007
[8] Nexperia TM 2.5G Multimedia Baseband
Processor PNX6515 - Objective
Specification — Version 02, NXP
Semiconductors PL Feature, 07 December 2007
[9] Nexperia TM EZ_EBMM_1 PCB - User
Manual — Version 0.03, NXP Semiconductors
MST-BB, 16 November 2004
[10] EZ_DIG OM6391- User Manual — Version
01.01, NXP Semiconductors MST-BB, 20
October 2004
[11] NAND Flashloader - Product Requirement
Specification — VYn_ps19040 - Version 1.0,
d
NXP Semiconductors MST-SYSOL, 01
December 2005
se
[12] NANDFLASH for Nexperia TM System
Solution - Software Interface
Specification — VYn_ps18566 - Version 3.0,
ea
NXP Semiconductors MST-SYSOL, 20 July

2007
el
R

only
9. Appendix
9.1 Error codes list

Table 5. Flash Loader error codes
Value Name Description
000 ERR_ERROR Unknown error
001 ERR_NOERROR No error detected
100 COMERR_NOTINITIALIZED The communication media is not initialized

101 COMERR_ALREADYINITIALIZED The communication media is already initialized
102 COMERR_CREATEEVENT Error during create Event
103 COMERR_OPENEVENT Error during reset Event
104 COMERR_RESETEVENT Error during open Event
d
105 COMERR_SETEVENT Error during set Event
106 COMERR_CLOSEHANDLE
se Error during close Event
107 COMERR_MEMORYALLOC Error during memory allocation
108 COMERR_INVALIDTARGET Wrong target type
ea
300 COMERR_ABORT Abort receive

301 COMERR_CMDNOTACK Command not acknowledged
el
302 COMERR_CMDKO Command error

R
303 COMERR_CMDUNAVAILABLE This command is not available on this target

304 COMERR_CHECKSUMERROR Check sum error during data transfert
305 COMERR_TXERROR Transmission error
306 COMERR_RXTIMEOUT Reception timeout
307 COMERR_RXUNCOMPLETE Reception uncomplete
308 COMERR_CREQNOTRECEIVE Connection request not received
309 COMERR_CACKNOTRECEIVE Connection acknowledge not received
310 COMERR_WRONGPARAMRANGE A command parameter is out of range
311 COMERR_WRONGPARAM A command parameter is wrong
312 COMERR_WRONGPARAMDEFAULTUSE A command parameter is wrong but default paramameter
value is used
313 COMERR_BADSIGNATURE Bad signature value or FLASH customer id not align with
OTP customer id index, have been detected by the
bootrom

only

500 COMERR_UARTBADCONFIG A parameter is wrong in the UART configuration structure

501 COMERR_UARTCREATEFILE The communication device cannot been opened
502 COMERR_UARTCLEARCOMERROR The communication device cannot been initialized
503 COMERR_UARTREADFILE Error during reception by the UART
504 COMERR_UARTWRITEFILE Error during sending by the UART
505 COMERR_UARTGETCOMSTATE The previous UART configuration cannot been read
506 COMERR_UARTSETCOMSTATE The current UART configuration cannot been written
507 COMERR_UARTSETCOMTIMEOUT The UART configuration cannot been set
508 COMERR_UARTOVERLAP Error during read overlapped data
600 COMERR_BRSTALL USB STALL message send by the BOOTROM, the
receive is in DfuIdle state
d
601 COMERR_LDSTALL USB STALL message send by the LOADER, the receive
is in DfuIdle state
se
602 COMERR_USBERR USB Error
603 COMERR_ERASE_ONE_BLOCK Error during erase one block for NandFlash
ea
604 COMERR_ERASE Error during erase operation for NorFlash

605 COMERR_WRITE Error during write data access
606 COMERR_VERIFY Error during verify data for NandFlash
el
607 COMERR_PROG Error during programm data

608 COMERR_READ Error during read data
R
609 COMERR_INVALIDFLASH Error flash invalid

610 COMERR_RESERVOIR_FULL Error reservoir control block(RCB) is full ( NandFlash
only)
611 COMERR_ADDRESS_WRITE
612 COMERR_BBM_WRITE Error during write RCB (NandFlash only)
613 COMERR_DMA_WRITE Error during DMA write operation
614 COMERR_LENGTH_WRITE Error on receive length value for a write operation
615 COMERR_RCB_FULL_WRITE Error during write RCB(NandFlash only), no more block
into RCB
616 COMERR_TIMEOUT_WRITE Timeout during write operation
617 COMERR_W_PROTECT_WRITE Error the flash is write protected
618 COMERR_LOADER_ENCRYPT_WRITE Error during encrypted data
619 COMERR_LENGTH_READ Error on receive length value for a read operation

only

620 COMERR_DMA_READ Error during DMA read operation
621 COMERR_TIMEOUT_READ Timeout during read operation
622 COMERR_ADDRESS_READ Error on receive address value for a read operation
700 DGLERR_NOTINITIALIZED The Dongle is not initialized

701 DGLERR_ALREADYINITIALIZED The Dongle is already initialized
702 DGLERR_NODONGLEFOUND The Dongle is not connected
703 DGLERR_DEVICELOCKED Cannot get access to the Dongle
704 DGLERR_NOTLOGGED The customer password is wrong
705 DGLERR_WRONGPARAM A command parameter is wrong
706 DGLERR_MEMORYALLOC Error during memory allocation
d
800 COMERR_FLASH_NOT_DETECTED The flash memory device is not detected in embedded
se
side : the manufacturer ID is not recognized in the known
list (refer to FL Delivery Note to see known list).
801 COMERR_FLASH_NOT_FOUND The flash memory is recognized in the embedded side
ea
but flash IDs cannot be found in Flash database.

el
R

only
10. Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2.2.2 USB CTO/LIPP driver (52xdfu) update and
1.1 Purpose and scope. . . . . . . . . . . . . . . . . . . . . . 4 uninstall procedures . . . . . . . . . . . . . . . . . . . . 29
1.2 Flashloader versions and applicable devices . . 4 3.2.2.3 USB CTO/LIPP and external USB drivers install
1.3 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1.4 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.3 File interface . . . . . . . . . . . . . . . . . . . . . . . . . 34
2 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4 Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.1 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1 Uninstall procedures . . . . . . . . . . . . . . . . . . . 35
2.1.1 Software components . . . . . . . . . . . . . . . . . . . . 8 4.1.1 Manual uninstall . . . . . . . . . . . . . . . . . . . . . . . 35
2.1.2 Hardware components . . . . . . . . . . . . . . . . . . . 8 4.1.2 Automatic uninstall. . . . . . . . . . . . . . . . . . . . . 35
2.2 General principle of downloading . . . . . . . . . . . 8 5 User interface . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.2.1 PL Feature and PL Entry ICs: UART downloading 5.1 Main window . . . . . . . . . . . . . . . . . . . . . . . . . 36
process differences. . . . . . . . . . . . . . . . . . . . . . 8 5.1.1 Target settings . . . . . . . . . . . . . . . . . . . . . . . . 38
2.2.2 USB Back Door (for PL Feature basebands) . . 9 5.1.2 Scenario settings . . . . . . . . . . . . . . . . . . . . . . 39
2.2.2.1 Hardware backdoor . . . . . . . . . . . . . . . . . . . . . 9 5.1.3 Communication settings. . . . . . . . . . . . . . . . . 40
2.2.2.2 Software backdoor . . . . . . . . . . . . . . . . . . . . . . 9 5.1.4 Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.2.3 Download into external RAM . . . . . . . . . . . . . . 9 5.1.5 Download status and Multiple device frame (USB
d
2.2.4 Download into SCRAM . . . . . . . . . . . . . . . . . . 11 / UART) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.2.5 Download into NOR flash (single file and multiple 5.2 Advanced settings window. . . . . . . . . . . . . . . 44
file programming) . . . . . . . . . . . . . . . . . . . . . . 12
se 5.3 Partition Table window . . . . . . . . . . . . . . . . . . 49
2.2.6 Download into DDRAM memory. . . . . . . . . . . 14 5.3.1 Partition Table File Syntax . . . . . . . . . . . . . . . 51
2.2.7 Download into NAND flash . . . . . . . . . . . . . . . 15 5.3.2 BootNand Major and SWboot Major versions 52
2.2.8 Download into OneNand flash . . . . . . . . . . . . 16 5.3.3 BootNand or SWboot Minor Version . . . . . . . 52
ea
2.3 Security features. . . . . . . . . . . . . . . . . . . . . . . 16 5.3.4 Bad Block Management. . . . . . . . . . . . . . . . . 53

2.3.1 Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.4 Flash Database Editor window . . . . . . . . . . . 53
2.3.2 Boot with a protected device . . . . . . . . . . . . . 17 5.5 Scenario for consecutive dowload execution. 57
2.3.3 Flash signature . . . . . . . . . . . . . . . . . . . . . . . . 17 5.5.1 Single & Multiple download over UART or USB. .
el
2.3.4 OTP fuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 57

2.3.5 Download into NOR flash with a protected device 5.5.2 Power on Sequence. . . . . . . . . . . . . . . . . . . . 58
(PL_FEATURE family) . . . . . . . . . . . . . . . . . . 18 5.5.3 WARNING for Multiple download over USB . 58
R
2.3.6 Download into NOR flash with a protected device 5.5.4 WARNING for a scenario over UART with “EXEC”
(PL_ENTRY family) . . . . . . . . . . . . . . . . . . . . 19 command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.3.7 Download into NAND flash with a protected device 5.6 Scenario for RAM and NOR flash . . . . . . . . . 59
(PL_FEATURE family) . . . . . . . . . . . . . . . . . . 19 5.7 Scenario for NAND flash . . . . . . . . . . . . . . . . 59
2.3.8 Download into NAND flash with a protected device 6 Burning and reading OTP. . . . . . . . . . . . . . . . 60
(PL_ENTRY family) . . . . . . . . . . . . . . . . . . . . 20
6.1 Burning OTP on PL_ENTRY targets . . . . . . . 60
3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 6.2 Reading OTP on PL_ENTRY targets. . . . . . . 69
3.1 Flash Loader installation procedures . . . . . . . 21 7 Restrictions for Multiple Download feature . 73
3.1.1 Msi Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.1 USB Limitations . . . . . . . . . . . . . . . . . . . . . . . 73
3.1.2 Zip package . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.2 UART Limitations . . . . . . . . . . . . . . . . . . . . . . 73
3.2 USB driver installation procedures . . . . . . . . . 25
3.2.1 Flash Loader setting for USB download . . . . . 25 8 References. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.2.1.1 Internal loader setting . . . . . . . . . . . . . . . . . . . 26 9 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.2.1.2 External Loader setting. . . . . . . . . . . . . . . . . . 26 9.1 Error codes list . . . . . . . . . . . . . . . . . . . . . . . . 75
3.2.2 USB driver (CTO/LIPP and external user) install / 10 Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
uninstall / update procedure . . . . . . . . . . . . . . 28
3.2.2.1 USB CTO/LIPP driver (52xdfu) installation. . . 28

only
d
se
ea
el
R

only
d
se
ea
el
R

only
d
se
ea
el
R

only
d
se
ea
el
R

only
d
se
ea
el
R

only
d
se
ea
el
R

only
d
se
ea
el
R

only
d
se
ea
el
R

only
d
se
ea
el
R

only
d
se
ea
el
R

only
d
se
ea
el
R


PL Feature - Boot Flash Loader - Um PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PL Feature - Boot Flash Loader - Um PDF

Caricato da

Copyright:

Formati disponibili

BU Feature

Boot & Flash Loader Software

Name Department Address

Christophe MONTAUD PL Feature LMS christophe.montaud@stericsson.com

For internal and customer use

01.21 8 Sep 09 Update after review. P. Mondoloni

01.18 30 Jun 09 Corrections and updates in User Interface section F. Craisson

PL-FEATURE_BOOT-FLASH-LOADER_UM © NXP B.V. 2010. All rights reserved.

User Manual Rev. 01.29 — 8 June 2010 2 of 89

Revision history …continued

01.01 10 Apr 08 Creation from single download documentation Julien Beal

PL-FEATURE_BOOT-FLASH-LOADER_UM © NXP B.V. 2010. All rights reserved.

User Manual Rev. 01.29 — 8 June 2010 3 of 89

1.1 Purpose and scope

This document is intended to the customers of this software.

1.2 Flashloader versions and applicable devices

• Flashloader 7.4 - Applicable devices

PL-FEATURE_BOOT-FLASH-LOADER_UM © NXP B.V. 2010. All rights reserved.

User Manual Rev. 01.29 — 8 June 2010 4 of 89

pages of NAND) necessary to support the process of executing 25

RAM either all or by pages (Page-On-Demand). 29

Dongle Hardware device used to allow code downloading on protected IC

User Manual Rev. 01.29 — 8 June 2010 5 of 89

User Manual Rev. 01.29 — 8 June 2010 6 of 89

User Manual Rev. 01.29 — 8 June 2010 7 of 89

2.1.1 Software components

User Manual Rev. 01.29 — 8 June 2010 8 of 89

User Manual Rev. 01.29 — 8 June 2010 9 of 89

Fig 3. Download in RAM 29

User Manual Rev. 01.29 — 8 June 2010 10 of 89

User Manual Rev. 01.29 — 8 June 2010 11 of 89

• Set the flash parameters into the embedded generic driver 25

device (PL_FEATURE family)”. 32

User Manual Rev. 01.29 — 8 June 2010 12 of 89

0x00000000 for PNX6511/PNX6515/PNX6516

User Manual Rev. 01.29 — 8 June 2010 13 of 89

User Manual Rev. 01.29 — 8 June 2010 14 of 89

2.2.7 Download into NAND flash

User Manual Rev. 01.29 — 8 June 2010 15 of 89

NAND Flash n+1 29

User Manual Rev. 01.29 — 8 June 2010 16 of 89

Only one dongle is required per PC when performing multi-target downloads.

2.3.3 Flash signature 29

User Manual Rev. 01.29 — 8 June 2010 17 of 89

2.3.4 OTP fuse

User Manual Rev. 01.29 — 8 June 2010 18 of 89

• Step 8: Flash Loader requests flash signature to SCROM. Signature is received

User Manual Rev. 01.29 — 8 June 2010 19 of 89

0xFFFF0000 for PNX5222/PNX5217/PNX67xx/PRISM 25

User Manual Rev. 01.29 — 8 June 2010 20 of 89

– “bfluart.dll, bflusb.dll, bfldongle.dll, bfldb.dll“: DLLs used by the Flash Loader to 25

User Manual Rev. 01.29 — 8 June 2010 21 of 89

Fig 10. Flash Loader Setup Wizard start

User Manual Rev. 01.29 — 8 June 2010 22 of 89

to complete USB driver installation:

User Manual Rev. 01.29 — 8 June 2010 23 of 89

Fig 12. Flash Loader Setup Wizard installation

User Manual Rev. 01.29 — 8 June 2010 24 of 89

3.1.2 Zip package

3.2 USB driver installation procedures 25

• An external USB stack may be installed. 32

User Manual Rev. 01.29 — 8 June 2010 25 of 89

3.2.1.1 Internal loader setting