2.98.12 Won't uBoot with Variscite IMX8M on custom carrier

Product support balenaOS
1

We have a custom carrier based on the Variscite IMX8M-Mini SOM.

We specifically do NOT have the PCI-e or CAN FD pieces implemented on our carrier and in version 2.5x of BalenaOS, this has not been an issue.

I’d previously reported this on 2.71 (UART Failure after upgrading to 2.71.3+rev1 from 2.50.1+rev1 on Variscite IMX8M) and unfortunately never really got that resolved.

We were excited to see 2.98 come out so immediately we tried the new OS uboot on a board and were met with disappointment.

Uboot starts up off the SD card, but then get stuck about 4 seconds in.

Trying to boot from MMC1











[    0.133192] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[    0.141478] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -517
[    0.741205] edt_ft5x06 1-0038: touchscreen probe failed
[    0.817165] ov5640_mipi 1-003c: Read reg error: reg=300a
[    0.826291] pca953x 3-0020: failed writing register
[    0.832055] pca953x 3-0021: failed writing register
[    0.965042] imx6q-pcie 33800000.pcie: iMX8 PCIe PLL lock timeout
[    0.965047] imx6q-pcie 33800000.pcie: imx8_pcie_wait_for_phy_pll_lock failed, pcie oscillator most likely missing on carrier board. Bail out to avoid hang at boot.
[    0.965055] imx6q-pcie 33800000.pcie: imx6_pcie_host_init failed: -19.
[    0.965070] imx6q-pcie 33800000.pcie: failed to initialize host
[    0.965074] imx6q-pcie 33800000.pcie: unable to add pcie port.
[    1.433492] mmc1: error -110 whilst initialising SD card
Starting version 244.3+
[    1.650766] mmc1: error -110 whilst initialising SD card
[    1.873564] mmc1: error -110 whilst initialising SD card
[    2.103289] mmc1: error -110 whilst initialising SD card
[    3.772669] fsl-asoc-card sound-wm8904: ASoC: failed to init link HiFi: -517
[    3.803505] fsl-asoc-card sound-wm8904: ASoC: failed to init link HiFi: -517
[    3.812849] fsl-asoc-card sound-wm8904: ASoC: failed to init link HiFi: -517
[    3.823956] fsl-asoc-card sound-wm8904: ASoC: failed to init link HiFi: -517
[    3.839110] fsl-asoc-card sound-wm8904: ASoC: failed to init link HiFi: -517
[    3.847588] fsl-asoc-card sound-wm8904: ASoC: failed to init link HiFi: -517
[    3.913001] debugfs: Directory '30030000.sai' with parent 'wm8904-audio' already present!
[    4.214972] mcp251xfd spi0.1 (unnamed net_device) (uninitialized): Failed to detect MCP251xFD (osc=0x00000000).
2

Hi, what I suggest is that you build a custom OS image and debug the default device tree to boot on your custom carrier board. Once you have a working device tree we will integrate it into a future release of balenaOS. This can happen in one of two ways:

  • We have a feature in the roadmap to allow for custom selection of device trees from boot.
  • If that is not ready on time (it’s not currently been prioritised), we will create a new device tree for your custom carrier board.
4

Hi, following up on this. Did you manage to modify the device tree to boot this custom carrier board?

6

Unfortunately not. We’ve tried a the new point releases but each fails in a unique way.