In a NAND Functional Tester I implemented the algorithm to detect during Read/Verify the actual ECC required per Block and Device.
Applying repeatedly Erase/Program/Read/Verify to the same block emphasized the Endurance (measured in number of Erase/Program cycles) based on the evolution of ECC detected during Read/Verify.
Lately a customer ran, on an ONFI2.2 Chip with ECC Unit of 1117 Bytes and minimum required ECC 40 according to the spec, repeatedly, Erase/Program/Read/Verify cycles on the same Block. During the first cycle the ECC detected by the tester for that Block was 6, after 3K cycles ECC detected was 17, after 5K cycles ECC 29.
NASA's Orion Flight Software Production Systems Manager Darrel G. Raines joins Planet Analog Editor Steve Taranovich and Embedded.com Editor Max Maxfield to talk about embedded flight software used in Orion Spacecraft, part of NASA's Mars mission. Live radio show and live chat. Get your questions ready.
Brought to you by