Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #31034
| From | Buzz McCool <buzz_mccool@yahoo.com> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | eMMC CSD Register ECC field |
| Date | 2022-04-12 17:54 -0700 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <t356vo$490$1@gioia.aioe.org> (permalink) |
Anyone here knowledgeable about eMMC memory? I have a high reliability application where there is concern about memory corruption. What would happen if I changed the ECC field in the eMMC's Card Specific Data (CSD) register from the default no ECC to the optional BCH(542,512) encoding? Would I still be able to write/read new values to the eMMC normally with the eMMC internally protecting the contents with BCH ECC at the cost of reduced memory capacity, or would a special driver on the host be needed to encode/decode ECC reads/writes? I've asked around and haven't found a definitive answer so far. Let me know if you can help ... Buzz
Back to comp.arch.embedded | Previous | Next — Next in thread | Find similar | Unroll thread
eMMC CSD Register ECC field Buzz McCool <buzz_mccool@yahoo.com> - 2022-04-12 17:54 -0700 Re: eMMC CSD Register ECC field Boudewijn Dijkstra <sp4mtr4p.boudewijn@indes.com> - 2022-06-09 16:06 +0200
csiph-web