From: Andrew Lunn <andrew@lunn.ch>
To: Manfred Gruber <gruber.m@utanet.at>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] change to flash_v2 tree problem
Date: Wed, 29 Jun 2005 09:56:00 -0000 [thread overview]
Message-ID: <20050629095641.GA5563@lunn.ch> (raw)
In-Reply-To: <200506290915.06896.gruber.m@utanet.at>
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
next prev parent reply other threads:[~2005-06-29 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 7:15 Manfred Gruber
2005-06-29 9:56 ` Andrew Lunn [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050629095641.GA5563@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gruber.m@utanet.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).