[ECOS] Re: Limit region of flash used by RedBoot for FIS?
Wed Nov 8 04:45:00 GMT 2006
On 2006-11-08, Gary Thomas <email@example.com> wrote:
>>>> It would be cool if that block showed up in fis list and could
>>>> be updated using RedBoot as long as it can't be deleted by
>>>> "fis del" and re-used for something else.
>>> It sounds like you need to add your own entries to the table,
>>> in the same way cfg/fis is added to the table and fis init
>>> known not to touch them.
>> I think it already works that way for the reserved space at
>> the bottom of flash. There's an option called
>> CYGOPT_REDBOOT_FIS_RESERVED_BASE with this description:
>> If an area of FLASH is reserved, it is informative to have
>> a fis entry describing it. This option controls creation
>> of such an entry by default in the fis init command.
>>> I don't think this is going to be a generic solution which you
>>> can contribute back. It seems to be too specific to your
>> I'm going to have to test it a bit, but I think the
>> FIS_RESERVED_BASE option does almost exactly what I want. What
>> I'm not positive there's a RedBoot command that will allow the
>> user to write a block of data into the reserved space. I think
>> that "fis create -f <addr>" will do that, but I'm not sure yet.
>> I just need the same thing at the top of flash as well. :)
> You can always use "fis write" (slightly misnamed as this isn't
> really a FIS operation) to write to anywhere in the FLASH.
Bingo. I thought there was a command like that -- I'm not sure
how I missed that when I was looking through the source.
Grant Edwards grante Yow! Yow! I want to mail
at a bronzed artichoke to
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss