On 18 December 2014 at 08:10, Yassin Jaffer <[email protected]> wrote: > Hi Michal > > add the following to the nand id table > > {"K9GBG08U0A 32G 3.3V 8-bit", > { .id = {0xec, 0xd7, 0x94, 0x7a, 0x54, 0x43} }, > SZ_8K, SZ_4K, SZ_1M, 0, 6, 640, NAND_ECC_INFO(40, SZ_1K), > 0 },
So with the extra entry I get: nand: device found, Manufacturer ID: 0xec, Chip ID: 0xd7 nand: chip id data: 0xec, 0xd7, 0x94, 0x7a, 0x54, 0x43; 0xec, 0xd7 BTW can you make kernel *NOT* insert newline after every other printk? nand: Samsung K9GBG08U0A 32G 3.3V 8-bit nand: 4096MiB, MLC, page size: 8192, OOB size: 640 Bad block table not found for chip 0 Bad block table not found for chip 0 Scanning device for bad blocks Bad eraseblock 20 at 0x0000014fe000 Bad eraseblock 21 at 0x0000015fe000 Bad eraseblock 36 at 0x0000024fe000 Bad eraseblock 37 at 0x0000025fe000 Bad eraseblock 38 at 0x0000026fe000 Bad eraseblock 39 at 0x0000027fe000 Bad eraseblock 40 at 0x0000028fe000 Bad eraseblock 41 at 0x0000029fe000 Bad eraseblock 42 at 0x000002afe000 Bad eraseblock 43 at 0x000002bfe000 Bad eraseblock 44 at 0x000002cfe000 ... Bad eraseblock 4094 at 0x0000ffefe000 Bad eraseblock 4095 at 0x0000ffffe000 No space left to write bad block table sunxi_nand 1c03000.nand: nand_scan_tail failed: -28 sunxi_nand 1c03000.nand: failed to init nand chips sunxi_nand: probe of 1c03000.nand failed with error -28 This looks like 100% bad blocks to me so the detection probably fails. Thanks Michal -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
