[U-Boot] sdhci_transfer_data: Error detected in status(0x208002) problem on Tiny4412 board
Siarhei Siamashka
siarhei.siamashka at gmail.com
Mon Mar 6 23:54:43 UTC 2017
On Fri, 3 Mar 2017 15:29:35 -0700 (MST)
xiaojimmychen <807065717 at qq.com> wrote:
> Hello everyone!
>
> I am working with my Tiny4412 board, and the u-boot version is U-Boot
> 2016.11. After burning the u-boot to sd card, and boot my board from it.
> There are some error ouput to the console. It seems like that my sd card
> doesn't initialize completely.
>
> I have enabled the MMC Debug configuration(CONFIG_MMC_TRACE). And the
> console output is as follow:
>
> U-Boot 2016.11-gbf241c8-dirty (Mar 04 2017 - 06:03:43 +0800) for TINY4412
>
> CPU: Exynos4412 @ 1.4 GHz
> Model: Insignal Tiny4412 evaluation board based on Exynos4412
> Board: Insignal Tiny4412 evaluation board based on Exynos4412
> DRAM: 1 GiB
> WARNING: Caches not enabled
> MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1
> CMD_SEND:0
> ARG 0x00000000
> MMC_RSP_NONE
> CMD_SEND:8
> ARG 0x000001AA
> MMC_RSP_R1,5,6,7 0x000001AA
> CMD_SEND:55
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000120
> CMD_SEND:41
> ARG 0x40300000
> MMC_RSP_R3,4 0x40FF8000
> CMD_SEND:55
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000120
> CMD_SEND:41
> ARG 0x40300000
> MMC_RSP_R3,4 0x40FF8000
> CMD_SEND:55
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000120
> CMD_SEND:41
> ARG 0x40300000
> MMC_RSP_R3,4 0xC0FF8000
> CMD_SEND:2
> ARG 0x00000000
> MMC_RSP_R2 0x03534453
> 0x53303847
> 0x80F3741D
> 0x31010700
>
> DUMPING DATA
> 000 - 03 53 44 53
> 004 - 53 30 38 47
> 008 - 80 F3 74 1D
> 012 - 31 01 07 00
> CMD_SEND:3
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0xAAAA0520
> CMD_SEND:9
> ARG 0xAAAA0000
> MMC_RSP_R2 0x400E0032
> 0x5B590000
> 0x3B377F80
> 0x0A404000
>
> DUMPING DATA
> 000 - 40 0E 00 32
> 004 - 5B 59 00 00
> 008 - 3B 37 7F 80
> 012 - 0A 40 40 00
> CMD_SEND:13
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000700
> CURR STATE:3
> CMD_SEND:7
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000700
> CMD_SEND:55
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:51
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:6
> ARG 0x00FFFFF1
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:6
> ARG 0x00FFFFF1
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:6
> ARG 0x00FFFFF1
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:6
> ARG 0x00FFFFF1
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:6
> ARG 0x80FFFFF1
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:55
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:6
> ARG 0x00000002
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:55
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:13
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:16
> ARG 0x00000200
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:17
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:16
> ARG 0x00000200
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:17
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:16
> ARG 0x00000200
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:18
> ARG 0x00000040
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:12
> ARG 0x00000000
> MMC_RSP_R1b 0x00000B00
> ** First descriptor is NOT a primary desc on 0:1 **
> CMD_SEND:16
> ARG 0x00000200
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:18
> ARG 0x00000031
> MMC_RSP_R1,5,6,7 0x00000900
> CMD_SEND:12
> ARG 0x00000000
> MMC_RSP_R1b 0x00000B00
> *** Warning - bad CRC, using default environment
>
> Hit any key to stop autoboot: 0
> CMD_SEND:0
> ARG 0x00000000
> MMC_RSP_NONE
> CMD_SEND:8
> ARG 0x000001AA
> MMC_RSP_R1,5,6,7 0x000001AA
> CMD_SEND:55
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000120
> CMD_SEND:41
> ARG 0x40300000
> MMC_RSP_R3,4 0x40FF8000
> CMD_SEND:55
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000120
> CMD_SEND:41
> ARG 0x40300000
> MMC_RSP_R3,4 0x40FF8000
> CMD_SEND:55
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000120
> CMD_SEND:41
> ARG 0x40300000
> MMC_RSP_R3,4 0xC0FF8000
> CMD_SEND:2
> ARG 0x00000000
> MMC_RSP_R2 0x03534453
> 0x53303847
> 0x80F3741D
> 0x31010700
>
> DUMPING DATA
> 000 - 03 53 44 53
> 004 - 53 30 38 47
> 008 - 80 F3 74 1D
> 012 - 31 01 07 00
> CMD_SEND:3
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0xAAAA0520
> CMD_SEND:9
> ARG 0xAAAA0000
> MMC_RSP_R2 0x400E0032
> 0x5B590000
> 0x3B377F80
> 0x0A404000
>
> DUMPING DATA
> 000 - 40 0E 00 32
> 004 - 5B 59 00 00
> 008 - 3B 37 7F 80
> 012 - 0A 40 40 00
> CMD_SEND:13
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000700
> CURR STATE:3
> CMD_SEND:7
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000700
> CMD_SEND:55
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:51
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:55
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:6
> ARG 0x00000002
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:55
> ARG 0xAAAA0000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:13
> ARG 0x00000000
> MMC_RSP_R1,5,6,7 0x00000920
> CMD_SEND:16
> ARG 0x00000200
> MMC_RSP_R1,5,6,7 0x00000900
> *CMD_SEND:17
> ARG 0x00000000
> sdhci_transfer_data: Error detected in status(0x208002)!
> RET -70*
> CMD_SEND:16
> ARG 0x00000200
> MMC_RSP_R1,5,6,7 0x00000900
> *CMD_SEND:17
> ARG 0x00000000
> sdhci_transfer_data: Error detected in status(0x208002)!
> RET -70*
> CMD_SEND:16
> ARG 0x00000200
> MMC_RSP_R1,5,6,7 0x00000900
> *CMD_SEND:18
> ARG 0x00000040
> sdhci_transfer_data: Error detected in status(0x208000)!
> RET -70*
> SD/MMC found on device 0
> *CMD_SEND:16
> ARG 0x00000200
> RET -110
> CMD_SEND:16
> ARG 0x00000200
> RET -110
> ** ext4fs_devread read error - block
> Failed to mount ext2 filesystem...
> ** Unrecognized filesystem type ***
> *CMD_SEND:16
> ARG 0x00000200
> RET -110
> CMD_SEND:16
> ARG 0x00000200
> RET -110
> ** ext4fs_devread read error - block
> Failed to mount ext2 filesystem...
> ** Unrecognized filesystem type **
> CMD_SEND:16
> ARG 0x00000200
> RET -110
> CMD_SEND:16
> ARG 0x00000200
> RET -110
> ** ext4fs_devread read error - block
> Failed to mount ext2 filesystem...
> ** Unrecognized filesystem type **
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!*
>
> If someone knows how to fix this bug, please help me!
>
> Thanks a lot!
Hello,
Yes, it's a known problem. You could even easily find the information
about it in google. This was posted to the U-Boot mailing list some
years ago:
https://lists.denx.de/pipermail/u-boot/2015-October/230749.html
Jaehoon Chung promised to have a look at it, but we haven't
heard anything back since then. Right now you can try to apply
this patch and check if it helps (essentially a revert of
a276172cf32386c211c75638f6bf3c0d59ba03ba):
https://github.com/ssvb/u-boot/commit/3dd6fdb016c088953f5f293d62d6df03a0f48d54
BTW, I can't seem to find any Tiny4412 board support code in the
current U-Boot git master branch. Are you using a patched U-Boot?
And if yes, then do you have plans to contribute these patches?
Thanks.
--
Best regards,
Siarhei Siamashka
More information about the U-Boot
mailing list