5A corrupts eMMC (was 5A does not boot)

#34

Sorry. I won’t continue this.

2 Likes
#35

Can you try overriding and increasing the pull-up level (drive-strength) of all the data lines here: kernel/rk3588s-pinctrl.dtsi at stable-5.10-rock5 · radxa/kernel · GitHub ?

PCB traces may be a bit too long (or other issue) for the default settings, hence why it works fine in lower HS mode or inherently slower cards (like the 16 GB one).

#36

Sorry, I don’t really know how to do this. Can you give me some example of how it’s done?

#37

Similarly, I am having trouble booting Rock 5A from emmc.
After powering on, the blue LED does not light up or even if it does
dimmc_rockhip fe2c0000.mmc: busy; trying anyway
and cannot proceed to the next step.
I would like to know the solution.
The emmc and power supply are purchased from allnet china.

#38

Like what @GinKage said, I was not able to reproduce this on 16GB Foresee eMMC module. I recently worked around a different eMMC issue on ROCK 4 by reducing to HS200 so I’ll test if that solves the issue.

@dylandn @hiro and @nyanmisaka please leave your eMMC size and model here as well.

#39

One official Foresee 64G eMMC module from Allnet and one homebrew KIOXIA 64G eMMC module (THGAMRG9T23BAIL). Both of them work fine with the official USB 3 eMMC reader and Rock 5B.

#41

iIt’s a Samsung 16GB KLMAG1JETD-B041

#42

@RadxaYuntian Also confirmed that downgrading to HS200 fixes the issue on my 5A with the 64G eMMC modules. So I’m guessing there might be a compatibility issue with the board itself.

#43

Actually I think it was Foresee having issue at HS400. We reproduced the issue in our office, and I’ll try adjust pin drive as suggested above.

Still need to figure out why Samsung was not working for @dylandn though.

#44

I tried to increase it from level 2 to 5 but it didn’t help. Is it still safe to set this to higher values?

The maximum value of it is 15 - pcfg_pull_up_drv_level_15

#45

In which case I think drive strength is unlikely to be the issue here. I’ll validate HS200 internally and create a PR if that solves the issue.

#46

My module seems to be identical to dylandn’s, identified in dmesg as “CJTD4R 58.2 GiB”.
Update: scratch that, my module has different capacity, I’ll post the part number later today.

#47

Can you take a picture of the front and back of your ROCK 5A and eMMC module?

I want to know the hardware version of ROCK 5A and the brand and capacity of eMMC module.

#48

Module info here: 5A corrupts eMMC (was 5A does not boot)

#49

I use the following emmc bought from allnet china.
EMMC 5.1 FOR ROCK 4 / 3A / 5B / 5A / E (ALSO FOR ODROID) 32GB

product page

emmc writer uses the following emmc writer purchased from allnet china
EMMC TO USD BOARD
product page

#50

Does your eMMC chip has FORESEE engraving?

#51

Yes, there is FORESEE engraving
Is there any other information you need?

#52

My eMMC module is Samsung KLMCG4JETD-B041 (without any FORESEE engraving), and 5A is V1.1.
So we now have five different modules with this issue (two Samsung, two Foresee and one Kioxia).

#53

I’d try setting them to 10.

#54

I’ll give it a try tomorrow.