[ECOS] change to flash_v2 tree problem

public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed

* [ECOS] change to flash_v2 tree problem
@ 2005-06-29  7:15 Manfred Gruber
  2005-06-29  9:56 ` Andrew Lunn
  0 siblings, 1 reply; 6+ messages in thread
From: Manfred Gruber @ 2005-06-29  7:15 UTC (permalink / raw)
  To: ecos-discuss

Hi !

I changed my ecos 2_0 tree to flash_v2 tree for use am29xxxxx_v2 later.

Now I try to get it working with am29xxxxx, redboot boots but i get an error 
on fconfig -i, also on on startup:

.. Read from 0x13fff000-0x13ffffff to 0x07fdf000:                                                                                                                                                              
**Warning** FLASH configuration checksum error or invalid key                                                                                                                                                   
Use 'fconfig -i' to [re]initialize database

 than it hangs, when i commit out config_init it boots but on fconfig -i I 
get: 

RedBoot> fconfig -i                                                                                                                                                                                             
Initialize non-volatile configuration - continue (y/n)? y                                                                                                                                                       
** command abort - illegal memory access?

I think I missed something on flash configuration: on the old ecos 2_0
I got: FLASH: 0x10000000 - 0x14000000, 512 blocks of 0x00020000 bytes each.
Now I get: FLASH: 0x10000000 - 0x13ffffff 512 x 0x20000 blocks 

The strange thing is that fis init works. but fconfig -i not. Has someone an 
idea? Maybe there is a problem on flash size on the last block or 
something...

I think it was wrong to take the memory layout files from ecos 2_0 for my 
target, did I there miss something... how do i make the memory layout files 
new ?

thanks for any help regards manfred

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [ECOS] change to flash_v2 tree problem
  2005-06-29  7:15 [ECOS] change to flash_v2 tree problem Manfred Gruber
@ 2005-06-29  9:56 ` Andrew Lunn
  2005-06-29 10:30   ` Manfred Gruber
  0 siblings, 1 reply; 6+ messages in thread
From: Andrew Lunn @ 2005-06-29  9:56 UTC (permalink / raw)
  To: Manfred Gruber; +Cc: ecos-discuss

On Wed, Jun 29, 2005 at 09:15:06AM +0200, Manfred Gruber wrote:
> Hi !
> 
> I changed my ecos 2_0 tree to flash_v2 tree for use am29xxxxx_v2 later.
> 
> Now I try to get it working with am29xxxxx, redboot boots but i get an error 
> on fconfig -i, also on on startup:
> 
> .. Read from 0x13fff000-0x13ffffff to 0x07fdf000:                                                                                                                                                              
> **Warning** FLASH configuration checksum error or invalid key                                                                                                                                                   
> Use 'fconfig -i' to [re]initialize database
> 
>  than it hangs, when i commit out config_init it boots but on fconfig -i I 
> get: 
> 
> RedBoot> fconfig -i                                                                                                                                                                                             
> Initialize non-volatile configuration - continue (y/n)? y                                                                                                                                                       
> ** command abort - illegal memory access?
> 
> I think I missed something on flash configuration: on the old ecos 2_0
> I got: FLASH: 0x10000000 - 0x14000000, 512 blocks of 0x00020000 bytes each.
> Now I get: FLASH: 0x10000000 - 0x13ffffff 512 x 0x20000 blocks 
 
These are equivelent. I changed the end address to be the real end
address, not the end address plus 1.

> The strange thing is that fis init works. but fconfig -i not. Has someone an 
> idea? Maybe there is a problem on flash size on the last block or 
> something...

Does you have two block in use, one for fis and one for config or is
it a shared block?

Could you do some more debugging. Which function is causing the
illegal memory access. Is it the cyg_flash_write()? What addresses are
passed?

> I think it was wrong to take the memory layout files from ecos 2_0 for my 
> target, did I there miss something... how do i make the memory layout files 
> new ?

They should be OK as far as i know.

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [ECOS] change to flash_v2 tree problem
  2005-06-29  9:56 ` Andrew Lunn
@ 2005-06-29 10:30   ` Manfred Gruber
  2005-06-29 11:00     ` Andrew Lunn
  2005-06-29 11:06     ` Manfred Gruber
  0 siblings, 2 replies; 6+ messages in thread
From: Manfred Gruber @ 2005-06-29 10:30 UTC (permalink / raw)
  To: ecos-discuss

Am Mittwoch, 29. Juni 2005 11:56 schrieb Andrew Lunn:
> > I think I missed something on flash configuration: on the old ecos 2_0
> > I got: FLASH: 0x10000000 - 0x14000000, 512 blocks of 0x00020000 bytes
> > each. Now I get: FLASH: 0x10000000 - 0x13ffffff 512 x 0x20000 blocks
>
> These are equivelent. I changed the end address to be the real end
> address, not the end address plus 1.

OK

> > The strange thing is that fis init works. but fconfig -i not. Has someone
> > an idea? Maybe there is a problem on flash size on the last block or
> > something...
>
> Does you have two block in use, one for fis and one for config or is
> it a shared block?

I use two.

> Could you do some more debugging. Which function is causing the
> illegal memory access. Is it the cyg_flash_write()? What addresses are
> passed?

OK i will do.

regards manfred

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [ECOS] change to flash_v2 tree problem
  2005-06-29 10:30   ` Manfred Gruber
@ 2005-06-29 11:00     ` Andrew Lunn
  2005-06-29 11:06     ` Manfred Gruber
  1 sibling, 0 replies; 6+ messages in thread
From: Andrew Lunn @ 2005-06-29 11:00 UTC (permalink / raw)
  To: Manfred Gruber; +Cc: ecos-discuss

On Wed, Jun 29, 2005 at 12:20:18PM +0200, Manfred Gruber wrote:
> > Does you have two block in use, one for fis and one for config or is
> > it a shared block?
> 
> I use two.

OK. So it might be an off by one error. It could be trying to acccess
the byte after the end of the flash...

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [ECOS] change to flash_v2 tree problem
  2005-06-29 10:30   ` Manfred Gruber
  2005-06-29 11:00     ` Andrew Lunn
@ 2005-06-29 11:06     ` Manfred Gruber
  2005-06-29 13:30       ` Bart Veer
  1 sibling, 1 reply; 6+ messages in thread
From: Manfred Gruber @ 2005-06-29 11:06 UTC (permalink / raw)
  To: ecos-discuss

Hi !

Sorry for the disturbing, found my problem. Its not in flash handling is in 
Ethernet ESA handling, which I have changed. My mistake ...
my handling breaks the flash_config_insert_value...

I will change my handling to correct use in redboot now.

Have you any, some information for me how I get am29xxxxx_v2 working, about 
what must i take care.

Sorry thanks regards manfred 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [ECOS] change to flash_v2 tree problem
  2005-06-29 11:06     ` Manfred Gruber
@ 2005-06-29 13:30       ` Bart Veer
  0 siblings, 0 replies; 6+ messages in thread
From: Bart Veer @ 2005-06-29 13:30 UTC (permalink / raw)
  To: gruber.m; +Cc: ecos-discuss

>>>>> "Manfred" == Manfred Gruber <gruber.m@utanet.at> writes:

    Manfred> Have you any, some information for me how I get
    Manfred> am29xxxxx_v2 working, about what must i take care.

The V2 AM29xxxxx package comes with documentation including porting
info. See the package's doc subdirectory.

Please note that the whole V2 flash branch is still considered a
development branch and there may still be some changes to the way a
V2 flash device gets instantiated.

Bart

-- 
Bart Veer                       eCos Configuration Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2005-06-29 13:30 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-29  7:15 [ECOS] change to flash_v2 tree problem Manfred Gruber
2005-06-29  9:56 ` Andrew Lunn
2005-06-29 10:30   ` Manfred Gruber
2005-06-29 11:00     ` Andrew Lunn
2005-06-29 11:06     ` Manfred Gruber
2005-06-29 13:30       ` Bart Veer

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).