CUBOX snapshots working?

Ian Lepore ian at freebsd.org
Tue Sep 26 14:27:15 UTC 2017


On Mon, 2017-09-25 at 21:39 -0600, Brett Glass wrote:
> While waiting for the new SolidRun board I just ordered to come in, 
> I decided to tinker with one of their older products: a CUBOX 
> I2U-300-D. I downloaded the latest CUBOX snapshot (12.0 r323729), 
> burned it onto an SD card, dropped the card into the box, plugged 
> in an HDMI monitor, and watched the onboard serial port as I 
> applied power. This is what I saw (on the serial port; the monitor 
> stayed blank):
> 
> U-Boot SPL 2017.07 (Sep 19 2017 - 23:14:46)
> Trying to boot from MMC1
> 
> 
> U-Boot 2017.07 (Sep 19 2017 - 23:14:46 +0000)
> 
> CPU:   Freescale i.MX6D rev1.2 996 MHz (running at 792 MHz)
> CPU:   Extended Commercial temperature grade (-20C to 105C) at 14C
> Reset cause: POR
> Board: MX6 Cubox-i
> DRAM:  1 GiB
> MMC:   FSL_SDHC: 0
> *** Warning - bad CRC, using default environment
> 
> No panel detected: default to HDMI
> Display: HDMI (1024x768)
> In:    serial
> Out:   serial
> Err:   serial
> Net:   FEC
> Hit any key to stop autoboot:  0
> ## Error: "boot¦md_mmc0" not defined
> ## Error: "boot¦md_usb0" not defined
> ## Error: "boot¦md_pxe" not defined
> ## Error: "boot¦md_dhcp" not defined
> 
> ...and of course it didn't boot. Without the HDMI monitor plugged 
> in, it failed with different errors, but still did not boot.
> 
> What's the last good snapshot?
> 
> --Brett Glass

I just DLed and booted that snapshot on my Cubox-4i without any
problems.  As near as I can tell, the only difference is you've got the
dual-core chip and mine has the quad.

The same u-boot should work for both.  At least, that was the case when
using the vendor-provided u-boot; the images are now built from
mainline u-boot.  The output you provided does show that it detected
the right kind of chip and amount of ram, so I think it should support
both flavors of cubox.

-- Ian


More information about the freebsd-arm mailing list