onenand bad block handling
Hi all,
I am working on an ARM platform with OneNAND as the permanent storage
for u-boot, Linux kernel and rootfs. I am using u-boot-2009.03 and linux kernel 2.6.27. I have some questions about the bad block handling of OneNAND.
1. How does the u-boot handle bad block for onenand?
2. If u-boot is creating a bad block table, does it need to pass to
the kernel? If not, how to ensure their bad block table are in sync?
3. How to deal with bad blocks after the writing of the u-boot, kernel
and rootfs image? Is it the job of UBI?
Thanks in advance.
Best regards,
Geiger
Hi,
Quoted 11 lines
Hi all,
I am working on an ARM platform with OneNAND as the
permanent storage
for u-boot, Linux kernel and rootfs. I am using u-boot-2009.03 and linux
kernel 2.6.27. I have some questions about the bad block handling of
OneNAND.1. How does the u-boot handle bad block for onenand?
Jsut skip the bad block and use only good bloks
Quoted 4 lines
2. If u-boot is creating a bad block table, does it need
to pass to
the kernel? If not, how to ensure their bad block table are in sync?
no need to pass bad block from uboot, kernel will create
table of bad blocks.
Quoted 3 lines
3. How to deal with bad blocks after the writing of the
u-boot, kernel
and rootfs image? Is it the job of UBI?
yes, UBI will manage
Quoted 9 lines
Thanks in advance.
Best regards,
Geiger
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Sharma-san,
If I use u-boot to write kernel image to onenand that the kernel image
across bad blocks, will u-boot able to skip blocks during read and successfully boot up the kernel?
Also, same case for rootfs, if I write JFFS2 format rootfs to onenand
using u-boot, how does the kernel handle the rootfs if rootfs across bad blocks?
Many thanks.
Best regards,
Geiger
Quoted 45 lines · Amit Kumar Sharma
Hi,
Quoted 10 lines
Hi all,
I am working on an ARM platform with OneNAND as the
permanent storage
for u-boot, Linux kernel and rootfs. I am using u-boot-2009.03 and linux
kernel 2.6.27. I have some questions about the bad block handling of
OneNAND.Quoted 2 lines
1. How does the u-boot handle bad block for onenand?
Jsut skip the bad block and use only good bloks
Quoted 5 lines
2. If u-boot is creating a bad block table, does it need
to pass to
the kernel? If not, how to ensure their bad block table are in sync?no need to pass bad block from uboot, kernel will create
table of bad blocks.Quoted 4 lines
3. How to deal with bad blocks after the writing of the
u-boot, kernel
and rootfs image? Is it the job of UBI?yes, UBI will manage
Quoted 9 lines
Thanks in advance.
Best regards,
Geiger
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot