[arvika]

Chips with this ID is quite popular lately. But there is many problem with correct reading this chip. I will try write below some informations based on our test reading, hope it will help Sergey and all of us.

So at the beginning we have different producent of memory nands. Toshiba and Sandisk is treat as same for configs. So if there is config with 98 xx xx xx, but our chip is 45 usually we can exchange first byte and config match. I think with ID 98 3c 98 b3 and 45 3c 98 b3 should be same.

I NR v457 we can see configs for:

**************************
ID: 45 3c 98 b3

// Chip
Company Toshiba
Name Monolith
ID code 45 3c 98 b3

// Structure
Bus 8
Banks 1 x 32 GB
Page 18336
Block 0xd6e000
Blocks 0xb8c

// Read
Cmd WL
Col 2
Row 3
DDR false

// Timings
RE_Up 2
RE_Down 2

// Special
Power
Retry
Skip_Mask_1 0xffffffff
Skip_Page_1 0xffffffff
Skip_Mask_2 0xffffffff
Skip_Page_2 0xffffffff
Join CE


**************************
ID: 98 3c 98 b3

// Chip
Company Toshiba
Name Monolith
ID code 98 3c 98 b3

// Structure
Bus 8
Banks 1 x 32 GB
Page 18336
Block 0x1adc00
Blocks 0x5c48

// Read
Cmd WL
Col 2
Row 3
DDR false

// Timings
RE_Up 2
RE_Down 2

// Special
Power
Retry
Skip_Mask_1 0xffffffff
Skip_Page_1 0xffffffff
Skip_Mask_2 0xffffffff
Skip_Page_2 0xffffffff
Join CE
**************************

We can see that configs are different. Size and quantity of blocks is other. Generally if we are lucky (chance 1:3) we can read with this config and it will be ok. As I notice result will be almost same for both (dumps will have different size, one will have just some blocks more).

*********************************************************************

So far we meet three type of this chip:

98 3c 98 b3 76 71
98 3c 98 b3 76 72
98 3c 98 b3 76 e3

We must look on sixth byte from ID, four is too small for this memory. It determines config properties.
So from my expirience configs should look like this:


**************************
ID: 98 3c 98 b3 76 71

// Chip
Company Toshiba
Name Monolith
ID code 98 3c 98 b3

// Structure
Bus 8
Banks 1 x 32 GB
Page 18336
Block 0xa12800
Blocks 0xf68

// Read
Cmd WL
Col 2
Row 3
DDR false

// Timings
RE_Up 2
RE_Down 2

// Special
Power
Retry
Skip_Mask_1 0xff
Skip_Page_1 0xc0
Skip_Mask_2 0xffffffff
Skip_Page_2 0xffffffff
Join CE



**************************
ID: 98 3c 98 b3 76 72

// Chip
Company Toshiba
Name Monolith
ID code 98 3c 98 b3

// Structure
Bus 8
Banks 1 x 32 GB
Page 18336
Block 0xd6e000
Blocks 0xb8c

// Read
Cmd WL
Col 2
Row 3
DDR false

// Timings
RE_Up 2
RE_Down 2

// Special
Power
Retry
Skip_Mask_1 0xffffffff
Skip_Page_1 0xffffffff
Skip_Mask_2 0xffffffff
Skip_Page_2 0xffffffff
Join CE



**************************
ID: 98 3c 98 b3 76 e3

// Chip
Company Toshiba
Name Monolith
ID code 98 3c 98 b3

// Structure
Bus 8
Banks 1 x 32 GB
Page 18336
Block 0x1425000
Blocks 0x7bb

// Read
Cmd WL
Col 2
Row 3
DDR true

// Timings
RE_Up 2
RE_Down 2

// Special
Power
Retry
Skip_Mask_1 0x1ff
Skip_Page_1 0x180
Skip_Mask_2 0xffffffff
Skip_Page_2 0xffffffff
Join CE

**************************

Denis somwhere write that for this ID can be 128x3, 192x3, 320x3. But from my expirience should be: 128x3 (block 384pages), 192x3 (block 576pages) and 384x3 (block 1152 pages). For ID: 98 3c 98 b3 76 e3 we have only one case so it would be good confirm it on other one. Maybe there is 4th type with 320x3 block?
Each this value is divided by 96, so as I understand Sergey try make config one for all, based on 96 pages block. Based on my test it will not work, because for different 6th byte of ID we have different size of blocks and different quantity of blocks.

It would be good solve this problem, because when config is wrong, layout could be wrong too, or some data could be missing. Lets make some statistics from different users.