Verification errors after reading eMMC

AdamS

Hello All,

Sometimse i have verification errors after reading, not after programming.
I don know how to unerstend. I don't know how to interpret it because veryification is also a readout of data from eMMC. errors always occur in the same places. I take readings at low speeds with an external power supply connected. I'm using an UFI standard for eMMC
did ufibox write data to a file incorrectly?

Can you help me?

Best regards,
Adam

madgoeslim

AdamS
Hello,
Can you provide screenshot regarding to your error verification problem?
This verify operation is mainly use to check the data integrity of the source files and the data inside emmc after do writing or backup procedure, by comparing it, to make sure there are no corruption issue during read or write process.

AdamS
I have check by myself, I did read bootloader partitions, and make verify after that, and got no problem.

I also did test in eMMC general, doing read, write, and verify, and i have no problem.
Means, data from emmc, after rewrite is the same after verify.

AdamS

One clarification. I use to red UFI eMMC socket. When I read, e.g. bootloader, then save it to a file and then perform verification, then the same errors occur in the same places. Are the same commands are used during reading and verification? this is not always the case but only with some bones.
I don't know which data is correct in file or in eMMC. For me domem data arę wrony data to file but wyj?

AdamS

???

AdamS

Hello madgoeslim,

I'm probably trying to read defectivie SkyHynix eMMC IC with EOL (End Of Life). See for below screenshots and my comments. I use verification after reading to check if the reading speed of the damaged eMMC is not too high. At high eMMC reading speeds from EOL (End Of Live) large more data is incorrect, e.g. when using UFI USB 3.0 dongle.
enter image description here

Then I load the file with partition template '1' and read the first partition '2'
enter image description here

I then verified. Every time an error occurs at the same point, as below.
enter image description here

I suspect (in simplified terms) that 'read' uses data after ECC correction from the spare area and 'verify' reads single bytes without ECC correction.
Can you check and explain it? Are my assumptions correct?

madgoeslim

AdamS You can do Nand Test for fast test procedure. This operation will do write and verify the first sector of Boot 1 and Userarea, and do test in random sector.
In above screenshot, verify is fail in primarygpt, while primarygpt is always in the first sector in userarea, means your userarea, especially at the first sector is damage or have bad block, thats why its always failed in verify.
Verify procedure is comparing the source file with the data inside chip, if the chip have damage in this area, thats will cause verify failed.

AdamS It seems like good suggestion, will talk to the team it is possible to add as new feature or not.

AdamS

Hello again madgoeslim,

I have a suggestion to add a function to load a partitions image files from a directory selected by the user, which would be selected by file names.
I know there is a function that will complete the partition images but only from the user data file.
I have created a template of 60 partitions from eMMC in one file, I need to rip data from one eMMC and copy selected or all partitions to another eMMC. It is bothersome to save 60 times to save image files when saving to a new eMMC. Sometimes the program for unknown reasons shuts down unexpectedly when repeatedly clicking and pointing to a 60 partition image. It takes a long time.
Thank you in advance for understanding and adding this function if possible.

enter image description here

AdamS

???

AdamS

Thank you, are able and you will manage to add such a function