From: Andrew Lunn <andrew@lunn.ch>
To: Per-Erik Johansson <perka@dtek.chalmers.se>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Questions about dual flash
Date: Fri, 14 Dec 2007 10:46:00 -0000 [thread overview]
Message-ID: <20071214094745.GC13033@lunn.ch> (raw)
In-Reply-To: <1354.213.15.68.47.1197552515.squirrel@webmail.chalmers.se>
> But if we then run fis init, our output from fis free becomes a bit
> confusing..
> RedBoot> fis free
> ... Read from 0x001e0000-0x001fffff to 0x407e0000:
> 0x00040000 .. 0x001C0000
> 0x001C1000 .. 0x001E0000
> 0x00200000 .. 0x001FFFFF
> 0x00000001 .. 0x20020042
>
> We have set the Maximum number of free chunks to 40 ((2MB + 8MB
> flash)/256k min image size) Are we thinking totally wrong here??
>
> One even more strange thing is that if we use telnet, instead of serial,
> we get get this output from the fis free:
> RedBoot> fis free
> ... Read from 0x001e0000-0x001fffff to 0x407e0000:
> 0x00040000 .. 0x001C0000
> 0x001C1000 .. 0x001E0000
> 0x00200000 .. 0x001FFFFF
> 0x3FFF2BA4 .. 0x000031AC
This looks like a bug to me. The code which finds free space is not so
simple and it got even hairier when we added support for multiple
flashes in the v2 branch. Take a look at
/packages/redboot/current/src/flash.c:find_free()
and see if you can find the problem.
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:[~2007-12-14 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 8:04 Per-Erik Johansson
[not found] ` <e37cb5250712030430v4e71799ase1c40bc57889a1fc@mail.gmail.com>
2007-12-03 12:31 ` Tom Deconinck
2007-12-13 14:48 ` Per-Erik Johansson
2007-12-14 10:46 ` Andrew Lunn [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-30 12:52 Per-Erik Johansson
2007-11-30 14:01 ` Andrew Lunn
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=20071214094745.GC13033@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=perka@dtek.chalmers.se \
/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).