From owner-freebsd-arm@freebsd.org Sun Dec 11 16:09:32 2016 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 9FFA2C729B7 for ; Sun, 11 Dec 2016 16:09:32 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7E45C1E24 for ; Sun, 11 Dec 2016 16:09:32 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7AB01C729B6; Sun, 11 Dec 2016 16:09:32 +0000 (UTC) Delivered-To: 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 7A4BBC729B5 for ; Sun, 11 Dec 2016 16:09:32 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3EDCF1E23 for ; Sun, 11 Dec 2016 16:09:32 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: by mail-oi0-x233.google.com with SMTP id v84so65981028oie.3 for ; Sun, 11 Dec 2016 08:09:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0kA1oIFJ+IybcK63QNzVo2mgo75j1gUAhcbUOiPtfFM=; b=xdPwvRUvIEJnlw6UqHrGKQYVB6GwUL2N7XJxSVIPlRyVu0oet0HwbaweLuy5KhsK1D 7x+3s8SxXucCoKSfQZTo3JOcvDk1/27258lSg1kRS93Yz5OvUqNs1YpaL09jYWmHRHVK zppgrZxX/tZJqZFMQkBPC71lBul8CU2sx0wS8bzvu/K+vtqHpYa3mD3zabSd8ZmxGabc fVkR2p8yIjlfIMvJ8UMD/Uqkh/9oy913FOSnmoCxZ6i38QHYwjC1PVeUWK4t+wkmjdbD G73oXGY0B2icjpE97CgW95+GjfaJKbmSNWKInP9dEj6KUWeotdsaZMNBhuCtZPa+RkOr mEiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0kA1oIFJ+IybcK63QNzVo2mgo75j1gUAhcbUOiPtfFM=; b=VXm2XqlYr2fkq/6kHs8wqCA02ZinuhrIRlI/7+APRn6rtoSiHF1pmRsI0IqubPrZ70 p/DOpJ9wpoD4U02rgbo3jJ0ZViL+wH/H6PgdMvi7WdzKq5h2moeLj6GjWCs9wNvlHVw8 sfvce2Ae2o3BOrrYy1mcMSKX0SyJ/MhMGyYRtD3GMaBVSznbeOg1VrWULGud1No0CaUf hhz6tuk886E5nah9oMNWQwtI+Ad20vK2ubRdLxeI9N1p9BusBagKKD++REq13WC9EnJA M3hSoO/dlH5xER8V+C36XskRQRKmJdVzsZV6ua8xDwprsA7L23GECFxho1x1fKUOZunB U3lg== X-Gm-Message-State: AKaTC02SE8IlnQnd/f2fxL0haWhofCOdrdVfJL/TDLyw4NxVVyvBUL9eQInsXRBcFQamPgLq19WSJ1k1VZfQ/Q== X-Received: by 10.157.51.104 with SMTP id u37mr52686936otd.9.1481472571503; Sun, 11 Dec 2016 08:09:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.145.33 with HTTP; Sun, 11 Dec 2016 08:09:31 -0800 (PST) In-Reply-To: <93729768-D887-4568-8686-FE691A881BC6@cs.huji.ac.il> References: <7FD12DD6-B390-4EF3-811B-391798410BC0@cs.huji.ac.il> <1480950103.1889.251.camel@freebsd.org> <93729768-D887-4568-8686-FE691A881BC6@cs.huji.ac.il> From: Ganbold Tsagaankhuu Date: Mon, 12 Dec 2016 00:09:31 +0800 Message-ID: Subject: Re: ubldr, was Re: dtb printout To: Daniel Braniss Cc: arm@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Sun, 11 Dec 2016 16:09:32 -0000 On Tue, Dec 6, 2016 at 5:17 PM, Daniel Braniss wrote: > > > On 5 Dec 2016, at 17:01, Ian Lepore wrote: > > > > On Mon, 2016-12-05 at 15:48 +0200, Daniel Braniss wrote: > >> Hi, > >> the short version: > >> is there a way to obtain the dtb from the kernel? > >> > >> the longer version: > >> I am developing on several different arm boards, rpi, rpi2, orangepi- > >> one, orange-pc, to mention > >> a few, and each one has a different u-boot, ubldr, dtb, and I keep > >> loosing track :-( > >> I find myself too often wondering which ddb file got loaded. > >> > >> cheers, > >> danny > > > > First: each one does NOT have a different ubldr. All ubldr.bin files > > are the same, they're not board-specific anymore. (The elf versions, > > ubldr without the .bin, may have a different load address in the elf > > header, but other than that, they're identical too and can actually be > > loaded at any address.) > > > > To see the contents of the dtb, use ofwdump. The output is not > > especially pretty. There is a manpage for it. > > > > To just get a quick reminder of which file was loaded, create a > > /boot/loader.rc.local (<-- .rc not .conf) that contains > > > > ubenv import fdtfile fdt_file > > > > Then in the running system you can use kenv and you'll see > > > > uboot.fdtfile=3D"bcm2835-rpi-b-rev2.dtb" > > > > Unfortunately, some u-boots use fdtfile, some use fdt_file. Grrr. > > > > You can, of course, use that ubenv import thing to pull any variable > > from the uboot environment into the kernel environment. If you just > > say ubenv import without naming a variable, you get all the vars > > (including vars that contain scripts, which is kind of messy). > > > > =E2=80=94 Ian > > > > as usual, I get more than I bargained for :-) > on rpi adding ubenv import worked, but on orange/allwinner I got a =E2=80= =98syntax > error=E2=80=99, > I tried to upgrade the ubldr, but so far i get: > > U-Boot SPL 2016.09 (Dec 05 2016 - 15:02:38) > DRAM: 1024 MiB > Trying to boot from MMC1 > > > U-Boot 2016.09 (Dec 05 2016 - 15:02:38 +0200) Allwinner Technology > > CPU: Allwinner H3 (SUN8I 1680) > Model: Xunlong Orange Pi PC > I2C: ready > DRAM: 1 GiB > WARNING: Caches not enabled > MMC: SUNXI SD/MMC: 0 > reading u-boot.env > > ** Unable to read "u-boot.env" from mmc0:1 ** > Using default environment > > In: serial > Out: serial > Err: serial > Net: phy interface0 > eth0: ethernet@1c30000 > starting USB... > USB0: USB EHCI 1.00 > USB1: USB OHCI 1.0 > USB2: USB EHCI 1.00 > USB3: USB OHCI 1.0 > USB4: USB EHCI 1.00 > USB5: USB OHCI 1.0 > scanning bus 0 for devices... 1 USB Device(s) found > scanning bus 2 for devices... 1 USB Device(s) found > scanning bus 4 for devices... 1 USB Device(s) found > Hit any key to stop autoboot: 0 > Booting from: mmc 0 ubldr.bin > reading ubldr.bin > 223912 bytes read in 53 ms (4 MiB/s) > ## No elf image at address 0x42000000 > ## Starting application at 0x42000000 ... > Did ubldr work for you? I feel like I have same problem: Booting from: mmc 0 ubldr.bin reading ubldr.bin 228276 bytes read in 67 ms (3.2 MiB/s) ## No elf image at address 0x42000000 ## Starting application at 0x42000000 ... Ganbold > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"