RedBoot: fis delete won't erase

[David Vrabel]

Gary Thomas wrote:
> David Vrabel said:
> 
>>fis delete no longer needs to erase the flash as fis free now uses the
>>FIS directory to determine free space.  Erasing the flash twice (once
>>for fis delete and then again for fis create) is also unnecessary.
> 
> I'll look at this when I'm back in my office, but in reality, it
> doesn't really matter to be extra thorough - the "erase" routines
> are optimized to check for erased data and avoid touching the device
> if the segment is already blank.

Hmm. I definately remember it erasing it twice.  (investigates further) 
It seems that checking for erased blocks is broken in my local tree.

Still, not doing an erase in fis delete would allow you to recover from 
a botched fis delete command.  Not that I do that very often... :P

David Vrabel

ps. No need to CC.
-- 
David Vrabel, Design Engineer

Arcom, Clifton Road           Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK         Web: http://www.arcom.com/


_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.

This message has been checked for all viruses by MessageLabs Virus Control Centre.