From owner-freebsd-arm@FreeBSD.ORG Wed Dec 12 23:37:15 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D5B4E6F6 for ; Wed, 12 Dec 2012 23:37:15 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 647958FC12 for ; Wed, 12 Dec 2012 23:37:15 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id qBCNbEB2044152 for ; Wed, 12 Dec 2012 16:37:14 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id qBCNbCO6057029; Wed, 12 Dec 2012 16:37:12 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Subject: Re: sheevaplug nand type not recognized? From: Ian Lepore To: Ronald Klop In-Reply-To: References: <1355353104.87661.468.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Wed, 12 Dec 2012 16:37:11 -0700 Message-ID: <1355355431.87661.472.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit 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: Wed, 12 Dec 2012 23:37:15 -0000 On Thu, 2012-12-13 at 00:16 +0100, Ronald Klop wrote: > On Wed, 12 Dec 2012 23:58:24 +0100, Ian Lepore > wrote: > > > On Wed, 2012-12-12 at 23:41 +0100, Ronald Klop wrote: > >> Hello, > >> > >> I just compiled a FreeBSD-10-current (src from 22 Nov.) kernel+world and > >> installed it on a usb stick. > >> It has NAND support compiled in, but I see no nand devices in /dev. > >> Dmesg does not list a lnand0 device like the example in > >> http://wiki.freebsd.org/NAND#NAND_Framework. > >> > >> Booting Debian finds this: > >> ... > >> NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB > >> 3,3V 8-bit) > >> Scanning device for bad blocks > >> Bad eraseblock 168 at 0x000001500000 > >> Bad eraseblock 169 at 0x000001520000 > >> Bad eraseblock 1193 at 0x000009520000 > >> 2 cmdlinepart partitions found on MTD device orion_nand > >> Creating 2 MTD partitions on "orion_nand": > >> 0x000000100000-0x000000500000 : "uImage" > >> 0x000000500000-0x000020000000 : "rootfs" > >> UBI: attaching mtd1 to ubi0 > >> ... > >> > >> I don't see this Samsung version in sys/dev/nand/nand_id.c. > >> Would it be easy to add it? I understand the manufacturer id and chip > >> id, > >> but I don't know what I should change more. > > > > That looks like the same chip that's in my DreamPlug 1001N, the attached > > diff should fix it for you. > > > > -- Ian > > > > Supernice! > > nand0: mem 0xf9300000-0xf93fffff on localbus0 > nandbus0: on nand0 > lnand0: on nandbus0 > lnand0: No BBT found. Prescan chip... > ##lnand0: Bad block(168) > lnand0: Bad block(169) > ##########lnand0: Bad block(1193) > ############################# > > > root@sh10:~ # ls -l /dev/*nand* > crw-r----- 1 root operator 0x2f Dec 12 23:09 /dev/gnand.raw0 > crw-r----- 1 root operator 0x33 Dec 12 23:09 /dev/gnand.raw0s.root > crw-r----- 1 root operator 0x32 Dec 12 23:09 /dev/gnand.raw0s.u-boot > crw-r----- 1 root operator 0x2e Dec 12 23:09 /dev/gnand0 > crw-r----- 1 root operator 0x31 Dec 12 23:09 /dev/gnand0s.root > crw-r----- 1 root operator 0x30 Dec 12 23:09 /dev/gnand0s.u-boot > crw-rw-rw- 1 root wheel 0x19 Dec 12 23:09 /dev/nand0.0 > > Now I can't go to sleep without playing some more with it. :-) > > Cheers, > Ronald. Heh. Be careful. My dreamplug 1001N is a brick because I typed a command in the wrong window and wiped the nand on it, and I haven't had any success trying to use openocd to flash it (or even get it to boot as a one-shot). -- Ian