Firefly Open Source Community

   Login   |   Register   |

System freezing when replaced with another eMMC

34

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
34
Posted at 4/20/2017 16:34:33     
Last edited by motive1 In 4/20/2017 16:36 Editor

System freezing when replaced with another eMMC

How to reproduce:
1. Replace the original 32GB Samsung eMMC with another manufacturer's eMMC
2. Download Firefly-RK3399_Android6.0_201703181519.img using AndroidTool
3. After downloading and rebooting, the system will freeze after proceeding to the following kernel log.(Attached the full log.)
...
[ 1.715125] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[ 1.717158] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.718873] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.721783] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[ 1.733657] u?
[ 1.782257] mmc_host mmc2: Bus speed (slot 0) = 200000000Hz (slot req 208000000Hz, actual 200000000HZ div = 0)

I have tested eMMCs from other manufacturers (Sandisk, Micron, Hynix Toshba, etc.) but all have the same problem except for the original soldered eMMC.
It is the same symptom in other types of memory even made by Samsung.


Somebody please help me.


teraterm_20170420_172652_recovery.zip

14.75 KB, Down times: 6

full log

Reply

Use props Report

34

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
34
Posted at 4/20/2017 16:47:41     

I modified the mmc driver to print all eMMC commands.
As a result, I confirmed that the system had access to the RPMB area of eMMC at the point of the problem.
Does the platform check the authenticated eMMC to limit its operation?

[    1.571560] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.573428] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.575325] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.578638] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.587821] mmc1: CMD(6) = 0x03B30301           <== Select RPMB Area
[    1.587946] mmc1: CMD(13) = 0x00010000
[    1.588021] mmc1: CMD(13) = 0x00010000
[    1.588143] mmc1: CMD(25) = 0x00000000
[    1.588276] mmc1: CMD(13) = 0x00010000
[    1.588421] mmc1: CMD(18) = 0x00000000        < read somthing
[    1.588735] mmc1: CMD(13) = 0x00010000
[    1.588923] mmc1: CMD(6) = 0x03B30001        <== Select RPMB Area
[    1.589101] mmc1: CMD(13) = 0x00010000
Reply

Use props Report

39

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
39
Posted at 6/11/2018 18:29:14     
was the issue resolved?
I came across the same issue, and please teach me how to modify mmc driver to print all emmc commands
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list