User Guide

CCS Technical Documentation Troubleshooting — RF
RH-17
Issue 1 04/2003 Nokia Corporation Confidential Page 15
4 Next, try and flash phone using correct SW version. In Phoenix: Flashing>FPS-8
Flash>Press Flash. Next select OK from pop-up screen. Under next screen, Flash
File Selection, choose Image File “set”. In correct directory where you store your
flash files (usually programs, then Nokia, Phoenix, Flash) select correct Flash SW
xxxxxxx.nep (if not sure what correct SW to use, file name should match SW in a
known good phone. To check this, take good phone in Phoenix and go Prod-
uct>Phone Information and check MCU SW Version). Once correct SW file is
found, select OK. You will be prompted to save settings, select “yes”. Flashing
should begin at this point. For first time, set up of prommer this could take a few
minutes due to PC loading file to prommer RAM first. After first use, prommer
stores this in internal RAM and should proceed faster with subsequent phones
downloading of flash software. If phone passes, then more than likely a false fail.
If phone fails, read prommer failure code and use Code Sheet in TS.
Troubleshooting
Make sure phone has PSN and SW version is correct by checking Phone Information. Ref-
erence the following guides to TS flash problem: Haukka BB Operation doc, Prommer
Codes, and Flash Block Diagram.
Test 5 ST DBUS
Description
The purpose of this test is to verify that the connections between the DSP inside the UPP
and the UEM, via the DBUS, are intact. The DSP will write an arbitrary value to DBUS
General Control register in UEM; then DSP will read DBUS from General Control register
in UEM and valid repeatability.
Explanation of Result
Pass or Fail
Manual Verification
In Phoenix, put phone in Local Mode. Next, BB Self Tests - select ST_UEM_DBUS_TEST,
then Run.
Troubleshooting
Connections tested at UPP: DBUSDA (pad L3) check test point J414, DBUSCLK (pad K3)
check test point J413, DBUSEN1X (pad J3) check test point J415. At UEM: DBUSDA (pad
A11), DBUSCLK (pad D10), and DBUSENX (pad B10). Bus interface name is RFCONVC-
TRL(2:0).
Test 6 ST CBUS
Description
The purpose of this test is to verify that the connections between the MCU inside the
UPP and the UEM, via the CBUS, are intact. The MCU will read CBusADCR register and
verify UEM chip version is valid.