* [BUG] mx6cuboxi : broken MMC support
@ 2020-10-10 6:49 François Perrad
2020-10-10 19:11 ` Baruch Siach
0 siblings, 1 reply; 9+ messages in thread
From: François Perrad @ 2020-10-10 6:49 UTC (permalink / raw)
To: u-boot
With 2020.07 (or 2020.04 or 2020.10), something goes wrong on this board.
I think it is related to
https://gitlab.denx.de/u-boot/u-boot/-/commit/6c3fbf3e456c49c2f43c0c286106a0d4b099b67b
2020.01 works fine with mmc0 (mmc0 is current device)
2020.07 fails with mmc1
both versions are built in the Builroot environment,
and I use a Micro SD with the Cubox.
Here, the working version 2020.01
U-Boot SPL 2020.01 (Oct 09 2020 - 22:28:05 +0200)
Trying to boot from MMC1
U-Boot 2020.01 (Oct 09 2020 - 22:28:05 +0200)
CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 30C
Reset cause: POR
Board: MX6 Cubox-i
DRAM: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default
environment
No panel detected: default to HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Net: FEC
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
336 bytes read in 106 ms (2.9 KiB/s)
## Executing script at 12000000
36612 bytes read in 121 ms (294.9 KiB/s)
8552176 bytes read in 652 ms (12.5 MiB/s)
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800bf03
Starting kernel ...
Now, with the version 2020.07
U-Boot SPL 2020.07 (Oct 06 2020 - 13:33:44 +0200)
WDT: Not found!
Trying to boot from MMC1
U-Boot 2020.07 (Oct 06 2020 - 13:33:44 +0200)
CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 36C
Reset cause: POR
Board: MX6 Cubox-i
DRAM: 512 MiB
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default
environment
No panel detected: default to HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Net:
Warning: ethernet at 2188000 using MAC address from ROM
eth0: ethernet at 2188000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
336 bytes read in 12 ms (27.3 KiB/s)
## Executing script at 12000000
SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc2(part 0) is current device
** No partition table - mmc 2 **
No SATA device found!
starting USB...
Fran?ois
^ permalink raw reply [flat|nested] 9+ messages in thread
* [BUG] mx6cuboxi : broken MMC support
2020-10-10 6:49 [BUG] mx6cuboxi : broken MMC support François Perrad
@ 2020-10-10 19:11 ` Baruch Siach
2020-10-10 19:23 ` Fabio Estevam
2020-10-11 8:07 ` François Perrad
0 siblings, 2 replies; 9+ messages in thread
From: Baruch Siach @ 2020-10-10 19:11 UTC (permalink / raw)
To: u-boot
Hi Fran?ois
On Sat, Oct 10 2020, Fran?ois Perrad wrote:
> With 2020.07 (or 2020.04 or 2020.10), something goes wrong on this board.
> I think it is related to
> https://gitlab.denx.de/u-boot/u-boot/-/commit/6c3fbf3e456c49c2f43c0c286106a0d4b099b67b
>
> 2020.01 works fine with mmc0 (mmc0 is current device)
> 2020.07 fails with mmc1
> both versions are built in the Builroot environment,
> and I use a Micro SD with the Cubox.
>
> Here, the working version 2020.01
>
> U-Boot SPL 2020.01 (Oct 09 2020 - 22:28:05 +0200)
> Trying to boot from MMC1
>
>
> U-Boot 2020.01 (Oct 09 2020 - 22:28:05 +0200)
>
> CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
> CPU: Commercial temperature grade (0C to 95C) at 30C
> Reset cause: POR
> Board: MX6 Cubox-i
> DRAM: 512 MiB
> MMC: FSL_SDHC: 0, FSL_SDHC: 1
> Loading Environment from MMC... *** Warning - bad CRC, using default
> environment
>
> No panel detected: default to HDMI
> Display: HDMI (1024x768)
> In: serial
> Out: serial
> Err: serial
> Net: FEC
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> Found U-Boot script /boot/boot.scr
> 336 bytes read in 106 ms (2.9 KiB/s)
> ## Executing script at 12000000
> 36612 bytes read in 121 ms (294.9 KiB/s)
> 8552176 bytes read in 652 ms (12.5 MiB/s)
> ## Flattened Device Tree blob at 18000000
> Booting using the fdt blob at 0x18000000
> Using Device Tree in place at 18000000, end 1800bf03
>
> Starting kernel ...
The 'boot.scr' script here is board/solidrun/mx6cubox/boot.scr.txt from
the Buildroot repo:
setenv finduuid "part uuid mmc 0:1 uuid"
run finduuid
run findfdt
setenv bootargs "console=ttymxc0,115200 root=PARTUUID=${uuid} rootwait rootfstype=ext4"
load mmc 0:1 ${fdt_addr} boot/${fdtfile}
load mmc 0:1 ${loadaddr} boot/zImage
bootz ${loadaddr} - ${fdt_addr}
Is that correct?
> Now, with the version 2020.07
>
> U-Boot SPL 2020.07 (Oct 06 2020 - 13:33:44 +0200)
> WDT: Not found!
> Trying to boot from MMC1
>
>
> U-Boot 2020.07 (Oct 06 2020 - 13:33:44 +0200)
>
> CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
> CPU: Commercial temperature grade (0C to 95C) at 36C
> Reset cause: POR
> Board: MX6 Cubox-i
> DRAM: 512 MiB
> MMC: FSL_SDHC: 1, FSL_SDHC: 2
> Loading Environment from MMC... *** Warning - bad CRC, using default
> environment
>
> No panel detected: default to HDMI
> Display: HDMI (1024x768)
> In: serial
> Out: serial
> Err: serial
> Net:
> Warning: ethernet at 2188000 using MAC address from ROM
> eth0: ethernet at 2188000
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc1 is current device
> Scanning mmc 1:1...
This might be the cause of the problem. The script listed above
hardcodes "mmc 0:1". Changing that to "mmc 1:1" might fix this issue.
baruch
> Found U-Boot script /boot/boot.scr
> 336 bytes read in 12 ms (27.3 KiB/s)
> ## Executing script at 12000000
> SCRIPT FAILED: continuing...
> switch to partitions #0, OK
> mmc2(part 0) is current device
> ** No partition table - mmc 2 **
> No SATA device found!
> starting USB...
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
^ permalink raw reply [flat|nested] 9+ messages in thread* [BUG] mx6cuboxi : broken MMC support
2020-10-10 19:11 ` Baruch Siach
@ 2020-10-10 19:23 ` Fabio Estevam
2020-10-10 19:45 ` Baruch Siach
2020-10-11 8:07 ` François Perrad
1 sibling, 1 reply; 9+ messages in thread
From: Fabio Estevam @ 2020-10-10 19:23 UTC (permalink / raw)
To: u-boot
Hi Baruch,
On Sat, Oct 10, 2020 at 4:11 PM Baruch Siach <baruch@tkos.co.il> wrote:
> This might be the cause of the problem. The script listed above
> hardcodes "mmc 0:1". Changing that to "mmc 1:1" might fix this issue.
Wouldn't this break the HummingBoard variants? Or is this safe for all
Cubox-i and HummingBoard?
Thanks,
Fabio Estevam
^ permalink raw reply [flat|nested] 9+ messages in thread
* [BUG] mx6cuboxi : broken MMC support
2020-10-10 19:23 ` Fabio Estevam
@ 2020-10-10 19:45 ` Baruch Siach
2020-10-11 8:13 ` Peter Robinson
0 siblings, 1 reply; 9+ messages in thread
From: Baruch Siach @ 2020-10-10 19:45 UTC (permalink / raw)
To: u-boot
Hi Fabio,
On Sat, Oct 10 2020, Fabio Estevam wrote:
> On Sat, Oct 10, 2020 at 4:11 PM Baruch Siach <baruch@tkos.co.il> wrote:
>
>> This might be the cause of the problem. The script listed above
>> hardcodes "mmc 0:1". Changing that to "mmc 1:1" might fix this issue.
>
> Wouldn't this break the HummingBoard variants? Or is this safe for all
> Cubox-i and HummingBoard?
The SD card is attached to the same MMC peripheral on both Cubox-i and
Hummingboard variants (usdhc2). As I understand, the move to DT probe
changed mmc devices enumeration for all variants that U-Boot mx6cuboxi
board code supports.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
^ permalink raw reply [flat|nested] 9+ messages in thread* [BUG] mx6cuboxi : broken MMC support
2020-10-10 19:45 ` Baruch Siach
@ 2020-10-11 8:13 ` Peter Robinson
0 siblings, 0 replies; 9+ messages in thread
From: Peter Robinson @ 2020-10-11 8:13 UTC (permalink / raw)
To: u-boot
On Sat, Oct 10, 2020 at 8:48 PM Baruch Siach <baruch@tkos.co.il> wrote:
>
> Hi Fabio,
>
> On Sat, Oct 10 2020, Fabio Estevam wrote:
> > On Sat, Oct 10, 2020 at 4:11 PM Baruch Siach <baruch@tkos.co.il> wrote:
> >
> >> This might be the cause of the problem. The script listed above
> >> hardcodes "mmc 0:1". Changing that to "mmc 1:1" might fix this issue.
> >
> > Wouldn't this break the HummingBoard variants? Or is this safe for all
> > Cubox-i and HummingBoard?
>
> The SD card is attached to the same MMC peripheral on both Cubox-i and
> Hummingboard variants (usdhc2). As I understand, the move to DT probe
> changed mmc devices enumeration for all variants that U-Boot mx6cuboxi
> board code supports.
For reference I have a Hummingboard2 (SoM rev 1.5) and it works fine
on 2020.10 (and from memory also with 2020.07).
Peter
^ permalink raw reply [flat|nested] 9+ messages in thread
* [BUG] mx6cuboxi : broken MMC support
2020-10-10 19:11 ` Baruch Siach
2020-10-10 19:23 ` Fabio Estevam
@ 2020-10-11 8:07 ` François Perrad
2020-10-11 14:18 ` Fabio Estevam
1 sibling, 1 reply; 9+ messages in thread
From: François Perrad @ 2020-10-11 8:07 UTC (permalink / raw)
To: u-boot
Le sam. 10 oct. 2020 ? 21:18, Baruch Siach <baruch@tkos.co.il> a ?crit :
> Hi Fran?ois
>
> On Sat, Oct 10 2020, Fran?ois Perrad wrote:
> > With 2020.07 (or 2020.04 or 2020.10), something goes wrong on this board.
> > I think it is related to
> >
> https://gitlab.denx.de/u-boot/u-boot/-/commit/6c3fbf3e456c49c2f43c0c286106a0d4b099b67b
> >
> > 2020.01 works fine with mmc0 (mmc0 is current device)
> > 2020.07 fails with mmc1
> > both versions are built in the Builroot environment,
> > and I use a Micro SD with the Cubox.
> >
> > Here, the working version 2020.01
> >
> > U-Boot SPL 2020.01 (Oct 09 2020 - 22:28:05 +0200)
> > Trying to boot from MMC1
> >
> >
> > U-Boot 2020.01 (Oct 09 2020 - 22:28:05 +0200)
> >
> > CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
> > CPU: Commercial temperature grade (0C to 95C) at 30C
> > Reset cause: POR
> > Board: MX6 Cubox-i
> > DRAM: 512 MiB
> > MMC: FSL_SDHC: 0, FSL_SDHC: 1
> > Loading Environment from MMC... *** Warning - bad CRC, using default
> > environment
> >
> > No panel detected: default to HDMI
> > Display: HDMI (1024x768)
> > In: serial
> > Out: serial
> > Err: serial
> > Net: FEC
> > Hit any key to stop autoboot: 0
> > switch to partitions #0, OK
> > mmc0 is current device
> > Scanning mmc 0:1...
> > Found U-Boot script /boot/boot.scr
> > 336 bytes read in 106 ms (2.9 KiB/s)
> > ## Executing script at 12000000
> > 36612 bytes read in 121 ms (294.9 KiB/s)
> > 8552176 bytes read in 652 ms (12.5 MiB/s)
> > ## Flattened Device Tree blob at 18000000
> > Booting using the fdt blob at 0x18000000
> > Using Device Tree in place at 18000000, end 1800bf03
> >
> > Starting kernel ...
>
> The 'boot.scr' script here is board/solidrun/mx6cubox/boot.scr.txt from
> the Buildroot repo:
>
> setenv finduuid "part uuid mmc 0:1 uuid"
> run finduuid
> run findfdt
> setenv bootargs "console=ttymxc0,115200 root=PARTUUID=${uuid} rootwait
> rootfstype=ext4"
> load mmc 0:1 ${fdt_addr} boot/${fdtfile}
> load mmc 0:1 ${loadaddr} boot/zImage
> bootz ${loadaddr} - ${fdt_addr}
>
> Is that correct?
>
Yes, I use this script from Buildroot.
>
> > Now, with the version 2020.07
> >
> > U-Boot SPL 2020.07 (Oct 06 2020 - 13:33:44 +0200)
> > WDT: Not found!
> > Trying to boot from MMC1
> >
> >
> > U-Boot 2020.07 (Oct 06 2020 - 13:33:44 +0200)
> >
> > CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
> > CPU: Commercial temperature grade (0C to 95C) at 36C
> > Reset cause: POR
> > Board: MX6 Cubox-i
> > DRAM: 512 MiB
> > MMC: FSL_SDHC: 1, FSL_SDHC: 2
> > Loading Environment from MMC... *** Warning - bad CRC, using default
> > environment
> >
> > No panel detected: default to HDMI
> > Display: HDMI (1024x768)
> > In: serial
> > Out: serial
> > Err: serial
> > Net:
> > Warning: ethernet at 2188000 using MAC address from ROM
> > eth0: ethernet at 2188000
> > Hit any key to stop autoboot: 0
> > switch to partitions #0, OK
> > mmc1 is current device
> > Scanning mmc 1:1...
>
> This might be the cause of the problem. The script listed above
> hardcodes "mmc 0:1". Changing that to "mmc 1:1" might fix this issue.
>
>
After changing the 3 occurrences of "mmc 0:1",the fdt file and kernel are
not correctly loaded.
(nothing happens after the message "Starting kernel ...")
Here the full log :
U-Boot SPL 2020.07 (Oct 11 2020 - 09:41:04 +0200)
WDT: Not found!
Trying to boot from MMC1
U-Boot 2020.07 (Oct 11 2020 - 09:41:04 +0200)
CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 38C
Reset cause: POR
Board: MX6 Cubox-i
DRAM: 512 MiB
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default
environment
No panel detected: default to HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Net:
Warning: ethernet at 2188000 using MAC address from ROM
eth0: ethernet at 2188000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
336 bytes read in 13 ms (24.4 KiB/s)
## Executing script at 12000000
8552176 bytes read in 427 ms (19.1 MiB/s)
ERROR: Did not find a cmdline Flattened Device Tree
Starting kernel ...
> baruch
>
> > Found U-Boot script /boot/boot.scr
> > 336 bytes read in 12 ms (27.3 KiB/s)
> > ## Executing script at 12000000
> > SCRIPT FAILED: continuing...
> > switch to partitions #0, OK
> > mmc2(part 0) is current device
> > ** No partition table - mmc 2 **
> > No SATA device found!
> > starting USB...
>
> --
> ~. .~ Tk Open
> Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
> - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>
^ permalink raw reply [flat|nested] 9+ messages in thread* [BUG] mx6cuboxi : broken MMC support
2020-10-11 8:07 ` François Perrad
@ 2020-10-11 14:18 ` Fabio Estevam
2020-10-11 15:27 ` François Perrad
0 siblings, 1 reply; 9+ messages in thread
From: Fabio Estevam @ 2020-10-11 14:18 UTC (permalink / raw)
To: u-boot
Hi Fran?ois,
On Sun, Oct 11, 2020 at 5:08 AM Fran?ois Perrad
<francois.perrad@gadz.org> wrote:
> After changing the 3 occurrences of "mmc 0:1",the fdt file and kernel are not correctly loaded.
> (nothing happens after the message "Starting kernel ...")
>
> Here the full log :
>
> U-Boot SPL 2020.07 (Oct 11 2020 - 09:41:04 +0200)
> WDT: Not found!
> Trying to boot from MMC1
>
>
> U-Boot 2020.07 (Oct 11 2020 - 09:41:04 +0200)
>
> CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
> CPU: Commercial temperature grade (0C to 95C) at 38C
> Reset cause: POR
> Board: MX6 Cubox-i
> DRAM: 512 MiB
> MMC: FSL_SDHC: 1, FSL_SDHC: 2
> Loading Environment from MMC... *** Warning - bad CRC, using default environment
>
> No panel detected: default to HDMI
> Display: HDMI (1024x768)
> In: serial
> Out: serial
> Err: serial
> Net:
> Warning: ethernet at 2188000 using MAC address from ROM
> eth0: ethernet at 2188000
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc1 is current device
> Scanning mmc 1:1...
> Found U-Boot script /boot/boot.scr
> 336 bytes read in 13 ms (24.4 KiB/s)
> ## Executing script at 12000000
> 8552176 bytes read in 427 ms (19.1 MiB/s)
> ERROR: Did not find a cmdline Flattened Device Tree
>
> Starting kernel ...
I don't have access to a mx6cubox-i at the moment.
Does it boot if you manually if you reach the U-Boot prompt and do:
mmc dev 1
setenv finduuid "part uuid mmc 1:1 uuid"
run finduuid
run findfdt
setenv bootargs "console=ttymxc0,115200 root=PARTUUID=${uuid} rootwait
rootfstype=ext4"
saveenv
load mmc 1:1 ${fdt_addr} boot/${fdtfile}
load mmc1:1 ${loadaddr} boot/zImage
bootz ${loadaddr} - ${fdt_addr}
Thanks,
Fabio Estevam
^ permalink raw reply [flat|nested] 9+ messages in thread* [BUG] mx6cuboxi : broken MMC support
2020-10-11 14:18 ` Fabio Estevam
@ 2020-10-11 15:27 ` François Perrad
2020-10-11 15:43 ` Fabio Estevam
0 siblings, 1 reply; 9+ messages in thread
From: François Perrad @ 2020-10-11 15:27 UTC (permalink / raw)
To: u-boot
Le dim. 11 oct. 2020 ? 16:18, Fabio Estevam <festevam@gmail.com> a ?crit :
> Hi Fran?ois,
>
> On Sun, Oct 11, 2020 at 5:08 AM Fran?ois Perrad
> <francois.perrad@gadz.org> wrote:
>
> > After changing the 3 occurrences of "mmc 0:1",the fdt file and kernel
> are not correctly loaded.
> > (nothing happens after the message "Starting kernel ...")
> >
> > Here the full log :
> >
> > U-Boot SPL 2020.07 (Oct 11 2020 - 09:41:04 +0200)
> > WDT: Not found!
> > Trying to boot from MMC1
> >
> >
> > U-Boot 2020.07 (Oct 11 2020 - 09:41:04 +0200)
> >
> > CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
> > CPU: Commercial temperature grade (0C to 95C) at 38C
> > Reset cause: POR
> > Board: MX6 Cubox-i
> > DRAM: 512 MiB
> > MMC: FSL_SDHC: 1, FSL_SDHC: 2
> > Loading Environment from MMC... *** Warning - bad CRC, using default
> environment
> >
> > No panel detected: default to HDMI
> > Display: HDMI (1024x768)
> > In: serial
> > Out: serial
> > Err: serial
> > Net:
> > Warning: ethernet at 2188000 using MAC address from ROM
> > eth0: ethernet at 2188000
> > Hit any key to stop autoboot: 0
> > switch to partitions #0, OK
> > mmc1 is current device
> > Scanning mmc 1:1...
> > Found U-Boot script /boot/boot.scr
> > 336 bytes read in 13 ms (24.4 KiB/s)
> > ## Executing script at 12000000
> > 8552176 bytes read in 427 ms (19.1 MiB/s)
> > ERROR: Did not find a cmdline Flattened Device Tree
> >
> > Starting kernel ...
>
> I don't have access to a mx6cubox-i at the moment.
>
> Does it boot if you manually if you reach the U-Boot prompt and do:
>
> mmc dev 1
> setenv finduuid "part uuid mmc 1:1 uuid"
> run finduuid
> run findfdt
> setenv bootargs "console=ttymxc0,115200 root=PARTUUID=${uuid} rootwait
> rootfstype=ext4"
> saveenv
> load mmc 1:1 ${fdt_addr} boot/${fdtfile}
> load mmc1:1 ${loadaddr} boot/zImage
> bootz ${loadaddr} - ${fdt_addr}
>
> Thanks,
>
>
In interactive mode, I found a mismatch with ftdfile.
Now, it works.
And I could update MX6 Cubox on Buildroot.
Many thanks.
Fran?ois
> Fabio Estevam
>
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2020-10-11 15:43 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-10-10 6:49 [BUG] mx6cuboxi : broken MMC support François Perrad
2020-10-10 19:11 ` Baruch Siach
2020-10-10 19:23 ` Fabio Estevam
2020-10-10 19:45 ` Baruch Siach
2020-10-11 8:13 ` Peter Robinson
2020-10-11 8:07 ` François Perrad
2020-10-11 14:18 ` Fabio Estevam
2020-10-11 15:27 ` François Perrad
2020-10-11 15:43 ` Fabio Estevam
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.