WinCE -BSP NAND flash 坏块处理
2013-06-04 15:57
316 查看
(三星K9GAG08U0D)
1. Indentifying Initial Invalid Block(s)
All device locations are erased(FFh) except locations where the initial invalid block(s) information is written prior to shipping. The initial invalid block(s) status is defined by the 1st byte in the spare area. Samsung makes
sure that the last page of every initial invalid block has non-FFh data at the column address of 4096. The initial invalid block information is also erasable in most cases, and it is impossible to recover the information once it has been erased. Therefore,
the system must be able to recognize the initial invalid blocks based on the initial invalid block information and create the initial invalid block table via the following suggested flow char. Any intentional erasure of the initial invalid block information
is prohibited.
![](https://img-blog.csdn.net/20130604154108296)
2. Error in write or read operation
Within it's life time, additional invalid blocks may develop with NAND flash memory. Refer to the qualification report for the actual data. Block replacement should be done upon erase or program error.
![](https://img-blog.csdn.net/20130604154719750)
3. Block Replacement
![](https://img-blog.csdn.net/20130604154910593)
(1). when an error happens in the nth page of the block 'A' during erase or program operation.
(2). copy data in the 1st ~ (n-1)th page to the same location of another free block. (Block 'B')
(3). then, copy the nth page data of the block 'A' in the buffer memory to the nth page of the block 'B'
(4). do not erase or program block 'A' by creating an "invalid block" table or other appropriate scheme.
1. Indentifying Initial Invalid Block(s)
All device locations are erased(FFh) except locations where the initial invalid block(s) information is written prior to shipping. The initial invalid block(s) status is defined by the 1st byte in the spare area. Samsung makes
sure that the last page of every initial invalid block has non-FFh data at the column address of 4096. The initial invalid block information is also erasable in most cases, and it is impossible to recover the information once it has been erased. Therefore,
the system must be able to recognize the initial invalid blocks based on the initial invalid block information and create the initial invalid block table via the following suggested flow char. Any intentional erasure of the initial invalid block information
is prohibited.
2. Error in write or read operation
Within it's life time, additional invalid blocks may develop with NAND flash memory. Refer to the qualification report for the actual data. Block replacement should be done upon erase or program error.
3. Block Replacement
(1). when an error happens in the nth page of the block 'A' during erase or program operation.
(2). copy data in the 1st ~ (n-1)th page to the same location of another free block. (Block 'B')
(3). then, copy the nth page data of the block 'A' in the buffer memory to the nth page of the block 'B'
(4). do not erase or program block 'A' by creating an "invalid block" table or other appropriate scheme.
相关文章推荐
- WinCE BSP-NAND flash驱动(whimory)
- 一种基于FAT文件系统的NAND Flash坏块处理方法
- Nand Flash设计中针对坏块处理的理解
- 一种基于FAT文件系统的NAND Flash坏块处理方法
- wince 驱动开发 BSP目录
- hadoop-namenode启动过程及坏块处理流程
- WinCE--中断处理程序ISR 详…
- WinCE BSP工程文件pbcxml分析
- WinCE NAND flash - FAL
- WinCE下,快速编译驱动及BSP
- WinCE 4.2(.net精简框架集)下的图形双缓存处理
- WINCE FAL+FMD nand flash驱动
- WinCE NAND flash - FAL
- WinCE BSP中OAL层中的OEMIoControl介绍
- 坏块处理一
- WinCE BSP中OAL层中的OEMIoControl介绍
- WinCE BSP工程文件pbcxml分析
- WINCE的MFC中处理鼠标滚轮消息
- WinCE BSP中的DAT文件介绍
- Nand Flash基础知识与坏块管理机制的研究