ID 86 84 24 5F

[ddrecovery]

I have a Micro Center UFD Monolith that keeps giving me the ID 86 84 24 5F.
I have wired her up a few times and always get the same ID.
Anyone seen that ID before?

[arvika]

Show photo of monolith.

[ddrecovery]

Here you go.

Attachments

[arvika]

Are you sure if you not mix wires from data channel?

[jeremyb]

or you didn't short the wires on the data bus?

[ddrecovery]

Are you sure if you not mix wires from data channel?

Checked and all okay.

or you didn't short the wires on the data bus?

Not sure I understand?

[fzabkar]

or you didn't short the wires on the data bus?

Not sure I understand?

It may be a red herring, but bit #2 is always 1. The other bits change state.

[HaQue]

I think ID should be 0x88 0x89 0x28 0x5F

wiring looks like correct pinout used.

is this point broken?

Maybe go over the whole thing with microscope and look for any solder bridges or balls fallen onto PCB or cracks.

[fzabkar]

How about ID=0x89,0x88,0x28,0x5F,0x00,0x00

https://www.usbdev.ru/databases/toauflist/ic98/

Code:

86       84       24       5F
10000110 10000100 00100100 010111111
    **::
10001001 10001000 00101000 010111111
89       88       28       5F

This is what you would get if bit 0 were swapped with bit 1, and bit 2 with bit 3.

[HaQue]

Franc, yes, mine was a typo. that is a valid ID for a device with 1 bank of 8GB. Tim, what is the device capacity?

[ddrecovery]

It is a 16gb chip. But only reads as having one part.

[ddrecovery]

Thanks for the responses. Not sure where to take it from here. I have double and treble checked the pinout and it is wired correctly.

[ddrecovery]

I am not sure I understand the correlation between the flipped bits and the pinout of the monolith?
What would you guys suggest I try?

[fzabkar]

I am not sure I understand the correlation between the flipped bits and the pinout of the monolith?
What would you guys suggest I try?

If I'm right, then you should swap data bit 0 with data bit 1, and bit 2 with bit 3.

[ddrecovery]

I am not sure I understand the correlation between the flipped bits and the pinout of the monolith?
What would you guys suggest I try?

If I'm right, then you should swap data bit 0 with data bit 1, and bit 2 with bit 3.

Many thanks I will give it a try.

[ddrecovery]

Deleted, back with more info soon.

[ddrecovery]

It was a great suggestion swapping bits, but the new ID (A9 A8 28 7F) shows that swapping D0 with D1 and D2 with D3 actually changes more than these bits. I have studied the code but cannot see any viable patterns.

Code:

86       84       24       5F
10000110 10000100 00100100 010111111
    **::
10101001 10101000 00101000 011111111
A9       A8       28       7F



[fzabkar]

Now it appears that bit#5 is stuck high. :-?

[fzabkar]

I just tried this NAND ID decoder:
https://multi-recovery.com/decoder_beta.php

Found ID: 89 88 28 5F

Attachments

[HaQue]

As you aren't really using a LA, the "LINE" name isn't quite right, but call the pads LINE:0 , 3 , 4 & 6.

theoretically, when you ID 89 88 28 5F, you should have it wired correctly. But still not convinced nothing is wrong with the monolith!

24 possible combos:

Code:

(pad)  :     (wire D1, D2, D4, D6 from reader)
LINE:0 : 1 2 4 1 2 4 4 2 6 4 2 6 6 1 4 6 1 4 2 1 6 2 1 6
LINE:3 : 2 1 1 4 4 2 2 4 4 6 6 2 1 6 6 4 4 1 1 2 2 6 6 1
LINE:4 : 4 4 2 2 1 1 6 6 2 2 4 4 4 4 1 1 6 6 6 6 1 1 2 2
LINE:6 : 6 6 6 6 6 6 1 1 1 1 1 1 2 2 2 2 2 2 4 4 4 4 4 4

Theoretically you should be able to keep trying wire combos until ID is 89 88 28 5F. If the actual die is not 89 88 28 5F, then I'm not sure what you can do!

still not convinced nothing is wrong with the monolith though. Also, there could well be a change in pin order on the die, making the pinout different but in physical same locations (switching data lines) like we are seeing on some SD Cards


regarding the capacity conflict.. there could be a CE1 and maybe a RB1 as well somewhere, presenting the second crystal

or it could just be stuffed!