From owner-freebsd-arm@freebsd.org Tue Sep 26 03:40:05 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 735B6E2DDDC for ; Tue, 26 Sep 2017 03:40:05 +0000 (UTC) (envelope-from brett@lariat.net) Received: from mail.lariat.net (mail.lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id 42F307492B for ; Tue, 26 Sep 2017 03:40:04 +0000 (UTC) (envelope-from brett@lariat.net) Received: from Toshi.lariat.net (IDENT:ppp1000.lariat.net@localhost [127.0.0.1]) by mail.lariat.net (8.9.3/8.9.3) with ESMTP id VAA16701 for ; Mon, 25 Sep 2017 21:39:55 -0600 (MDT) Message-Id: <201709260339.VAA16701@mail.lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 25 Sep 2017 21:39:38 -0600 To: freebsd-arm@freebsd.org From: Brett Glass Subject: CUBOX snapshots working? Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit 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 03:40:05 -0000 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