CCS Technical Documentation RH-48 Series Transceivers Troubleshooting — BB Issue 1 11/2003 Confidential © 2003 Nokia Corporation
RH-48 Troubleshooting — BB CCS Technical Documentation Contents Page No Baseband Troubleshooting............................................................................................. 3 RH-48 Baseband Module Overview ............................................................................3 Baseband and RF Architecture ....................................................................................4 Power Up and Reset ...........................................................................
RH-48 Troubleshooting — BB CCS Technical Documentation Baseband Troubleshooting RH-48 Baseband Module Overview The Baseband module of the RH-48 transceiver is a CDMA single-band engine. The baseband architecture is based on the DCT4 Apollo engine. RH-48 cellular baseband consists of three ASICs: Universal Energy Management (UEM), Universal Phone Processor (UPP), and a 128/8 megabit combo FLASH. The baseband architecture supports a power-saving function called sleep mode.
RH-48 Troubleshooting — BB CCS Technical Documentation Baseband and RF Architecture VBatt Figure 1 CMAX Power Distribution PRODTP VPP Battery Audio Flash JTAG DC/DC GenIO Control Charger Bottom Conn. MBus UPP VIO UEM ExtBusC SIM Reader VANA FBusRx FBusTx VR1A V SIM VR1B Vflash1 VR2 Vflash2 VR3 Core DBus MBus VR4 Sleep Clk 32 KHz CBus FBus VR5 VR6 VR7 V Bat VCTCXO 19.
RH-48 Troubleshooting — BB CCS Technical Documentation • By the RTC Alarm, when the RTC logic has been programmed to give an alarm. After receiving one of the above signals, the UEM counts a 20ms delay and then enters its reset mode. The watchdog starts up, and if the battery voltage is greater than Vcoff+, a 200ms delay is started to allow references, etc. to settle. After this delay elapses, the VFLASH1 regulator is enabled. Then, 500us later VR3, VANA, VIO, and VCORE are enabled.
RH-48 Troubleshooting — BB CCS Technical Documentation Reference signal PwrOnX Charger Detection RTC UEMRSTX VFlash1 VIO VCORE VANA VR3 19.
RH-48 Troubleshooting — BB CCS Technical Documentation Figure 3: Measured power on sequence and timing Power up with PWR key When the Power on key is pressed, the UEM enters the power-up sequence. Pressing the power key causes the PWRONX pin on the UEM to be grounded. The UEM PWRONX signal is not part of the keypad matrix. The power key is only connected to the UEM. This means that when pressing the power key an interrupt is generated to the UPP that starts the MCU.
RH-48 Troubleshooting — BB CCS Technical Documentation and UEM enters into reset sequence. If VBAT is detected to fall below VMSTR during start-up charging, charging is cancelled. It will restart if new rising edge on VCHAR input is detected (VCHAR rising above VCHDET+). RTC alarm power up If phone is in POWER_OFF mode when RTC alarm occurs the wake-up procedure. After baseband is powered on, an interrupt is given to MCU. When RTC alarm occurs during ACTIVE mode, the interrupt for MCU is generated.
RH-48 Troubleshooting — BB CCS Technical Documentation in the active mode depending on the phone present state of the phone such as: burst reception, burst transmission, if DSP is working, etc. In active mode SW controls the UEM RF regulators: VR1A and VR1B can be enabled or disabled. VSIM can be enabled or disabled and its output voltage can be programmed to be 1.8V or 3.3V. VR2 and VR4 -VR7 can be enabled or disabled or forced into low quiescent current mode.
RH-48 Troubleshooting — BB CCS Technical Documentation Table 1: RH-48 Baseband regulators Regulator Maximum current (mA) Vout (V) Notes VCORE 300 1.5 Output voltage selectable 1.0V/1.3V/1.5V/1.8V Power up default 1.5V VIO 150 1.8 Enabled always except during power-off mode VFLASH1 70 2.78 Enabled always except during power-off mode VFLASH2 40 2.78 Enabled only when data cable is connected VANA 80 2.
RH-48 Troubleshooting — BB CCS Technical Documentation Clock Distribution RFClk (19.2 MHz Analog) The main clock signal for the baseband is generated from the voltage and temperature controlled crystal oscillator VCTCXO (G500). This 19.2 MHz clock signal is generated at the RF and is fed to Yoda pin 18 (TCXO_IN). Yoda then converts the analog sine waveform to a digital waveform with swing voltage of 0 tot 1.8V and sends it to the UPP from pin 16 at Yoda (19.2 Out) to the UPP pin M5 (RFCLK).
RH-48 Troubleshooting — BB CCS Technical Documentation Figure 5: Waveform of 19.2MHz Clk going to the UPP for Yoda ASIC at C711 This is the RFCLK signal for the UPP.
RH-48 Troubleshooting — BB CCS Technical Documentation RFConvClk (19.2 MHz digital) The UPP distributes the 19.2MHz internal clock to the DSP and MCU, where SW multiplies this clock by seven for the DSP and by two for the MCU. (See Figure 6.
RH-48 Troubleshooting — BB CCS Technical Documentation CBUSClk Interface A 1.2 MHz clock signal is use for CBUS, which is used by the MCU to transfer data between UEM and UPP. (See the following figure for Cbus data transfer.) Figure 7: Cbus Data Transfer DBUS Clk Interface A 9.6 MHz clock signal is use for DBUS, which is used by the DSP to transfer data between UEM and UPP. (See the following figure.
RH-48 Troubleshooting — BB CCS Technical Documentation The system clock is stopped during sleep mode by disabling the VCTCXO power supply (VR3) from the UEM regulator output by turning off the controlled output signal SleepX from UPP. SleepCLK (Digital) The UEM provides a 32kHz sleep clock for internal use and to UPP, where it is used for the sleep mode timing. (Figure 9.
RH-48 Troubleshooting — BB CCS Technical Documentation SleepCLK (Analog) However, when the system enters sleep mode or power off mode, the external 32KHz crystal provides a reference to the UEM RTC circuit to turn on the phone during power off or sleep mode. (Figure 10.) Figure 10: 32kHz analog waveform at 32KHz crystal input Flash programming Connections to Baseband The Flash programming equipment is connected to the baseband using test pads for galvanic connection.
RH-48 Troubleshooting — BB CCS Technical Documentation flash-programming mode, the MCU only waits for a specified time 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 UPP on the MBUSRX signal.
RH-48 Troubleshooting — BB CCS Technical Documentation FLASH_1 CH1 = BSI CH2 = MBUS CH3 = FBUSTX CH4 = FBUSRX Measure points Production test pattern (J396) Figure 11: Flashing starts by BSI being pulled up and password being sent to UEM • This boot code asks MCU to report prommer phone’s configuration information, including flash device type. Now prommer can select and send algorithm code to MCU SRAM (and SRAM/Flash self-tests can be executed).
RH-48 Troubleshooting — BB CCS Technical Documentation FLASH_3 CH1 CH2 CH3 CH4 = = = = PURX MBUS FBUSTX FBUSRX Measure points Production test pattern (J396) Data transfer has started (Fbus_Rx) Figure 13: Flashing, continued Charging operation Battery In RH-48, a Lithium-Ion cell battery with a capacity of 850 mAh is used. Reading a resistor inside the battery pack on the BSI line indicates the battery size.
RH-48 Troubleshooting — BB CCS Technical Documentation Figure 15: Interconnection diagram inside the battery pack Charging Circuitry The UEM ASIC controls charging depending on the charger being used and the battery size. External components are needed for EMC, reverse polarity and transient protection of the input to the baseband module. The charger connection is through the system connector interface. The RH-48 baseband is designed to support DCT3 chargers from an electrical point of view.
RH-48 Troubleshooting — BB CCS Technical Documentation Charger Detection Connecting a charger creates voltage on VCHAR input of the UEM. When VCHAR input voltage level is detected to rise above 2 V (VCHdet+ threshold) by UEM charging starts. VCHARDET signal is generated to indicate the presence of the charger for the SW. The charger identification/acceptance is controlled by EM SW. The charger recognition is initiated when the EM SW receives a ”charger connected” interrupt.
RH-48 Troubleshooting — BB UEM Pins CCS Technical Documentation R200 N10 VBAT .22 Ohms C201 C202 1uF 10nF M10 Figure 18: Charging circuity at the battery Audio The audio control and processing in RH-48 is provided by UEM, which contains the audio codec, and UPP — which contains the MCU and DSP blocks, handling and processing the audio data signals. The baseband supports three microphone inputs and two earpiece outputs. The microphone inputs are MIC1, MIC2, and MIC3.
RH-48 Troubleshooting — BB CCS Technical Documentation Figure 19: LCD Interface Accessory RH-48 supports Tomahawk and Universal Headset accessories, differential and singleended, respectively. Detection of Tomahawk accessories is done through the ACI signal where the Universal Headset is detected on GenIO (12). The following graphic shows the pin out of the Tomahawk connector.
RH-48 Troubleshooting — BB CCS Technical Documentation The pin out on the Tomahawk connector is as follows: 1. Charger 2. Charger GND 3. ACI 4. Vout 5. USB Vbus 6. USB D+ / Fbus Rx 7. USB D- / Fbus Tx 8. Data GND 9. XMic N 10. XMic P 11. HSear N 12. HSear P 13. HSear R N 14. HSear R P In Tomahawk accessories, the following functions may be performed: charging, accessory detection, FBUS communication, USB communication, and fully differential audio interface for mono- and stereo outputs.
RH-48 Troubleshooting — BB CCS Technical Documentation In Channel 4 PURX is released; this indicates when the phone operation goes from “RESET” mode to “POWER_ON” mode.
RH-48 Troubleshooting — BB CCS Technical Documentation Tomahawk Headset Detection Accessory detection on the Tomahawk is done digitally.
RH-48 Troubleshooting — BB CCS Technical Documentation FBus Detection FBus communication in Tomahawk is done through the following lines: Pin 2 (Charge GND) Pin 3 (ACI) Pin 4 (Vout) Pin 6 (FBus Rx) Pin 7 (FBus Tx) A waveform for such communication is illustrated here: Accessory Detection Through ACI USB and Audio on (mono or stereo) and FM radio communication in Tomahawk is done through the following signals: USB Audio/FM Pin 5 (USB Vbus) Pin 9 (XMic N) Pin 6 (USB +) Pin 10 (SMIC P) Pin 7 (USB -)
RH-48 Troubleshooting — BB CCS Technical Documentation A waveform showing this interface follows: Page 28 © 2003 Nokia Corporation Confidential Issue 1 11/2003
RH-48 Troubleshooting — BB CCS Technical Documentation SIM CAR RH-48 supports SIM CAR. The following waveform may be used to verify that sim_vcc; sim_i/o, cim_clk, and sim_rst signals are activated in the correct sequence at power up. This picture may be taken when the SIM CAR is installed on the phone to measure the signals when the phone is turned on. The diagram shows the proper waveforms when the interface is working. See Figure 23 (bottom view) diagram for the test point’s location.
RH-48 Troubleshooting — BB CCS Technical Documentation Test Points Figure 22: RH-48 BB test points, regulators, and BB ASICs Page 30 © 2003 Nokia Corporation Confidential Issue 1 11/2003
RH-48 Troubleshooting — BB CCS Technical Documentation Figure 23: RH-48 BB test points, regulators, and BB ASICs Issue 1 11/2003 © 2003 Nokia Corporation Confidential Page 31
RH-48 Troubleshooting — BB CCS Technical Documentation Troubleshooting The following hints should help finding the cause of the problem when the circuitry seems to be faulty. Troubleshooting instructions are divided following sections: 1 Top troubleshooting map 2 Phone is totally dead 3 Power doesn‘t stay on or the phone is jammed 4 Flash programming doesn‘t work 5 Display is not working 6 Audio fault 7 Charging fault First, carry out a through visual check of the module.
RH-48 Troubleshooting — BB CCS Technical Documentation Top troubleshooting map T op P hone totally dead YE S P hone dead YE S F las h faults YE S P hone is jammed YE S C harger faults NO F las h programming does n't work NO P hone does n't s tart up or phone is jammed NO C harging does n't work NO Issue 1 11/2003 © 2003 Nokia Corporation T op page 2 Confidential Page 33
RH-48 Troubleshooting — BB CCS Technical Documentation T op 2 A udio faults YE S A udio faults YE S Dis play faults YE S K eypad faults NO Dis play or L E Ds not working NO K eypad does n't work E ND Page 34 © 2003 Nokia Corporation Confidential Issue 1 11/2003
RH-48 Troubleshooting — BB CCS Technical Documentation Phone is totally dead Phone is dead Phone current is zero or too high? ¾ If current is zero, check X103 and make sure Vbatt connector makes contact. ¾ If current is too high, check for shorts. ¾ Make sure all BB regulators are at their respective voltage levels (VANA, VIO, VCORE, VFlash1, and VR3). See phone's top view diagram for test points. ¾ Make sure the System Clk is 19.
RH-48 Troubleshooting — BB CCS Technical Documentation Flash programming doesn‘t work Flash faults The phone does not set Flashbus TXD line high after the startup YES Measure BSI pulse during Flash programming. Is it OK? NO Check BSI line X103, R202, R206, C100, C111, C240 YES Measure FBusRX (2.78V) signal during flash programming from production pattern and test point J412 (1.8V).
RH-48 Troubleshooting — BB CCS Technical Documentation Flash faults, page 2 Can you read the manufacturer ID and the device ID? NO Reflow or change Flash YES Is the phone totally dead? YES Phone dead YES Phone is jammed NO Phone doesn't start up or the phone is jammed NO Retest Issue 1 11/2003 © 2003 Nokia Corporation Confidential Page 37
RH-48 Troubleshooting — BB CCS Technical Documentation Power doesn‘t stay on or the phone is jammed Phone is jammed Check VBATT, VIO, VCORE, VFlash1, VANA, VR3 capacitors. Are they OK? NO Measure VIO, VCORE, VFlash1, VANA, and VR3 voltages. Are they OK? YES Check BSI/BTEMP lines and VBATT lines. If OK, reflow or change UEM Repair NO YES Measure 32kHz Sleep Clk from testpoint. Is it OK? Measure the 32kHz Clk crystal. Is it OK? NO NO Change B200 YES Reflow or change UEM YES Measure 19.
RH-48 Troubleshooting — BB CCS Technical Documentation Phone is jammed, page 2 Phone shutdown after 32 seconds Has the phone been flashed? YES NO Flash the phone NO Measure DBusClk 9.6MHz and Dbus interface signals at test points J413, J414, J415. OK? Reflow or change UPP. YES Read phone info. Is it OK? YES Retest NO Measure watchdog signal at CBus interface at test points J406, J407, and J408. Is it OK? NO NO Reflow or change UEM and reflash.
RH-48 Troubleshooting — BB CCS Technical Documentation Charger Charger faults Connect Charger. Make sure battery is connected. Battery bar doesn't work (scroll) NO Retest NO Check X102, F100, L100, V100, C106 NO Change UEM NO Change UEM YES Measure voltage over V100. Is it >3.0 Vdc? YES Read BTEMP value. Is it ~25C (0319)? YES Remove (fuse) F100 and measure current.
RH-48 Troubleshooting — BB CCS Technical Documentation Audio faults Audio faults Is the earpiece working? NO Change earpiece. Is it working now? YES Retest NO Set phone in Local Mode. Use Phoenix "Baseband Audio Control" and set the following: Enable Tx, Enable Rx, Select MIC2 (0dB), Enable earpiece and enable digital loopback only. Inject a 1KHz sine signal 20mVp-p on XMIC. YES Is the signal coming out of the UEM on EARP and EARN? Audio faults, page 2 Issue 1 11/2003 NO Check R177, R178.
RH-48 Troubleshooting — BB CCS Technical Documentation Audio faults, page 2 Is the microphone working? NO Change the microphone. Is it working now? YES Retest NO Check connections at C180 and R170. If OK, change UEM NO Check connections at R171, R172, R173, C171, C172, C169, C179, C178. If OK, change microphone NO Check L103, R168, R167, R105. If OK, change UEM NO Set phone in Local Mode.
RH-48 Troubleshooting — BB CCS Technical Documentation Audio faults, page 3 Is internal handsfree speaker (IHF) working? NO Select a ring tone and measure signals at L150 and L151. Is signal OK? YES Change B301 NO Change UPP NO Repair NO Measure GenIO28. Is it OK (1.8V)? YES YES Check N150, R154, C165, C155, C164, R157, C168, C167, R156.
RH-48 Troubleshooting — BB CCS Technical Documentation Audio faults, page 4 Is Vibra working? NO Measure VBATT voltage pin 1 of M300. Is it OK? NO Check VBATT line YES Set phone in Local Mode. Use Phoenix "Message Sender" and navigate as follows: DEV_HOST-->DEV_PC--> PN_ACCESSORY--> PN_OBJ_ROUTING_REQ--> PN_OBJ_PC->UTID_100--> ACC_VIBRA_CTRL_REQ. Select "ACC_ON" and click "Send" YES Measure the UEM signal on pin 2 of M300.
RH-48 Troubleshooting — BB CCS Technical Documentation Display faults Display faults Are the UI module LEDs turned on when phone is turned on or when making a phone call? NO Measure VBATT voltage at C313. Is it OK? NO Check VBATT line YES Set phone in Local Mode. Use Phoenix "Message Sender" and navigate as follows: DEV_HOST--> DEV_PC-->PN_LIGHT--> OBJ_ROUTING_REQ-->OBJ_PC--> UTID--> LIGHT_CONTROL__REQ-> LIGHT_CONTROL_TARGER_KBD.
RH-48 Troubleshooting — BB CCS Technical Documentation Display faults, page 2 Does the Display start? NO Try changing display module. Does it work? YES Retest NO YES Set phone in Local Mode. Use Phoenix "Message Sender" and navigate as follows: DEV_HOST-->DEV_PC--> PN_TEST-->OBJ_ROUTING_REQ--> OBJ_PC-->UTID--> TEST_UI_TEST_REQ--> TEST_DISPLAY_SET-->NUM_SB--> TEST_SB_UI_DISPLAY_PATTERN--> SB_LENGTH.
RH-48 Troubleshooting — BB CCS Technical Documentation Keypad faults Keypad faults Is the power key working? NO Measure voltage at S300. Is it high? Check S302, C310, and R306. If OK, change UEM NO YES Measure voltage at S302 when power key is pressed. Is it high? YES Check S302.
RH-48 Troubleshooting — BB CCS Technical Documentation Keypad faults, page 2 Are the UI modules keys working? NO Change keypads module. Is it working? YES Retest NO YES Measure ROW0-5 (P10-P15) signals between UPP and keypad at J325, J320, J321, J322, J323. Are they ~1.8V? NO Make sure there are no shorts on Z300. If OK, change UPP NO Make sure there are no shorts on Z300.
