OCZ Vertex 2 (AKA paperweight)

[Zorb]

I have a Vertex 2 60GB that just came in. Thermal image looks normal. Power usage is normal for idle.

Drive doesn't identify at all. Green power light is on, red Fault light is on, blue Activity light is not on. My research suggests that it might be a controller lockup issue.

My last experience with OCZ was a Solid2 drive that was solved by shorting the data legs of the serial EEPROM/flash chip and, powering it on, and then removing the short after a couple of minutes. That isn't working here.

Anyone have any suggestions?

Customer doesn't want to put much more than a couple hundred dollars into it. I'm into it for the learning experience at this point. If it wastes 7 or 8 hours of my time, so be it. They literally told me to throw it in the garbage if I want to if I can't solve it easily.

[Zorb]

In case it gives some ideas:

Bottom of PCB: https://drive.google.com/open?id=1oU5m2 ... kPgHi0ru6Y

Top of PCB: https://drive.google.com/open?id=1I8SbP ... km2l0lPpc9

The drive outputs data at 115kbps via serial port when started, and it turns into a string of failure messages if EEPROM fata is shorted.

[Zorb]

Here's the serial output dump..Most of it's garbage. If I delete the "▒" characters, I get this, which starts to be more intelligible, with some readable strings:

CLI> PINRST
*** ROM 106 Mar 12 2009 20:29:35 ***
FW_SRC 0 SHA PASS!
*** EEPROM 202 Apr 30 2010 16:53:54 BuildServer:FW_Common_Critical_Fixes:FW_Common_Build_Release-247324 ***
Micron Timing EPch
*** Patch 1.4.1 Oct 26 2010 16:51:37 BuildServer:RC_3_4_0_MP3_again:P1_3_4_3_MP3_Patch1_snapshot2-278118 ***
Micron Timing EPch
RCPch SAK0
d$dTdޛwiRЌ
33&6
|h?H
5
ގp2

޴:w g
??y`?l?3\
Xg
ބggf>
Xg
ބgg f> B
Xg
XgބggBf>Bcy9
ބggB f>B q5ddTdޛkWd@MZUGd(d`d}Pkތ`@ ހ]_[ddTdeʝO޴@Jd8dTd!!
ސ޿d(d`dPkތ`@(j$ddTdaE`OTO@.]dd`dǩ @1.25ދdd`d .zXc~d(d`d
4\Pkތ`@
8
6_ ddTd
ܕ!O@4Ŏ"d(d`d
w0%O@,3&d(d`d޴YdTd
'HoH@ޓ@U]<(d(d`d`[)oH@ v?j2*d(d`dT|+Pkތ`@
8
▒ީR,ddTdk-OX@ӟ.d(d`d$"/Pk]@ޤP0dd`dE"1hJ{2J
3J
߻O4J

h{5d(d`dR6Pk]@
޶7
p?l@S8dd`d▒ޭ$9(:d`dt
;0?ހ= $1▒ް?+>d(d`d.b?Pk^@ޤ-@dd`dT+Ap
##(޾cbBd(d`dޢCPk6^@
ޤoB.D
0?l@ՠeOEdd`dޗFF(Nq?Gd`dވ/,
H0?#ހ#J d
$1▒ް?
5Kd(d`dL+LPk^@ޤ/~Mdd`dwB}FNp
##▒ެ(υA-Od(d`d %WbPPk6^@
Q ޤ~
0p?lޠ? @%ӜRdd`d!ޔS(އdTd`d"'1"
U0?ހ#Vd\d#-6KW?+.Xd`d$޷CY@(޼?<ьZd`d%ޏ%k[@o?Kp\d`d&5K]@ސ޼?ݙ^d`d't:_@ކ޼?/`d`d(
a@,޼?bd`d)2c@s޼?gdd`d*zpe@޼?vEfd`d+B1ug@޼?գhd`d,rni@ދ?qh 2jd`d-ҷFk@O޼?Eld`d.ޚt?m@|޼?nd`d/ޢ5o@?dpd`d0q@G޼? crd`d1,{(s@ޅ޼?Otd`d2d(Qu@޼?tvd`d3\iyw@/޼?=nxd`d4ȣy@]޼?Ghzd} d5$1▒ް?X6V~dd`d7G/
xt@<Jހ`7dd`d8)
xޡރSdd`d9f\
txކ;dd`d:{
ވ޽<:d(d`d;WAފPk_@#Иd(d`d<޳_ތPk_@
8
e%d(d`d=pTpBގHoޜ@
vސ I&d(d`d?bgdޒoޜ@`
QFLj
.clistrings0mޕL
-▒ްELF^LyE0
.clistrings11tޘL
.fELF^cLL@".symtabYޛL
0x▒ްELF^dL_#o?.strtabޟޞL
1()}ELF^lL
`()
}ELF^ .dump.elfDӉޡL
ޥwELF^4KddXd@޿>[ޣl▒ުUeSddXdA|5<ޥllPX▒ަL
ސ$?ELF^▒ާN
Nޥ@?X@?=
@
_1tran: $Z278118 d!-
A▒ެM
Э`?ޥ@?ހ}▒ޭM

h`?ޥ@?ހֈ▒ޮM
3NMޥ@?ހf{▒ޯ
N
M(ޥ@?ހm]2d(d`dBJ( ޱHoހ@
ޡ@pdd`dC޳޵Ѻdd`dD"
޵ș1.25 Ddd`dE.

޷+Bdd`dFn_
޹ 8=\dd`dG錴w
޻`7IAFAh-dd`dH
D޽7޶dd`dI!l޿7I▒ޫdIndd`dJޕj7AA9Tdd`dK▒ޭR}B7Fxdd`dL޲q8}
AFAޤMp
AFAޤ(AKd`dMBns,<
Pdd`dN(1Yޒ7dd`dOjwŏLzdd`dPLޏr{dd\dQWgކӟd(d`dR▒ޭ`T Foތ@@brd(d`dSnk3 oތ@vB>8d(d`dTފu oހ@
IddTdUFN&od(d`dVMd=Pkތ`@(`EddTdWr?FO@yd(d`dXޅY_Pkތ`@|▒ޫddTd[zO<@d(d`d\4Pkތ`@B&ddTd]_:O
@zd(d`d^%Pk@޼▒ޮNsd(d`d_.Pk5@;Id(d`d`yPka@c@CRSTF@0c1
C??ހp?SSސ?q`W9d(d`da0oPk@
WdTdb]0
޾H

#
9c
ކg2
ޜI▒ޮ
▒ެ&E%$8&dd0d`dc▒ިE0d
#XNJd0d`ddL[=\#9BT
|?SSސ?d0d`deޓ d
'Tf
<
cg)m6d
fqd(d`df~]Pka@;Y

Assuming this is a panic lock situation, where does that lockup exist? Is it somewhere in the linear flash/eeprom chip, or is it actually something "flagged" somehow on the main NAND?

[HaQue]

looks like Baud rate changes shortly after bootup

[Zorb]

looks like Baud rate changes shortly after bootup

Nope. There's still intelligible text in there. I have tried two interfaces, one of which can automatically synchronize data rates.

115200 N 8 1.