Bad Block Management: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 112: | Line 112: | ||
<h2>Contents <a href="javascript:void(0);" class="hide-link" onclick="toggleTOC()">[hide]</a></h2> | <h2>Contents <a href="javascript:void(0);" class="hide-link" onclick="toggleTOC()">[hide]</a></h2> | ||
<ul> | <ul> | ||
<li><a href="#section1"> background information</a></li> | |||
<li><a href="#section1"> | |||
<li><a href="#section3"> Flow chart of order of operations</a></li> | <li><a href="#section3"> Flow chart of order of operations</a></li> | ||
<li><a href="#section5"> Related Topics</a></li> | <li><a href="#section5"> Related Topics</a></li> | ||
<li><a href="#section6"> Further reading</a></li> | <li><a href="#section6"> Further reading</a></li> | ||
| Line 127: | Line 119: | ||
</div> | </div> | ||
<!-- background information --> | <!-- background information --> | ||
<h1> Background information </h1> | <h1 id="section1"> Background information </h1> | ||
<p>Bad Block management(BB) as the name suggests is responsible for handle bad blocks within the chip by using error detecting code(ECC) which is stored in a pages spare area.(link it)</br> | <p>Bad Block management(BB) as the name suggests is responsible for handle bad blocks within the chip by using error detecting code(ECC) which is stored in a pages spare area.(link it)</br> | ||
If a physical block is detected by the FTL as bad, it is recorded and replaced with a healthy block from the reserved area.(link it)</p> | If a physical block is detected by the FTL as bad, it is recorded and replaced with a healthy block from the reserved area.(link it)</p> | ||
<h1 id="section3">Flow chart of order of operations</h1> | <h1 id="section3">Flow chart of order of operations</h1> | ||
<p>Insert a flow chart of steps and actions for each task (create using diagram)</p> | <p>Insert a flow chart of steps and actions for each task (create using diagram)</p> | ||
<h1 id="section5">Related Topics</h1> | <h1 id="section5">Related Topics</h1> | ||
Latest revision as of 16:01, 15 January 2025
Background information
Bad Block management(BB) as the name suggests is responsible for handle bad blocks within the chip by using error detecting code(ECC) which is stored in a pages spare area.(link it)
If a physical block is detected by the FTL as bad, it is recorded and replaced with a healthy block from the reserved area.(link it)
Flow chart of order of operations
Insert a flow chart of steps and actions for each task (create using diagram)
Related Topics
Topics such as desoldering to chip off or firmware dumping for disk PCB repairs
Further reading
External references in wiki references can just be cited through the keyword link
- Reference 1: Source details
- Reference 2: Source details