From owner-freebsd-arm@FreeBSD.ORG Sat Mar 28 04:29:17 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D8A2E74; Sat, 28 Mar 2015 04:29:17 +0000 (UTC) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (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 ADF58A51; Sat, 28 Mar 2015 04:29:16 +0000 (UTC) Received: by labe2 with SMTP id e2so84055621lab.3; Fri, 27 Mar 2015 21:29:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+HEPsnnKja9UkvlOqg+pM4+qfiVPLCxDgwhxZGuWB4o=; b=KqhXsUiP5+O7HkXj8rRTHSxLVqmKzPlicQFWFsw2dQdeLF0Er51gupg0yTvs5Uhklc tZXiPCSKL0NuItubrnWgai/Hm6qCZsdPUUSrOibP8RcB8mr5oh+cQ2FWoj43fIFcsy7p W8MjIvc//VeQbe0gb5ra4LFn0dzcSYJoIzmzw/zVa0BfWIzyRGfAsKDMalnZYes9waI0 v+B7Bnt1E7iL4LB/HHdBlthUSipXpV9hdn69b3D5UcIhZVfRmKgTrFUP4JOB4z8eiKXX cyMCuGrQbM5wibTyHu4NnFtjqL7ImlPXXvMjf7HBngzrn6ft7BI0Usg54NSZcS7qvXtF xTlg== MIME-Version: 1.0 X-Received: by 10.152.87.46 with SMTP id u14mr20169984laz.82.1427516954650; Fri, 27 Mar 2015 21:29:14 -0700 (PDT) Received: by 10.152.37.3 with HTTP; Fri, 27 Mar 2015 21:29:14 -0700 (PDT) In-Reply-To: <1427292010.75747.2.camel@freebsd.org> References: <622469F8-C245-4E84-B5E1-FE360D3C9B4C@me.com> <215C10E1-9F47-46B6-A60B-430D7DEDA090@me.com> <1427212609.5591.10.camel@freebsd.org> <1427220117.1588.1.camel@freebsd.org> <1427292010.75747.2.camel@freebsd.org> Date: Fri, 27 Mar 2015 21:29:14 -0700 Message-ID: Subject: Re: Digi-CCWMX53 - u-boot From: Russell Haley To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Mar 2015 04:29:17 -0000 Well, Mr. Lapore had to all but type 'make install' into my console for me, but in the end I did get u-boot to build in a 10-RELEASE jail. I was able to boot all the way into userland, although I think I missed a step in creating my rootfs. So this is what is up for me next: - learn how to get ubldr working - play around a bit and see what works and what doesn't. I may get my hands on a Phytec iMX6 SOM from work, but I'm still interested in finding out about Krait support in the Qualcomm snapdragons.That is ultimately my target. There are some fun looking reference boards here: http://shop.intrinsyc.com/collections/qualcomm That said, the new snapdragon 810 is 64 bit (and a reference design from ARM is my layman's understanding). Maybe I should try to leap frog and get ahead of the curve? I'll have to check out the level of support in arm64. Later! Russ On Wed, Mar 25, 2015 at 7:00 AM, Ian Lepore wrote: > On Tue, 2015-03-24 at 22:42 -0700, Russell Haley wrote: >> Thanks Ian, >> >> Sorry, getting another error. This is in a fresh 10-Release jail. I >> installed arm-none-eabi-gcc from pkgng. The missing "m" in make is not >> a copy/paste error. >> >> # pwd >> /usr/ports/sysutils/u-boot-ccwmx53 >> # make install >> make: "/usr/ports/sysutils/u-boot-ccwmx53/Makefile" line 29: >> Unassociated shell command "${U_BOOT_DIR}/README" >> "ake: "/usr/ports/sysutils/u-boot-ccwmx53/Makefile" line 32: >> Unassociated shell command "CROSS_COMPILE=arm-none-eabi- \ >> make: "/usr/ports/sysutils/u-boot-ccwmx53/Makefile" line 33: >> Unassociated shell command "HOSTCC=cc" >> make: Fatal errors encountered -- cannot continue >> make: stopped in /usr/ports/sysutils/u-boot-ccwmx53 >> >> Russ > > Unassociated shell command in make is nearly always trouble with tabs > versus spaces, or line endings. Did you just cut and paste the diff > from the mail? If so, try doing it as a "save attachment" instead; mail > clients often screw up the whitespace (which I why I always do diffs as > attachments, but with the hint set to allow clients to display them > inline as well). > > -- Ian > >