summaryrefslogtreecommitdiff
path: root/src/flash/s3c24xx_nand.c
diff options
context:
space:
mode:
authordbrownell <dbrownell@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-09-17 18:56:17 +0000
committerdbrownell <dbrownell@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-09-17 18:56:17 +0000
commit9536577c0214d6f59e9589fce75f295755fa9f6c (patch)
tree1b05c209a4eb3d662c17bdb52d67b76c732d29a5 /src/flash/s3c24xx_nand.c
parent9655c5b093d459df001d7a11742d9a84183ce1f2 (diff)
downloadopenocd+libswd-9536577c0214d6f59e9589fce75f295755fa9f6c.tar.gz
openocd+libswd-9536577c0214d6f59e9589fce75f295755fa9f6c.tar.bz2
openocd+libswd-9536577c0214d6f59e9589fce75f295755fa9f6c.tar.xz
openocd+libswd-9536577c0214d6f59e9589fce75f295755fa9f6c.zip
Minor fixes to NAND code and docs
Erase logic: - command invocation + treat "nand erase N" (no offset/length) as "erase whole chip N" + catch a few more bogus parameter cases, like length == 0 (sigh) - nand_erase() should be static - on error + say which block failed, and if it was a bad block + don't give up after the first error; try to erase the rest - on success, say which nand device was erased (name isn't unique) Device list ("nand list"): - say how many blocks there are - split summary into two lines - give example in the docs Doc tweaks: - Use @option{...} for DaVinci's supported hardware ECC options For the record, I've observed that _sometimes_ erasing bad blocks causes failure reports, and that manufacturer bad block markers aren't always erasable (even when erasing their blocks doesn't trigger an error report). git-svn-id: svn://svn.berlios.de/openocd/trunk@2724 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'src/flash/s3c24xx_nand.c')
0 files changed, 0 insertions, 0 deletions