This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: 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>
>> >
>>
>>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]