* RE: [ECOS] FLASH configuration checksum error
@ 2001-09-25 8:23 Warren Jasper
2001-09-25 16:06 ` Gary Thomas
0 siblings, 1 reply; 12+ messages in thread
From: Warren Jasper @ 2001-09-25 8:23 UTC (permalink / raw)
To: 'Gary Thomas'; +Cc: 'eCos Discussion'
In that case, there will always be a checksum error on the RedBoot monitor
when loading redboot.bin. I guess I could always load it to RAM and then
save it
into ROM with fis create ...
-----Original Message-----
From: Gary Thomas [ mailto:gthomas@redhat.com ]
Sent: Monday, September 24, 2001 6:04 PM
To: Jonathan Larmour
Cc: Warren Jasper; 'eCos Discussion'
Subject: Re: [ECOS] FLASH configuration checksum error
On Mon, 2001-09-24 at 23:53, Jonathan Larmour wrote:
> Warren Jasper wrote:
> >
> > I don't think that's it. I looked at the code, and it has
> > the correct ending block. However, when I do a
> >
> > fis list -c
> > Name Flash addr Checksum Length Entry point
> > RedBoot 0x08000000 0x00000000 0x00040000 0x00000000
> > RedBoot[backup] 0x08040000 0x00000000 0x00040000 0x00000000
> > RedBoot config 0x07870000 0x00000000 0x00010000 0x00000000
> > FIS directory 0x087C0000 0x00000000 0x00040000 0x00000000
> >
> > Why are all the checksum entries zero? How do I set them?
>
> They're meant to be set automatically when the config is written. UTSL.
Actually, they are only set when a file/image is written ('fis create').
Building the directory ('fis init') will set them to zero.
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: [ECOS] FLASH configuration checksum error
2001-09-25 8:23 [ECOS] FLASH configuration checksum error Warren Jasper
@ 2001-09-25 16:06 ` Gary Thomas
0 siblings, 0 replies; 12+ messages in thread
From: Gary Thomas @ 2001-09-25 16:06 UTC (permalink / raw)
To: Warren Jasper; +Cc: 'eCos Discussion'
On Wed, 2001-09-26 at 00:23, Warren Jasper wrote:
>
>
> In that case, there will always be a checksum error on the RedBoot monitor
> when loading redboot.bin. I guess I could always load it to RAM and then
> save it
> into ROM with fis create ...
>
Actually if the stored CRC is zero, no checks are made.
> -----Original Message-----
> From: Gary Thomas [ mailto:gthomas@redhat.com ]
> Sent: Monday, September 24, 2001 6:04 PM
> To: Jonathan Larmour
> Cc: Warren Jasper; 'eCos Discussion'
> Subject: Re: [ECOS] FLASH configuration checksum error
>
>
> On Mon, 2001-09-24 at 23:53, Jonathan Larmour wrote:
> > Warren Jasper wrote:
> > >
> > > I don't think that's it. I looked at the code, and it has
> > > the correct ending block. However, when I do a
> > >
> > > fis list -c
> > > Name Flash addr Checksum Length Entry point
> > > RedBoot 0x08000000 0x00000000 0x00040000 0x00000000
> > > RedBoot[backup] 0x08040000 0x00000000 0x00040000 0x00000000
> > > RedBoot config 0x07870000 0x00000000 0x00010000 0x00000000
> > > FIS directory 0x087C0000 0x00000000 0x00040000 0x00000000
> > >
> > > Why are all the checksum entries zero? How do I set them?
> >
> > They're meant to be set automatically when the config is written. UTSL.
>
> Actually, they are only set when a file/image is written ('fis create').
> Building the directory ('fis init') will set them to zero.
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: [ECOS] FLASH configuration checksum error
2001-09-26 5:12 Warren Jasper
2001-09-26 5:30 ` Mark Salter
@ 2001-09-26 18:15 ` Gary Thomas
1 sibling, 0 replies; 12+ messages in thread
From: Gary Thomas @ 2001-09-26 18:15 UTC (permalink / raw)
To: Warren Jasper; +Cc: 'eCos Discussion'
On Wed, 2001-09-26 at 21:12, Warren Jasper wrote:
>
> If that is the case, why do I always get the message:
>
> FLASH configuration checksum error or invalid key
>
> How do I turn that message off (besides commenting it out of the code)?
>
This message simply says that the 'fconfig' database is not setup
correctly. Running 'fconfig' and making some change which will cause
the database to be written to FLASH should fix it.
>
> -----Original Message-----
> From: Gary Thomas [ mailto:gthomas@redhat.com ]
> Sent: Tuesday, September 25, 2001 7:03 PM
> To: Warren Jasper
> Cc: 'eCos Discussion'
> Subject: RE: [ECOS] FLASH configuration checksum error
>
>
> On Wed, 2001-09-26 at 00:23, Warren Jasper wrote:
> >
> >
> > In that case, there will always be a checksum error on the RedBoot monitor
>
> > when loading redboot.bin. I guess I could always load it to RAM and then
> > save it
> > into ROM with fis create ...
> >
>
> Actually if the stored CRC is zero, no checks are made.
>
> > -----Original Message-----
> > From: Gary Thomas [ mailto:gthomas@redhat.com ]
> > Sent: Monday, September 24, 2001 6:04 PM
> > To: Jonathan Larmour
> > Cc: Warren Jasper; 'eCos Discussion'
> > Subject: Re: [ECOS] FLASH configuration checksum error
> >
> >
> > On Mon, 2001-09-24 at 23:53, Jonathan Larmour wrote:
> > > Warren Jasper wrote:
> > > >
> > > > I don't think that's it. I looked at the code, and it has
> > > > the correct ending block. However, when I do a
> > > >
> > > > fis list -c
> > > > Name Flash addr Checksum Length Entry point
> > > > RedBoot 0x08000000 0x00000000 0x00040000 0x00000000
> > > > RedBoot[backup] 0x08040000 0x00000000 0x00040000 0x00000000
> > > > RedBoot config 0x07870000 0x00000000 0x00010000 0x00000000
> > > > FIS directory 0x087C0000 0x00000000 0x00040000 0x00000000
> > > >
> > > > Why are all the checksum entries zero? How do I set them?
> > >
> > > They're meant to be set automatically when the config is written. UTSL.
> >
> > Actually, they are only set when a file/image is written ('fis create').
> > Building the directory ('fis init') will set them to zero.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] FLASH configuration checksum error
2001-09-26 5:12 Warren Jasper
@ 2001-09-26 5:30 ` Mark Salter
2001-09-26 18:15 ` Gary Thomas
1 sibling, 0 replies; 12+ messages in thread
From: Mark Salter @ 2001-09-26 5:30 UTC (permalink / raw)
To: Warren.Jasper; +Cc: gthomas, ecos-discuss
>>>>> Warren Jasper writes:
> If that is the case, why do I always get the message:
> FLASH configuration checksum error or invalid key
> How do I turn that message off (besides commenting it out of the code)?
According to the RedBoot manual, running 'fconfig' should get rid
of it.
--Mark
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: [ECOS] FLASH configuration checksum error
@ 2001-09-26 5:12 Warren Jasper
2001-09-26 5:30 ` Mark Salter
2001-09-26 18:15 ` Gary Thomas
0 siblings, 2 replies; 12+ messages in thread
From: Warren Jasper @ 2001-09-26 5:12 UTC (permalink / raw)
To: 'Gary Thomas'; +Cc: 'eCos Discussion'
If that is the case, why do I always get the message:
FLASH configuration checksum error or invalid key
How do I turn that message off (besides commenting it out of the code)?
-----Original Message-----
From: Gary Thomas [ mailto:gthomas@redhat.com ]
Sent: Tuesday, September 25, 2001 7:03 PM
To: Warren Jasper
Cc: 'eCos Discussion'
Subject: RE: [ECOS] FLASH configuration checksum error
On Wed, 2001-09-26 at 00:23, Warren Jasper wrote:
>
>
> In that case, there will always be a checksum error on the RedBoot monitor
> when loading redboot.bin. I guess I could always load it to RAM and then
> save it
> into ROM with fis create ...
>
Actually if the stored CRC is zero, no checks are made.
> -----Original Message-----
> From: Gary Thomas [ mailto:gthomas@redhat.com ]
> Sent: Monday, September 24, 2001 6:04 PM
> To: Jonathan Larmour
> Cc: Warren Jasper; 'eCos Discussion'
> Subject: Re: [ECOS] FLASH configuration checksum error
>
>
> On Mon, 2001-09-24 at 23:53, Jonathan Larmour wrote:
> > Warren Jasper wrote:
> > >
> > > I don't think that's it. I looked at the code, and it has
> > > the correct ending block. However, when I do a
> > >
> > > fis list -c
> > > Name Flash addr Checksum Length Entry point
> > > RedBoot 0x08000000 0x00000000 0x00040000 0x00000000
> > > RedBoot[backup] 0x08040000 0x00000000 0x00040000 0x00000000
> > > RedBoot config 0x07870000 0x00000000 0x00010000 0x00000000
> > > FIS directory 0x087C0000 0x00000000 0x00040000 0x00000000
> > >
> > > Why are all the checksum entries zero? How do I set them?
> >
> > They're meant to be set automatically when the config is written. UTSL.
>
> Actually, they are only set when a file/image is written ('fis create').
> Building the directory ('fis init') will set them to zero.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] FLASH configuration checksum error
2001-09-24 7:53 ` Jonathan Larmour
@ 2001-09-24 15:07 ` Gary Thomas
0 siblings, 0 replies; 12+ messages in thread
From: Gary Thomas @ 2001-09-24 15:07 UTC (permalink / raw)
To: Jonathan Larmour; +Cc: Warren Jasper, 'eCos Discussion'
On Mon, 2001-09-24 at 23:53, Jonathan Larmour wrote:
> Warren Jasper wrote:
> >
> > I don't think that's it. I looked at the code, and it has
> > the correct ending block. However, when I do a
> >
> > fis list -c
> > Name Flash addr Checksum Length Entry point
> > RedBoot 0x08000000 0x00000000 0x00040000 0x00000000
> > RedBoot[backup] 0x08040000 0x00000000 0x00040000 0x00000000
> > RedBoot config 0x07870000 0x00000000 0x00010000 0x00000000
> > FIS directory 0x087C0000 0x00000000 0x00040000 0x00000000
> >
> > Why are all the checksum entries zero? How do I set them?
>
> They're meant to be set automatically when the config is written. UTSL.
Actually, they are only set when a file/image is written ('fis create').
Building the directory ('fis init') will set them to zero.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] FLASH configuration checksum error
2001-09-24 7:43 Warren Jasper
@ 2001-09-24 7:53 ` Jonathan Larmour
2001-09-24 15:07 ` Gary Thomas
0 siblings, 1 reply; 12+ messages in thread
From: Jonathan Larmour @ 2001-09-24 7:53 UTC (permalink / raw)
To: Warren Jasper; +Cc: 'eCos Discussion'
Warren Jasper wrote:
>
> I don't think that's it. I looked at the code, and it has
> the correct ending block. However, when I do a
>
> fis list -c
> Name Flash addr Checksum Length Entry point
> RedBoot 0x08000000 0x00000000 0x00040000 0x00000000
> RedBoot[backup] 0x08040000 0x00000000 0x00040000 0x00000000
> RedBoot config 0x07870000 0x00000000 0x00010000 0x00000000
> FIS directory 0x087C0000 0x00000000 0x00040000 0x00000000
>
> Why are all the checksum entries zero? How do I set them?
They're meant to be set automatically when the config is written. UTSL.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: [ECOS] FLASH configuration checksum error
@ 2001-09-24 7:43 Warren Jasper
2001-09-24 7:53 ` Jonathan Larmour
0 siblings, 1 reply; 12+ messages in thread
From: Warren Jasper @ 2001-09-24 7:43 UTC (permalink / raw)
To: 'Jonathan Larmour'; +Cc: 'eCos Discussion'
I don't think that's it. I looked at the code, and it has
the correct ending block. However, when I do a
fis list -c
Name Flash addr Checksum Length Entry point
RedBoot 0x08000000 0x00000000 0x00040000 0x00000000
RedBoot[backup] 0x08040000 0x00000000 0x00040000 0x00000000
RedBoot config 0x07870000 0x00000000 0x00010000 0x00000000
FIS directory 0x087C0000 0x00000000 0x00040000 0x00000000
Why are all the checksum entries zero? How do I set them?
-----Original Message-----
From: Jonathan Larmour [ mailto:jlarmour@redhat.com ]
Sent: Friday, September 21, 2001 4:48 PM
To: Warren Jasper
Cc: 'eCos Discussion'
Subject: Re: [ECOS] FLASH configuration checksum error
Warren Jasper wrote:
>
> When you say near the end of flash, is that the end that it thinks it is
> (ie 0x9000000) or where I told it it was (0x08800000).
I'm saying that it may have gotten confused and want to put it at
0x9000000-2*blocksize rather than 0x8800000-2*blocksize. It would be a bug
yes, but that's my theory.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] FLASH configuration checksum error
2001-09-21 13:45 Warren Jasper
@ 2001-09-21 13:48 ` Jonathan Larmour
0 siblings, 0 replies; 12+ messages in thread
From: Jonathan Larmour @ 2001-09-21 13:48 UTC (permalink / raw)
To: Warren Jasper; +Cc: 'eCos Discussion'
Warren Jasper wrote:
>
> When you say near the end of flash, is that the end that it thinks it is
> (ie 0x9000000) or where I told it it was (0x08800000).
I'm saying that it may have gotten confused and want to put it at
0x9000000-2*blocksize rather than 0x8800000-2*blocksize. It would be a bug
yes, but that's my theory.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: [ECOS] FLASH configuration checksum error
@ 2001-09-21 13:45 Warren Jasper
2001-09-21 13:48 ` Jonathan Larmour
0 siblings, 1 reply; 12+ messages in thread
From: Warren Jasper @ 2001-09-21 13:45 UTC (permalink / raw)
To: 'Jonathan Larmour'; +Cc: 'eCos Discussion'
When you say near the end of flash, is that the end that it thinks it is
(ie 0x9000000) or where I told it it was (0x08800000).
When I do a fis list, I don't see the configuration block only
the FIS directory at 0x087C0000 of length 0x00040000.
-----Original Message-----
From: Jonathan Larmour [ mailto:jlarmour@redhat.com ]
Sent: Friday, September 21, 2001 3:38 PM
To: Warren Jasper
Cc: 'eCos Discussion'
Subject: Re: [ECOS] FLASH configuration checksum error
Warren Jasper wrote:
>
> I am using a StrongARM SA1110 CPU with tow (2) 28F640J3A Flash
> chips. I think the hardware for our development board is
> not addressing the chip correctly, since I can only see
> half of the FLASH. To fix this problem, I set CYGNUM_FLASH_BASE_MASK =
> 0xFF800000
> instead of 0xFE000000. This works great. I get the following messages:
>
> FLASH: Oversized device! End addr 0x09000000 changed to 0x08800000
> FLASH configuration checksum error or invalid key
>
> RAM: 0x00000000-0x01000000, 0x0000dc88-00fbf000 available
> FLASH: 0x08000000 - 0x08800000, 32 blocks of 0x00040000 bytes each.
>
> Which is correct since I can only see half of the flash. My question is
> how to get rid of the line
>
> FLASH configuration checksum error or invalid key
>
> I tried to run flconfig -i but that does not get rid of the problem.
>
> Any suggestions? I could ignore it, but I wanted to know how to set the
> checksum correctly.
The flash configuration block is set near the end of flash. There's
probably something in the code which is still trying to write to the half
of the flash you don't have.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] FLASH configuration checksum error
2001-09-21 7:10 Warren Jasper
@ 2001-09-21 12:38 ` Jonathan Larmour
0 siblings, 0 replies; 12+ messages in thread
From: Jonathan Larmour @ 2001-09-21 12:38 UTC (permalink / raw)
To: Warren Jasper; +Cc: 'eCos Discussion'
Warren Jasper wrote:
>
> I am using a StrongARM SA1110 CPU with tow (2) 28F640J3A Flash
> chips. I think the hardware for our development board is
> not addressing the chip correctly, since I can only see
> half of the FLASH. To fix this problem, I set CYGNUM_FLASH_BASE_MASK =
> 0xFF800000
> instead of 0xFE000000. This works great. I get the following messages:
>
> FLASH: Oversized device! End addr 0x09000000 changed to 0x08800000
> FLASH configuration checksum error or invalid key
>
> RAM: 0x00000000-0x01000000, 0x0000dc88-00fbf000 available
> FLASH: 0x08000000 - 0x08800000, 32 blocks of 0x00040000 bytes each.
>
> Which is correct since I can only see half of the flash. My question is
> how to get rid of the line
>
> FLASH configuration checksum error or invalid key
>
> I tried to run flconfig -i but that does not get rid of the problem.
>
> Any suggestions? I could ignore it, but I wanted to know how to set the
> checksum correctly.
The flash configuration block is set near the end of flash. There's
probably something in the code which is still trying to write to the half
of the flash you don't have.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
^ permalink raw reply [flat|nested] 12+ messages in thread
* [ECOS] FLASH configuration checksum error
@ 2001-09-21 7:10 Warren Jasper
2001-09-21 12:38 ` Jonathan Larmour
0 siblings, 1 reply; 12+ messages in thread
From: Warren Jasper @ 2001-09-21 7:10 UTC (permalink / raw)
To: 'eCos Discussion'
I am using a StrongARM SA1110 CPU with tow (2) 28F640J3A Flash
chips. I think the hardware for our development board is
not addressing the chip correctly, since I can only see
half of the FLASH. To fix this problem, I set CYGNUM_FLASH_BASE_MASK =
0xFF800000
instead of 0xFE000000. This works great. I get the following messages:
FLASH: Oversized device! End addr 0x09000000 changed to 0x08800000
FLASH configuration checksum error or invalid key
RAM: 0x00000000-0x01000000, 0x0000dc88-00fbf000 available
FLASH: 0x08000000 - 0x08800000, 32 blocks of 0x00040000 bytes each.
Which is correct since I can only see half of the flash. My question is
how to get rid of the line
FLASH configuration checksum error or invalid key
I tried to run flconfig -i but that does not get rid of the problem.
Any suggestions? I could ignore it, but I wanted to know how to set the
checksum correctly.
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2001-09-26 18:15 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-09-25 8:23 [ECOS] FLASH configuration checksum error Warren Jasper
2001-09-25 16:06 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2001-09-26 5:12 Warren Jasper
2001-09-26 5:30 ` Mark Salter
2001-09-26 18:15 ` Gary Thomas
2001-09-24 7:43 Warren Jasper
2001-09-24 7:53 ` Jonathan Larmour
2001-09-24 15:07 ` Gary Thomas
2001-09-21 13:45 Warren Jasper
2001-09-21 13:48 ` Jonathan Larmour
2001-09-21 7:10 Warren Jasper
2001-09-21 12:38 ` Jonathan Larmour
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).