i.mx6 Dual Lite mmcblk0rpmb: error -110 transferring data

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

i.mx6 Dual Lite mmcblk0rpmb: error -110 transferring data

720 Views
kbtess
Contributor II

we have an old custom design based on i.mx 6 dual lite processor. recently we have to produce a few boards based on the same design. Due to pandemic we were unable to source the 4GB  micron emmc 5.0 part , instead we used 8GB micron 5.1 emmc  part. the software ( bsp+ application running on both the boards were same but we are getting the following error.

=============================================ERROR LOG========================

mmcblk0rpmb: error -110 transferring data, sector 8064, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
Begin: Running /scripts/local-premount ... done.
mmcblk0rpmb: error -110 transferring data, sector 8176, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
udevd[140]: symlink '../../mmcblk0boot0' '/dev/disk/by-path/platform-219c000.usdhc.udev-tmp' failed: File exists

mmcblk0rpmb: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 8, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 8184, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 7928, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 8128, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 7936, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 7792, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 2048, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 24, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 56, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 120, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 16, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 128, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 64, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
EXT4-fs (mmcblk0p6): recovery complete
EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null)
mmcblk0rpmb: error -110 transferring data, sector 512, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 32, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read
mmcblk0rpmb: error -110 transferring data, sector 4096, nr 8, cmd response 0x900, card status 0xb00
mmcblk0rpmb: retrying using single block read

===============================================================================

We have tried all the normal debugging .

Changed the drive strength , changed the pull ups on CMD and D0 lines. tried on multiple boards , but all revert back to the same error. the count of error and the sector number is same across all trials,

one more thing , the 5.1 emmc have around 20 initial bad blocks while 5.0 have zero bad blocks. 

Really looking forward for a solution for this

 

Labels (2)
0 Kudos
1 Reply

711 Views
igorpadykov
NXP Employee
NXP Employee

Hi Binu

 

one can look at similar case described on

https://community.nxp.com/t5/i-MX-Processors/eMMC-8GB-to-4GB-crash-on-linux-yocto-boot/m-p/373231

 

Best regards
igor

0 Kudos