![Ronetix PEEDI Скачать руководство пользователя страница 78](http://html1.mh-extra.com/html/ronetix/peedi/peedi_user-manual_1485040078.webp)
Using PEEDI
with ECC data (6 bytes for 512 bytes page, 24 bytes for 2048 bytes page).
•
JFFS2_NO_EM - like JFFS2 but PEEDI does not write erase/clean markers
•
RAW - data and spare bytes will be loaded from the image file, default if
OOB_INFO parameter is missing
•
YAFFS - like RAW, but bad blocks are skipped
•
FF - only data bytes will be read from the image file, spare bytes will be set to
0xFF
•
ONDIE_ECC - Micron NAND FLASH On-Die ECC
•
AT91_PMECC - Atmel AT91SAM9X5 and SAMA5
•
BLACKFIN_ECC - ADI Blackfin hardware ECC
•
IMX_ECC - Freescale iMX hardware ECC
•
IMX23_BCH - Freescale iMX23 hardware ECC
•
LPC_ECC - NXP LPC hardware ECC
•
OMAP3_ECC - TI Omap3 hardware ECC
•
OMAP4_BCH8_ROMCODE - TI Omap4 hardware ECC
•
OMAP4_BCH8 - TI Omap4 hardware ECC
•
OMAP4_HAMMING - TI Omap4 hardware ECC
•
PXA_ECC - Marvell PXA3XX hardware ECC
•
ONENAND - OneNAND hardware ECC
•
DAVINCI_ECC - TI DaVinci Hardware ECC, 4 bytes per 512 bytes data
•
DAVINCI_ECC_HW6_512 - DaVinci hardware ECC, 6 bytes per 512 bytes
data
•
DAVINCI_ECC_HW6_512_2610 - DaVinci hardware ECC, 6 bytes per 512
bytes data with workaround for a JFFS2 bug in Linux kernel 2.6.10
•
DAVINCI_ECC_HW10_512 - DaVinci hardware ECC, 10 bytes per 512 bytes
data
•
DM355_BOOT - TI TMS320DM355 hardware ECC
•
DM355_LINUX - TI TMS320DM355 hardware ECC
PEEDI User’s Manual
78