toggle quoted message
Show quoted text
On 5/29/21, Jupiter <jupiter.hce@...> 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@...> 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
|