The tuning operations of the TFF-3 are carried out using the Service Soft-
ware. The Service Software program turns the phone into Locals Mode,
in which the phone can be outwardly controlled via the M2BUS interface.
Tuning is based on the Service Software communicating with the D/A and
A/D converters of the phone.
The calibration data of the phone resides on the EEPROM. The contents
of the EEPROM can be read by the Service Software. The program also
enables writing of the factory preset calibration data to the EEPROM, af-
ter which the whole tuning process should be carried out again.
If a repair has been carried out on the RF section of a system module
then the appropriate tunings should be performed as described in the fol-
lowing section and using th on–screen help menus as a guide. Spare sys-
tem modules will be delivered pre–tuned from the factory and will not re-
quire retuning.
PAMS Technical Documentation
During tuning, proceed as follows:
– Take care not to damage sensitive measuring instruments with exces-
sive RF power.
– Carry out all tuning steps in the shortest possible time to avoid exces-
sive heating of RF units.
– Perform all tuning steps in the order presented.
– Never try to mask a fault by tuning it out!
Minimum Required Servicing Equipment
–PC/AT Computer with Service Software installed: See Service Software
instructions.
–M2BUS cable XCM-3 and other service software accessories; see
equipment set–up pictures.
–Audio analyzer.
–RF power meter, power measurement sensitivity –10 dBm.
–RF generator.
–Device to provide specified test modulation to modulate RF generator.
–Multimeter or DVM.
–Attenuator and branching unit.
–Power supply, nom. voltage 13.5 V .
Equipment Setup
Turn off the computer before connecting the cable to avoid possible damage to the serial port.
Page 4
Nokia Mobile Phones Ltd.
Issue 1 08/99
PAMS Technical Documentation
Caution:Do not connect the PKD–1 to the serial port. This could damage
the PKD–1 !
Connect the modular cable between the terminal and the modular adapter. The modular adapter must be connected to the D9–D25 cable. Connect the 9–pin male D–connector in your PC serial port.
For transmit, audio measuring and adjustment connect ADS–1 EAR/MIC
breakout cables as follows:
– EAR line to test equipment AF INPUT
– MIC line to test equipment AF GEN OUTPUT
Connect PCS-1 power cable to the power supply. Supply voltage is set to
13.5 V.
TFF-3
Tuning Instructions
Issue 1 08/99
Nokia Mobile Phones Ltd.
Page 5
TFF-3
Tuning Instructions
Equipment Setup For TFF-3 Tuning
11
PAMS Technical Documentation
ItemService AccessoryTypeCode
1 WLL Unit TFF–3
2 Power cable PCS–10730012
3 Modular cable XCM–14626131
4Modular T-Connector 4626134
5 RF Service Cable SRC-60630178
6 Marconi Tester
7 D9–D25 Cable 4626170
8 M2Bus AdapterDAU-20750006
9Service PC
10WinTesla Service software diskette 3,5”0774071
10Dongle Drivers for Win 3.1, 95 and NT diskette 3,5” 0770137
Note: items 7. and 8. can be replaced by DAU–9S cable (0730108)
Page 6
Nokia Mobile Phones Ltd.
Issue 1 08/99
PAMS Technical Documentation
Manual Tuning Steps
General
If any repairs or replacements have not been made, manual tuning is not
necessary on the phone. Spare modules have been tuned at the factory.
If some repair or replacements have been made, manual tuning is nessessary.
If you do not want to use phone country version dependent tuning channels, proceed as follows:
1. Choose RF controls from the Configure menu.
2. Change channel values.
3. Choose Write File –button in order to save channel values in
”TESLA.ini” –file.
TFF-3
Tuning Instructions
The program saves the channel settings and uses them every time when
Tunings or Testing menu is chosen. The program uses ordinary channels
depending on the phone country version, if you don’t change channels.
Default channels in RF–controls
dialog
Using
Channel low for 1 band phonesAfc and afc–limits tuning, basic settings
Channel mid for 1 band phonesAfc and afc–limits tuning, basic settings
Channel high for 1 band phonesAfc and afc–limits tuning, basic settings
Channel low for 2 band phonesAfc and afc–limits tuning, basic settings
Channel mid for 2 band phonesAfc and afc–limits tuning, basic settings
Channel high for 2 band phonesAfc and afc–limits tuning, basic settings
Rssi channel low band 1Rssi ch compensation
Rssi channel mid band 1Rssi ch compensation
Rssi levels and agc (1 band phones)
Rssi channel high band 1Rssi ch compensation
Rssi channel low band 2Rssi ch compensation
Rssi channel mid band 2Rssi ch compensation
Rssi channel high band 2Rssi ch compensation
Rssi mid ch for 2 band phonesRssi levels and agc (2 band phones)
Issue 1 08/99
Nokia Mobile Phones Ltd.
Page 7
TFF-3
Tuning Instructions
1 – AFC Middle Frequency Tuning
This dialog is used for adjusting the TX frequency for the phone’s middle
channel.
The phone is turned to the default middle channel (RX and TX) and transmitter is activated.
Note:Ambient temperature during tuning should be approx. +25 °C.
AFC middle frequency tuning procedure:
– Select Tunings/AFC middle frequency tuning
– Connect devices and set values to measuring equipment according to
information texts.
– Measurement device shows the AFC frequency D/A converter reading.
PAMS Technical Documentation
– Tune until the value is the middle TX frequency.
– Use the arrow keys or mouse to change the value and ALT–S to write
the value to EEPROM.
2 – AFC Frequency Limits Tuning
This dialog is used for adjusting the TX frequency limits for the phone’s
middle channel.
The phone is turned to the default middle channel (RX and TX) and transmitter is activated.
AFC frequency limits tuning procedure:
– Select Tunings/AFC frequency limits tuning
– Set the RF–generator frequency and signal level according to the information given in dialog box..
– Measurement device shows the AFC frequency D/A converter reading.
– Tune until the value is the TX frequency ± 2.5 kHz.
– Use the arrow keys or mouse to change the value and ALT–S to write
the value to EEPROM.
Page 8
Nokia Mobile Phones Ltd.
Issue 1 08/99
PAMS Technical Documentation
3 – RSSI and AGC Tuning
This dialog is used for adjusting the RSSI and AGC levels.
RSSI tuning procedure:
– Select Tunings/RSSI and AGC Tuning
– Set RF–generator frequencies and signal levels according to the in-
formation given by the Service Software.
– The Service Software reads values given by A/D converter for received
signal.
– The Service Software tunes three tuning points for channel compensa-
tion (Low, high and middle channel).
– The program also executes the six tuning points for RSSI levels.
– Set the RF signal levels according to the information given by the Service Software.
– The program shows the AGC ON and the AGC OFF levels.
4 – Deviation Tuning
Deviation tuning procedure:
– Select Tunings/Deviation tuning
– Connect devices and set measurement equipment values according to
information texts.
– Use the arrow keys or mouse to change tuning values and ALT–S to
write them to the phone. Use TAB key to change field.
– Compare measurement device values to the program information text
values.
– Tune until the measured value is within range given by dialogs informa-
tion texts.
Issue 1 08/99
Nokia Mobile Phones Ltd.
Page 9
TFF-3
Tuning Instructions
FFSK Deviation Tuning
This adjustment is used to set outgoing FFSK data deviation.
The command turns the phone to default middle channel (RX and TX),
activates the transmitter, opens the data path, and sets up the modem to
send a continuous 1800 Hz, ”0” signal.
To adjust, enter values (0–15) for the D/A converter, and compare results
to the reading given by the deviation meter.
Nominal Deviation Tuning
The purpose of this tuning operation is to adjust the nominal deviation of
voice and DTMF signaling.
The command turns the phone to the default middle channel, and activates the transmitter.
PAMS Technical Documentation
To adjust, enter values from the range 0–7 into the D/A converter and
compare results with deviation meter readings.
Maximum Deviation Tuning
This adjustment has an effect on voice and DTMF signal maximum deviation.
The command turns the phone on the default middle channel, and activates the transmitter.
Enter various values from the range 0–7 into the D/A converter, and
compare results with the reading in the deviation meter.
Note:Deviation will increase when D/A reading is decreased.
Rx Tri Tuning
The purpose of this adjustment is to adjust Rx Trimmer.
The transmitter is turned off.
To adjust, enter values from the range 0–15 into the D/A converter.
Use ALT+1 and ALT+2 keys to enable/disable expander. Tune until the
level in EXTEAR–pin is the same with and without expander.
Phi Signal Deviation Tuning
The purpose of this adjustment is to adjust phi signal (SAT) deviation.
The command turns the phone on the default middle channel (RX and
TX), activates transmitter, and enables the φ loop.
To adjust, enter values (0–31) to the D/A converter and compare changes
to deviation meter readings.
Page 10
Nokia Mobile Phones Ltd.
Issue 1 08/99
PAMS Technical Documentation
5 – TX Output Power Tuning
This adjustment writes the power levels of the phone transmitter into the
EEPROM. When doing this, a power meter must be used.
TFF–3 has twelve (12) power levels to tune. Power levels low, middle and
high are tuned at all four bands.
Tuning can be interrupted when necessary by pressing Esc key.
Power levels tuning procedure:
– Connect power meter to the antenna connector of the phone.
– Adjust the phone supply voltage to +13.5 V
– Select Tunings/TX output power
– Use the arrow keys, or mouse to change the tuning value.
– Change tuning value until the power meter value is at the target power
value given in dialog’s information texts.
TFF-3
Tuning Instructions
– Use TAB key to change field and ALT–S to write values to EEPROM.
6 – Show Tuning Values
This dialog box enables reading of the phone tuning parameters, and
writing of the default values.
Note:Spare modules received from the factory are factory–tuned.
Issue 1 08/99
Nokia Mobile Phones Ltd.
Page 11
TFF-3
Tuning Instructions
Introduction to Flashing
The Flash Programming procedure can be divided into six main steps.
1. Prommer synchronous clock pin is set to low.
2. Phone power is switched on. The ASIC boot software is now ready to
receive the secondary boot code.
3. The secondary boot is loaded into the internal phone MCU RAM at a
low communication speed.
4. As response to a successful secondary boot down loading and execution the phone returns its current HW configuration and MCU SW version.
5. The prommer selects one of the target specific download codes and
sends it to the phone. The code selection is executed automatically based
on the phone configuration data. The transmission speed used is as
fast as the target HW allows. Down load code is loaded and executed in
the RAM.
PAMS Technical Documentation
6. MCU SW is programmed into the phone FLASH using the flashing algorithm provided in down load code. The data is transmitted in data
frames, frame size varies from one to several kilobytes. The download
code includes flash erase and flashblank check routines for the MCU SW
update purposes.
8AC Charger (Item incl. in FPS-4 pack)ACL-3E0680015
The table continues next page.
Page 12
Nokia Mobile Phones Ltd.
Issue 1 08/99
PAMS Technical Documentation
Equipment Setup For TFF-3 Flashing
TFF-3
Tuning Instructions
Continued from previous page
ItemService AccessoryTypeCode
9 D15–D15 Cable AXS–50730091
(item included in FPS–4 sales package)
10D9–D9 Cable AXS–40730090
(item included in FPS–4 sales package)
11Printer Cable 0730029
(item included in FPS–4 sales package)
12Software protection keyPKD–10750018
(Service dongle)
13Software FPS–4 prommer diskette 3.5”0774043
(item included in FLA-5/FPS-4 sales package)
13Software Flash program TFF–3 diskette 3.5”0774131
Issue 1 08/99
Nokia Mobile Phones Ltd.
Page 13
TFF-3
Tuning Instructions
HW requirements: IBM compatible PC, CPU 80486 or later.
One Serial and one Parallel port.
Parallel port can be LPT1 to LPT3.
Serial port can be any of COM1 to COM4.
If selected port is non default (LPT1 or COM1) port you must run prom-
mer setup.
SW requirements: MSDOS 3.x (5.x) or later.
The installation program ’SETUP.BAT’ needs later DOSversion. It uses
DOS command ’choice.com’ which ismissing old (< 5.x) DOS versions.
Prommer software does not run under WINDOWS properly.
PC MCU speed have no affects to phone programming times!
MCUSW downloading speed depends directly on PC speed !
PAMS Technical Documentation
Installation
1. Connect parallel cable from PC LPT port to FPS–4 Parallel Input.
2. Connect serial cable from PC COM port to FPS–4 Serial Input.
3. Connect the Flash Loading Adapter to the FPS–4 Phone Connector.
4. Connect Power Plug to FPS–4 PWR connector.
5. Run setup utility program ’SETUP’ on your diskette drive.
Give the target directory in parameter ( e.g. A:> SETUP C:\FPS4 ).
Check that parallel and serial port numbers and your Flash loading
adapter type are selected correctly.
NOTE! You can change FPS–4 prommer io–port numbers later from
prommer setup menu when you run prommer with ’–S’ option ( e.g.
C:\FPS4> FPS4 –S ). The Flash adapter type can be changed any time
in setup menu.
All prommer settings are saved to ’SETUP.FPS’ file in prommer default
directory.
Prommer use interface
After sales version screen menu map
Main Menu
Help on Help
Program Phone by Type
Program Phone by File Name
Page 14
Nokia Mobile Phones Ltd.
Issue 1 08/99
PAMS Technical Documentation
Advanced Options Menu...
Read Phone SW & HW ID
Download MCUSW to Prommer Box
Program Phone with Code in Box
Move MCUSW Prommer SRAM–>Flash
Delete MCUSW from Prommer
Action updates MCUSW code to target HW almost automatically; only
thing that user must do is to select correct target HW type from menu.
This action uses data file ’RELEASES.FPS’, which links each target HW
to MCUSW code file. This file must be update manually in DOS ASCII text
editor.
Program Phone by File Name
Action loads selected MCUSW file to prommer SRAM and flashes it immediately to target.
Read Phone SW & HW ID
Action displays detailed list of target HW & SW configuration.
Download MCUSW to Prommer Box
Action loads selected MCUSW file to prommer SRAM.
Program Phone with Code in Box
PAMS Technical Documentation
Action flashes selected MCUSW code in prommer memory to target.
Old MCUSW code is deleted automatically from target Flash before pro-
gramming.
Move MCUSW Prommer SRAM–>Flash
Action moves MCUSW code to prommer SRAM to Flash.
Delete MCUSW from Prommer
Action deletes MCUSW from prommer memory.
Prommer SW Version Info
Action displays all code versions (execpt MCUSW codes) in prommer
box.
How to start Prommer software
Preparations:
Install prommer software with ‘SETUP.BAT’ batch program.
1.Run flash prommer software called ‘FPS4’ in directory where FPS4 was
installed.
Page 16
NOTE! Prommer software do not run properly under WINDOWS.
Nokia Mobile Phones Ltd.
Issue 1 08/99
TFF-3
PAMS Technical Documentation
Tuning Instructions
Troubleshooting
Prommed does not run
Failure: Prommer power LED does not light up.
Check internal fuse in the prommer box (size 5x20 mm, 500 mA).
Failure: Prommer internal RAM test is failed if both of Mode LEDs are blinking simultaneously.
Reboot prommer. If RAM test fails again, send prommer to service.
Failure: Prommer programs do not reach MAIN MENU.
1. If prommer is still in IDLE state:
Check Parallel cable and used PC port number.
Run setup to change LPT setup settings or restart FPS4 with ’–s’ option
and change LPT number.
2. If prommer is still in WAIT BOOT COMMAND state:
Check Serial cable and used PC port number.
Run setup to change COM setup settings or restart FPS4 with ’–s’ option
and change COM number.
3. If both of prommer MODE LEDs are off, prommer application does not
start properly:
Run setup or restart FPS4 with ’–s’ option and download FPGA and Application 1 in second setup menu.
4. If prommer is stuck on any reason and it does not give boot response,
you must disconnect ALL cables from prommer box.
Prommer power consumption is so low that it get power from communication cables and do not exit fail loop where it was stuck.
Prommer is in IDLE state when MODE 1 / MODE 2 LEDs are toggled
slowly (once /sec).
Prommer is in WAIT BOOT COMMAND state when Mode LEDs are
toggled very fast. This state has 20 second time–out. After time–out
prommer returns to the IDLE state.
Corrupted phone flash ID
If the target Flash ID bytes is set wrong way or they are corrupted, you
can not reprogram phone normally or even erase it without corrected
Flash ID bytes. There is two ways to change Flash ID bytes:
1. ’RELEASES.FPS’ file includes Flash ID description field which is
used when phone is programmed from ’Program Phone by Type’ menu.
Issue 1 08/99
Nokia Mobile Phones Ltd.
Page 17
TFF-3
Tuning Instructions
The Flash ID in target system is replaced always with Flash ID in
’RELEASES.FPS’ file.
2. ’Modify flash id bytes’ command (only in R&D version) in prommer
menu for FLASH ID byte modifying.
TIP! You can force prommer to use Flash id bytes in MCUSW file simply
by setting Flash id bytes to FF FF FF FF (Prommer act like Flash is
empty)
Wrong value of FLASH ID bytes may fail target erasing and programming
in many ways:
– The number of Flash devices is wrong
– Flash size is wrong
– Flash type is set to OTP
– Memory access too fast for Flash or SRAM memory
In the start of MCU code are four Flash ID bytes which defines the target
base band hardware. Do not confuse these bytes to two Flash manufacture and device identifier bytes, which are read directly from Flash device
HW and are descripted in ’DEV_LIST.FSP’ file.
PAMS Technical Documentation
Where prommer gets the Flash ID bytes?
1. Empty Flash (All Flash ID bytes are FFHs)
–> Prommer uses Flash ID in MCUSW file
2. Programmed Flash
– OTP device (First target Flash id byte bits xxx000xx are zeros)
–> NMP Flash id = OTP device
–> Prommer do not want to reprogram target
– Non OPT devices
–> Prommer uses Flash ID read from target device
3. FLASH ID bytes are modified
– New Flash ID bytes are entered by user. (MCUSW file Flash ID
byte are discard)
4. ’Program Phone by Type’ selection uses always Flash ID bytes in
’RELEASES.FPS’ file when available.
WARNING! Do not try to program phone with real OTP device!
Page 18
Nokia Mobile Phones Ltd.
Issue 1 08/99
PAMS Technical Documentation
Appendix A
FPS–4 Flash prommer files
FPS4.EXE FPS–4 prommer user interface, executed in PC
FPGA0100.MCS Code for FPS–4 internal FPGA chip (update from setup
utility or FPS4 menus.
FPS4 may need to run with ’–S’ setup parameter) BBSW1x.xxx Applica-
tion 1 code, executed in FPS–4 box.’x.xxx’ is the vesion number. (update
from setup utility or FPS4 menus.
FPS4 may need to run with ’–S’ setup parameter)
BOOT2.BIN Secondary boot, executed in target phone (update from
setup utility or FPS4 menus)
28F008.BIN Flash algorithm file for Intel 28F00x memories, executed in
target phone. (update from setup utility or FPS4 menus)
TFF-3
Tuning Instructions
DEV_LIST.FPS This DOS text file includes Flash descriptions and Flash
alias data. (file can be modified by user with ASCII text editor)
HELP.FPS FPS4 help file. File is in hyper text format and it can give
case sensitive help.
RELEASES.FPS This DOS text file includes list of current MCUSW release versions for all HW versions individually. The User must update this
file with any DOS ASCII text editor. Main Menu selection ’F2 Program
Phone by Type’ needs this file.
SETUP.FPS Prommer creates this DOS text file automatically. File includes all prommer settings.
FLASH.LOG Prommer creates this DOS text file with –tn parameters
automatically. File is appended with prommer M2BUS messages. This file
is very useful if something fails...
Issue 1 08/99
Nokia Mobile Phones Ltd.
Page 19
TFF-3
Tuning Instructions
PAMS Technical Documentation
Appendix B: FPS–4 Front plate
+–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+
| o o |
| FPS4 FLASH PROMMER NOKIA |
| MODE1 |
| | MODE2 |
| | | M2BUS |
| DAU2 | | | VPP_TARGET |
| +––––+ | | | | FPGA_LOADED |
| | | | | | | | POWER |
| | | o o o o o o |
| +––––+ |
| o o |
+–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––+
MODE1 & MODE 2 LEDS
These LEDs display prommer status.
– MODE1 & MODE2 LEDs are toggled slowly (once / second)
Prommer is in IDLE state, DAU2 connector can be used for M2BUS com-
munication.
– MODE1 & MODE2 LEDs are toggled very fast (5 times / second)
Prommer is in WAIT BOOT COMMAND state.
This state has 20 second time–out.. After time–out prommer returns to
the IDLE state.
– MODE1 LED is ON
Prommer runs DCT Application (not available yet).
– MODE2 LED is ON
Prommer runs DCT2 Application.
– MODE2 LEDs blinks slowly (once / second)
M2BUS LED
This LED light up when M2BUS is used.
VPP TARGET LED
Page 20
This LED light up when target Vpp is switched on.
FPGA LOADED LED
This LED should always light up when prommer software is running.
POWER LED
This LED should always light up when prommer has power on.
Nokia Mobile Phones Ltd.
Issue 1 08/99
PAMS Technical Documentation
Appendix C, Vocabulary
AbbreviationDescription
Application codePrommer software, executed in prommer
ASIC–bootBootstrap code
Bootstrap code Code that resides in target hardware, either in
is not lost even when power down
FPS4Name of second generation Flash prommer
M2BUSSerial communication bus which can be con
nected to accessory devices and test PC
MCUMaster Control Unit
MEMobile Equipment
MSMobile Station
OTPOnce Time Programmable device (Mask PROM
or non erasable EPROM)
PCIBM PS/AT or compatible personal computer
PKDParallel Port Software Protection Device
RFRadio Frequency parts
Secondary bootSecond bootstrap code, loads download code
SRAMRandom access memory , data is lost when power
SWSoftware
TargetPhone hardware
Issue 1 08/99
into target RAM. Executed in target hardware.
down
Nokia Mobile Phones Ltd.
Page 21
TFF-3
Tuning Instructions
PAMS Technical Documentation
[] 1
This page intentionally left blank.
Page 22
Nokia Mobile Phones Ltd.
Issue 1 08/99
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.