You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not an issue in fact, but I wandered how to support hardware ECC, maybe some changes should be a better way to support HW ECC.
Current source code logic in fs_dev_nand_ctrlr_gen.c:SecWr,
write sector data
calculate ECC of sector + OOS data (p_ctrlr_data->CtrlrExtPtr->ECC_Calc)
SparePack OOS data
write OOS to OOB (ECC included after OOS)
I suppose the following process can be followed to support HW ECC:
write sector data
SparePack OOS data
write OOS to OOB
p_ctrlr_data->CtrlrExtPtr->ECC_Calc
in this callback function, get ECC from HW like STM32 MCU FSMC register (it calculates ECC for each certain bytes data written)
write ECC to OOB
With these changes, both software ECC and HW ECC can be supported.
I don't know if it makes sense. Thanks!
The text was updated successfully, but these errors were encountered:
It is not an issue in fact, but I wandered how to support hardware ECC, maybe some changes should be a better way to support HW ECC.
Current source code logic in fs_dev_nand_ctrlr_gen.c:SecWr,
I suppose the following process can be followed to support HW ECC:
in this callback function, get ECC from HW like STM32 MCU FSMC register (it calculates ECC for each certain bytes data written)
With these changes, both software ECC and HW ECC can be supported.
I don't know if it makes sense. Thanks!
The text was updated successfully, but these errors were encountered: