Flash Concept On - Nokia 616 Service Manual

Carkit phone (tfe-4/rv-1)
Hide thumbs Also See for 616:
Table of Contents

Advertisement

TFE-4/RV-1
TF4 Technical Information
For TFE-4/RV-1 SW update is possible by using TFE-4/RV-1 specific Flash cable, which
can be connected at one side to the display unit connector and with the other side to the
FLS-4S or FPS-8. Because FLS-4S and FPS-8 only support phone compatible output volt-
ages an extra power supply for 12V is needed, and the AD-2 power adapter. To enable
flashing the power test has to be disabled on the AD-2 and ignition switch has to be
active. With FPS-8 (when flashcable is connected properly) and active radio unit can be
seen when MBUS LED is off. When power supply is switched off (or power connector is
disconnected) the MBUS light of FPS-8 will lighten. Unfortunately this cannot be
detected by FLS-4S.
In some cases a slow blinking MBUS LED can be seen, generally this can be ignored but
this shows that there is a major bug within the phone memory. But even in this case
flashing can be initiated in normal way, just by choosing the TFE-4/RV-1 product within
TSS software and starting flashing.
The complete Flashbus including BSI-Line is directed via the TF5R PWB to the system
Bord-2-Bord connector and the phone PWB will get power via the power bord2bord con-
nectors. The actual programming is indicated to the UPP by using the MBUS_RX signal
between the UPP and the UEM. The MBUS signal from the UEM to the flash prommer
(FPS8 box) is used as clock for the synchronous communication. The flash prommer keeps
the MBUS line low during UPP boot, to indicate that the flash prommer is connected. If
the UPP MBUS_RX signal is low on UPP, the MCU enters flash programming mode. If the
signal is high, the MCU starts loading software from the flash.
The VPP is not directed outside to connectors, so this option only can be used with MJ-1,
when the production testpattern of TF-4 is accessible.
Flash concept on TF-4
Like all DCT-4 products, the TF4 Engine PWB thee MCU only waits a specified time. In
order to avoid accidental entry to the "flash programming mode", to get input data from
the flash prommer. If the timer expires without any data being received, the MCU will
continue the boot sequence. The MBUS signal from UEM to the external connection is
used as clock during flash programming. This means that flash-programming clock is
supplied to the UPP on the MBUS_RX signal. The flash prommer indicates to the UEM
that flash programming/reprogramming by writing an 8-bit password to the UEM. The
data is transmitted on the FBUS_RX line and the UEM clocks the data on the FBUS_RX
line into a shift register. When the 8-bits have been shifted in the register, the FPS8-box
generates a falling-edge on the BSI line. This loads the shift register content in the UEM
into a compare register. These 8-bits will be compared in a register to see if they match
the "secret" default value inside the UEM. At this point the flash prommer must pull the
MBUS signal to UEM low, in order to indicate to the MCU that the flash prommer is con-
nected. The UEM reset-state machine performs a reset to the system (PURX low for 10–
100 ms). The UEM "flash-programming mode" is valid until MCU sets a bit in the UEM
register, which indicates the "end of flash programming". Setting this bit also clears the
compare register in the UEM previously loaded, at the falling edge of the BSI signal. Dur-
ing the "flash-programming mode" the UEM watchdog is disabled. When the bit is set it
indicates "end of flash programming" and it resets the UEM watchdog timer to it's
default value. Clearing the flash programming bit also causes the UEM to generate a
Page 8b-30
Company Confidential
Copyright © 2005 Nokia Corporation.
Company Confidential
Nokia Customer Care
Issue 2.0 Mar/2005

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

610

Table of Contents