From owner-freebsd-arm@FreeBSD.ORG Wed Oct 1 06:48: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 367D1F42 for ; Wed, 1 Oct 2014 06:48:15 +0000 (UTC) Received: from mail-yh0-x229.google.com (mail-yh0-x229.google.com [IPv6:2607:f8b0:4002:c01::229]) (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 EA32BEA1 for ; Wed, 1 Oct 2014 06:48:14 +0000 (UTC) Received: by mail-yh0-f41.google.com with SMTP id i57so72457yha.28 for ; Tue, 30 Sep 2014 23:48: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=tDZvZaIb0i+vApAhPiUq3U8m+IR1bGw+lyNsjuK+oPo=; b=U+c63FDNdmsHkFZtw2OM9cxugXLBUQDjUkVljoDnUWK84Ond2dYRUt9sTgWQqGCLMu 5m4sNNH3S6QYMuii48CnrWJZ/AdpXUQfdV3Q6Y0G6o/oGQe8nAWeEj6eZJnH83qDTcWW xm7//nUvC+0xLT6jQ5OcH1cxLiNwEmaxZg8LgtBZB6/ChNdtsfE9/XknKIKsRiKRUs+c UTU/3cYtXRnHii3/k5uHENSNdzXpf6lmuGSVMGKgj+N5eDdITTHj7aF5cfaGxCGvOiGO cQcdzVa+ASbHk5DssAKigmpwy9Y2xWvnVz8cinwVuBUi2Gr+za33mJE8QWcwjpWJoRQp BikQ== MIME-Version: 1.0 X-Received: by 10.236.124.33 with SMTP id w21mr2127688yhh.73.1412146094089; Tue, 30 Sep 2014 23:48:14 -0700 (PDT) Received: by 10.170.208.13 with HTTP; Tue, 30 Sep 2014 23:48:14 -0700 (PDT) In-Reply-To: References: Date: Tue, 30 Sep 2014 23:48:14 -0700 Message-ID: Subject: Re: Digi CCWMX53 From: Russell Haley To: Warner Losh 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, Rui Paulo 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: Wed, 01 Oct 2014 06:48:15 -0000 Warner, First, I was just watching your 2010 talk on supporting FreeBSD in a commercial environment. Has there been any updates in the process of maintaining a commercial branch in the last 4 years (not that I have any commercial ventures yet! lolz)? Anyway, I talked to an Engineer about the NAND controller spec and he chided me for being naive (poor little software developer, in way over his head. tisk tisk). He mentioned a FIVE THOUSAND page reference manual, which I have yet to find on the Digi site. I have however found this hardware reference: http://ftp1.digi.com/support/documentation/90001270_E.pdf >From Page 41: NAND flash memory The ConnectCore for i.MX53 module provides 8GB of NAND flash memory. On the module in the development kits a 512MByte, 2Kbyte page, NAND flash chip is used. This NAND flash device is connected to NAND flash Chip Select 0. The NAND flash controller signals are available on the module connectors. There are pin references to NAND further down in the section "GPIO multiplexing table in the ConnectCore for i.MX53 module" on page 44 and 49. I fear this is not the information we are looking for. I have found another u-boot fork for the CCWMX53 on github here: https://github.com/Varcain/uboot-ccwmx53-digi With what seems to be the information about booting from NAND here: https://github.com/Varcain/uboot-ccwmx53-digi/tree/master/nand_spl If you can let me know what I am looking for I can both ask a more directed question at work and also perform a better search. I have also started looking over the Architecture handbook as well because I have a feeling there is going to be lots of driver code in my future. Okay, I need to stop staying up this late! Good Night, Russ On Sun, Sep 28, 2014 at 12:12 AM, Warner Losh wrote: > > On Sep 27, 2014, at 9:49 PM, Russell Haley wrote: > > > I will attempt to load the kernel from tftp as soon as I can. I will ne= ed > > to figure out how to get ethernet to the unit. > > > > I know nothing about u-boot so forgive my ignorance but I was hoping to > > modify the Arndale configuration to work such as: > > > > # mmc read 1 0x70800000 0x800 0x1800; > > #go 0x70800000; > > > > and then point the rootfs to /dev/da1s1 > > > > On another note, do you know where I could find out more about the > missing > > MTD support? > > A spec for the NAND controller is needed to make that work=E2=80=A6 Is o= ne about? > > Warner > > > > BTW, I thought your wireless mesh stuff was pretty cool. Ah, so many co= ol > > projects, so little time... > > > > Thanks, > > > > 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 differen= t. > >> You should be able to load a kernel from the network. Can you do that= ? > >> > >> -- > >> Rui Paulo > >> > >> > >> > >> > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >