Инструкции По Обслуживанию для Nokia n-gageqd
![Nokia](https://files.manualsbrain.com/attachments/dce7461e47de2eca5f7d09be31ff1fc55db75997/common/fit/150/50/3540f9922a492527aa17737eb6cc8428f11e9c5169db0829a90bcdf9088f/brand_logo.jpeg)
Nokia Customer Care
6b - Baseband Troubleshooting
Company Confidential
RH-29
Issue 1 05/2004
Copyright ©
2004 Nokia Corporation
Page 27
Company Confidential
Memory troubleshooting
Most memory related errors are found through flashing the device, flashing the device is
therefore recommended before any of the steps described in this chapter. Check flashing
troubleshooting section first.
therefore recommended before any of the steps described in this chapter. Check flashing
troubleshooting section first.
There are however a few memory related errors that cannot be found through flashing.
•
- SDRAM(D310) partially damaged. This can mean that the SDRAM
component itself is partially damaged and all the memory locations can-
not be successfully read or there is a soldering problem somewhere
either under UPP or SDRAM. There is a BB self test for testing SDRAM
component quite thoroughly, but the problem is that if SDRAM doesn't
function properly one may not be able to run those tests as SDRAM is
used during the device boot and self-test cannot be run if the device
hasn't booted.
component itself is partially damaged and all the memory locations can-
not be successfully read or there is a soldering problem somewhere
either under UPP or SDRAM. There is a BB self test for testing SDRAM
component quite thoroughly, but the problem is that if SDRAM doesn't
function properly one may not be able to run those tests as SDRAM is
used during the device boot and self-test cannot be run if the device
hasn't booted.
•
DEVICE may inform about being "out of memory " more often than it
should
should
•
- flash1 (D312) is partially/totally damaged. During flashing the manu-
facturer, device and revision id's are read, but flashing is done based on
id's of the flash0 (D311). This means that one cannot see any error
messages displayed on Phoenix window during flashing if flash1 is fail-
ing. Id's are however displayed on the Phoenix window and successful
read of flash1 id's can be checked from there.
facturer, device and revision id's are read, but flashing is done based on
id's of the flash0 (D311). This means that one cannot see any error
messages displayed on Phoenix window during flashing if flash1 is fail-
ing. Id's are however displayed on the Phoenix window and successful
read of flash1 id's can be checked from there.