0508 ita gsm rf adjust xmm6260

N e v e r s t o p t h i n k i n g .

Confidential

ITA RF Adjustment - GSM

XMM6260

Specification

Revision 0.9, 20/09/2010

l

ABM®, ACE®, AOP®, ARCOFI®, ASM®, ASP®, DigiTape®, DuSLIC®, EPIC®, ELIC®, FALC®, GEMINAX®, IDEC®, INCA®, IOM®, IPAT®-2, ISAC®, ITAC®, IWE®, IWORX®, MUSAC®, MuSLIC®, OCTAT®, OptiPort®, POTSWIRE®, QUAT®, QuadFALC®, SCOUT®, SICAT®, SICOFI®, SIDEC®, SLICOFI®, SMINT®, SOCRATES®, VINETIC®, 10BaseV®, 10BaseVX® are registered trademarks of Infineon Technologies AG. 10BaseS™, EasyPort™, VDSLite™ are trademarks of Infineon Technologies AG. Microsoft® is a registered trademark of Microsoft Corporation, Linux® of Linus Torvalds, Visio® of Visio Corporation, and FrameMaker® of Adobe Systems Incorporated.

Edition 20/09/2010

Published by Infineon Technologies AG, St.-Martin-Strasse 53, 81669 München , Germany

© Infineon Technologies AG <2005> All Rights Reserved.

Attention please!

The information herein is given to describe certain components and shall not be considered as a guarantee of characteristics.

Terms of delivery and rights to technical change reserved.

We hereby disclaim any and all warranties, including but not limited to warranties of non-infringement, regarding circuits, descriptions and charts stated herein.

Information

For further information on technology, delivery terms and conditions and prices please contact your nearest Infineon Technologies Office (www.infineon.com ).

ITA RF Adjustment - GSM Specification

Confidential

i Revision 0.9, 20/09/2010

Revision History

Revision Date Author Item / Section Comment

0.1 2009-10-27 STS All pages Document created

0.2 2010-01-22 STS Tx part Tx part updated

0.3 2010-02-11 STS All sections Review

0.4 2010-03-16 STS All sections Rx diversity and XMM6260 added

0.5 2010-04-26 GBO 5.4 Pedestal calibration updated

0.6 2010-06-16 STS All sections New parameters and clean up

0.7 2010-08-03 STS All sections Minor updates in all sections

0.8 2010-08-30 STS Rx part Offset set to 67 kHz. Set comp 6 removed.

0.9 2010-08-20 STS RF adjust Pre setup, Rx temperature and pedestal target changed/added.


Confidential

ii Revision 0.9, 20/09/2010

Table of Contents

1 Introduction....................................... ............................................................................................. 1 1.1 Scope............................................................................................................................................... 1

2 Test Recommendations ............................... ................................................................................. 2 2.1 Test Case Sequence ....................................................................................................................... 2

3 Test Setup ......................................... ............................................................................................. 4

4 Interface Description.............................. ....................................................................................... 5 4.1 AT interface ..................................................................................................................................... 5 4.2 Selecting channel numbers for the PCS1900 band ........................................................................ 5 4.3 Band indexing of calibration parameters ......................................................................................... 5

5 RF Adjustment ...................................... ......................................................................................... 6 5.1 Initialize the ME to RF Adjust .......................................................................................................... 6 5.1.1 Preconditions ............................................................................................................................... 6 5.1.2 Test Sequence............................................................................................................................. 6 5.2 VCTCXO Adjustment....................................................................................................................... 6 5.2.1 Preconditions ............................................................................................................................... 7 5.2.2 Test Sequence............................................................................................................................. 7 5.2.3 Calculation formulas and tables................................................................................................... 8 5.2.4 Storage of Adjusted Parameters.................................................................................................. 9 5.3 Rx Adjustment ................................................................................................................................. 9 5.3.1 Preconditions ............................................................................................................................. 10 5.3.2 Test Sequence........................................................................................................................... 10 5.3.3 Storage of Adjusted Parameters................................................................................................ 11 5.4 Tx Adjustment................................................................................................................................ 12 5.4.1 Preconditions ............................................................................................................................. 13 5.4.1.1 Preconditions for calculations................................................................................................ 13 5.4.2 Test Sequence........................................................................................................................... 14 5.4.2.1 Test Sequence open loop calibration at centre frequency .................................................... 14 5.4.2.2 Test Sequence for power vs. frequency................................................................................ 15 5.4.3 Calculation formulas and tables................................................................................................. 15 5.4.3.1 Power vs. frequency .............................................................................................................. 15 5.4.3.2 Power at centre frequency..................................................................................................... 16 5.4.3.3 Detector offset (Vdet_idle) ..................................................................................................... 18 5.4.3.4 PA pedestal calculation ......................................................................................................... 19 5.4.4 Storage of Adjusted Parameters................................................................................................ 19

Test References .................................... ......................................................................................................... 20

Abbreviations / Terminology ........................ ................................................................................................ 21


Confidential

iii Revision 0.9, 20/09/2010

List of Figures

Figure 1: Outlined sequence diagram ............................................................................................................... 3 Figure 2: Test setup........................................................................................................................................... 4

List of Equations

Equation 1: Slope calculation ............................................................................................................................ 8 Equation 2: Updating XoTune ........................................................................................................................... 8 Equation 3: Scaling slope to representation in NV-RAM................................................................................... 8 Equation 4: Calculating Tx frequency compensation arfcn_comp_parms ...................................................... 15 Equation 5: Frequency compensation of raw measured dBm power.............................................................. 16 Equation 6: Transforming dBm power to voltage domain (units of √0.05 volt)................................................ 17 Equation 7: Equation to be used for Target [dBm] at 10 dBm and above for interpolating Vdet. ................... 17 Equation 8: Equation to be used for Target [dBm] less than 10 dBm for interpolating Vdet. .......................... 17 Equation 9: Interpolating PA pedestal (normal temperature). ......................................................................... 19

List of Tables

Table 1: Set of test step..................................................................................................................................... 2 Table 2: Set of test step..................................................................................................................................... 2 Table 3: AFC calibration limits for MS with VCTCXO........................................................................................ 9 Table 4: Numerical example for arfcn_comp_parms calculation..................................................................... 16 Table 5: Measurement points for low bands ................................................................................................... 18 Table 6: Linear interpolation in Voltage domain .............................................................................................. 18


Confidential

1 / 1 Revision 0.9, 20/09/2010

1 Introduction This document describes the 2.5G production RF-adjustment of mobile phones (ME’s) based on Infineon’s Mobile Platform XMM6260.

1.1 Scope

The description covers the Conventional Adjustment method for GSM/GPRS/EGPRS calibration, using a spectrum analyzer and an RF generator. An example of a combination of a spectrum analyzer and signal generator is R&S CMU200, used in non-signaling mode, but several other possibilities exist, e.g. Agilent 8960

The document is complemented by the ITA_UMTS_RF_adjust_XMM6260 [1] describing the Conventional Adjustment method for UMTS calibration, using the same (or similar) instruments. For fast calibration please see document [4].

This ITA is based on the SMARTi- UE2™ calibration specification [5].


Confidential

2 / 2 Revision 0.9, 20/09/2010

2 Test Recommendations The RF adjustment is done in non signaling mode, followed by calculation of correction parameters. These correction parameters are stored in the ME using AT commands.

Default compensation values in ME are created when the ME is first booted (first boot after initial SW download).Not all of these compensation values must subsequently be adjusted, fine tuned, for each individual ME in production.

Among configuration and compensation parameters inside the ME’s NV-RAM are also parameters that configure the calibration, e.g. frequency numbers and levels to use for calibration. These are mentioned in the preconditions section for each calibration step.

Calibration of the reference frequency is covered by the AFC adjustment and must be done prior to Rx and Tx calibration. If the system clock is not accurately adjusted before Rx and Tx measurements are done, this will result in inaccuracies.

The following Table specifies the set of test step.

Step Adjustment Comment

AFC Adjustment Done in only one 2G band Mandatory

Rx Adjustment Done in all 2G bands Mandatory

Tx Adjustment Done in all 2G bands Mandatory

Table 1: Set of test step.

In addition to these 2G calibrations, the 3G parameters must also be calibrated. This is described in [1]:

Step Adjustment Comment

Rx UMTS Adjustment Done in all 3G bands Mandatory

Tx UMTS Adjustment Done in all 3G bands Mandatory

Table 2: Set of test step.

2.1 Test Case Sequence

This section describes outlined sequence and detail sequence diagrams.

The flow chart shows brief sequence of adjustments. After the adjustments are performed, RF verification is generally needed.

Adjust AFC default value and AFC slope

TX power calibration including pedestal levels


Confidential

3 / 3 Revision 0.9, 20/09/2010

Figure 1: Outlined sequence diagram

The ME is powered on in test mode

Rx gain and frequency compensation adjustment

UMTS calibration is described in ITA_UMTS_RF_adjust_XMM6260.pdf [1]

Start

Initialize ME for RF Adjustment

The ME is set into ”Non Signaling Test Mode” which allows the RF drivers to run without using the protocol stack

VCTCXO adjustment

2GRx adjustment

2GTx adjustment

Perform UMTS calibration

Adjust AFC default value and AFC slope

Tx power compensation including pedestal levels


Confidential

4 / 4 Revision 0.9, 20/09/2010

3 Test Setup A typical test setup is illustrated in Figure 2, which primarily consist of a Test PC with an Interface to the ME and a set of test instruments. The test PC controls the ME and the test instruments and executes the calibration.

The following equipment is typically used in the production setup:

• Test PC

• Power supply

• Spectrum analyzer

• Signal generator

All RF adjustments are performed on the coaxial test adapter and should be done with all shielding mounted. It is recommended to use a small RF attenuator (e.g. 3 – 6 dB) as close as possible to the coaxial test adapter for minimizing RF mismatch.

Figure 2: Test setup.

Spectrum analyzers and generators can be separate instruments, or combined. Examples of combined instruments are Rohde & Schwarz CMU200 or CMW500, and Agilent 8960.

Controlling PC

Test Management SW

Allignment Application

HW Drivers

AT command / DWDIO.DLL

GPIB/VXI/ PXI/..

Mobile Equipment Shielded Environment

HW Interface

RS-232 or USB com port (115.2 kBaud)

Instruments


Confidential

5 / 5 Revision 0.9, 20/09/2010

4 Interface Description Adjustment of the phones in production is mainly based on the use of AT commands which constitutes the SW test interface between test-PC and the ME.

AT commands are used to control the ME, i.e. set up the MON burst and to get fixed and adjustable parameters to and from the ME see [2] and [3] for details of AT commands.

Before starting any test sequence on any ME, the ME must be flashed with a suitable target SW on a complete erased flash and rebooted to ensure proper initialization of all parameters.

4.1 AT interface

When AT commands are send to the ME, the return strings are always structured in the same way.

at@command_to_ME Return string case 1: Return string followed by a carriage return and one or more new line charcters. An “OK” followed by a carriage return and new line. Return string case 2: Return string (optional error description) terminated by carriage return, one or more new line charcters,

“ERROR” and carriage return plus new line.

The interface to the ME can be implemented using IPICOM.dll. This supports sending of AT commands and collecting responses terminated by “\nOK\r” or “\nERROR\r” or timeout (specified in ms).

4.2 Selecting channel numbers for the PCS1900 band

The 3GPP absolute radio frequency channel numbers ARFCN for DCS1800 and PCS1900 overlap. DCS1800 contain ARFCN numbers 512 to 885 in the 1800 MHz frequency range, and PCS1900 contain ARFCNs 512 to 810 in the 1900 MHz frequency range. To allow unambiguous channel numbering the XMM6180 platform functions requires that PCS1900 channel numbers are offset by 0x8000 (hexadecimal) or 32768 (normal decimal notation).

E.g. PCS1900 ARFCN 610 must be indicated as channel number 610+32768 = 33378.

4.3 Band indexing of calibration parameters

When accessing calibration data using AT commands, it is necessary to know, which bands the ME is capable. The typical built SW supporting all the normal 4 GSM bands will enumerate GSM bands in ascending frequency order: GSM850, EGSM900, DCS1800, and PCS1900. Band enumeration is configured in NV-RAM [2].


Confidential

6 / 6 Revision 0.9, 20/09/2010

5 RF Adjustment

5.1 Initialize the ME to RF Adjust

Before calibrating any ME, the ME must be flashed and booted with a suitable target SW. After test-PC connection is established to the ME. The ME has to be set into non signaling mode.

5.1.1 Preconditions

During adjustments the ME must be supplied with the product prescribed nominal battery voltage (V_bat) directly on the battery terminals with a stable power supply capable of delivering the necessary current. Sense cable is recommended to ensure that the cable loss is compensated. Adding a large capacitor close to the terminals can improve the dynamic performance of the power supply.

After applying power it is necessary to wait for the ME to boot and initialize. This takes in the order of a few seconds, before the connection to the ME can be established.

5.1.2 Test Sequence

1. Open the COM port and set the serial speed to 115.2 kBaud and stop protocol stack activity. int32 handle = 0; //port number IPICOM_ComportClose() //Close the com port, if already open IPICOM_ComportSetup(port ) //Set the com port, where port , is the port number IPICOM_ComportBaudrateSetup(baud_rate ) //Set the baud rate, which in this case should be 115200 IPICOM_SetRTS(1) //Sets RTS IPICOM_SetDTR(0) //Sets DTR ATE0 //Disable echo on the at@ interface at@prodctrl:set_mode(pmode_ptest) //Sets target in ptest mode and stops protocol stack activity

2. Set the ME into GSM “Non signaling test mode” by at@gcal:set_non_sig()

5.2 VCTCXO Adjustment

The VCTCXO is controlled by the AFC-DAC line from SMARTi-UE2™. There are two values in the NV-RAM which have to be calibrated:

default_dac_value: [0 .. 4095] 12 bits (AFC value for smallest frequency error at phone start-up)

dac_step_gsm_in_hz_32: [0 .. 4095] 12 bits (frequency step in 1/32 Hz of 1 DAC step)

The slope parameter dac_step_gsm_in_hz_32 is defined as the change in RF frequency in 1/32 Hz per DAC step assuming low band. The VCTCXO is adjusted using channel 62 in the 900 MHz band. The slope parameter is hence calculated based on obtained measurements. The measured slope parameter shall be referred to 932 MHz before rounding to integer precision, as a middle value for the Rx frequency range for all bands.

The procedure described for AFC adjustment can be iterated, relying on a good initial guess of “default_dac_value”. As initial value the current value is read-out, using AT command, and used for the first iteration. Usually the first two measurements allow a good level of confidence without iteration.

The AFC adjustment is performed at moderate power, high enough to ensure good measurement accuracy and low enough to prevent self heating affecting the frequency.


Confidential

7 / 7 Revision 0.9, 20/09/2010

5.2.1 Preconditions

1. Acquire existing (default or already calibrated) default_dac_value and dac_step_gsm_in_hz_32 from the ME: at@nvm:cal_rf_ue2.afc_cal.default_dac_value? Return string example: default_dac_value=1600 Where 1600 is the default dac value. at@nvm:cal_rf_ue2.afc_cal.dac_step_gsm_in_hz_32? Return string example: dac_step_gsm_in_hz_32 = 224 Where 7 is the default dac step value (224 = 7 Hz / DAC step)

5.2.2 Test Sequence

1. Disable use of compensation parameters. Note: This also configures the transmitter to transmit open loop, using the Vrmptrg values defined for calibration and not PCLs. char errorMsg[1000] = “”; at@gcal:set_comp(7,0)

2. Turn on Tx on ARFCN 62 in 900 MHz band with one Tx slot and moderate high power Vrmptrg (e.g. index 5, i.e. the 6th highest power in the open loop calibration table). at@gcal:set_cal_tx(arfcn, Vrmptrg_index,tx_state,tsc) Where: arfcn has to be set to 62. Vrmptrg_index has to be set to 10. tx_state has to be set to 1 for on, 0 will set Tx off tsc is the training sequence, which has to be set to 0. Return string example: vdet=528 Were 528 is the measured detector voltage. The range is 0V to 2.3V in 2048 steps, which is approximately

a 1.1mV resolution. 528 equals 593 mV. 3. Setup the instrument to perform a RF burst analysis at the selected frequency and same training

sequence as the target is configured for, e.g. training sequence 0. NOTE: the ME will send GMSK bursts with training sequence. For result values of readout frequency error values, use Average values

4. Initialize AFC control value for the first iteration, XoTune1 = default_dac_value and slope = dac_step_gsm_in_hz_32 / 32, see Section 5.2.1.

5. Set AFC control value to XoTune1 at@nvm:cal_rf_ue2.afc_cal.default_dac_value=X // Where X = default_dac_value at@nvm:cal_rf_ue2.afc_cal.dac_step_gsm_in_hz_32= Y // Where Y = dac_step_gsm_in_hz_32

6. Measure corresponding frequency error FreqError1 (average over i.e. 10 bursts to get a stable result).

7. Optional: Iteration can be used for coarse tuning: If the first XoTune value gives a large frequency error, the initial guess can be replaced by an improved guess. By using Equation 2 a new value can be found, if the new guess for XoTune differs from the previous value by more than e.g. 200 XoTune steps, this new XoTune value has to replace the first XoTune1 guess so the measurement can be repeated. If such iterations are done, the estimate for AFC slope can be improved using Equation 1. if(abs(FreqError1 / slope) > 200) { XoTune2 = XoTune1 – FreqError1 / slope; at@gcal:set_afc(XOTune2 ,0) FreqError2 = MeasureFrequencyError(); If(FreqError2 != FreqError1) { Slope = (FreqError1 - FreqError2) / (XoTune1 – XoTune2); } FreqError1 = FreqError2; XoTune1 = XoTune2; }


Confidential

8 / 8 Revision 0.9, 20/09/2010

8. With XoTune1and FreqError1 defined, select XoTune2 to allow accurate slope measurement. The distance between XoTune1 and XoTune2 must be at least 100 for accurate slope measurement, and the distance is selected at 50 larger than the nominal value defined by Equation 2: if(FreqEror1 > 0) { XoTune2 = XoTune1 – ((FreqError1 / slope > 50) ? (FreqError1 / slope + 50) : 100); } else { XoTune2 = XoTune1 – ((FreqError1 / slope < -50) ? (FreqError1 / slope - 50) : -100); } at@gcal:set_afc(XOTune2 ,0) FreqError2 = MeasureFrequencyError(); if(FreqError2 != FreqError1) { Slope = (FreqError1 - FreqError2) / (XoTune1 – XoTune2); }

9. Optional: If the two measured frequency errors have the same sign, an iteration can be done by replacing XoTune1 and FreqError1 with XoTune2 and FreqError2 and repeating step 8

10. Assume a linear relationship between frequency and XoTune and calculate a ‘new’ nominal XoTune value XoTune = XoTune2 – FreqError2 / Slope, see Equation 2.

11. Set XoTune to the newly calculated value and optionally measure frequency error again to verify that it is possible to achieve low frequency error (within e.g. +/- 50 Hz). If the frequency error is found to be too high, it is possible to go back to step 7 to perform a new iteration.

12. The transmission must be switched OFF after AFC calibration is finished. at@gcal:set_cal_tx(arfcn,Vrmptrg_index,tx_state ,tsc) where: tx_state has to be set to 0 for off, 1 will set Tx on

5.2.3 Calculation formulas and tables

As the AFC calibration method contains iterative elements, the calculations are described inline in the sequence above. The slope calculation is:

21

21

XoTuneXoTune

FreqErrorFreqErrorSlope

−−=

Equation 1: Slope calculation

The algorithm for predicting an XoTune from a previous pair of XoTune, FreqError values is:

Slope

FreqErrorXoTuneXoTune n

nn −=+1

Equation 2: Updating XoTune

This final value of XoTune giving low frequency error is stored as new default_dac_value in NV-RAM, whereas the dac_step_gsm_in_hz_32 is found by scaling the found slope by the ratio between actual RF frequency and the Rx centre frequency 932 MHz:

)932

32(32_____TXARFCNyRFfrequenc

MHzSloperoundhzingsmstepdac ⋅⋅=

Equation 3: Scaling slope to representation in NV-RAM

Where the RF frequency for Tx ARFCN 62 is 902.4 MHz, and Slope is defined by Equation 1.


Confidential

9 / 9 Revision 0.9, 20/09/2010

In summary to calibrate the slope and XoTune, two measurements are needed plus one measurement for verification. In addition an extra measurement is needed for coarse tuning, if the defaults are not suitable.

Validating the result of calibration requires that a verification measurement is obtained showing low frequency error, below e.g. +/- 50 Hz. But if this verification is not performed quickly after the two measurements used for deriving the calibration value a temperature change can cause a few hundred Hz of drift. The AFC Slope value must be small enough to allow considerable margin compared to the +/- 0.1 ppm frequency stability requirement (i.e. significantly less than 90 Hz per step), and the value for default DAC must be centered enough in the 12 bit resolution range to allow aging plus normal regulation range, taking the slope into consideration. This can be quantified from the VCTCXO specification into some limits in Table 3, and if these limits are not met the ME is defect and must be repaired.

Unit Minimum Typical Maximum

dac_step_gsm_in_hz_32 1/32 Hz/Step 64 208 2880

default_dac_value dac 500 1500 3596

Verifcation (optional) Hz -100 0 100

Table 3: AFC calibration limits for MS with VCTCXO

5.2.4 Storage of Adjusted Parameters

Calculated XoTune and slope must be stored in the NV-RAM with AT commands [6].

1. Store the values for nominal XoTune value and calculated Slope in NV-RAM at@nvm:rf_ue2.calib.afc_cal_ue2_ue2.default_dac_value=X // Where X = XoTune at@nvm:rf_ue2.calib.afc_cal_ue2_ue2.dac_step_gsm_in_hz_32=X // Where X = slope in 1/32 Hz

2. Move the calibrated values from NVM mirror to NVM at@nvm:store_nvm(cal_rf_ue2)

5.3 Rx Adjustment

Receiver adjustment is here described for both main receiver (Rx) only and combined calibration with the diversity receiver (Rd), as the XMM6260 platform supports diversity (Rd). If only Rx or Rd is calibrated, everything regarding the other receiver path can be omitted.

Rx gain compensation in the XMM6260 platform is implemented as frequency dependent gain offset compensation for LNA in high gain mode (sr_rc_gain_corr_a) and a frequency dependent offset between LNA high gain and LNA low gain mode (sr_rc_gain_corr_b). Both gain compensation factors are stored in 1/8 dB resolution. There are 8 channel compensation values for each supported band. The channel numbers are stored in NV-RAM, and have to be read out to determine which frequencies calibration has to be performed at.

Calibration is performed by imposing a CW at the ARFCN frequency plus 67 kHz at -60 dBm (67 kHz CW has to be used, as the calibration command is also used to calibrate the corner frequency of the base band channel selection filter). When the CW is enabled at the antenna input, the rx_cal_setup command shall be given to the ME and the SMARTi-UE2™ will calibrate itself and return the correction parameters when done.


Confidential

10 / 10 Revision 0.9, 20/09/2010

5.3.1 Preconditions

1. Read the frequency list for each band. Note: See section 4.3 for description of band enumerations at@nvm:cal_rf_ue2.rx_cal.sr_rc_gain_corr_freq[X] // Where X = band Return string example: {8692,8726,8760,8794,8828,8862,8896,8938} Has to be read as [in frequency]: {869.2 MVH, 872.6 MHz, 876.0 MHz, 879.4 MHz, 882.8 MHz, 886.2 MHz, 889.6 MHz, 893.8 MHz} Which is [in channel numbers]: {128, 145, 162, 179, 196, 213, 230, 251}

2. Read the band mapping for storage of compensation parameters in NV-RAM. at@nvm:fix_rf_ue2.rx_fix.sr_rx2g_gct_mapping[0,3]? Return string example: {10, 11, 12, 13} Has to be read as: 850 (Rx) has index 10, 900 (Rx) has index 11, 1800 (Rx) has index 12 and 1900 (Rx) has index 13. at@nvm:fix_rf_ue2.rx_fix.sr_rd2g_gct_mapping[0,3]? Return string example: {14, 15, 255, 17} Has to be read as: 850 (Rd) has index 14, 900 (Rd) has index 15, 1800 (Rd) is not supported and 1900 (Rd) has index 17.

5.3.2 Test Sequence

The following description is given per band, and must be repeated for all supported bands:

1. Set the RF generator to -60 dBm CW at 67 kHz plus the downlink frequency of the first ARFCN in the channel list, and wait for the RF generator to settle

2. Send the rx_cal_setup command, to enable the SMARTi-UE2™ self calibration [2]. at@gcal:gcal_rx_cal_setup(1,ARFCN,div_mode,epected_rxlev,n_avg,mc_idx,temp_meas,meas_only,last_idx,

corr_min, corr_max) Where: ARFCN is the channel number div_mode defines which Rx 2G signal path shall be calibrated, 0 = Rx (main receive path), 1 = Rd (diversity

receive path) and 2 = RxRd (both receive paths) expected_rxlev = expected Rx level at the antenna input, i.e. rxlev 50 for a generator level of –60 dBm (110 -

60 = 50) n_avg = 2 // Always use an average of 2 measurements mc_idx is the frequency index, where the first channel in a band is 0, and on until the 8th channel which is 7. temp_meas is the temperature measurement request. If set to 1 a temperature measurement is triggered. Meas_only defines if the calibrated values should be stored in Standby-RAM tables or not. 0 stores the values,

1 does not. last_idx defines if the calibrated values should be stored in Standby-RAM tables or not. 0 stores the values, 1

does not. Corr_min is the minimum Valid Gain Correction Value in dB. Corr_max is the maximum Valid Gain Correction Value in dB. Return string example: rx2gcal=0 0 370 9252 0 192 192 252 252 1st number, 0 in this case, is the Rx error code: 0: no errors, 1: RF level to low, 2: No center frequency found, 4:

Gain state A out of range, 8: Gain state B out of range. 2nd number, 0 in this case, is the Rd error code: 0: no errors, 1: RF level to low, 2: No center frequency found, 4:

Gain state A out of range, 8: Gain state B out of range. 3rd number, 370 in this case, is the MC_TEMP_DATA (Temperature measurement), scale from -30˚C in steps of

5/32˚C (i.e 370 = 57.8 – 30 = 27.8˚C ) 4th number, 9252 in this case is the MC_GAIN_CORR_FREQ, which is given in 100 kHz i.e. 9252 is 925.2 MHz. 5th number, 0 in this case, is the MC_LNA_FCENTER which is the frequency adjustment of the band selection

filters.


Confidential

11 / 11 Revision 0.9, 20/09/2010

6th number, 192 in this case, is the MC_RX_GAIN_CORR_A is the gain correction of the Rx LNA in high gain mode in dB/16.

7th number, 192 in this case, is the MC_RD_GAIN_CORR_A is the gain correction of the Rd LNA in high gain mode in dB/16.

8th number, 252 in this case, is the MC_RX_GAIN_CORR_B is the gain correction of the Rx LNA in gain step from high to low gain in dB/16.

9th number, 252 in this case, is the MC_RD_GAIN_CORR_B is the gain correction of the Rx LNA in gain step from high to low gain in dB/16.

3. For the whole channel list, set generator for the next channel (-60 dBm CW at 67 kHz plus the downlink frequency of the ARFCN), wait for it to settle, repeat configuration and measurement in step 2.

4. After the last channel in the channel list for each band, the calibration should be stopped, using the this command

at@gcal:gcal_rx_cal_setup(0,ARFCN,div_mode,epected_rxlev,n_avg,mc_idx,temp_meas,meas_only ,last_idx,corr_min, corr_max)

Where: ARFCN is the last channel number used for calibration Meas_only has to be set to 1 to stop calibration. div_mode, expected_rxlev, n_avg, mc_idx, last_idx, temp_meas, Corr_min and Corr_max are don’t care Return string example: rx2gcal=0 0 0 0 0 0 0 0 0

5. Read I/Q imbalance for the calibrated band. at@ucal:ucal_rd_cal_tab_per_band(RxBand ,RdBand ) Where: RxBand is the Rx band mapping RdBand is the Rd band mapping Return string example: Calibration result={0,0,0,0,1,1,0,0 9252,0,211,0,0,0,0,0 9300,0,216,254,0,0,0,0 9348,0,216,255,0,0,0,0 9396,0,216,254,0,0,0,0 9444,0,217,255,0,0,0,0 9492,0,213,255,0,0,0,0 9540,0,213,255,0,0,0,0 9598,0,207,255,0,0,0,0} OK Where: The first 4 integers should be ignored, as they are only used for 3G. 5th integer , which in this case is 1 is the I imbalance parameter for the selected RxBand. 6th integer , which in this case is 1 is the Q imbalance parameter for the selected RxBand. 7th integer , which in this case is 0 is the I imbalance parameter for the selected RdBand. 8th integer , which in this case is 0 is the Q imbalance parameter for the selected RdBand. The rest of the return string could be ignored, as this information is already collected in step 2.

6. Continue with next band, starting from 1 or stop calibration if all bands have been calibrated:


Returned correction parameters, have to be stored in the NV-RAM [6].

1. Store MC_RX_GAIN_CORR_A and MC_RD_GAIN_CORR_A for all the calibrated channels

at@nvm:cal_rf_ue2.rx_cal.sr_rc_gain_corr_a[Band_index ][0,(X-1)]={Corr_a1 ,Corr_a2 ,……..Corr_aX } Where: Band_index is the band index found in Section 5.3.1 point 2 X is the number adjusted channels Corr_a(1��X) is the returned MC_RX_GAIN_CORR_A value for each adjusted channel

2. Store MC_RX_GAIN_CORR_B and MC_RD_GAIN_CORR_A for all the calibrated channels

at@nvm:cal_rf_ue2.rx_cal.sr_rc_gain_corr_b[Band_index ][0,(X-1)]={Corr_b1 ,Corr_b2 ,……..Corr_bX } Where: Band_index is the band index found in Section 5.3.1 point 2 X is the number adjusted channels


Confidential

12 / 12 Revision 0.9, 20/09/2010

Corr_b(1 ��X) is the returned MC_RX_GAIN_CORR_B value for each adjusted channel

3. Store MC_LNA_FCENTER for all the calibrated channels

at@nvm:cal_rf_ue2.rx_cal.sr_rc_lna_fcenter[Band_index ][0,(X-1)]={LNA_Fcenter1 ,LNA_Fcenter2 ,……..LNA_FcenterX }

Where: Band_index is the band index found in Section 5.3.1 point 2 (lna_fcenter must always be stored as an Rx

parameter). X is the number adjusted channels LNA_FCENTER(1��X) is the returned MC_LNA_FCENTER value for each adjusted channel

4. Store I/Q imbalance for the calibrated band. at@nvm:cal_rf_ue2.rx_cal.sr_rc_imb_w[Band_index ][IQ_index ]=IQ_data Where: Band_index is the band index found in Section 5.3.1 point 2 IQ_index is 0 in case of I data and 1 in case of Q data IQ_data is the IQ data to be stored

5. 1 to 4 has to be performed for all adjusted bands. 6. Store the calibration temperature

at@nvm: cal_rf_ue2.rx_cal.sr_rc_temp_ref=RxTemperature Where: RxTemperature , which must be integer, is the last measured TEMP_DATA in Deg C

7. Store the saved parameters from the NVM mirror to the NVM RAM

at@nvm:store_nvm(cal_rf_ue2)

5.4 Tx Adjustment

XMM6260 uses a power detector with an automatic power control loop. But for calibration the ME will be switched to operate in open loop mode. This gives the possibility to obtain additional performance information of the forward characteristic of the transmitter.

For normal operation, the SMARTi-UE2™ uses a calibration table for power vs. detector characteristics and a frequency dependent power correction table. These two tables shall be adjusted.

The protocol stack requests a PCL which is mapped to a requested power (Section 5.4.1 point 5). This table is not changed by calibration (but it can be read for verification, see 5.4.1 point 5).

In addition to these tables which together define the power in the useful part of the burst, for some PA solutions a calibration of PA pedestal is needed. Pedestal calibration should only be performed on platforms where it is needed.

The SMARTi-UE2™ internal registers controlling the radio are defined as two super bands high and low, where low band covers GSM850 and EGSM900, and high band covers DCS1800 and PCS1900. This implies that only one power vs. detector characteristic is needed per super band, one for low band with index 0, and one for high band with index 1.

The open loop calibration procedure of SMARTi-UE2™ is to program the Vrmptrg voltage of SMARTi-UE2™ with different values (via the RAMP-DAC), and measure the resulting output powers and additionally read out the corresponding power-detector ADC-values. This implies that reading of power vs. reading of detector is used for calibrating the power levels, whereas the reading of power vs. applied RAMP-DAC control values are used for calibrating the PA pedestal levels.

In open loop calibration mode RAMP-DAC is controlled by a separate table mapping Vrmptrg indexes to Vrmptrg values, where Vrmptrg indexes are defined from 0 for highest power down to 15. This is used for reading back the detector offset.


Confidential

13 / 13 Revision 0.9, 20/09/2010

The recommended procedure for Tx adjustment is based on a non-iterative approach where the individual Pout versus Vrmptrg characteristic for each phone (with default DAC values) are determined by output power measurements on a number of selected channels and Vrmptrg levels.

5.4.1 Preconditions

1. Read the channel list for each band. These Tx channel numbers have special representation, so translation to ARFCN numbers is needed. Band enumeration according to section 4.3

at@nvm:cal_rf_ue2.tx_cal.sr_tp_tx2g_fecorr_table[0][Band ].sr_tp_gp_arfcn [0,4]? Where: Band is the band. Return string example: {128, 158, 189, 220, 251}

2. Transform the read Tx channel numbers to ARFCN numbers: For GSM850 it is ARFCN numbers, for EGSM, the lowest frequency ARFCN (ARFCN 975) is channel number 0, and for high bands DCS1800 + PCS1900, the lowest frequency (ARFCN 512) is channel number 1.

Uint16 txch2arfcnOffset = 0; if (band == gsm_900) txch2arfcnOffset = 975; else if ((band == gsm_1800) || (band == gsm_1900)) txch2arfcnOffset = 511; uint16 arfcnList[5]; for (int i = 0; i < 5; i++) arfcnList[i] = (tx_channels[i] + tx2arfcnOffset) & 1023;

3. Disable Tx compensation. This also selects open loop mode using Vrmptrg values for calibration at@gcal:set_comp(7,0)

5.4.1.1 Preconditions for calculations

The following parameters are needed for the calculation, but not for defining the measurement sequence

1. For the power level calibration: Read the dBm targets (in 1 dBm resolution) for each of the 16 points in the power calibration table

at@nvm:cal_rf_ue2.tx_cal.sr_tp_tx2g_calibtable_cal[X].sr_tp_gp_calpout [0,15]? // X: 0 for low band, 1 for high Return string example: {34, 33, 31, 29, 27, 25, 23, 21, 19, 17, 15, 13, 11, 9, 7, 5}

2. For the PA pedestal calibration: Read the PA vendor information to detect if PA pedestal calibration is needed. Currently vendor ID 1 (RFMD) does not require PA pedestal:

at@ nvm:fix_rf_ue2.tx_fix.sr_pa_vendor? 3. For PA pedestal values calculation: Read the Vrmptrg values used in open loop calibration mode

at@nvm:cal_rf_ue2.tx_cal.sr_tp_tx2g_calibtable_cal[X]. sr_tp_p_vdettrg[0,15]? // X: 0 for low band, 1 for high Return string example: {1600, 1480, 1412, 1187, 993, 839, 727, 635, 553, 481, 401, 372, 333, 280, 240, 200}

4. For PA pedestal values calculation: Read the target power for PA pedestal. at@nvm:fix_rf_ue2.tx_fix.target_pa_pedestal_power[0,7]? Return string example: {-10, -10, -10, -10, -10, -10, -10, -10. -10, -10, -10, -10, -10, -10, -10, -10} Where: 1st digit is the target for first PCL range in the 850 band, 2nd digit for the second range in the 850 band and so on

until the 5th digit which is for the first range in the 900 band and the 9th digit which is for the first range in the 1800 band and the 13th digit which is for the first range in the 1900 band and so on.

5. For validation of detector calibration and for verification measurements: Read the target power in dBm from measurement equipment for all PCLs (in 1/16 dBm resolution).

at@nvm:fix_rf_ue2.tx_fix.fixed.target_gmsk_output_power[Band ][0,19]? // Band is the band index, see Section 4.3


Confidential

14 / 14 Revision 0.9, 20/09/2010

Return string example: {520, 520, 520, 520, 520, 520, 496, 464, 432, 400, 368, 336, 304, 272, 240, 208, 176, 144, 112, 80} Which translated to dBm’s is: {32,5, 32,5, 32,5, 32,5, 32,5, 32,5, 31, 29, 27, 25, 23, 21, 19, 17, 15, 13, 11, 9, 7, 5} dBm For PCL {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19}

5.4.2 Test Sequence

5.4.2.1 Test Sequence open loop calibration at cent re frequency

Calibration of power and detector response (Vdet) is performed on ‘centre frequency’ for both low band and high band. The ‘center frequency’ of low bands is defined as EGSM 975 for low bands and DCS1800 ARFCN 885 for high band.

The measurements can be done in any order, but in order to prevent influencing the low power measurements, due to self-heating, it is recommended to do the open loop measurements at centre frequency before the closed loop power measurement vs. frequency.

The ‘centre frequency’ of low bands is defined as EGSM900 ARFCN 975 for low band and DCS1800 ARFCN 885 for high band.

15 measurements are performed for low bands and for high bands, looping from Vrmptrg index 1 down to Vrmptrg index 15.

Note: It might be possible to reduce the calibration effort for deriving the power vs. Vdet. The number of measured points might be reduced and more sophisticated interpolation used.

1. Start transmit on the low band centre ARFCN, using first Vrmptrg index value 1, Tx enabled for one slot, and training sequence matching instrument (e.g. 0)

at@gcal:set_cal_tx(ARFCN,Vrmptrg_index,tx_state,tsc) Where: ARFCN is the channel number Vrmptrg_index is the Vrmptrg index tx_state has to be set to 1 for on, 0 will set Tx off tsc is the training sequence, which should be set to 0. Return string example: vdet=4528 Were 4582 (4 * the actual Vdet) is the measured detector voltage. 4582 / 4 = 1132. The range is 0V to 2.3V

in 2048 steps, which is approximately a 1.1mV resolution. 1132 equals 1245 mV. 2. Record the Vdet[i] value. The raw read back value is the sum of 4 measurements during the burst,

so a floating point representation is assumed as a quarter of the read back value: vdet[i] = 0.25 * vdet_readback.

3. Measure the power with the instrument, in calculation section referred to as dBm[i] 4. Repeat 1) to 3) for all the required Vrmptrg from 1 down to 15, and repeat for high band 5. Stop transmit

at@gcal:set_cal_tx(ARFCN,Vrmptrg_index,tx_state ,tsc) Where: tx_state has to be set to 0 for off ARFCN, Vrmptrg_index and tsc are not used by the ME, when tx_state is set to 0.

Note: This leaves the 2G Tx in open loop calibration mode. To switch to normal mode, after calibration is completed, using closed loop and compensation values, use at@gcal:set_comp(7,1) or do a power cycle.


Confidential

15 / 15 Revision 0.9, 20/09/2010

This is usually done after calibration values have been calculated and stored, so the proper compensation values take effect.

5.4.2.2 Test Sequence for power vs. frequency

Calibration of power vs. frequency is done on 5 frequencies on each of the 4 GSM bands. This is done using Vrmptrg index 0 of the calibration mode Vrmptrg tables, but operated in closed loop. Default parameter for index 0 is set to ensure not to drive the PA into saturation, which will result in bad frequency compensation. So in addition to the at@gcal:set_comp(7,0) executed as part of the preconditions, this requires that at@gcal:set_comp(10,1) is called before these measurements [2], and is disabled with at@gcal:set_comp(10,0) after the measurements are completed.

1. Change from open loop calibration mode to closed loop calibration mode at@gcal:set_comp(10,1)

2. Initialize instrument for power measurement 3. Start transmit on the first ARFCN (Section 5.4.1 point 1), using closed loop Vrmptrg index 0, Tx

enabled for one slot, and training sequence matching instrument (e.g. 0) at@gcal:set_cal_tx(ARFCN,Vrmptrg_index,tx_state,tsc) where: ARFCN is the channel number, see Section 4.2 for details. Vrmptrg_index should be set to 0. tx_state has to be set to 1 for on, 0 will set Tx off tsc is the training sequence, which should be set to 0. Return string example: vdet=4528 Were 4582 is (4 * the actual Vdet) is the measured detector voltage. 4582 / 4 = 1132. The range is 0V to

2.3V in 2048 steps, which is approximately a 1.1mV resolution. 1132 equals 1245 mV. 4. Measure the power with the instrument, in calculation section referred to as dBmAtFrequency[i] 5. Repeat 3) and 4) for all frequencies on all bands 6. Change from closed loop calibration mode to open loop calibration mode, as this is the default for

calibration mode: at@gcal:set_comp(10,0)

5.4.3 Calculation formulas and tables

5.4.3.1 Power vs. frequency

The frequency compensation parameters must be positive, to insure positive power in dBm after frequency correction for target power of 0dBm (PCL15) in high band. This means that the power vs. frequency compensation must be relative to the highest power measured over frequency for both low bands and to the highest power measured over frequency for both high bands. The arfcn_comp_parms value is in 1/16 dB resolution, so it is 16 times the difference between the maximum and the individual measurement, i.e. for low bands (GSM850 and EGSM900):

[ ] ( ) [ ]( )( )iencydBmAtFrequencydBmAtFrequMAXroundi LowBands −⋅= 16_parmsarfcn_comp

Equation 4: Calculating Tx frequency compensation arfcn_comp_parms

And similar for the high bands (DCS1800 and PCS1900).

In order to validate the power vs. frequency calibration, the maximum value of arfcn_comp_parms value is compared to a maximum allowed ARFCN compensation value. This value should be found in the development phase and potentially adjusted when information from production is available. It is initially set to 3 dB.


Confidential

16 / 16 Revision 0.9, 20/09/2010

Note: It might be possible to reduce the calibration effort for deriving the power vs. frequency calibration parameters. The number of measured frequencies might be reduced, by using interpolation. This might also be combined with default values evaluated through statistical analysis over a representative amount of measurements.

Numerical example

Channel number from target

ARFCN Measured power dBm

Max power for lowHighBand

arfcn_comp_parms

5.4.1 point 1 5.4.1 point 2 5.4.2.2 point 4 MAX(5.4.2.2 point 4) Equation 4 128 GSM850 128 31.060 31.088 0 159 GSM850 159 31.078 31.088 0 189 GSM850 189 31.078 31.088 0 220 GSM850 220 31.084 31.088 0 251 GSM850 251 31.088 31.088 0 0 EGSM900 975 31.000 31.088 1 43 EGSM900 1018 31.016 31.088 1 87 EGSM900 38 31.020 31.088 1

130 EGSM900 81 31.034 31.088 1 173 EGSM900 124 31.038 31.088 1

1 DCS1800 512 27.114 28.559 23 94 DCS1800 605 27.146 28.559 23

187 DCS1800 698 27.113 28.559 23 280 DCS1800 791 27.106 28.559 23 374 DCS1800 885 27.136 28.559 23

1 PCS1900 512 27.268 28.559 21 77 PCS1900 586 27.513 28.559 17

150 PCS1900 661 27.86 28.559 11 224 PCS1900 735 28.223 28.559 5 299 PCS1900 810 28.559 28.559 0

Table 4: Numerical example for arfcn_comp_parms calculation

5.4.3.2 Power at centre frequency

The calculation of power calibration values at centre frequency depends on the frequency correction factor for this frequency, arfcn_comp_parms[centre_frequency_index]. So the first step is to offset all dBm measurements by this offset (in dB, i.e. the compensation parameter divided by 16):

dBm_calculation[i] = dBm_raw[i] + arfcn_comp_params[centre_frequency_index] / 16.0

Equation 5: Frequency compensation of raw measured dBm power

The vdet detector values read back during calibration measurements are the sum of 4 ADC readings across the burst, so for high gain the vdet readback divided by 4 is equivalent to the closed loop Vdet.

The power detector is based on a detector diode. This implies that in the linear region the output voltage is proportional to the voltage of the RF signal. So to perform the interpolation, both measurements and target values are transformed from the logarithmic dBm domain to voltage domain by raising 10 to the power of a twentieth of the measured dBm (the multiplier square root of 0.05 for 50 ohms load an 1 mW reference is not


Confidential

17 / 17 Revision 0.9, 20/09/2010

necessarily included as we only need relative values for the interpolation, the same factor applies to both measurements and targets):

( )voltofunitsinVoltagevaluedBm

05.010 20

_

=

Equation 6: Transforming dBm power to voltage domain (units of √0.05 volt)

This equation is used for both the measured dBm values corrected for frequency and for the dBm target values for the interpolation points to store.

The linear proportionality between increase in RF voltage and output voltage is a good approximation in the linear range of the detector. At very high power some compression occurs (the slope of change in detector vs. change in RF voltage is decreasing), and at very low power the slope is also decreasing because below a ‘knee voltage’ the output voltage becomes proportional to the square of the RF voltage.

The compression at highest power is dealt with by adding additional measurement points in this region.

The change in diode characteristic at low power is dealt with by raising the target voltages to an exponent of 1.5 at targets in the 0 to 10 dBm range. This range is somewhat half way between the linear region and the quadratic region at very low power.

Before doing the interpolations, the measurements are validated: All measurements with Vdet read back value exceeding 4 * 2000 are removed, as ADC can be saturated.

Interpolation is performed for each power target by selecting the two closest measured points (the first above and the first below if both exist – otherwise using extrapolation from the two closest values, and performing linear interpolation, i.e. finding slope and offset on the measurements and using these to find the closed loop Vdet corresponding to the power target in the voltage domain.

[ ] ( ) ))det()()1(

)det()1det()(arg5.0(int)(det xV

xVmeasxVmeas

xVxVxVmeasetVtjV +

−+−+⋅−+=

Equation 7: Equation to be used for Target [dBm] at 10 dBm and above for interpolating Vdet.

[ ] ( ) ))det()()1(

)det()1det()(arg5.0(int)(det

5.15.15.15.1 xV

xVmeasxVmeas

xVxVxVmeasetVtjV +

−+−+⋅−+=

Equation 8: Equation to be used for Target [dBm] less than 10 dBm for interpolating Vdet.

Where: 0.5 is added to ensure the correct rounding, as everything on the right side of the decimal is lost when converting to integer. Vtarget is the target power in voltage domain and Vmeas is the measured power in voltage domain.

If the interpolated Vdet is higher then the max value of 2047 then the calibration should be considered as failed. In addition the calibration should also be considered as failed if Vdet for max target power plus max channel offset is bigger then 2000 because the ADC or detector can be saturated.


Confidential

18 / 18 Revision 0.9, 20/09/2010

Numerical example for low bands:

Vrmptrg index

Open loop Vrmptrg

Raw vdet_readback

Vdet Raw

measurement dBm

dBm corrected for

frequency

Power in voltage domain

5.4.1 point 2 5.4.2.1 point 0 5.4.2.1 point 0 5.4.2.1 point 3 Equation 5 Equation 6 0 1584 5176 1294 33.377 33.439 46.98 1 1579 5154 1288.5 33.206 33.268 46.07 2 1412 4786 1196.5 31.386 31.448 37.36 3 1187 4340 1085 28.169 28.231 25.8 4 993 3925 981.25 26.885 26.948 22.25 5 839 3538 884.5 25.455 25.518 18.88 6 727 3240 810 23.546 23.609 15.15 7 635 2997 749.25 21.96 21.022 11.25 8 553 2734 683.5 19.172 19.234 9.156 9 481 2488 622 17.059 17.121 7.179

10 401 2213 553.25 15.95 16.012 6.318 11 372 2120 530 13.256 13.318 4.633 12 333 1945 486.25 11.276 11.338 3.689 13 285 1707 426.75 9.234 9.296 2.916 14 267 1495 373.75 6.785 6.847 2.2 15 210 1195 298.75 4.458 4.52 1.683

Table 5: Measurement points for low bands

dBm target Target in voltage

domain Interpolate using

indexes Interpolated Vdet

5.4.1 point 1 Equation 6 Table 5 Equation 7 / Equation 8 34 50,12 0, 1 1313 33 44,67 1, 2 1274 31 35.48 2, 3 1178 29 28.18 2, 3 1108 27 22.39 3, 4 985 25 17.78 5, 6 863 … … … … 9 2,82 13, 14 419 7 2,24 13, 14 377 5 1,78 14, 15 312

Table 6: Linear interpolation in Voltage domain

5.4.3.3 Detector offset (Vdet_idle)

If the power detector in the used PA requires temperature compensation, the detector reading for low Vrmptrg must be stored, that would be the lowest vdet value returned. But currently Detector offset is not used, and no current plans to use it exist.


Confidential

19 / 19 Revision 0.9, 20/09/2010

5.4.3.4 PA pedestal calculation

If the PA vendor ID is 1 (see Section 5.4.1.1 point 2), PA pedestal calibration calculation is skipped. For other PA vendor ID’s it is needed.

The purpose of the calculations is to find the PA pedestal values yielding the 4 power levels per band specified as PA pedestal targets in Section 5.4.1.1 point 4. The open loop measurements from Section 5.4.2.1 vs. the ramp scale values from Section 5.4.1.1 point 3 are used for the interpolation.

Calculation of PA pedestals is performed as linear interpolation in the dB domain. The rampscale values used in the open loop calibration mode and the associated measured dBm value are the measurement points, from which the PA pedestal targets in dBm are used to interpolate the open loop rampscale values at normal temperature.

The representation of PA pedestal is in units of 2.2 mV (nominally), where the ramp scale representation is in units of 1.1 mV, so a multiplier of 0.5 is used.

[ ][ ][ ][ ] 5.0*))rdestalPowetargetPaPe((

armspedestal_p

665

656 rampscale

dBmdBm

rampscalerampscaledBmpclRangedhighLowBan

pclRangedhighLowBan

+−−

⋅−

=

Equation 9: Interpolating PA pedestal (normal temperature).


Calculated high gain and gain select calibration factors must be stored in the NV-RAM.

1. Store the power vs. ARFCN compensation parameters in NV-RAM for all 4 bands at@nvm:cal_rf_ue2.tx_cal.sr_tp_tx2g_fecorr_table[0][Band ].sr_tp_gp_offset[0,4]={Z0, Z1, Z2, Z3, Z4} Where: Band is the band index, see Section 4.3 Z0 – Z4: ARFCN compensation parameters to be stored

2. Store the power vs. detector target calibration points in NV-RAM for low bands and for high bands at@nvm:cal_rf_ue2.tx_cal.sr_tp_tx2g_calibtable_cal[Band ].sr_tp_p_vdettrg[0,15]={ Z0, Z1, ,,, Z14, Z15} Where: Band is the band index, see Section 4.3 Z0 – Z15: Vdet to be stored

3. If detector offset (Vdet_idle) calibration is used, store it in NV-RAM for low bands and for high bands. Currently not used.

at@nvm:cal_rf_ue2.tx_cal.sr_tp_tx2g_vdetidle_reg.sr_tp_gpl_cal_vdetidle=Z0 at@nvm:cal_rf_ue2.tx_cal.sr_tp_tx2g_vdetidle_reg.sr_tp_gpm_cal_vdetidle=Z1 Where: Z0 is vdet_idle for low bands and Z1 is vdet_idle for high bands

4. Store the PA pedestal calibration tables in NV-RAM for low bands and for high bands at@nvm:cal_rf_ue2.tx_cal.sr_tp_g_ped[Band ][0,3]={ Z0, Z1, Z2, Z3, Z4} Where: Band is the band index, see Section 4.3 Z0 – Z4: Pedestal compensation parameters to be stored

5. Store the saved parameters in the NVM mirror in NV-RAM at@nvm:store_nvm(nvm_cal_rf_ue2)

6. Enable the stored parameters by copying them to the SMARTi-UE2™ chip at@gcal:set_comp(7,1)


Confidential

20 / 20 Revision 0.9, 20/09/2010

Test References

No/Name Title Revision

1 ITA_UMTS_RF_adjust_XMM6260.pdf

2 ISpec_Drv-GCAL.doc

3 UCAL_interface_specification.doc

4 ITA_FastCalibration_XMM6260

5 SMARTiUE2_Engine_Calibration.pdf 0V2

6 XMM6260_RF_parametrical_structure.doc


Confidential

21 / 21 Revision 0.9, 20/09/2010

Abbreviations / Terminology

[ ] Reference item

ARFCN Absolute Radio Frequency Channel Number

CW Continuous Wave (sine wave)

dBm dB relative to 1 mW

GS Gain Select

HG High Gain

LG Low Gain

ME Mobile equipment

MMI Man Machine Interface

NV-RAM Non Volatile Memory

PCL Power Control Level

RF Radio Frequency

RSSI Receiver Signal Strength Indicator

SW Software

0508 ita gsm rf adjust xmm6260

Documents

conventional

infineon technologies

coaxial test

outlined sequence

ita rf adjustment

interpolating

pa pedestal

pa pedestal