* Bricking and debricking
@ 2004-09-20 2:15 Joshua Wise
2004-09-20 3:12 ` [H2200-port] " Joshua Wise
0 siblings, 1 reply; 2+ messages in thread
From: Joshua Wise @ 2004-09-20 2:15 UTC (permalink / raw)
To: h2200-port mailing list; +Cc: linux-mtd
Okay, so, good news and bad news.
Good news first: I can successfully brick an iPAQ.
wiseguy586@bluefire /mnt/raid/iPAQ/linux/debrick/hamcop $ ./hamcop -b
Found HAMCOP on h2210
Now bricking...
Successfully bricked your iPAQ. Enjoy your new doorstop.
wiseguy586@bluefire /mnt/raid/iPAQ/linux/debrick/hamcop $
-b (Brick) erases the first sector of flash. You must first brick before
you can unbrick. (Actually, this is a bit strange. I expected -b to
erase the first 16k of flash, although it only erased the first 528 bytes.)
Bad news second: I can't quite seem to unbrick it.
There's code in CVS to send what should be the write commands, but it
seems to write only 0x00. Oddly enough, it seems to be consistent with
the number of bytes I send (i.e., if I send 256 bytes, I get 256 0s and
the rest FF, if I send 512, I get 512 0s, and if I send 528 bytes, I get
all 0s), but the data just isn't there. The flash part reports that all
went okay with the program, so there might be a problem with actually
transporting the data to the device over JTAG.
Thoughts? CC'ing to mtd list too.
joshua
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [H2200-port] Bricking and debricking
2004-09-20 2:15 Bricking and debricking Joshua Wise
@ 2004-09-20 3:12 ` Joshua Wise
0 siblings, 0 replies; 2+ messages in thread
From: Joshua Wise @ 2004-09-20 3:12 UTC (permalink / raw)
To: Joshua Wise; +Cc: linux-mtd, h2200-port mailing list
> There's code in CVS to send what should be the write commands, but it
> seems to write only 0x00. Oddly enough, it seems to be consistent with
> the number of bytes I send (i.e., if I send 256 bytes, I get 256 0s and
> the rest FF, if I send 512, I get 512 0s, and if I send 528 bytes, I get
> all 0s), but the data just isn't there. The flash part reports that all
> went okay with the program, so there might be a problem with actually
> transporting the data to the device over JTAG.
Ugh. Sorry, d'oh. I was loading the byte to program into the input chain
instead of the output chain. Problem solved.
joshua
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-09-20 3:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-20 2:15 Bricking and debricking Joshua Wise
2004-09-20 3:12 ` [H2200-port] " Joshua Wise
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox