[U-Boot] Regression in 2019.01-rc2 for eMMC boot on mxs board?

[Michael Heimpold]

Hi,

I'm currently testing latest git tree U-Boot on an I2SE Duckbill 2 device and 
it seems that I've found a regression compared to v2018.11:

Such a Duckbill device is equipped with a NXP i.MX28 CPU and boots from eMMC.
The eMMC has a typical DOS MBR with a special boot loader partition where
U-Boot is stored in. Then U-Boot loads kernel and device tree from an ext 
partition.
When I run latest git U-Boot (see following trace for commit hash), then the
normal boot procedure fails (fallbacks to netboot, fails again) and gives me a 
prompt on Debug UART, see following trace.
The funny part is, that when typing "mmc part" command to list partitions
on eMMC and then calling "boot" again, all works and Linux boot succceeds.

Any quick ideas? Or should I start bi-secting tomorrow...

--snip--
HTLLCLLC

U-Boot 2019.01-rc2-00199-g1cd7b8f120 (Jan 04 2019 - 23:28:55 +0100)

CPU:   Freescale i.MX28 rev1.2 at 454 MHz
BOOT:  SSP SD/MMC #0, 3V3
DRAM:  128 MiB
MMC:   MXS MMC: 0
Loading Environment from MMC... MMC0: Command 8 timeout (status 0xe0384020)
MMC0: Command 55 timeout (status 0xe0284020)
OK
In:    serial
Out:   serial
Err:   serial
Board: I2SE Duckbill 2
Net:   FEC0 [PRIME]
Autobooting in 1 seconds, press <c> to stop
MMC0: Command 8 timeout (status 0xe0384020)
MMC0: Command 55 timeout (status 0xe0284020)
switch to partitions #0, OK
mmc0(part 0) is current device
MMC0: Command 8 timeout (status 0xe0384020)
MMC0: Command 55 timeout (status 0xe0284020)
** No partition table - mmc 0 **
Booting from net ...
BOOTP broadcast 1
DHCP client bound to address 192.168.8.127 (6 ms)
Using FEC0 device
TFTP from server 192.168.8.253; our IP address is 192.168.8.127
Filename 'zImage'.
Load address: 0x42000000
Loading: *
TFTP error: 'File not found' (1)
Not retrying...
BOOTP broadcast 1
DHCP client bound to address 192.168.8.127 (6 ms)
Using FEC0 device
TFTP from server 192.168.8.253; our IP address is 192.168.8.127
Filename 'imx28-duckbill-2.dtb'.
Load address: 0x41000000
Loading: *
TFTP error: 'File not found' (1)
Not retrying...
Bad Linux ARM zImage magic!
=> mmc part

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            16384           5452574f-01     53 Boot
  2     20480           3731456         5452574f-02     83
=> boot
MMC0: Command 8 timeout (status 0xe0384020)
MMC0: Command 55 timeout (status 0xe0284020)
switch to partitions #0, OK
mmc0(part 0) is current device
MMC0: Command 8 timeout (status 0xe0384020)
MMC0: Command 55 timeout (status 0xe0284020)
3437936 bytes read in 1019 ms (3.2 MiB/s)
Booting from mmc ...
19479 bytes read in 111 ms (170.9 KiB/s)
Kernel image @ 0x42000000 [ 0x000000 - 0x347570 ]
## Flattened Device Tree blob at 41000000
   Booting using the fdt blob at 0x41000000
   Loading Device Tree to 47b80000, end 47b87c16 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
--snap--

Regards,
Michael