Firefly Open Source Community

   Login   |   Register   |
New_Topic
Print Previous Topic Next Topic

[Android] eMMC error

19

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
19

【Android】 eMMC error

Posted at 8/26/2020 07:57:21      View:5802 | Replies:3        Print      Only Author   [Copy Link] 1#
Hi, I've received RK3399 few weeks ago, and after flashing android image from this web site I got following issue:
  1. DDR Version 1.12 20180518
  2. In
  3. Channel 0: DDR3, 800MHz
  4. Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
  5. Channel 1: DDR3, 800MHz
  6. Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
  7. 256B stride
  8. ch 0 ddrconfig = 0x101, ddrsize = 0x20
  9. ch 1 ddrconfig = 0x101, ddrsize = 0x20
  10. pmugrf_os_reg[2] = 0x32817281, stride = 0x9
  11. OUT
  12. Boot1: 2018-04-08, version: 1.12
  13. CPUId = 0x0
  14. ChipType = 0x10, 215
  15. mmc: ERROR: SDHCI:Transfer data timeout
  16. mmc: ERROR: SDHCI ERR:cmd:0x153a,stat:0x0
  17. mmc: ERROR: Tuning procedure failed, falling back to fixed sampling clock
  18. mmc: ERROR: tuning execution failed
  19. emmc reinit
  20. mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
  21. mmc: ERROR: Card did not respond to voltage select!
  22. emmc reinit
  23. init complete media->high_capacity: 1
  24. mmc: ERROR: SDHCI ERR:cmd:0x209,stat:0x18000
  25. SdmmcInit=2 1
  26. mmc0:cmd8,32
  27. mmc0:cmd5,32
  28. mmc0:cmd55,32
  29. mmc0:cmd1,32
  30. mmc0:cmd8,32
  31. mmc0:cmd5,32
  32. mmc0:cmd55,32
  33. mmc0:cmd1,32
  34. mmc0:cmd8,32
  35. mmc0:cmd5,32
  36. mmc0:cmd55,32
  37. mmc0:cmd1,32
  38. SdmmcInit=0 1
  39. powerOn 12335346
Copy the code


In case when it succeeds to get to kernel it got following error:
  1. [    1.880835] rk-hdmi-dp-sound hdmi-dp-sound: multicodec <-> ff8a0000.i2s mapping ok
  2. [    1.880939] hdmi-audio-codec hdmi-audio-codec.10.auto: ASoC: Failed to create Playback debugfs file
  3. [    1.886382] rk808-rtc rk808-rtc: setting system clock to 2013-01-18 08:50:03 UTC (1358499003)
  4. [    1.887744] It doesn't contain Rogue gpu
  5. [    1.897053] mmc1: MAN_BKOPS_EN bit is not set
  6. [    1.899485] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
  7. [    1.901670] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
  8. [    1.903818] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
  9. [    1.907626] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
  10. [    1.912084] mmc2: queuing unknown CIS tuple 0x81 (9 bytes)
  11. [    1.929478] mmc1: error -110 whilst initialising MMC card
  12. [    1.975332] mmc_host mmc2: Bus speed (slot 0) = 200000000Hz (slot req 208000000Hz, actual 200000000HZ div = 0)
  13. [    2.195440] dwmmc_rockchip fe310000.dwmmc: Successfully tuned phase to 235
  14. [    2.202504] mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
  15. [    2.202673] mmc2: new ultra high speed SDR104 SDIO card at address 0001
  16. [    4.584326] vendor storage:20160801 ret = -1
  17. [    5.184255] iep dpi mode inactivity
  18. [   20.207747] INFO: task swapper/0:1 blocked for more than 10 seconds.
  19. [   20.207837]       Not tainted 4.4.126 #226
  20. [   20.207854] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  21. [   20.207870] swapper/0       D ffffff8008085a58     0     1      0 0x00000000
  22. [   20.207906] Call trace:
  23. [   20.207941] [<ffffff8008085a58>] __switch_to+0x8c/0xb4
  24. [   20.207966] [<ffffff8008b312cc>] __schedule+0x6a8/0x6dc
  25. [   20.207985] [<ffffff8008b31374>] schedule+0x74/0x94
  26. [   20.208006] [<ffffff8008b33dbc>] schedule_timeout+0x40/0x268
  27. [   20.208098] [<ffffff8008b31f14>] wait_for_common+0xd4/0x168
  28. [   20.208118] [<ffffff8008b31fbc>] wait_for_completion+0x14/0x1c
  29. [   20.208139] [<ffffff800845a424>] drm_dev_wait+0x14/0x1c
  30. [   20.208163] [<ffffff80090bbce4>] drm_misc_init+0x25c/0x2fc
  31. [   20.208181] [<ffffff8008083468>] do_one_initcall+0x84/0x1a4
  32. [   20.208204] [<ffffff8009090e50>] kernel_init_freeable+0x224/0x228
  33. [   20.208223] [<ffffff8008b2ff5c>] kernel_init+0x10/0xf8
  34. [   20.208240] [<ffffff80080832a0>] ret_from_fork+0x10/0x30
Copy the code


All points to faulty eMMC, but I can't get support to reply. They seems to ignore me. I got mail from sales advising to contact after sale, but no description how to do this. In my account after sale there is nothing that can be done...
Reply

Use props Report

1562

Credits

0

Prestige

0

Contribution

vip

Rank: 6Rank: 6

Credits
1562
Posted at 8/26/2020 16:56:36        Only Author  2#
Did you do anything with emmc before this?
Reply

Use props Report

19

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
19
Posted at 8/30/2020 06:48:11        Only Author  3#
phkr Posted at 8/26/2020 16:56
Did you do anything with emmc before this?

No, I just flashed Android image when I received the device.
Reply

Use props Report

19

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
19
Posted at 9/14/2020 14:09:16        Only Author  4#
I got replacement that works fine after update.
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