April 8th, 2013, 2:29
April 8th, 2013, 4:46
fzabkar wrote:hhddrec wrote:L1=0,97V
L1=2,79V
about other voltages
Fuse pins to ground = 4,9V
JTAG P1 to ground = 3,22V
I presume the two L1 readings actually refer to L1 and L2. If so, then the 2.79V reading must be the supply for the NAND flash array, and 0.97V must be the Vcore supply for the SandForce controller.
If so, then the JTAG supply must be coming from some other IC, possibly U3 near the SATA power input (or U22).
In any case, 2.79V is too low for the NAND array. My searching suggests that the OCZ M2502128T048AX22 NAND flash parts are rebadged Micron MT29F128G08CFAAAWP chips. These are 3.3V, 128Gb, 16G x 8 parts.
If this measurement is correct, and if my analysis is correct, then the POWR607 chip is probably holding the SF-1222TA3-SBH controller in a reset state.
Can you tell me the markings on U3 and U4?
Could you also measure the resistances of R4, R5, R22, and R23? These will allow us to calculate the correct supply voltages for the "OFA" regulators.
I'm a bit concerned about the "stuff" in the top right corner of the IC. It could be a manufacturing mark (the IC is in-circuit programmable), but I'm not sure.
In any case, 2.79V is too low for the NAND array. My searching suggests that the OCZ M2502128T048AX22 NAND flash parts are rebadged Micron MT29F128G08CFAAAWP chips. These are 3.3V, 128Gb, 16G x 8 parts.
April 8th, 2013, 4:49
BlackST wrote:The problem is in any case elsewhere.
But be real : if one of the flash is broken, if the controller is broken/malfunctioning, and if the circuit is malfunctioning without knowing how it works (and expensive tools) no amount of tinkering will get a a byte out of it. Also, there's encryption to deal with. Good luck.
April 8th, 2013, 5:13
April 8th, 2013, 8:57
hhddrec wrote:BlackST wrote:The problem is in any case elsewhere.
But be real : if one of the flash is broken, if the controller is broken/malfunctioning, and if the circuit is malfunctioning without knowing how it works (and expensive tools) no amount of tinkering will get a a byte out of it. Also, there's encryption to deal with. Good luck.
Thanks BlackST but i think that fzabkar advices are very interesting.
Maybe in this way we can fix SSD problems, and take out data.
But thanks for your comments
April 8th, 2013, 10:04
Just my opinion, I see it everyday. Here the rule is always no money = no data, but when it's no data = little money - just the diagnose fee. That's why I exclude tinkering and guessing.
April 8th, 2013, 16:21
April 9th, 2013, 5:28
If you could measure the voltages on pins #1 and 3, then this should tell us whether the MOSFETs are switched on. Pins #5 - 8 will be the inputs.
It appears that the 3.3V JTAG supply, and the Vcc supply on pins #4 and #21 of the POWR607, may be provided by U3 (9A27). I haven't been able to identify this chip, but I suspect that it may be an LDO regulator. If you could measure the voltages on each of its pins, then that might help to identify it.
The bottom line is that the Vio voltage (2.8V) still doesn't look right, but I'm wondering if that is indeed the correct voltage. One way to determine whether the "OFA" chips are regulating correctly would be to measure the feedback voltages at the junctions of R4 and R5, and R22 and R23. This voltage should be 0.60V.
April 9th, 2013, 7:34
April 9th, 2013, 8:16
fzabkar wrote:You've measured the wrong voltages at U22, but in any case they are OK. I was wanting to see the voltages with respect to SATA ground, not with respect to each other. As you can see, U22 consists of two MOSFETs. Each MOSFET switches Vin to Vout. Vin and Vout are the Vcore and Vio inputs and outputs. If each switch is working correctly, then Vin = Vout.
U3 is indeed an LDO 3.3V regulator. It provides the supply for the POWR607.
The R4/R5 and R23/R22 junction readings are very strange. It's as if the FB (FeedBack) pin were sitting at ground. Are you using SATA ground as your ground reference for measurements? If not, have you been using pin #4 of the "OFA" chips as your ground. If so, then this would explain why Vio is reading approximately 0.6V lower than it should be.
April 9th, 2013, 12:58
April 9th, 2013, 13:21
Randy wrote:hhddrec, do you have another (similar to it) SSD OCZ drive?
If you do, then what voltage for NAND chips it is provide? Can you measure it?
And, what exactly written on U5 chip? Is it SPI flash?
If it is, then, do you have a SPI programmer to read it?
If you do, then it is possible to try to analize a dump from it.
But again, chances to get data are low, it is difficult case.
April 9th, 2013, 14:12
April 9th, 2013, 16:23
April 9th, 2013, 17:08
April 9th, 2013, 18:02
April 10th, 2013, 1:57
April 10th, 2013, 4:03
April 10th, 2013, 6:20
April 10th, 2013, 6:32
hhddrec wrote:Thanks to:
Randy, fzabkar, arvika, BlackST,
I am surprised with your responses, all of them are very smart and interesting, including BlackST responses because I understand you:
Profesionally quick responses are needed, if not, customer get you in troubles, and customers do not accept problems, investigation, tests, and so on. So, with this kind of cases, you don't get positive feedback from customers
But in pro of Knowledge.
It's not a SPI flash IC. Seems it's ATMEL 256 Kbit EEPROM.
Datasheet: http://www.atmel.com/Images/doc8568.pdf
I doubt, that it contains a firmware code. Most likely, it contains some firmware constants, working data, smart data, counters etc. But i may be wrong.
If you'll be able to make a dump, then we can see, what inside. And make suggestions, what it is.
fzabkar has done a good analisys, and i suggest to you first follow his instructions. At least, to make sure, what NAND array is powered with correct voltage.
Even if U5 is just a some kind of configuration storage, because of power failure (if), it may contain now a "garbage".
Make sure also, that U5 is also powered with correct voltage.
Powered by phpBB © phpBB Group.