public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Joshua Wise <joshua@joshuawise.com>
To: h2200-port mailing list <h2200-port@handhelds.org>
Cc: linux-mtd@lists.infradead.org
Subject: Bricking and debricking
Date: Sun, 19 Sep 2004 22:15:29 -0400	[thread overview]
Message-ID: <414E3D41.6070507@joshuawise.com> (raw)

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

             reply	other threads:[~2004-09-20  2:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20  2:15 Joshua Wise [this message]
2004-09-20  3:12 ` [H2200-port] Bricking and debricking Joshua Wise

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=414E3D41.6070507@joshuawise.com \
    --to=joshua@joshuawise.com \
    --cc=h2200-port@handhelds.org \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox