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]
Other format: [Raw text]

Re: change to flash_v2 tree problem


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


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