Date: Sun, 30 Dec 2012 22:47:58 +0100 From: "Ronald Klop" <ronald-freebsd8@klop.yi.org> To: freebsd-arm@freebsd.org Subject: Re: sheevaplug nand type not recognized? Message-ID: <op.wp5f58p08527sy@pinky> In-Reply-To: <1355355431.87661.472.camel@revolution.hippie.lan> References: <op.wo76n6x58527sy@212-182-167-131.ip.telfort.nl> <1355353104.87661.468.camel@revolution.hippie.lan> <op.wo7784s78527sy@212-182-167-131.ip.telfort.nl> <1355355431.87661.472.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Dec 2012 00:37:11 +0100, Ian Lepore <freebsd@damnhippie.dyndns.org> wrote: > On Thu, 2012-12-13 at 00:16 +0100, Ronald Klop wrote: >> On Wed, 12 Dec 2012 23:58:24 +0100, Ian Lepore >> <freebsd@damnhippie.dyndns.org> 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: <Marvell NAND controller> mem 0xf9300000-0xf93fffff on localbus0 >> nandbus0: <NAND bus> on nand0 >> lnand0: <Samsung NAND 512MiB 3,3V 8-bit> 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 Hi, What would be needed to get the support for this NAND chip committed? Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wp5f58p08527sy>