View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002161 | UBoot | NAND-FMD | public | 2014-04-03 15:57 | 2014-04-09 07:51 |
| Reporter | Keller | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | fsvybrid-V1.2 | ||||
| Target Version | fsvybrid-V2.0 | Fixed in Version | fsvybrid-V2.0 | ||
| Summary | 0002161: Flash based Bad Block Table conflicts with UBI on TargetFS | ||||
| Description | The Vybrid implementation currently uses a flash based Bad Block Table (BBT) that is located in the last two blocks of the NAND flash. However this is neither supported in NBoot, nor in UBI in U-Boot or Linux. Therefore this BBT is not updated at all if a new bad block is encountered. And even more, UBI does not recognize this BBT location. Therefore when creating an UBI on the TargetFS (which includes these two blocks by default), the BBT is always overwritten. | ||||
| Steps To Reproduce | Start a fresh U-Boot. U-Boot tells that it did not find a BBT and writes a new one. Restart U-Boot, U-Boot does not complain about a missing BBT anymore. Now call ubi part TargetFS ubi create rootfs Then restart U-Boot. U-Boot again complains about a missing BBT and creates a new one. This is a conflicting usage of these two blocks: they are used as BBT by the NAND code on one hand and as regular blocks by UBI on the other hand. This can not work in the long term. | ||||
| Additional Information | We can switch to a dynamic BBT that is built by reading the spare areas of the NAND flash each time when starting U-Boot. | ||||
| Forum Link | |||||
