Re: [Yaffs] Disabling Checkpointing

On Thursday 19 September 2013 00:28:26 tom.edmond@schneider-electric.com
wrote:
> Hi,
>
> Read in the 'General debugging notes' post (26-Aug-2009) that disabling
> checkpointing
> might be a useful thing to do but can't find how to to disable it.
>
> Can someone tell me how to disable checkpointing ?
There are some runtime parameters to control this in the device initialisation
parameters:

dev->param.skip_checkpt_rd = 1; // skip reading checkpoint on mount (ie force
scan)
dev->param.skip_checkpt_wr = 1; // skip writing checkpoint on unmount (ie
force scan on next mount)

There are also some other useful fields
disable_summary (don't use block summaries).

During early bring-up, the following are very useful:
disable_bad_block_marking.
always_check_erased.

and others

Regards

Charles

>
> Regards
> ___________________________________________________________________________
>__________
>
>
> Tom Edmond | Schneider Electric | Infrastructure Business |
> United Kingdom | Senior Systems Development Engineer
> Phone: +44 (0) 1249 456116 | Fax: +44 (0) 1249 456150 |
> Email: tom.edmond@schneider-electric.com | Site:
> www.schneider-electric.com | Address: Connect 17 Building, Langley
> Park, Langley Road, Chippenham, Wiltshire, SN15 1GG
>
> Schneider Electric Limited is a company registered in England and Wales.
> Registered number: 1407228. Registered office: Stafford Park 5, Telford,
> Shropshire TF3 3BL.
> This message (and any associated files) is intended only for the use of
> the intended recipient and may contain information that is confidential,
> subject to copyright or constitutes a trade secret.
> If you are not the intended recipient you are hereby notified that any
> dissemination, copying or distribution of this message, or files
> associated with this message, is strictly prohibited.
> If you have received this message in error, please notify us immediately
> by replying to the message and deleting it from your computer.
> Any views or opinions presented are solely those of the author and do not
> necessarily represent those of the company.
> *** Please consider the environment before printing this e-mail