This post just talks about an experience which I have come across in 2012. It doesn't provide any other insights what are the issues faced and how they are solved.
I was working on a project where we have a reference Board Support Package (BSP) for Windows CE 6.0. So the BSP supports one of the peripheral eMMC.
The reference BSP uses a eMMC from vendor X. We have to port the eMMC driver to be functional with vendor Y .
I just assumed that after the Chip Erase the contents of the Flash will be restored to All 1's for both the eMMC devices which are from different vendors.
But, surprisingly after erasing, vendor X's ERASED_MEM_CONT shows a value of 0x01 and vendor Y's ERASED_MEM_CONT shows a value of 0x00 in the 512-byte Extended CSD Register.
So, always read the entire device technical manual.
Also the developers shall consider the availability of the technical support such as reference codes, technical manuals and etc... to be fully available while finalizing the part in the hardware.
I was working on a project where we have a reference Board Support Package (BSP) for Windows CE 6.0. So the BSP supports one of the peripheral eMMC.
The reference BSP uses a eMMC from vendor X. We have to port the eMMC driver to be functional with vendor Y .
I just assumed that after the Chip Erase the contents of the Flash will be restored to All 1's for both the eMMC devices which are from different vendors.
But, surprisingly after erasing, vendor X's ERASED_MEM_CONT shows a value of 0x01 and vendor Y's ERASED_MEM_CONT shows a value of 0x00 in the 512-byte Extended CSD Register.
So, always read the entire device technical manual.
Also the developers shall consider the availability of the technical support such as reference codes, technical manuals and etc... to be fully available while finalizing the part in the hardware.
