imx8mq allocation issue

[Heiko Thiery]

Hi Angus,

Am Fr., 9. Sept. 2022 um 18:38 Uhr schrieb Angus Ainslie <angus at akkea.ca>:
>
> Hi Heiko,
>
> On 2022-09-09 07:45, Heiko Thiery wrote:
> > Hi Angus,
> >
> > Am Fr., 9. Sept. 2022 um 16:43 Uhr schrieb Angus Ainslie
> > <angus at akkea.ca>:
> >>
> >> Hi Heiko,
> >>
> >> The librem5 (imx8mq) is able to boot using these [1] patches on top of
> >> u-boot-imx-20220729.
> >>
> >> I believe the change that fixed the allocation issue for me was
> >>
> >> CONFIG_SPL_MAX_SIZE=0x25000
> >
> > The imx8mq_evk board boots also but when enabling the DEBUG_UART the
> > output shown in my previous mail is seen. Could you also try to enable
> > the DEBUG UART please?
> >
> > --
> > Heiko
> >
>
> Yeah it still boots
>
> CUK**SH022.10-rc1-00013-g1b8b4362ac-dirty (Sep 09 2022 - 09:24:49 -0700)
> Initializing pinmux
> Initializing ECSPI
> Initializing DRAM
> SDRAM val 2
> SDRAM val 3
> SDRAM val 3
> spl_dram_init: LPDDR4 3 GiB
> USB Boot
> Trying to boot from USB SDP
> board_usb_init : index 0 type 1
> SDP: initialize...
> SDP: handle requests...
> Downloading file of size 946628 to 0x40400000... done
> Jumping to header at 0x40400000
> Header Tag is not an IMX image
> Found header at 0x40410c00
> board_usb_cleanup : 0
> ?2~3
>
> U-Boot 2022.10-rc1-00013-g1b8b4362ac-dirty (Sep 09 2022 - 09:24:49
> -0700)
>
> CPU:   Freescale i.MX8MQ rev2.1 1500 MHz (running at 1000 MHz)
> CPU:   Commercial temperature grade (0C to 95C) at 32C
> Reset cause: POR
> Model: Purism Librem 5r4
> DRAM:  3 GiB
> clk_register: failed to get <NULL> device (parent of ckil)
> clk_register: failed to get <NULL> device (parent of clock-osc-27m)
> clk_register: failed to get <NULL> device (parent of sys1_pll)
> clk_register: failed to get <NULL> device (parent of sys2_pll)
> clk_register: failed to get <NULL> device (parent of sys3_pll)
> Enabling regulator-hub
> tps65982 boot successful
> Core:  193 devices, 25 uclasses, devicetree: separate
> MMC:   FSL_SDHC: 0, FSL_SDHC: 1
> Loading Environment from MMC... *** Warning - bad CRC, using default
> environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Board name: librem5
> Board rev:  4
> USB Boot
> vol_down_key_pressed : 1
> Net:   No ethernet found.
> Hit any key to stop autoboot:  0
>

If this is the output with DEBUG_UART enabled then it seems the
problem is not seen on your board. As said, on the imx8mq-evk this is
seen. I also have a google coral (phanbell) that I will test.

-- 
Heiko

>
>
> >> Cheers,
> >> Angus
> >>
> >> [1]
> >> https://lore.kernel.org/u-boot/20220825134602.382775-1-angus@akkea.ca/
> >>
> >> On 2022-09-09 02:12, Heiko Thiery wrote:
> >> > HI,
> >> >
> >> > I think on the imx8mq platform we have a problem with the introduction
> >> > of the clock driver. I tried to debug the problem that the pitx-imx8m
> >> > board was not able to start for some time. I was wondering why the
> >> > pitx-im8m doesn't work anymore although the imx8mq_evk is running.
> >> >
> >> > So I switched to the imx8mq_evk for counter testing. As I already
> >> > figured out in [1] also the imx8mq_evk is not able to start properly.
> >> >
> >> > On the EVK I enabled the DEBUG_UART and see the outputs below. I
> >> > suspect all imx8mq boards have this problem.
> >> >
> >> > CONFIG_DEBUG_UART_BASE=0x30860000      # for uart1
> >> > CONFIG_DEBUG_UART_CLOCK=24000000
> >> >
> >> > --- 8< ----
> >> > U-Boot SPL 2022.10-rc4-00038-ge3fce5e560-dirty (Sep 09 2022 - 10:51:29
> >> > +0200)
> >> > PMIC:  PFUZE100 ID=0x10
> >> > SEC0:  RNG instantiated
> >> > Normal Boot
> >> > Trying to boot from MMC2
> >> > clk_register: failed to get <NULL> device (parent of ckil)
> >> > clk_register: failed to get <NULL> device (parent of clock-osc-27m)
> >> > alloc space exhausted
> >> > alloc space exhausted
> >> > alloc space exhausted
> >> > alloc space exhausted
> >> > :
> >> > :
> >> > alloc space exhausted
> >> > alloc space exhausted
> >> > alloc space exhausted
> >> > alloc space exhausted
> >> > alloc space exhausted
> >> > alloc space exhausted
> >> > alloc space exhausted
> >> > alloc space exhaustedÿ
> >> >
> >> > U-Boot 2022.10-rc4-00038-ge3fce5e560-dirty (Sep 09 2022 - 10:51:29
> >> > +0200)
> >> >
> >> > CPU:   Freescale i.MX8MQ rev2.1 at 1000 MHz
> >> > Reset cause: POR
> >> > Model: NXP i.MX8MQ EVK
> >> > DRAM:  3 GiB
> >> > clk_register: failed to get <NULL> device (parent of ckil)
> >> > clk_register: failed to get <NULL> device (parent of clock-osc-27m)
> >> > clk_register: failed to get <NULL> device (parent of sys1_pll)
> >> > clk_register: failed to get <NULL> device (parent of sys2_pll)
> >> > clk_register: failed to get <NULL> device (parent of sys3_pll)
> >> > Core:  147 devices, 21 uclasses, devicetree: separate
> >> > MMC:   FSL_SDHC: 0, FSL_SDHC: 1
> >> > Loading Environment from MMC... OK
> >> > In:    serial at 30860000
> >> > Out:   serial at 30860000
> >> > Err:   serial at 30860000
> >> > SEC0:  RNG instantiated
> >> > Net:   eth0: ethernet at 30be0000
> >> > Hit any key to stop autoboot:  0
> >> > u-boot=>
> >> > --- 8< ----
> >> >
> >> > Could the maintainers of the other imx8mq boards please check if they
> >> > can confirm this?
> >> >
> >> > [1]
> >> > https://lore.kernel.org/u-boot/CAEyMn7bCaC8Y8B0mOAi72yJTHMKDJt_oe_eBznrwHh4JxXodZw@mail.gmail.com/#t
> >> >
> >> > Thanks,
> >> > Heiko