From owner-freebsd-arm@FreeBSD.ORG Tue Sep 30 05:15:15 2014 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 3C43E43F for ; Tue, 30 Sep 2014 05:15:15 +0000 (UTC) Received: from mail-yh0-x22a.google.com (mail-yh0-x22a.google.com [IPv6:2607:f8b0:4002:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F1D71B20 for ; Tue, 30 Sep 2014 05:15:14 +0000 (UTC) Received: by mail-yh0-f42.google.com with SMTP id t59so1163382yho.1 for ; Mon, 29 Sep 2014 22:15: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=EokoSkx8OvqRqsEfTRs0moTg/AUxI5VP0ZYTDfafPxk=; b=YzjFzIcCoII6+G9m2VlT2UplzIxppwH5/2tEUR76EEtAWfoj9/d+lzglNMU5Jh3rU9 n+imnNwLu93Vd84zNl/XsDiYOPfOwjJ8Svs3mCnNLmgj4EwG+6Uh1IB04C1bVls31DrA vrZanHiFJm0tt0XKO1nW/pA5e5OtiX57eKT4Tq1VbRHzrG9IyDR3JJ0nEezPO4c7hWQT VMYy7OLvONEvqowJwO2IyeItDdWKKH2ptTnkZqMC8wQdy/gIaMN+uXz2YiGY8FJjJVao ouBhOpuTjBP7Gzn1gZzPHlh6u+v6e06sq6cCtMdmwVlU1150DYwZ5NbwYfVrI6NIgg1B /5/Q== MIME-Version: 1.0 X-Received: by 10.236.227.162 with SMTP id d32mr9903459yhq.100.1412054114153; Mon, 29 Sep 2014 22:15:14 -0700 (PDT) Received: by 10.170.208.13 with HTTP; Mon, 29 Sep 2014 22:15:14 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Sep 2014 22:15:14 -0700 Message-ID: Subject: Re: Digi CCWMX53 From: Russell Haley To: Rui Paulo Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-arm@freebsd.org 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: Tue, 30 Sep 2014 05:15:15 -0000 Rui, I've been able to build a kernel and upload it - again using a "Linux" version of the CCWMX53 u-boot - but it didn't boot. I cloned your git repo but I'm confuded (confused and befuddled or just a typo?) on how to cross compile it. Do I set "devenvvar" (?) to somehow point into my latest buildworld output and then just call make? Again I can only point to the arndale board setup but even those instructions "feel" incomplete to my novice brain. Any direction you could provide would be great. Here is my latest boot output: U-Boot 2009.08 - dub-1.6.4.1 - (Sep 25 2014 - 09:51:55) - GCC 4.4.6 for ConnectCore for i.MX53 on a JumpStart Kit Development Board I2C: ready NAND: 512 MiB MMC: FSL_ESDHC: 0, FSL_ESDHC: 1 DRAM: 1 GB In: serial Out: serial Err: serial Net: FEC0 [PRIME] Hit any key to stop autoboot: 0 FEC: enable RMII gasket Using FEC0 device TFTP from server 192.168.0.55; our IP address is 192.168.0.1 Filename 'kernel.bin'. Load address: 0x70800000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ############ done Bytes transferred =3D 4934472 (4b4b48 hex) ## Starting application at 0x70800100 ... Thanks again! Russ On Sun, Sep 28, 2014 at 1:12 PM, Russell Haley wrote= : > Rui, > > I was able to get a linux compatible copy of uboot to load a file from th= e > network last night. I don't have a working BSD kernel right now and it > wouldn't boot any of the uimage kernels I tried to upload. I'll work on > getting a BSD kernel to build. > > Russ > > On Sat, Sep 27, 2014 at 2:35 PM, Rui Paulo wrote: > >> On Sep 27, 2014, at 13:31, Russell Haley wrote: >> > >> > Rui, >> > >> > So no MTD means the NAND on the SOM is out, but can I boot the kernel >> and load rootfs from the microSD, like in this example: >> > =E2=80=A2 >> > ARNDALE5250 # setenv bootcmd "fatload mmc 0:1 0x40f00000 kernel.bin; >> go 0x40f00000" >> > >> > ARNDALE5250 # saveenv >> > >> > ARNDALE5250 # boot >> >> You can't use the Arndale config since the load addresses are different. >> You should be able to load a kernel from the network. Can you do that? >> >> -- >> Rui Paulo >> >> >> >> >