From owner-freebsd-arm@FreeBSD.ORG Sat Oct 4 18:29:43 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 934727B0 for ; Sat, 4 Oct 2014 18:29:43 +0000 (UTC) Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) (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 4EF13395 for ; Sat, 4 Oct 2014 18:29:42 +0000 (UTC) Received: by mail-ob0-f171.google.com with SMTP id va2so2314622obc.16 for ; Sat, 04 Oct 2014 11:29:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=rcd+1JiXY+Gqn6RsB0LUVK2f/pnmvooSRc52Ip3ZVj4=; b=R+7pMMZQg1inlnwFkI/8wz4swL3F6BY/wLXPAhxIplviYNKg00LwuQZ2/u2EvBRxAU ClXbNrf4tzJriuQ+PwxJXZwt5qXEld09hb3ddnlEXU6PT/SbRPNprftLVZw0fxDdc37v /+N/0tJruCi8Yh/9C3hXoGgiNrlpFgszCk2cpPQcRgEmRuOEPOh8h6z5ehdj4+9mitFo 6AJMUQUZt2qa1PTKVB0PJ5Hn4zFQa1sWKDQzBKa8j/htWCPWXHSQy11qiarVRz964Y3E p/0+RbJWFkU3UGr0dsk4t6uI9mo3o3EGu6fR3CJ7mqpCzi760M2jhJBdT1tYs8A/zMGW jzEg== X-Gm-Message-State: ALoCoQlxULsS1YjAEyu99ucY556BT+m9VmFtxBTcwi47hryAp/rlaWNPXP1Q/UXq6yHyAF+6rDGa X-Received: by 10.182.63.105 with SMTP id f9mr15749422obs.59.1412445902249; Sat, 04 Oct 2014 11:05:02 -0700 (PDT) Received: from bsdimp.bsdimp.com ([50.253.99.174]) by mx.google.com with ESMTPSA id fj8sm6696887obc.10.2014.10.04.11.05.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 04 Oct 2014 11:05:01 -0700 (PDT) Sender: Warner Losh Content-Type: multipart/signed; boundary="Apple-Mail=_67C87F7A-F051-4E36-82B2-11311A86BC80"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Digi CCWMX53 From: Warner Losh In-Reply-To: Date: Sat, 4 Oct 2014 12:05:19 -0600 Message-Id: References: <27A69721-D93D-4D4C-883A-718CFFF52B21@bsdimp.com> To: Russell Haley X-Mailer: Apple Mail (2.1878.6) 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: Sat, 04 Oct 2014 18:29:43 -0000 --Apple-Mail=_67C87F7A-F051-4E36-82B2-11311A86BC80 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hey Russ, A quick read suggests all, or nearly all, of the data needed to write a = full NFC for this chip is present. The programming and read sequences = and information about ECC error rates appear to be readily available. = The exact ECC used, however, appears opaque. This may or may not be a = problem. It even appears to have command sequencing built into the = controller. This is a great feature, but one the current code doesn=92t = make use of. Warner On Oct 2, 2014, at 10:44 PM, Russell Haley wrote: > Warner,=20 >=20 > I was looking for a Digi reference but it turns out the Nand Flash = Controller is part of the Freescale Processor. Here is the link to the = Reference Manual: >=20 > cache.freescale.com/files/32bit/doc/ref_manual/iMX53RM.pdf >=20 > The NAND Flash Controller is in Chapter 51 page 3571 to page 3647.=20 >=20 > Is this relevant to what you are looking at doing? = https://wiki.freebsd.org/NAND >=20 > I also found something called CHFS for NetBSD that looks interesting: = http://chewiefs.sed.hu/home >=20 > Thanks,=20 > Russ >=20 >=20 >=20 >=20 >=20 >=20 >=20 > On Thu, Oct 2, 2014 at 2:34 PM, Warner Losh wrote: >=20 > On Oct 1, 2014, at 12:48 AM, Russell Haley = wrote: >=20 > > 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. >=20 > URL + section number. 5k pages doesn=92t necessarily mean it will be = useful, though. :( >=20 > > I have however found this hardware reference: > > > > http://ftp1.digi.com/support/documentation/90001270_E.pdf > > > > =46rom 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. >=20 > This basically says nothing more useful than =93There=92s NAND on this = board that=92s 4Gbits on CS0.=94 which is useful, but far from = sufficient. How do I program the DMA so that ECC is added to the OOB = areas of that NAND? How do I set different ECC tables? How do I do ECC = error correction and detection? If you can=92t answer that sort of = question from the docs you have, then they aren=92t helpful enough. >=20 > > 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. >=20 > Not really. The GPIO info might be mildly helpful in a few cases >=20 > > 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. >=20 > A good first step would be to get a URL or search string to get the = URL for that big spec. It is of the right size to possibly be useful, = but sometimes really long specs have 1-2 page descriptions of things = like the SD controller or the NAND controller that you need special NDAs = + business arrangements to get, so it is hard to say=85 >=20 > Warner >=20 > > > > 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 need > > > 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=85 Is = one about? > > > > Warner > > > > > > > BTW, I thought your wireless mesh stuff was pretty cool. Ah, so = many cool > > > 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: > > >>> =95 > > >>> 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 > > >> > > >> > > >> > > >> > > > _______________________________________________ > > > 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" > > > > >=20 >=20 --Apple-Mail=_67C87F7A-F051-4E36-82B2-11311A86BC80 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUMDbfAAoJEGwc0Sh9sBEAX68QANnGQiChMTro8dOT2SQDWLBh eCnTsqsJGNkNrsKxQjWsrGFt7IvOmMs5jA3iCiA6vhrLx2bSD2twFiuX4ZX9LID1 4dJ9hhj+Z3C0h3yHOBr+cKUsDjvrJ1WG+dMlSNiLa4Aa4gMw+GHF63nOPx4sTlsj P4dSsJzRpKpE4eYUm8qGh4FF5QJsSGiBt0RVe/2KWxET0UhCQjB+XI/tGTK7lsyj OiuPFssaG3uV6hWlAqIpKtzpaBTuQZvRi4iwSwteICuU/LHHupp4ul+Vz7+VHkBP W2jtvzD15/nEb0AbUcFgfiFYEK4iWjzlRden6DcRLbWI/2YxOb9EDpWh6RP42w+K DU3nLRwifkYSKTHHTdbJXNZuTHNBbO3xlX9NNHDSbCz6y9CDWzSO8c/NmyH2BQfD IjpsvEYkZ059ctIeKbpwx65vn8E4lP8igWvQoVCtxmMHiBGLzBPbUFQ6RDcXb9cV SPSOR7eU352wEt+jopUdj2U38Py0acQfgcuOPLOGING0nSONxNATu4hx0T05Ednx D7/RCAXFO5vHbkZir7J5SpjrayIHKDfhJa8bdqH8a4xsmP2BrurTqhSWTI56JQ+h Zpbkjtul56xuSiaYIno4/uiym0c7vahH0V083VFE0845jQP/Tl+AA/X+tH9xVCpj 72NHvC3VuNt42h4oZfc3 =iy1O -----END PGP SIGNATURE----- --Apple-Mail=_67C87F7A-F051-4E36-82B2-11311A86BC80--