* Failed to create MTD partitions @ 2021-05-28 11:00 Jupiter 2021-05-29 0:08 ` Jupiter 0 siblings, 1 reply; 3+ messages in thread From: Jupiter @ 2021-05-28 11:00 UTC (permalink / raw) To: linux-mtd Hello, I am using MTD in kernel 4.19, I was able to run kernel boot to create MTD partitions when I used NAND Winbond W29N02GV: [ 7.961966] nand: device found, Manufacturer ID: 0xef, Chip ID: 0xda [ 7.968545] nand: Winbond W29N02GV [ 7.972267] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB siz e: 64 [ 7.986814] Bad block table found at page 131008, version 0x01 [ 7.994254] Bad block table found at page 130944, version 0x01 [ 8.002152] 3 cmdlinepart partitions found on MTD device gpmi-nand [ 8.008479] Creating 3 MTD partitions on "gpmi-nand": .................... Since we could not get Winbond W29N02GV supply anymore, we changed Samsung NAND, Both are 3.3V 2Gib devices with the same memory organization (2k pages + 64b OOB / 128k blocks) so these two parts should be equivalent in terms of internal organization, but it failed to create MTD partitions in kernel boot: [ 8.137591] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xda [ 8.144246] nand: Samsung NAND 256MiB 3,3V 8-bit [ 8.148995] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 8.158330] gpmi-nand 1806000.gpmi-nand: Error setting BCH geometry : -22 [ 8.166690] gpmi-nand: probe of 1806000.gpmi-nand failed with error -22 Since it is a new board, I suspect one of following problem might cause that error: - HW - MTD does not support Samsung? - Need kernel configure? Appreciate your comments and advice. Thank you very much. - jupiter ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/ ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Failed to create MTD partitions 2021-05-28 11:00 Failed to create MTD partitions Jupiter @ 2021-05-29 0:08 ` Jupiter 2021-05-31 22:48 ` JH 0 siblings, 1 reply; 3+ messages in thread From: Jupiter @ 2021-05-29 0:08 UTC (permalink / raw) To: linux-mtd Hello, There is another statement before the device found, is the Error setting BCH geometry : -22 caused by ECC or by invalid JEDEC? It is kernel version 4.19 on iMX6ULZ MCU. [ 8.130891] nand: Could not find valid JEDEC parameter page; aborting [ 8.137591] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xda [ 8.144246] nand: Samsung NAND 256MiB 3,3V 8-bit [ 8.148995] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB siz e: 64 [ 8.158330] gpmi-nand 1806000.gpmi-nand: Error setting BCH geometry : -22 [ 8.166690] gpmi-nand: probe of 1806000.gpmi-nand failed with error -22 Thank you. Kind regards, - jupiter On 5/28/21, Jupiter <jupiter.hce@gmail.com> wrote: > Hello, > > I am using MTD in kernel 4.19, I was able to run kernel boot to create > MTD partitions when I used NAND Winbond W29N02GV: > > [ 7.961966] nand: device found, Manufacturer ID: 0xef, Chip ID: 0xda > [ 7.968545] nand: Winbond W29N02GV > [ 7.972267] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB > siz > e: 64 > [ 7.986814] Bad block table found at page 131008, version 0x01 > [ 7.994254] Bad block table found at page 130944, version 0x01 > [ 8.002152] 3 cmdlinepart partitions found on MTD device gpmi-nand > [ 8.008479] Creating 3 MTD partitions on "gpmi-nand": > .................... > > Since we could not get Winbond W29N02GV supply anymore, we changed > Samsung NAND, Both are 3.3V 2Gib devices with the same memory > organization (2k pages + > 64b OOB / 128k blocks) so these two parts should be equivalent in > terms of internal organization, but it failed to create MTD partitions > in kernel boot: > > [ 8.137591] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xda > [ 8.144246] nand: Samsung NAND 256MiB 3,3V 8-bit > [ 8.148995] nand: 256 MiB, SLC, erase size: 128 KiB, page size: > 2048, OOB size: 64 > [ 8.158330] gpmi-nand 1806000.gpmi-nand: Error setting BCH geometry : > -22 > [ 8.166690] gpmi-nand: probe of 1806000.gpmi-nand failed with error -22 > > Since it is a new board, I suspect one of following problem might > cause that error: > > - HW > - MTD does not support Samsung? > - Need kernel configure? > > Appreciate your comments and advice. > > Thank you very much. > > - jupiter > -- "A man can fail many times, but he isn't a failure until he begins to blame somebody else." -- John Burroughs ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/ ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Failed to create MTD partitions 2021-05-29 0:08 ` Jupiter @ 2021-05-31 22:48 ` JH 0 siblings, 0 replies; 3+ messages in thread From: JH @ 2021-05-31 22:48 UTC (permalink / raw) To: Tom Hochstein; +Cc: Lauren Post, Jun Zhu, meta-freescale Hello Tom, We have another issue to use Samsung NAND K9F2G08U0D-SCB0, I found a similar issue posted in NXP community that NXP driver did not support similar Samsung NAND https://community.nxp.com/t5/i-MX-Processors/ECC-errors-with-Samsung-NAND-K9K8G08U0F-on-i-MX6UL/m-p/676885 We are using meta-freescale, does meta-freescale NXP driver support Samsung K9F2G08U0D-SCB0? Or which version of the meta-freescale NXP driver can support Samsung K9F2G08U0D-SCB0? Thank you very much. Kind regards, Jupiter On 5/29/21, Jupiter <jupiter.hce@gmail.com> wrote: > Hello, > > There is another statement before the device found, is the Error > setting BCH geometry : -22 caused by ECC or by invalid JEDEC? It is > kernel version 4.19 on iMX6ULZ MCU. > > [ 8.130891] nand: Could not find valid JEDEC parameter page; aborting > [ 8.137591] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xda > [ 8.144246] nand: Samsung NAND 256MiB 3,3V 8-bit > [ 8.148995] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB > siz > e: 64 > [ 8.158330] gpmi-nand 1806000.gpmi-nand: Error setting BCH geometry : > -22 > [ 8.166690] gpmi-nand: probe of 1806000.gpmi-nand failed with error -22 > > Thank you. > > Kind regards, > > - jupiter > > > On 5/28/21, Jupiter <jupiter.hce@gmail.com> wrote: >> Hello, >> >> I am using MTD in kernel 4.19, I was able to run kernel boot to create >> MTD partitions when I used NAND Winbond W29N02GV: >> >> [ 7.961966] nand: device found, Manufacturer ID: 0xef, Chip ID: 0xda >> [ 7.968545] nand: Winbond W29N02GV >> [ 7.972267] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, >> OOB >> siz >> e: 64 >> [ 7.986814] Bad block table found at page 131008, version 0x01 >> [ 7.994254] Bad block table found at page 130944, version 0x01 >> [ 8.002152] 3 cmdlinepart partitions found on MTD device gpmi-nand >> [ 8.008479] Creating 3 MTD partitions on "gpmi-nand": >> .................... >> >> Since we could not get Winbond W29N02GV supply anymore, we changed >> Samsung NAND, Both are 3.3V 2Gib devices with the same memory >> organization (2k pages + >> 64b OOB / 128k blocks) so these two parts should be equivalent in >> terms of internal organization, but it failed to create MTD partitions >> in kernel boot: >> >> [ 8.137591] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xda >> [ 8.144246] nand: Samsung NAND 256MiB 3,3V 8-bit >> [ 8.148995] nand: 256 MiB, SLC, erase size: 128 KiB, page size: >> 2048, OOB size: 64 >> [ 8.158330] gpmi-nand 1806000.gpmi-nand: Error setting BCH geometry : >> -22 >> [ 8.166690] gpmi-nand: probe of 1806000.gpmi-nand failed with error >> -22 >> >> Since it is a new board, I suspect one of following problem might >> cause that error: >> >> - HW >> - MTD does not support Samsung? >> - Need kernel configure? >> >> Appreciate your comments and advice. >> >> Thank you very much. >> >> - jupiter >> > ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-05-31 22:49 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-05-28 11:00 Failed to create MTD partitions Jupiter 2021-05-29 0:08 ` Jupiter 2021-05-31 22:48 ` JH
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.