Re: [ECOS] Re: Limit region of flash used by RedBoot for FIS?

[Andrew Lunn <andrew at lunn dot ch>]

> That's the exact same situation I'm in: the top 1MB contains
> that's loaded into an FPGA by hardware on startup (before the
> CPU starts).

Our setup was different. The CPU downloaded the bitstream in the
FPGA. So erasing the flash did not brick the system. It just mean the
FPGA did not "boot".
 
> However, I don't want "fis init -f" to erase that block, and it
> appears that it would do so as the code exists now.  Is that
> correct?
 
It looks like that.

> I'd like to be able to do that as well, so perhaps my proposed
> solution isn't the best.  
> 
> What I really want is:
> 
>  * A reserved block in the top of flash for the CPLD data.
> 
>    That block must be left untouched by "fis init -f".
> 
>    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 don't think this is going to be a generic solution which you
can contribute back. It seems to be too specific to your platform.

    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