This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Hosed ipaq
- To: Nick Clarey <nclarey at 3glab dot com>
- Subject: RE: [ECOS] Hosed ipaq
- From: Gary Thomas <gthomas at cambridge dot redhat dot com>
- Date: Fri, 15 Jun 2001 05:17:37 -0600 (MDT)
- Cc: ecos-discuss at sourceware dot cygnus dot com
- Organization: Red Hat, Inc.
I'm afraid that your iPAQ will have to be reflashed. Send it (and return
postage please) to:
Compaq Computer Corporation
Cambridge Research Lab
iPAQ Valhalla
One Cambridge Center
Cambridge, MA 02142
****************************************************************************
****************************************************************************
** **
** A T T E N T I O N ! ! **
** **
** Installing RedBoot on the iPAQ can be dangerous in that the unit may **
** be turned into a "brick" if not done correctly. We have developed a **
** procedure which allows RedBoot to be installed safely, but it must **
** be followed exactly. **
** **
** Attempting to install RedBoot by any other means (i.e. not following **
** the current, published instructions) has a high likelyhood of failure. **
** We (the eCos team) cannot be responsible if your iPAQ is rendered **
** [temporarily] inopperative by such attempts to install RedBoot. **
** **
****************************************************************************
****************************************************************************
I wish I could say this louder, write it bigger, make it stronger, etc.
We want you to use (or at least test) RedBoot on the iPAQ, but the
instructions have to be followed. Anything less is simply asking for
trouble.
****************************************************************************
****************************************************************************
On 15-Jun-2001 Nick Clarey wrote:
> Howdy all,
>
> This is a bit complicated, but I'll try to make the situation reasonably
> clear :->
>
> 1) Compaq Ipaq, old compaq bootloader at 0x0, works fine
>
> 2) Flashed an old RedBoot image into 0x00100000, jumped to it, worked
> fine.
>
> 3) Loaded a current RedBoot RAM image into RAM at 0x00100000 (virtual),
> jumped to it, worked fine.
>
> 4) Created a current RedBoot ROM image, flashed it into ROM at 0x50200000
> (virtual) as a test, checked the first couple of bytes, looked like it had
> worked ok.
>
> 5) Flashed image from (4) into ROM at 0x50100000 (virtual), because the
> old RedBoot image had swapped 0x50000000 and 0x50100000 (virtual) around
> (so said physaddr). Physaddr reports that 0x50100000 virtual == 0x00000000
> physical, so that ought to mean that I now have the RedBoot ROM image
> living at 0x0 physical.
>
> 6) Hit the reset button. <cricket> <cricket>
>
> 7) Opened up minicom. Junk on screen. Figure that these are <phew> GDB
> stubs, point GDB at them, connect okay.
>
> 8) Take the RAM image and try to load it and cont it, see if it'll give me
> RedBoot back. No dice; I get some "program no longer exists" message and a
> SIGKILL. Figure that the MMU hasn't been set up and that GDB is trying to
> load the image into flash, which isn't working.
>
> 9) Roll a RAM image with base address 0xc0100000 in the hopes that it will
> like it better there. Load it up, correct base address, try to cont it,
> and no dice, same message about program no longer existing, SIGKILL.
>
> 10) Figure I'll try a RAM image with base address 0xc0000000, in the hopes
> that it will work better. No dice. In fact, this time I get some bad
> packets in gdb while trying to load. Hairs on the back of my neck stand
> up. GDB stops communicating.
>
> 11) Hit the reset button, figuring that flash will still be okay. Nothing.
> Not even GDB stubs. <sob>
>
> Is my iPAQ toast? Or is there some hope of redemption?
>
> Help.
>
> See ya,
>
> Nick
>
> --
> Nick Clarey, System Architect | "Sometimes when you fill a vacuum,
> 3G LAB | it still sucks." - Rob Pike
> ph 44-1223-478900 fax 44-1223-478901 |