Odd messages booting Cubox-i4 Pro "imx-gpc 20dc000.gpc: failed to get pu regulator: -517" and "ERROR: could not get clock /usdhc1_pwrseq:ext_clock(0)"
Does anyone know what the error messages
Does anybody know what is causing the subject error messages?
It almost looks like the DTB is claiming a couple of devices that don't exist on this hardware... But I don't understand enough of that process to be sure.
Anybody got some clues?
I've attached the first several lines of the boot log, up-to and including the error messages, in hopes that they may have some information about the hardware.
Thanks!
Rick
> U-Boot 2015.10+dfsg1-3 (Nov 24 2015 - 22:14:29 +0000)
>
> CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
> CPU: Extended Commercial temperature grade (-20C to 105C) at 29C
> Reset cause: WDOG
> Board: MX6 Cubox-i
> DRAM: 2 GiB
> MMC: FSL_SDHC: 0
> 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.scr
> 1474 bytes read in 32 ms (44.9 KiB/s)
> ## Executing script at 12000000
> 3415976 bytes read in 371 ms (8.8 MiB/s)
> 33984 bytes read in 98 ms (337.9 KiB/s)
> 17496691 bytes read in 1231 ms (13.6 MiB/s)
> Booting Debian 4.3.0-1-armmp from mmc 0:1...
> Kernel image @ 0x12000000 [ 0x000000 - 0x341fa8 ]
> ## Flattened Device Tree blob at 18000000
> Booting using the fdt blob at 0x18000000
> Using Device Tree in place at 18000000, end 1800b4bf
>
> Starting kernel ...
>
> [ 0.098389] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
>
> [ 1.485042] imx-sdma 20ec000.sdma: firmware: failed to load imx/sdma/sdma-imx6q.bin (-2)
> [ 1.544474] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> [ 1.551844] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> Loading, please wait...
> [ 2.221380] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> [ 2.257486] ERROR: could not get clock /usdhc1_pwrseq:ext_clock(0)
>
Reply to: