From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yang, Wenyou Date: Tue, 27 Feb 2018 09:55:02 +0800 Subject: [U-Boot] U-Boot In-Reply-To: References: <4f6a449d-3987-6c5f-2818-af9619dade5d@denx.de> <3ae879db-a158-857a-d27c-1e8a1709eea3@microchip.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: u-boot@lists.denx.de Hi Mariano, On 2018/2/27 1:09, Mariano Coromac wrote: > Hello Again, > I have been working with UBoot but now when I try to boot my Linux > kernel image that's inside my eMMC it displays the following: > => boot > CMD_SEND:0 >         ARG             0x00000000 >         RET             -110 > mmc_init: -110, time 10 > ** Bad device mmc 1 ** > CMD_SEND:0 >         ARG             0x00000000 >         RET             -110 > mmc_init: -110, time 11 > ** Bad device mmc 1 ** > > I know it is a timeout error and I also know that the error occurs > inside mmc-uclass line 31. I'm aware send_cmd() is defined in mmc.h > but I honestly don't know how to dig deeper into this error. > > mmc info works fine. Here's the mmc rescan log if it makes any use: > => mmc rescan > CMD_SEND:0 >         ARG             0x00000000 >         MMC_RSP_NONE > CMD_SEND:8 >         ARG             0x000001AA >         RET             -110 > CMD_SEND:55 >         ARG             0x00000000 >         RET             -110 > CMD_SEND:0 >         ARG             0x00000000 >         MMC_RSP_NONE > CMD_SEND:1 >         ARG             0x00000000 >         MMC_RSP_R3,4         0x00FF8080 > CMD_SEND:1 >         ARG             0x40360080 >         MMC_RSP_R3,4         0xC0FF8080 > CMD_SEND:2 >         ARG             0x00000000 >         MMC_RSP_R2         0xEB010D65 >                            0x4D4D4320 >                            0x205000AC >                            0x008E7300 > >                     DUMPING DATA >                     000 - EB 01 0D 65 >                     004 - 4D 4D 43 20 >                     008 - 20 50 00 AC >                     012 - 00 8E 73 00 > CMD_SEND:3 >         ARG             0x00010000 >         MMC_RSP_R1,5,6,7      0x00000500 > CMD_SEND:9 >         ARG             0x00010000 >         MMC_RSP_R2         0xD04F0132 >                            0x0F5903FF >                            0xFFFFFFEF >                            0x8A400000 > >                     DUMPING DATA >                     000 - D0 4F 01 32 >                     004 - 0F 59 03 FF >                     008 - FF FF FF EF >                     012 - 8A 40 00 00 > CMD_SEND:13 >         ARG             0x00010000 >         MMC_RSP_R1,5,6,7      0x00000700 > CURR STATE:3 > CMD_SEND:7 >         ARG             0x00010000 >         MMC_RSP_R1,5,6,7      0x00000700 > CMD_SEND:8 >         ARG             0x00000000 >         MMC_RSP_R1,5,6,7      0x00000900 > CMD_SEND:8 >         ARG             0x00000000 >         MMC_RSP_R1,5,6,7      0x00000900 > CMD_SEND:6 >         ARG             0x03B90100 >         MMC_RSP_R1b         0x00000800 > CMD_SEND:13 >         ARG             0x00010000 >         MMC_RSP_R1,5,6,7      0x00000900 > CURR STATE:4 > CMD_SEND:8 >         ARG             0x00000000 >         MMC_RSP_R1,5,6,7      0x00000900 > CMD_SEND:6 >         ARG             0x03B70100 >         MMC_RSP_R1b         0x00000800 > CMD_SEND:13 >         ARG             0x00010000 >         MMC_RSP_R1,5,6,7      0x00000900 > CURR STATE:4 > CMD_SEND:8 >         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 > > Any guidance would be appreciated. Please check if there is a pin conflict to configure, or if the mmc sequential number is correct. On sama5d2 Xplained board, the eMMC works with the commands, => mmc info Device: sdio-host at a0000000 Manufacturer ID: fe OEM: 14e Name: MMC04 Tran Speed: 52000000 Rd Block Len: 512 MMC version 4.4.1 High Capacity: Yes Capacity: 3.7 GiB Bus Width: 4-bit Erase Group Size: 512 KiB HC WP Group Size: 4 MiB User Capacity: 3.7 GiB Boot Capacity: 1 MiB ENH RPMB Capacity: 128 KiB ENH > Thank you. > > On Wed, Feb 14, 2018 at 3:27 PM, Mariano Coromac > wrote: > > Forget it guys, I just realized what was wrong. > reg = <0xf8038200 0x200>; > Before it was > reg = <0xf8038200 0x100>; > So if anyone else (that wants to use the flexcom uart) asks you > about this now there's another thing you can point to. > If I encounter another problem or something I'll get back to you. > > > > > -- > Mariano Coromac > I&D of Electronics Engineer > mcoromac at stsa.info > +502 41544712 > www.gps.gt > Best Regards, Wenyou Yang