《NOKIA1220NKC-1X951569.pdf》由会员分享，可在线阅读，更多相关《NOKIA1220NKC-1X951569.pdf（34页珍藏版）》请在taowenge.com淘文阁网|工程机械CAD图纸|机械工程制图|CAD装配图下载|SolidWorks_CaTia_CAD_UG_PROE_设计图分享下载上搜索。
1、CCS Technical DocumentationNKC-1X Series TransceiversIssue 1 02/03Nokia CorporationTroubleshooting InstructionsNKC-1X Troubleshooting InstructionsCCS Technical DocumentationPage 2 Nokia CorporationIssue 1 02/03Table of ContentsPage NoTransceiver Troubleshooting.4Baseband Troubleshooting.4General abo
2、ut testing.4Troubleshooting.4Power up faults.5Flash Programming does not work.10Charging.12Audio failures.13Accessory detection.15Sleep Clock.16Display/Keyboard lights do not work.18Display does not work.19Buzzer does not work.20Keyboard does not work.20Receiver Troubleshooting.21General instruction
3、s for RX troubleshooting.21Path of the received signal.21Fault finding charts for receiver chain.21Transmitter Troubleshooting.25General instructions for TX troubleshooting.25Path of the transmitted signall.25Fault finding charts for the transmitter.25Synthesizer Troubleshooting.2919.44 MHz referenc
4、e oscillator.29RX VHF.31TX VHF.32UHF SYNTHESIZER.33CCS Technical DocumentationTroubleshooting InstructionsNKC-1XIssue 1 02/03Nokia CorporationPage 3List of FiguresPage NoFig 1 Power up sequence.7Fig 2 Fault tree,phone does not power up.9Fig 3 Fault tree,charging.13Fig 4 Fault tree,earpiece fail.14Fi
5、g 5 Fault tree,microphone fail.15Fig 6 Fault tree,accessory detection.16Fig 7 Fault tree,sleep clock.17Fig 8 Fault tree,Display/Keyboard lights.18Fig 9 Fault tree,Display does not work.19Fig 10 Fault tree.AMPS.22Fig 11 Fault tree.Transmitter troubleshooting.26Fig 12 Fault tree:Power control loop.28F
6、ig 13 Detected voltage levels.29Fig 14 Fault tree:19.44 MHz oscillator.30Fig 15 Fault tree:RX VHF VCO.31Fig 16 Fault tree:TX VHF VCO.32Fig 17 Fault tree:UHF Synthesizer.33NKC-1X Troubleshooting InstructionsCCS Technical DocumentationPage 4 Nokia CorporationIssue 1 02/03Transceiver TroubleshootingThe
7、 first thing to do when you are encountered with a problem is to carry out a thoroughvisual check of the module.Make sure that:there are no mechanical damagesthe solder joints are OKNote:Before changing anything,ALL SUPPLY VOLTAGES AND THE SYSTEMCLOCK/SLEEP CLOCK should be checked.Baseband Troublesh
8、ootingGeneral about testingThe phone has three different modes for testing and/or repairing the phone.The modescan be selected with suitable resistors connected to BSI-and BTEMP-lines as illustratedin the table below:If the corresponding resistors are connected,the MCU software automatically enters
9、intothe local or test mode when the supply voltage is connected to the phone.The power can be switched on by:1Pressing the power key.2Connecting the local/test mode resistors to the bsi/btemp lines and connectingthe battery voltage to the phone.3Connecting a charger.4Phones internal functions(Real t
10、ime clock alarm)In the local and test mode,the baseband can be controlled through MBUS or FBUS(FBUSis recommended)connections using Phoenix service software.TroubleshootingNote:Most of the baseband repair actions require removing the baseband shield.The shield must not be removed unless separately a
11、uthorized by the program.Table 1:Phone operating modeModeBSI-resistorBTEMP resistorRemarksNormal68k47kLocal560_(1k560_(DSP starts runningNote:In figure below,the RF_Clk frequency appears to be lower than 19.44MHzbecause of a too low oscilloscope sampling frequency(2kS/s).CCS Technical DocumentationT
12、roubleshooting InstructionsNKC-1XIssue 1 02/03Nokia CorporationPage 7Figure 1:Power up sequenceFigure 2:Power up sequence1Power key pressedAfter 20ms UEM enters RESET MODE if VBATVmstr+VFLASH1,Vana,Vcore,Vio and VR3 goes high.VCTCXO enabled by VR3-RFClk 19.44 MHz running.2Purx releasedPurx released
13、by UEM,UEMINT goes high for 100 ms,SleepX goes high and UEMstarts feeding SleepClk(32 KHz)to UPP.Note:The sleepclock starts running in the crystal circuitry(B200)immediately whenthe battery voltage is supplied.3Software runningDefault value for Vcore is 1.5 volts when the software is running.Cbus(1.
14、08MHz)clock starts running.NKC-1X Troubleshooting InstructionsCCS Technical DocumentationPage 8 Nokia CorporationIssue 1 02/03Phone does not start up normally or does not stay onNote:In case of power up faults,it is not possible to force the phone on by disablingthe watchdog.Instead,measurements sho
15、uld be taken immediately when thepower key is pressed or when the battery voltage is connected to the phone(local/test mode).The easiest way to check if the software is running when the phone takes an abnormal amount of current is to measure the cbusclk and Vcore.The Dbus clock(programmable 9.72MHz)
16、is not automatically visible in the test and localmodes.CCS Technical DocumentationTroubleshooting InstructionsNKC-1XIssue 1 02/03Nokia CorporationPage 9Figure 3:Fault tree,phone does not power upTry to start phone to test or local modeCheck the power keyCheck X101Measure Vflash1,Vana,Vio,Vcore,VR3w
17、hen pwr key pressedCheck 19.44MHz RF-clock from C420Check that purx goes up to 1.8V Change UPP(D400)Change the UEM(D200)OKMeasure VBAT from C261Check R202,R205,C217,C220Check G790(missing,misaligned)Measure J406.Should be 1.08 MHzCheck C420Check 19.44MHz from G790Change N801FAILRe-flash phoneOKOKFAI
18、LVANA&VR3missingFAILOKOKOKCheck R792,C792,C793Change G790OKFAILFAILOKOKFAILOKOKOKFAILProgrammng ok,but phone doesnt startGo to flash failure chartProgrammingfailsR206,R207,C220,C240NKC-1X Troubleshooting InstructionsCCS Technical DocumentationPage 10 Nokia CorporationIssue 1 02/03Flash Programming d
19、oes not workFlash programming procedure1The phone communicates with the prommer via the production test pattern,using the following signals:FBUSTX(serial data to phone)FBUSRX(serial data from phone)MBUS(serial clock for FBUSRX)VPP(External flashing voltage for speed up flashing)The BSI line is also
20、used when initializing flashing(battery connector).2When the phone is powered(VBAT3V),the MBUS and FBUSTX lines are pulledup internally by the phone.3The prommer sends a command to the UEM,using FBUSRX,to enter the Flash-mode.During the sending of this command,the prommer keeps the BSI line highand
21、MBUS is used as a serial clock.4When the Flash-mode command is acknowledged,UEM enters the Flash-modeand releases reset(PURX)to MCU.5After reset is released,UPP checks if there is a request for the Bootstrap code(that resides in the UPP ROM).6The request for Bootstrap is the MBUS pulled down by the
22、prommer(if the boot-strap is not requested,the bootstrap code jumps to FLASH SW).7If the Bootstrap code is requested,UPP enters the Flash-mode and sets FbusTX to0 as an acknowledgement to the prommer.This is an indication that UPP canrun,at least,the fixed Bootstrap code although it is not able to r
23、un the FLASHcode.UPP then sends an UPP-ID to the prommer via the FBUSTX line.8After the prommer has received the UPP-ID,it sends a corresponding SecondaryBoot Code to the phone via FBUSRX.The Secondary Boot Code,when run in UPP,requests UPP to send information to the prommer about the flash type and
24、 otherHW-related parameters about the device to be flashed.9Prommer then sends the Algorithm Code corresponding to the HW parameters,and this algorithm,when run in UPP,takes over handling the MCUSW transfer toFlash.10 12 volts can be supplied to Vpp(by the prommer)to speedup flashing.CCS Technical D
25、ocumentationTroubleshooting InstructionsNKC-1XIssue 1 02/03Nokia CorporationPage 1111 The FLASH Program includes a package of MCU and DSP software and all defaultparameters for the phone.The tuning values will be added/rewritten during theFlash/Alignment phase.Flash programming error codesThe variou
26、s error codes can be seen from the FPS-8 Flash in Phoenix.The underlined text in the table below means that the item under consideration is beingused for the first time in the flashing sequence.Table 2:Table 2.Flash programming error codes.ErrorDescriptionNot working properlyC101The Phone does not s
27、et FbusTx line high after the startup.VbattVflash1VcoreVIOBSI and FbusRX from prommer to UEM.FbusTx from UPP-UEM-Prommer(SA0)C102The Phone does not set FbusTx line low after the line has been high.The Prommer generates this error also when the Phone is not connected to the Prommer.PURX(also to Safar
28、i)VR3Rfclock(VCTCXO-Safari-UPP)Mbus from Prommer-UEM-UPP(MbusRx)(SA1)FbusTx from UPP-UEM-Prommer(SA1)C103Boot serial line fail.Mbus from Prommer-UEM-UPP(MbusRx)(SA0)FbusRx from Prommer-UEM-UPPFbusTx from UPP-UEM-PrommerC104MCU ID message sending failed in the Phone.FbusTx from UPP-UEM-PrommerC105The
29、 Phone has not received Secondary boot codes length bytes correctly.Mbus from Prommer-UEM-UPP(MbusRx)FbusRx from Prommer-UEM-UPPFbusTx from UPP-UEM-PrommerC106The Phone has not received Secondary code bytes correctly.Mbus from Prommer-UEM-UPP(MbusRx)FbusRx from Prommer-UEM-UPPFbusTx from UPP-UEM-Pro
30、mmerC107The Phone MCU can not start Secondary code correctly.UPPA204The flash manufacturer and device IDs in the existing Algorithm files do not match with the IDs received from the target phone.FlashSignals between UPP-FlashA387The MCU ID in the MCUSW.”UPPC601The prommer has detected that Vpp volt-
31、age level has dropped below the limitVpp from prommer-FlashNKC-1X Troubleshooting InstructionsCCS Technical DocumentationPage 12 Nokia CorporationIssue 1 02/03ChargingNote:The charging voltage and current can be checked by connecting the phone tothe service software and reading the ad-converter valu
32、es of the vchar andichar.If charging fails when the LCH-9 is used,and works with ACP-7 and ACP-8,check thatthe charge control pin of the system connector is connected to the ground.C383C583C683The Prommer has not received Phone acknowledge to the message.(C383-during algorithm download to tar-get ph
33、one)(C583-during erasing)(C683-during programming)FlashUPPSignals between UPP-FlashC384C584C684The Phone has generated NAK signal dur-ing data block transfer.(C384-during algorithm download to tar-get phone)(C584-during erasing)(C684-during programming)FlashUPPSignals between UPP-FlashC585C685Data b
34、lock handling timeout(C585-during erasing)(C685-during programming)FlashUPPSignals between UPP-FlashC586C686The status response from the Phone informs about fail.(C586-during erasing)(C686-during programming)FlashCCS Technical DocumentationTroubleshooting InstructionsNKC-1XIssue 1 02/03Nokia Corpora
35、tionPage 13Figure 4:Fault tree,chargingAudio failuresIn case of audio failures,there are three possibilities to check the audio lines.1Make a phone call against tester and check audios.2In case the earpiece/XMIC fails:Feed a 1Khz signal to the XMIC line and measurethe signal from the earpiece line.T
36、he Audio test box JBA-8 is needed.The Audioloop(Audio test/Ext In Hp Out)must be switched on by the Phoenix service soft-ware.This loop will connect audios only through the UEM.In this case,the UPP isnot used.In case the internal microphone/XEAR fails:Feed the tone to the microphone andmeasure the s
37、ignal from the XEAR line.The Audio test box JBA-8 is needed.ThePhone doesnt start chargingConnect charger and check VCHARINChange the UEMCheck F100,L100,V100,C105Check bottom connector-VIN-Charge control pinCheck R202,R203,R205,C217,C220,C201,C202 and R200FailOKCheck ICHAROKFAILOKR202.R206,R207,C201
38、,C202,C220,C240 and R200 F100,L100,V100,C105NKC-1X Troubleshooting InstructionsCCS Technical DocumentationPage 14 Nokia CorporationIssue 1 02/03Audio loop(Audio test/Hp In Ext Out)must be switched on by the Phoenix servicesoftware.This loop will connect audios only through the UEM.In this case,theUP
39、P is not used.3Run the audio-loop self-test with Phoenix(BB Self Tests/ST_EAR_DATA_LOOP_TEST).This loop will test the ear-data/mic-data linesbetween the UPP and the UEM.Earpiece or external microphone line does not workFigure 5:Fault tree,earpiece failEarpiece doesnt workRun audio-loop selftest with
40、 phoenixCheck R157Check earpieceChange UEMFeed 1KHz to Xmic by JBA-8 and measure from earpieceChange UPPFailOKOKOKFailOKCCS Technical DocumentationTroubleshooting InstructionsNKC-1XIssue 1 02/03Nokia CorporationPage 15Microphone or XEAR line does not workFigure 6:Fault tree,microphone failAccessory
41、detection1Start the phone in the normal mode when checking for accessory detection.2The Ad-converter value of the hookint-line can be checked with the Xmic-switch on an MJS-18 test jig.Changes normally from high to low when no acces-sory is connected.3When the headset HDC-5 is connected,the hookint-
42、value should be between600 and 800.Microphone doesnt workRun audio-loop selftest with phoenixCheck R156,C151,C152,C157,L164Check microphoneChange UEMFeed 1KHz to Mic by JBA-8 and measure from XearChange UPPFailOkOkOkOkFailNKC-1X Troubleshooting InstructionsCCS Technical DocumentationPage 16 Nokia Co
43、rporationIssue 1 02/03Figure 7:Fault tree,accessory detectionSleep Clock Missing/non-functional sleep clock causes entering sleep mode fails(higher current consumption-shorter standby time).The Baseband self tests cannot be run.Phone clock(on display)does not function properly.Accessory detection do
44、esnt work normallyCheck HeadInt ad-value with Phoenix(No accessory connected)-HeadInt 0 *)Change UEMCheck R152,C161,L160Check R150,R201,C104,C105,L162,L163Check R151 and C160Check bottom connector*On local or test mode Headint 12 dBCheck UHF Vc(from C773)V:1.8.2.1 VStart synthesizer troubleshootingA
45、MPSRX-chain OKYYNYNStart synthesizer troubleshootingYApply 881.49 MHz-30dBm,sine signal to external RF-connector X900.NNote!These tests are done in local mode by using RFTest UI.CCS Technical DocumentationTroubleshooting InstructionsNKC-1XIssue 1 02/03Nokia CorporationPage 23NNCheck input level at d
46、iplexer(Z907)input.Check input level at duplex filter.You can also check level atdiplexer outputCheck input level atLNA input(J800).Change EXT RF Connector Note!Check all soldering and componentsin antenna circuit before changingNYChange diplexer Z906Note!Check all soldering and discretecomponents o
47、f frontend.Change duplex filter(Z906)YCheck RF level at RX800 band filter input.Change SAFARI(N801)Check RF level at MIX1_A input.Change SAFARI(N801)Note!Check all solderings and discrete copmponents around SAFARI before changingNYNYNYNote!From the begin to MIX_1A inputyou should see strong RF signa
48、llevel at 881.49 MHz.Exact levelis difficult to define here becausevariable impedances in RX path.Also used probe type affects tothe results.Z907.TACOTACOMIX1Ain P/N.TACONKC-1X Troubleshooting InstructionsCCS Technical DocumentationPage 24 Nokia CorporationIssue 1 02/03Check RF level at RX IF filter
49、 output at 135.54 MHzChange SAFARI(N801)Check RF level by L730 without having electrical contact at 271.08 MHz Note!Check all discrete components andvoltages around SAFARI Check RF level at RX IF filter input at 135.54 MHzCheck RF level at J751 and J752 at 2034.06 MHzNYYNYNYStart synthesizer trouble
50、shootNChange RX IF filter(Z830)Start synthesizer troubleshootCheck RX I and Q signals at I:J801(+),J803(-)and Q:J804(+),J802(-)NChange SAFARI(N801)Check UEM and start baseband troubleshootYTACO.TACOTACOCCS Technical DocumentationTroubleshooting InstructionsNKC-1XIssue 1 02/03Nokia CorporationPage 25