From owner-freebsd-arm@freebsd.org Tue Sep 26 14:27:15 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B575FE0D1B4 for ; Tue, 26 Sep 2017 14:27:15 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from nov-007-i577.relay.mailchannels.net (nov-007-i577.relay.mailchannels.net [46.232.183.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 59B1667C00 for ; Tue, 26 Sep 2017 14:27:13 +0000 (UTC) (envelope-from ian@freebsd.org) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 44FEE5C1D3A for ; Tue, 26 Sep 2017 14:21:21 +0000 (UTC) Received: from outbound1a.eu.mailhop.org (unknown [100.96.147.57]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id 269355C1848 for ; Tue, 26 Sep 2017 14:21:19 +0000 (UTC) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [172.20.67.103]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Tue, 26 Sep 2017 14:21:21 +0000 X-MC-Relay: Forwarding X-MailChannels-SenderId: _forwarded-from|73.78.92.27 X-MailChannels-Auth-Id: duocircle X-Glossy-Zesty: 250675fc474f9ff0_1506435680673_1544152468 X-MC-Loop-Signature: 1506435680673:952194870 X-MC-Ingress-Time: 1506435680672 X-MHO-User: f4a222b1-a2c5-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id f4a222b1-a2c5-11e7-a893-25625093991c; Tue, 26 Sep 2017 14:21:16 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v8QELDcv001208; Tue, 26 Sep 2017 08:21:14 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1506435673.73082.129.camel@freebsd.org> Subject: Re: CUBOX snapshots working? From: Ian Lepore To: Brett Glass , freebsd-arm@freebsd.org Date: Tue, 26 Sep 2017 08:21:13 -0600 In-Reply-To: <201709260339.VAA16701@mail.lariat.net> References: <201709260339.VAA16701@mail.lariat.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 14:27:15 -0000 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