PDA

Просмотр полной версии : RAM память - диагностика ...


Роман
24.09.2017, 12:20
Часто возникает проблема после установки новой флешки с Ram получаем нерабочий ТА.
Через коретку флешка пишется-стирается-читается.
Рандомная проверка тоже проходит нормально.
Есть какие нибудь варианты диагностики таких EMMC ?
Полученные с али флешки очень часто имеют такой брак.
KMQ72000SM-B316 (5шт. получил с али-с виду как новые) - рабочей оказалась только одна (ZTE A510)
Да- и почему то S.M.A.R.T отчет не проходит на BGA221
Compression is ON
Z3X EasyJtag Box JTAG Софт версия. 2.6.0.1
Loading eMMC GEN1 Firmware... IO: 3300 mV
Box С/Н: 0100D01B61******, ,Микропрограмма Вер.: 01.60
Напряжение подтяжки линии CMD :2433 mV
Напряжение активной линии CMD :2774 mV
Box IO Level:3300 mV
CLK Rate:7000 khz
HiPower mode is off!
---------- eMMC Device Information ----------

EMMC CID : 150100513732534D420030B4C4EFB230
EMMC CSD : D02701320F5903FFF6DBFFEF8E40400C
Изготовитель eMMC: ID: 0015 , OEM ID: 0100
EMMC Date: 11/2015 Rev.0x0
EMMC NAME: Q72SMB , S/N: 817153263
EMMC NAME (HEX): 513732534D4200
EMMC ROM1 (Main User Data) Capacity: 7456 MB
EMMC ROM2 (Boot Раздел 1) Емкость: 4096 kB
EMMC ROM3 (Boot Раздел 2) Емкость: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 512 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
EMMC Password Locked: No
Extended CSD rev 1.7 (MMC 5.0)
Boot configuration [PARTITION_CONFIG: 0x00] No boot partition configured.
Boot bus config [177]: 0x00 , width 1bit , Partition config [179]: 0x00.
H/W reset function [RST_N_FUNCTION]: 0x00
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x00000000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------
Backup saved: Q72SMB_ 817153263_20170924_1216.extcsd
Partition table scan:
GPT: not present
Сделано.

Running:SAMSUNG: Read S.M.A.R.T Report...
Z3X EasyJtag Box JTAG Софт версия. 2.6.0.1
Skip loading eMMC Addon Firmware
Напряжение подтяжки линии CMD :2433 mV
Напряжение активной линии CMD :2774 mV
Box IO Level:3300 mV
CLK Rate:7000 khz
Reading S.M.A.R.T
S.M.A.R.T Ver. 0 , Card Error mode : Invalid
S.M.A.R.T Report Done.

hank6
24.09.2017, 12:36
Да- и почему то S.M.A.R.T отчет не проходит на BGA221

HiPower mode is OFF
Frequence: 21 Mhz
CMD Pullup Level: 1711 mV
CMD Active Level: 1753 mV
EMMC Device Information :
EMMC CID: 1501005137585341420105A1E6E3120E
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400C
EMMC Manufacture Name: SAMSUNG
EMMC NAME: Q7XSAB , S/N: 05A1E6E3 , rev. 01
EMMC NAME (HEX): 513758534142
EMMC ROM 1 (Main User Data) Capacity: 7456 MB (0001D2000000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 512 KB (000000080000)
Extended CSD Information :
Extended CSD rev: 1.7 (MMC 5.0, MMC 5.01)
Backup saved: Q7XSAB_05A1E6E3_20170924_123040.extcsd
EMMC Init completed.

Reading S.M.A.R.T Report ...

Supported modes [493]: 0x03
FFU is supported by the device
Vendor Specific mode is supported by the device
FFU Features [492]: 0x00
Device does not support MODE_OPERATION_CODES field
Operation Codes Timeout [491]: 0x00 Not defined
FFU Argument [497_490]: 0x00000000
Number of FW sectors correctly programmed [302_305]: 0x00000000
Vendor Proprietary Health Report [301_270]:
VENDOR_PROPRIETARY_HEALTH_REPORT [301]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [300]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [299]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [298]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [297]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [296]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [295]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [294]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [293]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [292]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [291]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [290]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [289]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [288]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [287]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [286]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [285]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [284]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [283]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [282]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [281]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [280]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [279]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [278]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [277]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [276]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [275]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [274]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [273]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [272]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [271]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [270]: 0x00
Device Life Time Estimation Type B [269]: 0x02
10% - 20% device life time used
Device Life Time Estimation Type A [268]: 0x02
10% - 20% device life time used
Pre EOL information [267]: 0x01
Normal

Optimal Read Size [266]: 0x00 Not defined
Optimal Write Size [265]: 0x04 16 KB
Optimal Trim Unit Size [264]: 0x01 4 KB

Device Version [263_262]: 0x00 - 0x00
Firmware version [261_254]:
FIRMWARE_VERSION [261]: 0x00
FIRMWARE_VERSION [260]: 0x00
FIRMWARE_VERSION [259]: 0x00
FIRMWARE_VERSION [258]: 0x00
FIRMWARE_VERSION [257]: 0x00
FIRMWARE_VERSION [256]: 0x00
FIRMWARE_VERSION [255]: 0x00
FIRMWARE_VERSION [254]: 0x01


видимо чипы с ali изношенные вхлам

slaventiy76
25.09.2017, 10:56
Есть какие нибудь варианты диагностики таких EMMC ?

Только установкой в заведомо рабочий аппарат.

Zlion
25.09.2017, 11:10
RAM память это ОЗУ, ее можно проверить только на плате.
ROM память это ПЗУ, ее можно проверить средствами бокса.

Layder
25.09.2017, 11:30
недавно приехала колодка, начал тестить bga221 группу, что образовалась с б.у. плат.
KMQ72000SM-B316 - Reading MoviNand S.M.A.R.T Report ... Card Error mode: Invalid - у всех 4шт.
KMR310001M - S.M.A.R.T нормально читает, еще у одного тоже норм.

А вот чтобы ОЗУ тестить надо отдельный бокс делать. только никому он не нужен. проще взять плату мтк как донора и флештулом тестировтаь впаивая туда микросхемы, если очень надо

23.09.2017 13:19:09> Backup saved: R311MB_9C13DC35_20170923_131909.extcsd
23.09.2017 13:19:09> EMMC Init completed.
23.09.2017 13:19:09>
23.09.2017 13:19:09> Reading S.M.A.R.T Report ...
23.09.2017 13:19:09>
23.09.2017 13:19:09> Supported modes [493]: 0x01
23.09.2017 13:19:09> FFU is supported by the device
23.09.2017 13:19:09> Vendor Specific Mode (VSM) is not supported by the device
23.09.2017 13:19:09> FFU Features [492]: 0x00
23.09.2017 13:19:09> Device does not support MODE_OPERATION_CODES field
23.09.2017 13:19:09> Operation Codes Timeout [491]: 0x00 Not defined
23.09.2017 13:19:09> FFU Argument [497_490]: 0xC7810000
23.09.2017 13:19:09> Number of FW sectors correctly programmed [302_305]: 0x00000000
23.09.2017 13:19:09> Vendor Proprietary Health Report [301_270]:
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [301]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [300]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [299]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [298]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [297]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [296]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [295]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [294]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [293]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [292]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [291]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [290]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [289]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [288]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [287]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [286]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [285]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [284]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [283]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [282]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [281]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [280]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [279]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [278]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [277]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [276]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [275]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [274]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [273]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [272]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [271]: 0x00
23.09.2017 13:19:09> VENDOR_PROPRIETARY_HEALTH_REPORT [270]: 0x00
23.09.2017 13:19:09> Device Life Time Estimation Type B [269]: 0x01
23.09.2017 13:19:09> 0% - 10% device life time used
23.09.2017 13:19:09> Device Life Time Estimation Type A [268]: 0x01
23.09.2017 13:19:09> 0% - 10% device life time used
23.09.2017 13:19:09> Pre EOL information [267]: 0x01
23.09.2017 13:19:09> Normal
23.09.2017 13:19:09>
23.09.2017 13:19:09> Optimal Read Size [266]: 0x00 Not defined
23.09.2017 13:19:09> Optimal Write Size [265]: 0x10 64 KB
23.09.2017 13:19:09> Optimal Trim Unit Size [264]: 0x01 4 KB
23.09.2017 13:19:09>
23.09.2017 13:19:09> Device Version [263_262]: 0x00 - 0x00
23.09.2017 13:19:09> Firmware version [261_254]:
23.09.2017 13:19:09> FIRMWARE_VERSION [261]: 0x00
23.09.2017 13:19:09> FIRMWARE_VERSION [260]: 0x00
23.09.2017 13:19:09> FIRMWARE_VERSION [259]: 0x00
23.09.2017 13:19:09> FIRMWARE_VERSION [258]: 0x00
23.09.2017 13:19:09> FIRMWARE_VERSION [257]: 0x00
23.09.2017 13:19:09> FIRMWARE_VERSION [256]: 0x00
23.09.2017 13:19:09> FIRMWARE_VERSION [255]: 0x00
23.09.2017 13:19:09> FIRMWARE_VERSION [254]: 0x01
23.09.2017 13:19:09>
23.09.2017 13:19:09> Reading MoviNand S.M.A.R.T Report ...
23.09.2017 13:19:09>
23.09.2017 13:19:10> Card Error mode: Normal
23.09.2017 13:19:10> Super Block size: 0x01000000 (16777216 bytes)
23.09.2017 13:19:10> Super Page size: 0x00008000 (32768 bytes)
23.09.2017 13:19:10> Optimal Write size: 0x00010000 (65536 bytes)
23.09.2017 13:19:10> Read Reclaim count: 0x0
23.09.2017 13:19:10> Optimal TRIM size: 0x00001000 (4096 bytes)
23.09.2017 13:19:10> Total Number of banks: 0x2
23.09.2017 13:19:10> Initial bad blocks per bank: 8,8,0,0
23.09.2017 13:19:10> Runtime bad blocks per bank: 0,0,0,0
23.09.2017 13:19:10> Reserved blocks left per bank : 20,20,0,0
23.09.2017 13:19:10> All Erase counts (min,avg,max): 4,62,1184
23.09.2017 13:19:10> SLC Erase counts (min,avg,max): 417,1104,1184
23.09.2017 13:19:10> MLC Erase counts (min,avg,max): 4,41,120

Backup saved: FN12MB_C230C40D_20170925_113552.extcsd
EMMC Init completed.

Reading S.M.A.R.T Report ...

Supported modes [493]: 0x03
FFU is supported by the device
Vendor Specific mode is supported by the device
FFU Features [492]: 0x00
Device does not support MODE_OPERATION_CODES field
Operation Codes Timeout [491]: 0x00 Not defined
FFU Argument [497_490]: 0xC7810000
Number of FW sectors correctly programmed [302_305]: 0x00000000
Vendor Proprietary Health Report [301_270]:
VENDOR_PROPRIETARY_HEALTH_REPORT [301]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [300]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [299]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [298]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [297]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [296]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [295]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [294]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [293]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [292]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [291]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [290]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [289]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [288]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [287]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [286]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [285]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [284]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [283]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [282]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [281]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [280]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [279]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [278]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [277]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [276]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [275]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [274]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [273]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [272]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [271]: 0x00
VENDOR_PROPRIETARY_HEALTH_REPORT [270]: 0x00
Device Life Time Estimation Type B [269]: 0x01
0% - 10% device life time used
Device Life Time Estimation Type A [268]: 0x01
0% - 10% device life time used
Pre EOL information [267]: 0x01
Normal

Optimal Read Size [266]: 0x00 Not defined
Optimal Write Size [265]: 0x08 32 KB
Optimal Trim Unit Size [264]: 0x01 4 KB

Device Version [263_262]: 0x00 - 0x00
Firmware version [261_254]:
FIRMWARE_VERSION [261]: 0x00
FIRMWARE_VERSION [260]: 0x00
FIRMWARE_VERSION [259]: 0x00
FIRMWARE_VERSION [258]: 0x00
FIRMWARE_VERSION [257]: 0x00
FIRMWARE_VERSION [256]: 0x00
FIRMWARE_VERSION [255]: 0x00
FIRMWARE_VERSION [254]: 0x05

Reading MoviNand S.M.A.R.T Report ...

Card Error mode: Normal
Super Block size: 0x00800000 (8388608 bytes)
Super Page size: 0x00008000 (32768 bytes)
Optimal Write size: 0x00008000 (32768 bytes)
Read Reclaim count: 0x0
Optimal TRIM size: 0x00001000 (4096 bytes)
Total Number of banks: 0x1
Initial bad blocks per bank: 5,0,0,0
Runtime bad blocks per bank: 0,0,0,0
Reserved blocks left per bank : 23,0,0,0
All Erase counts (min,avg,max): 2,159,2435
SLC Erase counts (min,avg,max): 2399,2430,2435
MLC Erase counts (min,avg,max): 2,113,381

Dimaster
25.09.2017, 11:43
Да- и почему то S.M.A.R.T отчет не проходит на BGA221
S.M.A.R.T. читается для любой еММС версии выше 5.0
По крайней мере должен читаться.
По проверке еММС возникли также некоторые вопросы к команде, но это уже другая история.

Layder
25.09.2017, 12:46
S.M.A.R.T. читается для любой еММС версии выше 5.0
По крайней мере должен читаться.
По проверке еММС возникли также некоторые вопросы к команде, но это уже другая история.
расширенный S.M.A.R.T., что в логе, он выдается для emmc 5.0 и выше для всех микросхем.

в данном случае S.M.A.R.T. Invalid это родной Samsung S.M.A.R.T.
это бывает или когда firmware флеши тупит, лечится только апдейтом firmware. но бывает с этим Invalid флешки работают еще.

А по проверке - напишите мне в личку.