Flash Extractor
© Soft-Center
About     Shop     Downloads     Manual     Library     Forum     Services     Contacts
Reading Bad Quality Chips   Search  Register  Log in
23.09.2023 - tech support stopped
23.09.2024 - forum closed
Reply to topic
Author Message
jeremyb



Joined: 09 Dec 2008
Posts: 1950
Location: RecoverMyFlashDrive.com Bridgeport, CT, USA

PostPosted: Sun Feb 16, 2020 0:53    Post subject: Reading Bad Quality Chips
Reply with quote

arvika wrote:
Currently there is a big problem with reading chips with good quality dump.

What are some IDs of NAND chips that are having issues?
Has adjusting the Vcc helped?
Has Read Retry helped?

My antidotal notes and thoughts not backed up with fact:

WL Toshiba / SanDisk:
Erasing a block doesn’t set all bits to 1 or 0, instead most of the bits are set to 1 or 0. (See picture).. FE gets stuck on these trying to process the data.

My solution: Count the state of bits in the first 128bits of a block, if its more than 85% either way disregard the block and fill the block with set bits.. its a variable percentage but my reasoning is XOR distributes the number of bits, if the distribution is bad the underlying data is probably bad. This greatly speeds up FE on applicable cases (eg: SanDisk)

Variable Voltage: Do Toshiba/SanDisk NAND work with the Power Adapter? From memory every time I've tried I get an ID of 0x00ffffff, ?? Do Toshiba Chips NOT start up Tri-State ??.. From memory covering Vcc pin on the NR and supplying external voltage (eg: 2.55v) only works for monolithics, especially monolithics where the controller powers up when external 3.3v is applied sending spurious data to the NR..

Constant Voltage: Some Toshiba/SanDisk NAND chips need voltage applied to pins not supported by TSOP-48 adapter v3... eg WP or 16bit I/O.. This must be done manually.

Hynix:
Many of these chips need Read Retry Modes and the applicable registers vary by ID however its implementation would be complicated. Specifically, unlike SanDisk or Intel where a Read Retry mode is generally valid for an entire bank.. Hynix Read Retry modes are only valid for a page (upper, middle, lower), block, or plane. If a bad page is encountered every read retry mode is cycled through to find a good value. Currently the only option is ECC combine however it's not efficient. I haven't had any luck using different voltages but I haven't done any extensive testing with Power Adapter v3 so I might be wrong..

My Solution: Use Read Retry Codes in Segments and merge the files together..

Intel / Micron:
Variable Voltage - Use Power Adapter

Also sometimes I think it must be acknowledged the the chip might just be bad.

Does anyone else have any antidotal input on bad quality chips?
Capture.JPG
Erased block where most bits are set to 1
Amarbir[CDR-Labs]



Joined: 01 Jan 2017
Posts: 15
Location: Chandigarh [India]

PostPosted: Sun Apr 26, 2020 13:02    Post subject:
Reply with quote

Hello ,
Thank You For This Post ,It matters a lot to newbies like us ,Who get the idea ...
Display posts from previous:   
Reply to topic All times are GMT + 4 Hours
Page 1 of 1

 

Last added
AU6989NHL-2   98 d7 98 b2   1x1 SM3281L-AB   45 3c 98 b3   1x1   v5 Monolith Micro SD_76   98 3c 99 a3   1x4 SM3265P-AC   45 3e 98 03   1x1 SM3281N-AB   45 48 9a b3   2x2 Monolith Micro SD_75   32 2c c3 08   1x1 Monolith Micro SD_74   45 3e 98 b3   1x4   Ref AU6989SNHL-2   45 de 98 92   1x1 SM3261L-AB   45 de 98 92   1x1 SM2232T AC   89 d7 94 3e   4x2
News
01.02.2024 Save FE key
23.09.2022 The End
11.11.2021 Legs for NR
16.08.2021 Sector Number Slow
15.07.2021 New drivers
© Soft-Center ltd.