User Guide

PAMS
Technical Documentation
RAE-3
8. Troubleshooting
Page 8 – 15
Issue 1 06/01
2.1.3 Flash VPP Error
FLASH programming does not work
If the fault information from the prommer is:
a) The erasing status response from the Phone informs about fail. The Prommer copies the
Phone response contents to the preceeding FIASCO_GENERAL_INFO_IND message.
b) The Prommer measures the PPD voltage level at flashing start. If the level is below the limit
the Prommer returns the corresponding error code.*
c) The programming status response from the Phone informs about fail.
The Prommer copies the phone response contents to the preceding FIASCO_GENERAL_
INFO_IND message
Note: A new error message will be shown with next coming Wintesla RAE–3 dll release
Check that UL8 flex connector is properly connected to Board to board connector on BL8
(=X400) ; (pins 15 (FLVPP) and 16 (PROG_EN) are connected in UL8 flex)
Check voltage from Board to board adapter JC4
connector pin 16 (= 2.8 V)
Note: By default tested with known good UL8 flex.
Check FLVPP voltage level
(= 2.8 V) during programming. (See Memory tests measurement points C368)
Note: By default tested with known good UL8 flex
Check BL8’s
connector
X400
Check that UL8 Flex connector (=X12) is not broken and flex is OK.
Note: By default tested with known BL8 module.
Faulty UL8 Flex
Faulty MADLinda D300
(DSPGenOut2)
Wintesla informs which memory address the erasing fails. See note which
address corresponds which Flash components.
Faulty components D351, D352 or D353
YES
OK
NO
OK
OK
NOT OK
OK
Erasing/programming fails
YES
NOT OK
* The VPP voltage level limit is 3 to 5 per cent below
Note:
Flash 2 (=D353) erasing area starts 0x02000000
Flash 2 (=D353) erasing area stops 0x023FFFFF
Serial Flash (=D354) erasing area starts 0x8000000
Serial Flash (=D354) erasing area stops 0x841FFFF
the set VPP voltage level.
Note:
Flash 0 (=D351) erasing area starts 0x00000000
Flash 0 (=D351) erasing area stops 0x003FFFFF
Flash 1 (=D352) erasing area starts 0x01000000
Flash 1 (=D352) erasing area stops 0x013FFFFF
Figure 7.