Gary-


First off, thanks for such a quick reply. I really appreciate your
help!


On 7 Dec 04, at 11:15 PM, Gary Thomas wrote:


<excerpt>On Tue, 2004-12-07 at 07:47, Sean Moss-Pultz wrote:

<excerpt>+FLASH: 0x50000000 - 0x51000000, 64 blocks of 0x00040000
bytes each.

FLASH configuration checksum error or invalid key

... Waiting for network card: ..........No network interfaces found


RedBoot(tm) bootstrap and debug environment - built 09:51:53, Jun 22  

2001


Platform: Compaq iPAQ Pocket PC (StrongARM 1110)

Copyright (C) 2000, 2001, Red Hat, Inc.


RAM: 0x00000000-0x02000000, 0x0004f000-0x01fb0000 available

RedBoot>

</excerpt>

Nothing wrong with this - it just means you need to initialize your

FLASH configuration.  Use the "fc -i" command.

</excerpt>

I've tried this and still seem to be running into problems. Here's my
full output:


<color><param>FFFF,0000,0000</param>+FLASH: 0x50000000 - 0x51000000,
64 blocks of 0x00040000 bytes each.

FLASH configuration checksum error or invalid key

... Waiting for network card: ..........No network interfaces found


RedBoot(tm) bootstrap and debug environment - built 09:51:53, Jun 22
2001


Platform: Compaq iPAQ Pocket PC (StrongARM 1110)

Copyright (C) 2000, 2001, Red Hat, Inc.


RAM: 0x00000000-0x02000000, 0x0004f000-0x01fb0000 available

RedBoot> fc -i

Initialize non-volatile configuration - are you sure (y/n)? y

Run script at boot: false

Use BOOTP for network configuration: true

Console baud rate: 38400

GDB connection port: 9000

Network debug at boot time: false

RedBoot></color>


Nothing else happens. I'm a bit confused as to the "Run script at
boot" option. I assume this is a custom script (that I want to run),
not the script to reset the flash. Is this correct? I restarted the
iPAQ after this point and still have that error message.


<excerpt><excerpt>

------------------------------------------------------------------------ 

-----------------------------------------------------

I figured maybe I could proceed so I just entered the first command  

again:


(lo -r -b 0x100000 redboot_ROM.bin)

and here is the output:

------------------------------------------------------------------------ 

-----------------------------------------------------

RedBoot> lo -r -b 0x100000 redboot_ROM.bin

... Erase from 0x00080000-0x00000000:

... Unlock from 0x00040000-0x00093d48: ..

... Erase from 0x00040000-0x00093d48: Err = 200020


    initialization failed 0x00040000: 0x2(Error trying to erase)

... Lock from 0x00040000-0x00093d48: Err = 500050

------------------------------------------------------------------------ 

</excerpt>

This output did not come from that command :-(  Please send the exact

command(s) that you used for us to be able to help.

</excerpt>

This is quite possible. Unfortunately I don't have this now. (I was a
bad installer and didn't take notes. It won't happen again!) 


I tried to run that command again and I get the following now:


<color><param>FFFF,0000,0000</param>RedBoot> lo -r -b 0x100000
redboot_ROM.bin

Can't load 'redboot_ROM.bin': invalid parameter

RedBoot></color>


I have redboot_ROM.bin in both the "My Documents" and the "My Device"
folder (just to be sure). I could have sworn that I ran this very
command yesterday and got the output that I sent you yesterday ...


<excerpt>

Also, did you have this plugged in at the time?  That unit was prone

to FLASH problems if the battery was low.

</excerpt>

I did notice that the device came unplugged while I was messing around
with it this past weekend. I do not believe it was unplugged while I
executed these commands though. 


-Sean