[U-Boot] [PATCH 55/93] arm: Remove chiliboard board

Simon Glass
2018-11-22T20:50:17Z

Hi Marcin,

On Wed, 21 Nov 2018 at 06:05, Marcin NiestrÃ³j
<m.niestroj@grinn-global.com> wrote:
>
> Hi Simon, All,
>
> Simon Glass <sjg@chromium.org> writes:
>
> > This board has not been converted to CONFIG_DM_BLK by the deadline.
> > Remove it.
>
> I just got my hands on chiliboard to start using device-model
> drivers. Unfortunately this board does not boot already on master
> branch. `git bisect` returned d0851c8937067ad396f2bdafc46d0326bf3317db
> ("blk: Call part_init() in the post_probe() method") as the first bad
> commit. It would not be a big problem if we would switch after 1-2 weeks
> anyway, but I am not sure that will happen based on the
> discussions. Anyway, it is better you know about that problem. Below you
> can find logs from boot process.
>
> After bad commit:
>
> U-Boot SPL 2018.11 (Nov 21 2018 - 13:35:44 +0100)
> Trying to boot from MMC1
>
>
> U-Boot 2018.11 (Nov 21 2018 - 13:35:44 +0100)
>
> CPU : AM335X-GP rev 2.1
> I2C: ready
> DRAM: 256 MiB
> NAND: 256 MiB
> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Loading Environment from MMC... *** Warning - bad CRC, using default environment
>
> <ethaddr> not set. Validating first E-fuse MAC
> Net: cpsw
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> ** No partition table - mmc 0 **
> ** No partition table - mmc 0 **
> Booting from nand ...
>
> Before bad commit:
>
> U-Boot SPL 2018.11 (Nov 21 2018 - 13:36:26 +0100)
> Trying to boot from MMC1
>
>
> U-Boot 2018.11 (Nov 21 2018 - 13:36:26 +0100)
>
> CPU : AM335X-GP rev 2.1
> I2C: ready
> DRAM: 256 MiB
> NAND: 256 MiB
> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Loading Environment from MMC... *** Warning - bad CRC, using default environment
>
> <ethaddr> not set. Validating first E-fuse MAC
> Net: cpsw
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> 5892272 bytes read in 370 ms (15.2 MiB/s)
> 32494 bytes read in 4 ms (7.7 MiB/s)
> ## Flattened Device Tree blob at 87800000
> Booting using the fdt blob at 0x87800000
> Loading Device Tree to 8df48000, end 8df52eed ... OK
>
> Starting kernel ...

I am not sure what is wrong. Does it hang in part_init()? It looks
like you don't have a partition table, but it should still be OK to
probe for it.

Regards,
Simon