Date: Tue, 26 Sep 2017 08:21:13 -0600 From: Ian Lepore <ian@freebsd.org> To: Brett Glass <brett@lariat.net>, freebsd-arm@freebsd.org Subject: Re: CUBOX snapshots working? Message-ID: <1506435673.73082.129.camel@freebsd.org> In-Reply-To: <201709260339.VAA16701@mail.lariat.net> References: <201709260339.VAA16701@mail.lariat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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,=A0 > I decided to tinker with one of their older products: a CUBOX=A0 > I2U-300-D. I downloaded the latest CUBOX snapshot (12.0 r323729),=A0 > burned it onto an SD card, dropped the card into the box, plugged=A0 > in an HDMI monitor, and watched the onboard serial port as I=A0 > applied power. This is what I saw (on the serial port; the monitor=A0 > stayed blank): >=20 > U-Boot SPL 2017.07 (Sep 19 2017 - 23:14:46) > Trying to boot from MMC1 >=20 >=20 > U-Boot 2017.07 (Sep 19 2017 - 23:14:46 +0000) >=20 > CPU:=A0=A0=A0Freescale i.MX6D rev1.2 996 MHz (running at 792 MHz) > CPU:=A0=A0=A0Extended Commercial temperature grade (-20C to 105C) at 14= C > Reset cause: POR > Board: MX6 Cubox-i > DRAM:=A0=A01 GiB > MMC:=A0=A0=A0FSL_SDHC: 0 > *** Warning - bad CRC, using default environment >=20 > No panel detected: default to HDMI > Display: HDMI (1024x768) > In:=A0=A0=A0=A0serial > Out:=A0=A0=A0serial > Err:=A0=A0=A0serial > Net:=A0=A0=A0FEC > Hit any key to stop autoboot:=A0=A00 > ## Error: "boot=A6md_mmc0" not defined > ## Error: "boot=A6md_usb0" not defined > ## Error: "boot=A6md_pxe" not defined > ## Error: "boot=A6md_dhcp" not defined >=20 > ...and of course it didn't boot. Without the HDMI monitor plugged=A0 > in, it failed with different errors, but still did not boot. >=20 > What's the last good snapshot? >=20 > --Brett Glass I just DLed and booted that snapshot on my Cubox-4i without any problems. =A0As 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. =A0At least, that was the case when using the vendor-provided u-boot; the images are now built from mainline u-boot. =A0The 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1506435673.73082.129.camel>