Re: [ECOS] A problem install Redboot in ROM on iPaq H3630

[Gary Thomas <gthomas at cambridge dot redhat dot com>]

On 06-Jun-2001 pradeep wrote:
> Ok I fixed the system clock,
> 

Cool.

> It is very much the same  o/p that  Kent has mailed,
> 
> By power cycling or resetting I am not getting anything on the screen,
> its totally blank, I am not able to get the bootloader prompt on hyper terminal
> 

This doesn't seem to be the same as reported below.  He had trouble writing
anything to the flash (thank goodness!).

I'm afraid that if the screen remains black after a power-cycle, your flash
has been destroyed.  We've been working on exactly this problem recently and
as of this last weekend (sadly just after you tried this), we now have what
we believe is a 100% safe process for installing RedBoot on the iPAQ.

Please refer to the latest install instructions for details.

As for your uncooperative unit, it can be repaired.  If you return it to
Compaq at this address and explain that it needs to be re-flashed, they
will help you out.  Prepaid return postage is suggested as, at least at
this time, they aren't charging for this service.  The address is:
    Compaq Computer Corporation
    Cambridge Research Lab
    iPAQ Valhalla
    One Cambridge Center
    Cambridge, MA 02142

Sorry for the trouble, but this is the best I can offer at this time.

> Please respond
> 
> pradeep
> 
> Gary Thomas wrote:
> 
>> Note: you should consider fixing your system's clock.  It's reporting
>> something like 13 hours in the future.
>>
>> On 07-Jun-2001 Pradeep M wrote:
>> > Hi
>> >
>> > These are the steps  from
>> > http://sources.redhat.com/ecos/docs-latest/redboot/ipaq.htm
>> > these things I  took a printout on 01/jun/01 , these were the
>> > contents on that day.....
>> >
>> > lo -r -b 0x100000 -m xmodem
>> > fi unl -f 0x50000000 -l 0x40000
>> > fis init
>> > fi cr RedBoot -b 0x100000
>> > fi loc -f 0x50000000 -l 0x40000
>>
>> What happened when you ran these steps?  Note that they are not the
>> same as reported by "kent xu <xu_kent@sina.com>" below, but rather
>> the older setup.
>>
>> > reboot
>> >
>> > No I am not able to get back to wince as Reboot
>> > is not coming up .
>>
>> Is anything running at this point?  Have you pressed "reset" or
>> power-cycled the unit?
>>
>> >
>> > Please respond....
>> >
>> > pradeep
>> >
>> >
>> >
>> > ----- Original Message -----
>> > From: Gary Thomas <gthomas@cambridge.redhat.com>
>> > To: Pradeep M <pradeep@ncoretech.com>
>> > Cc: <ecos-discuss@sourceware.cygnus.com>
>> > Sent: Wednesday, June 06, 2001 6:13 PM
>> > Subject: Re: [ECOS] A problem install Redboot in ROM on iPaq H3630
>> >
>> >
>> >>
>> >> On 06-Jun-2001 Pradeep M wrote:
>> >> > Hi all,
>> >> >
>> >> >         I  tried the same steps as  done by kent,
>> >> > but its the same error (I used iPaq H3600)  now I am
>> >> > receiving your mail, now the problem with me is
>> >> > that I am not able to get the redboot prompt on
>> >> > my Hyper Terminal, what can I do ,how to restore it
>> >> >  can any one help me....
>> >>
>> >> Exactly what steps have you taken?
>> >>
>> >> Can you get back to Win/CE and start over?
>> >>
>> >> >
>> >> >
>> >> > pradeep
>> >> >
>> >> >
>> >> >
>> >> > ----- Original Message -----
>> >> > From: Gary Thomas <gthomas@cambridge.redhat.com>
>> >> > To: kent xu <xu_kent@sina.com>
>> >> > Cc: <ecos-discuss@sourceware.cygnus.com>
>> >> > Sent: Wednesday, June 06, 2001 5:49 PM
>> >> > Subject: RE: [ECOS] A problem install Redboot in ROM on iPaq H3630
>> >> >
>> >> >
>> >> >> Oops!  It looks like we forgot to update the redboot_WinCE.bin file on
>> >> >> the web site.
>> >> >>
>> >> >> However, all is not lost.  Simply replace the command:
>> >> >>   fi cr RedBoot -b 0x100000
>> >> >> with
>> >> >>   fi cr RedBoot[backup] -b 0x100000
>> >> >> and continue.
>> >> >>
>> >> >> Also note, the final command is "reset", not "reboot".
>> >> >>
>> >> >> On 06-Jun-2001 kent xu wrote:
>> >> >> > Dear Sir,
>> >> >> >
>> >> >> > When I  install Redboot in ROM on iPaq H3630, can't initialize the
>> >> > FLASH,
>> >> >> > and can't program Redboot into FLASH ROM.
>> >> >> > The error message as following:
>> >> >>
>> >> -----------------------------------------------------------------------
>> >> >> > RedBoot> lo -r -b 0x100000 -m xmodem
>> >> >> > CCRaw file loaded 0x00100000-0x00128a80
>> >> >> > RedBoot> - CRC mode, 1302(SOH)/0(STX)/0(CAN) packets, 4 retries
>> >> >> > RedBoot>
>> >> >> > RedBoot>
>> >> >> > RedBoot> fi loc -f 0x50000000 -l 0x40000
>> >> >> > ... Lock from 0x50000000-0x50040000: .
>> >> >> > RedBoot> fi init
>> >> >> > About to initialize [format] FLASH image system - are you sure (y/n)?
>> > y
>> >> >> > *** Initialize FLASH Image System
>> >> >> >     Warning: device contents not erased, some blocks may not be
>> > usable
>> >> >> > ... Unlock from 0x50fc0000-0x51000000: .
>> >> >> > ... Erase from 0x50fc0000-0x51000000: .
>> >> >> > ... Program from 0x01fb0000-0x01fb0400 at 0x50fc0000: .
>> >> >> > ... Lock from 0x50fc0000-0x51000000: .
>> >> >> > RedBoot> fi unl -f 0x50040000 -l 0x40000
>> >> >> > ... Unlock from 0x50040000-0x50080000: .
>> >> >> > RedBoot> fi cr RedBoot -b 0x100000
>> >> >> > An image named 'RedBoot' exists - are you sure (y/n)? y
>> >> >> > * CAUTION * about to program 'RedBoot'
>> >> >> >             at 0x50000000..0x5003ffff from 0x00100000 - are you sure
>> >> > (y/n)?
>> >> >> > y
>> >> >> > ... Erase from 0x50000000-0x50040000: Err = a200a2
>> >> >> >
>> >> >> > Can't erase region at 0x50000000: 0x2(Error trying to erase)
>> >> >> > ... Unlock from 0x50fc0000-0x51000000: .
>> >> >> > ... Erase from 0x50fc0000-0x51000000: .
>> >> >> > ... Program from 0x01fb0000-0x01ff0000 at 0x50fc0000: .
>> >> >> > ... Lock from 0x50fc0000-0x51000000: .
>> >> >> > RedBoot> fi loc -f 0x50040000 -l 0x40000
>> >> >> > ... Lock from 0x50040000-0x50080000: .
>> >> >> > RedBoot> reboot
>> >> >> > ** Error: Illegal command: "reboot"
>> >> >> > RedBoot>
>> >> >> >
>> >> >>
>> >> >>
>> >>
>> >>