Hi Sean,

The output is the MTD subsystem telling you what logically was configured - MTD layout is arbitrary and not defined per standard partition tables. The other warning was OOB (Out Of Band) block related. NAND uses OOB metadata (literally extra bits per block) to flag known bad blocks and the like. It has been many years since I hacked on YAFFS but I don't think much has changed in this area. Happy New Year.

Jon.

-- 
Sent from my iPad

On Dec 27, 2012, at 14:56, Sean Omalley <omalley_s@rocketmail.com> wrote:

This isn't rewriting the internal nand?

[   35.091406] Creating 3 MTD partitions on "orion_nand":
[   35.132266] 0x000000000000-0x000000100000 : "u-boot"
[   35.203610] 0x000000100000-0x000000500000 : "uImage"
[   35.272698] 0x000000500000-0x000008000000 : "root"

I can't test atm. I bricked it trying to switch u-boot since "saveenv" was not writing to the nand and saving.

reboot did work on it, before I bricked it. :)

Now with the jtag I am getting:

unknown NAND flash device found, manufacturer id: 0x00 device id: 0x00
in procedure 'nand'

I was getting a list of nand drivers and orion was listed but not loading.. Not exactly sure what to do here..


From: Jonathan Masters <jcm@redhat.com>
To: Sean Omalley <omalley_s@rocketmail.com>
Cc: "arm@lists.fedoraproject.org" <arm@lists.fedoraproject.org>
Sent: Thursday, December 27, 2012 5:16 AM
Subject: Re: [fedora-arm] Pogoplug pink E02

Not rewriting, but the OOB (Out Of Band) data for those blocks indicates they have failed. It's just informational. 

-- 
Sent from my iPad

On Dec 24, 2012, at 15:59, Sean Omalley <omalley_s@rocketmail.com> wrote:

I was able to get the pogo pink to boot the F18-kirkwood-20121220.img.xz off a usb thumb drive.
It uses 1.1 usb which is doggy slow, and it is NOT saving env vars which is a PITA.

But they are:
setenv usb_boot 'if ext2load usb $usb_device 0x1100000 /uInitrd; then bootm 0x800000 0x1100000;else bootm 0x800000;fi;'
setenv usb_load_uimage 'mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /uImage'
setenv usb_root /dev/sda3
(this is the doozan uboot, but I am wondering if I shouldnt get something else. anyone tried anything else?)

I am also seeing this during the boot: Is this rewriting the nand??

[   34.638654] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), page size: 2048, OOB size: 64
[   34.723723] Scanning device for bad blocks
[   34.728417] Bad eraseblock 6 at 0x0000000c0000
[   34.733218] Bad eraseblock 11 at 0x000000160000
[   34.740889] Bad eraseblock 53 at 0x0000006a0000
[   34.749666] Bad eraseblock 110 at 0x000000dc0000
[   34.762924] Bad eraseblock 226 at 0x000001c40000
[   34.774550] Bad eraseblock 320 at 0x000002800000
[   34.786623] Bad eraseblock 420 at 0x000003480000
[   34.794733] Bad eraseblock 467 at 0x000003a60000
[   34.802999] Bad eraseblock 516 at 0x000004080000
[   34.821846] Bad eraseblock 707 at 0x000005860000
[   34.826595] Bad eraseblock 709 at 0x0000058a0000
[   34.832545] Bad eraseblock 727 at 0x000005ae0000
[   34.837667] Bad eraseblock 734 at 0x000005bc0000
[   34.843248] Bad eraseblock 747 at 0x000005d60000
[   35.091406] Creating 3 MTD partitions on "orion_nand":
[   35.132266] 0x000000000000-0x000000100000 : "u-boot"
[   35.203610] 0x000000100000-0x000000500000 : "uImage"
[   35.272698] 0x000000500000-0x000008000000 : "root"


Also, the 'reboot' command isn't working on the guruplug plus. I haven't tried it on the pogoplug ironically as I have to leave right now.


_______________________________________________
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm


_______________________________________________
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm