From owner-freebsd-arm@FreeBSD.ORG Sat Feb 23 22:01:47 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F2795448 for ; Sat, 23 Feb 2013 22:01:47 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id D26D377E for ; Sat, 23 Feb 2013 22:01:46 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r1NM1i3U011783; Sat, 23 Feb 2013 22:01:44 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id 7hvd2v6r7u5vtqxde23rhqfw96; Sat, 23 Feb 2013 22:01:44 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: Unable to copy DTB into module directory Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Tim Kientzle In-Reply-To: Date: Sat, 23 Feb 2013 14:01:42 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <3A8BA2BC-6707-4309-B6E3-5B15712ED67D@kientzle.com> To: Alie Tan X-Mailer: Apple Mail (2.1283) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Feb 2013 22:01:48 -0000 > >> > >> I just built RasPi image and keeps getting this message: > >> > >> "unable to copy DTB into module directory" > >> > >> then the raspi reboot again and again. > > > > Try backing out r247045 and see if that fixes > > it for you. > > >=20 > Fyi, Reverting r247045 didn't help my proble :-( > Sorry for incomplete information. Reverting r247045 removes "unable to = copy DTB into module directory" error message but my raspi still keeps = rebooting after boot loader I believe that r247201 fixes the bug I introduced with r247045 and should allow RPi to boot cleanly again. (Though I seem to have some other problem locally that I need to track down=85) This should also make it possible to have U-Boot pick up the FDT from the RPi boot code (by adding "fdt addr 0x100" to the right place in uEnv.txt or the u-boot loader script) and remove that command from loader.rc. If U-Boot knows about the FDT, then ubldr should pick it up automatically now. I've made the necessary adjustment to my build scripts; it should be a very small tweak to Oleksandr's as well. Let me know if this works for you. Tim