CCS Technical Documentation NPD-1 Series Transceivers Troubleshooting — BB Issue 1 11/2002 Confidential Nokia Corporation
NPD-1 Troubleshooting — BB Page 2 Nokia Corporation CCS Technical Documentation Confidential Issue 1 11/2002
NPD-1 Troubleshooting — BB CCS Technical Documentation Contents Page No Troubleshooting Overview ............................................................................................ 5 Flash programming ......................................................................................................6 Connections to Baseband .......................................................................................... 6 Baseband Power Up .............................................................
NPD-1 Troubleshooting — BB Page 4 Nokia Corporation CCS Technical Documentation Confidential Issue 1 11/2002
NPD-1 Troubleshooting — BB CCS Technical Documentation Troubleshooting Overview The baseband module of the Eagle transceiver is a CDMA dual band engine. The baseband architecture is based on the Columbia phone but includes some additional features, such as MIDI and gray-scale LCD. The baseband consists of three ASICs: Universal Energy Management (UEM), Universal Phone Processor (UPP), and FLASH 64Megabit. The baseband architecture supports a power-saving function called ”sleep mode”.
NPD-1 Troubleshooting — BB CCS Technical Documentation PRODTP VBatt VPP Battery XEAR Output VIO ExBusC XMIC Input Flash DC/DC Add/Data Bus System Connector Charger Sleep Clk 32 KHz UEM VANA FBusRx FBusTx GenIO VR1A Vflash1 VR1B RX I/Q Data Vflash2 TX I/Q Data VR2 UPP RX Audio Data VR3 TX Audio Data VR4 CBus VR5 MBus VR6 RF_BUS DBus FBus VR7 L CD Data Bus VCTCXO 19.
NPD-1 Troubleshooting — BB CCS Technical Documentation FBUSRX, MBUS, and BSI connections for the connection to the baseband. The connection is through the UEM — which means that the logic levels correspond to 2.7V. Power is supplied using the battery contacts. Baseband Power Up The baseband power is controller by the flash prommer in production and in reprogramming situations. Applying supply voltage to the battery terminals, the baseband will power up.
NPD-1 Troubleshooting — BB • CCS Technical Documentation When phone is connected to the prommer, the prommer will first set BSI to "1" and then uses FBUSRX for writing and MBUS for clocking. The prommer will indicate to UEM that flash programming will take place by writing 8-bit password (*0xC9") to UEM after BSI is set to high. After the password is checked, BSI is set back to "0”. See the following figure.
NPD-1 Troubleshooting — BB CCS Technical Documentation FLASH_2 CH1 CH2 CH3 CH4 = = = = PURX MBUS FBUSTX FBUSRX M easure points Production test pattern (J396) Figure 3: Flashing (2) Ch1-> PURX Ch2-> MBUS toggled three times for MCU initialization Ch3-> FBUS_TX low, MCU indicates that prommer has been noticed Ch4-> FBUS_RX • This boot code asks MCU to report prommer phone’s configuration information, including flash device type.
NPD-1 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 4: Flashing (continued) Power Up and Reset Power up and reset is controlled by the UEM ASIC.
NPD-1 Troubleshooting — BB CCS Technical Documentation acknowledged at the rising edge of the PURX signal in order to always give the same watchdog response time to the MCU. The following timing diagram represents UEM start-up sequence from reset to power-on mode. Reference signal PwrOnX Charger Detection RTC UEMRSTX VFlash1 VIO VCORE VANA VR3 19.
NPD-1 Troubleshooting — BB CCS Technical Documentation Figure 6: 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.
NPD-1 Troubleshooting — BB CCS Technical Documentation output voltage. As the battery charges, its voltage rises, and when VBAT voltage level is higher than master reset threshold limit (VMSTR+) is detected START_UP charge is terminated. Monitoring the VBAT voltage level is done by charge control block (CHACON). MSTRX=‘1’ output reset signal (internal to UEM) is given to UEM’s RESET block when VBAT>VMSTR+ and UEM enters into reset sequence.
NPD-1 Troubleshooting — BB CCS Technical Documentation The average current consumption of the phone in sleep mode can vary depending mainly on SW; however, on average is about 9 mA. In the ACTIVE mode, the phone is in normal operation, scanning for channels, listening to a base station, transmitting and processing information. There are several sub-states in the active mode depending on the present state of the phone such as: burst reception, burst transmission, DSP working, etc.
NPD-1 Troubleshooting — BB CCS Technical Documentation Table 1: Baseband regulators Regulator Maximum current (mA) Vout (v) Notes VCORE (dc/dc) 300 1.5 Output voltage selecta ble 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 active cover is detected VANA 80 2.
NPD-1 Troubleshooting — BB CCS Technical Documentation Figure 7: Waveform of 19.2MHz clock from RF to UPP 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 the following figure.
NPD-1 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 figure below for Cbus data transfer.) Figure 9: Cbus data transfer DBUSClk Interface A 9.6 MHz clock signal is used for DBUS, which is used by the DSP to transfer data between UEM and UPP. (See following figure.
NPD-1 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. (See next figure.
NPD-1 Troubleshooting — BB CCS Technical Documentation Figure 12: 32kHz analog waveform at32KHz crystal input Charging operation Battery A 950 mAh Lithium-Ion cell battery is used. Reading a resistor inside the battery pack on the BSI line indicates the battery size. NTC-resistor inside the battery measures the battery temperature on the BTEMP line. Temperature and capacity information are needed for charge control. These resistors are connected to BSI and BTEMP pins of battery connector.
NPD-1 Troubleshooting — BB CCS Technical Documentation Figure 14: 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 baseband supports DCT3 chargers from an electrical point of view.
NPD-1 Troubleshooting — BB CCS Technical Documentation The charger recognition is initiated when the EM SW receives a ”charger connected” interrupt. The algorithm basically consists of the following three steps: 1 Check that the charger output (voltage and current) is within safety limits. 2 Identify the charger as a two-wire or three-wire charger. 3 Check that the charger is within the charger window (voltage and current).
NPD-1 Troubleshooting — BB CCS Technical Documentation input can have either a differential or single-ended AC connection to UEM circuit. The internal microphone (MIC1) and MIC2 are differential and MIC3 microphone is single-ended. The microphone signals from different sources are connected to separate inputs at UEM. Inputs for the microphone signals are differential type. Also, MICBIAS1 is used for MIC1 and MICBIAS2 is used for MIC2 and MIC3.
NPD-1 Troubleshooting — BB CCS Technical Documentation cables can be directly connected to system connector or 2.5mm jack supporting TTY/TDD or universal headset. Detection of the different accessories is based on the ACI code residing inside the accessories except for basic headset (HDB-4) and universal headset. The UHJ is detected by the interrupt generated on GenIO(12). The basic headset is detected via ACI detection algorithm. However, the ACI pin is always grounded.
NPD-1 Troubleshooting — BB CCS Technical Documentation VFLASH2 VR1A VR1B VR6 VR4 VANA VR2 VFLASH1 VR7 VREFRF02 UEM VR3 VREFRF01 VIO 19.
NPD-1 Troubleshooting — BB CCS Technical Documentation Troubleshooting/Flowcharts The following hints should help finding the cause of the problem when the circuitry seems to be faulty. This troubleshooting instructions are divided into the 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 thorough visual check of the module.
NPD-1 Troubleshooting — BB CCS Technical Documentation Top troubleshooting map Top lly ta to e d on ea Ph d YES Phone dead NO F g in m a m o rk r og w pr 't h esn s la d o YES Flash faults YES Phone is jammed NO t n' e es on do ph d e r on p o me Ph rt u jam a st is NO Charger h C t n' es do ng k gi or ar w YES NO Page 26 Nokia Corporation Top 2 Confidential Issue 1 11/2002
NPD-1 Troubleshooting — BB CCS Technical Documentation YES Audio faults Au dio fa ul ts Top 2 NO s ED L g or kin ay or l w isp t D no YES Display faults Ke yp ad wo do rk esn 't NO YES Keypad faults END Issue 1 11/2002 Nokia Corporation Confidential Page 27
NPD-1 Troubleshooting — BB CCS Technical Documentation Phone is totally dead Phone is dead - If current is zerro check X110 solder and VBATT lines -If current is too high check for shorts - Make sure all BB regulators are at their respective voltage levels like VANA, VIO , VCORE(DC-DC), VFlash1, and VR3. See phones top view diagram for test points. - Make sure the System Clk is 19.2MHz and that the Sleep Clk is 32KHz - Also m ake sure PURX and SleepX signals are high (1.8V).
NPD-1 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? Check BSI line X110, C230, R203, R202 No No Yes Measure FBusRx FBusTX and MBUS during flash programming at the bottom connector and Flash pads . Does waveform match Figure 1 No Check R100, R101, R104, C104, C105, and V101.
NPD-1 Troubleshooting — BB CCS Technical Documentation Phone is jammed Flash faults 2 Can you read the manufacturer ID and device ID? No Change flash Yes Is the phone totally dead? Yes GO TO Phone is dead Yes GO TO Phone is jammed No Phone doesn't start up or phone is jammed? No Re-test Page 30 Nokia Corporation Confidential Issue 1 11/2002
NPD-1 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 ? Measure VIO, VCORE, Vflash1, VANA, and VR3 voltages. Are they OK ? Yes Check BSI/BTEMP lines and VBATT lines if OK change UEM No No Repair Yes Measure 32kHz Sleep Clk from testpoint . Is it OK? No Measure the 32kHz Clk crystal. Is it OK? No Change B200 Yes Yes Change UEM Measure 19.
NPD-1 Troubleshooting — BB CCS Technical Documentation Jam m ed P age 2 Yes Phone shutdown after 32 seconds Has the phone been flashed? No Flash the phone Yes Change UPP and re-flash. If problem still exist, change UE M and reflash the phone No Read phone info.
NPD-1 Troubleshooting — BB CCS Technical Documentation Charger Charger Connect Charger Make sure battery is connedted. Battery bar doesn't work (scroll) No Retest Yes Measure voltage over V100. Is it > 3.0 Vdc? No Check X101,X102, F100, L100, V100, C106. Yes Unit Read BTEMP value. Is it ~ 25C (0319)? No Change UEM Yes Remove (fuse) F100 and measure current.
NPD-1 Troubleshooting — BB CCS Technical Documentation Audio faults Earpiece Audio faults Is the earpiece working? No Change earpiece. Is it working now? Yes Yes Retest No Set phone in LOCAL m ode. Use phoenix "Baseband Audio Control" and set the following: Enable Tx, Enable Rx, Select MIC2 (0dB), Enable earpiece only.
NPD-1 Troubleshooting — BB CCS Technical Documentation Microphone Audio faults 2 Is the m icrophone working? No Change the m ichropone. Is it working now? Yes Retest No Yes Set phone in LOCAL m ode. Use Phoenix "Baseband Audio Control" and set the following: Enable Tx, Enable Rx, Select MIC1, Enable HF only (differential ended). Talk throug the m ichrophone. For AM S, set voice loopback on the call box and m ake a phone call Measure MICB1 at C195 is it~2.1V? No Check C195, R176, R178, .
NPD-1 Troubleshooting — BB CCS Technical Documentation MIDI Audio faults 3 No Is MIDI working? Measure VBATT voltage from C196 Is it OK? No Check V BATT line. Yes Yes Set phone in LOCAL m ode. Use Phoenix to digital loop MIC1 to HF single ended output. Also Set GenIO(28) high For AM S, select different Nokia ringing tone Talk to MIC1.Check signal @ C157. Is signal OK? No Change the UEM Yes Check signal @ MIDI speaker pads.
NPD-1 Troubleshooting — BB CCS Technical Documentation Vibra Audio faults 4 No Is VIBRA working? Measure VBATT voltage pin 1 of M300. Is it OK? No Check VBATT line. Yes Yes Set phone in LOCAL mode. Use Phoenix "Message Sender" and navegate down 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' Measure the UEM signal on pin 2 of M300.
NPD-1 Troubleshooting — BB CCS Technical Documentation Display faults Display faults Are the UI-m odule LED's turned on when phone is turned on or when m aking a phone call? Yes No Measure VBATT voltage at C310 Is it OK? No Check V BATT line. Set phone in LOCAL Yes m ode. Use Phoenix "Message Sender" and navegate down as follows: DEV_HOST --> DEV_PC --> PN_LIGHT --> OBJ_ROUTING_REQ --> OBJ_PC --> UTID --> LIGHT_CONTROL_RE Q --> LIGHT_CONTROL_TARG ER_K No BD.
NPD-1 Troubleshooting — BB CCS Technical Documentation Display faults 2 Does the display start? No Try changing display m odule. Does is works? Yes Retest No Yes Set phone in LOCAL m ode. Use Phoenix "Message Sender" and navegate down as follows: DEV_HOS T --> DEV_PC --> P N_TEST --> OBJ_RO UTING_REQ --> OBJ_PC --> UTID --> TEST_UI_TEST_REQ --> TEST_DISPLAY_SET --> NUM_SB: --> TEST_SB_UI_DISPLAY_PATTE RN -->SB_LENGTH.
NPD-1 Troubleshooting — BB CCS Technical Documentation Keypad faults Power key Keypad faults Is the power key working? No Measure voltage at S300. Is it HIGH? No Check S300, and R304. If OK change UEM. Yes Yes Measure voltage at S300 when power key is pressed.
NPD-1 Troubleshooting — BB CCS Technical Documentation UI modules Keypad faults 2 Press malfunctioning key or keys on the keypad.
NPD-1 Troubleshooting — BB Page 42 Nokia Corporation CCS Technical Documentation Confidential Issue 1 11/2002
