<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: IMX7D NAND ECC error in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1557841#M197845</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/952"&gt;@hyoungkikim&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope you are doing well.&lt;/P&gt;
&lt;DIV id="bodyDisplay_0" class="lia-message-body lia-component-message-view-widget-body lia-component-body-signature-highlight-escalation lia-component-message-view-widget-body-signature-highlight-escalation"&gt;
&lt;DIV class="lia-message-body-content"&gt;
&lt;P&gt;It seems&amp;nbsp;Macronix MX30LF4G28AC NAND chip driver in new kernel is differ than in old one in point of ECC calculation.&lt;BR /&gt;So you need to re-format NAND structure with kobs-ng.&lt;/P&gt;
&lt;P&gt;Alternatively you can try to compile the driver from old kernel in new one.&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;
&lt;P&gt;Sanket Parekh&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Tue, 22 Nov 2022 13:16:37 GMT</pubDate>
    <dc:creator>Sanket_Parekh</dc:creator>
    <dc:date>2022-11-22T13:16:37Z</dc:date>
    <item>
      <title>IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1556173#M197696</link>
      <description>&lt;P&gt;hi&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;on&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;MCIMX7D SABRE board.&amp;nbsp; to use NAND , i reworked the board with&amp;nbsp;Macronix MX30LF4G28AC&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;kernel is 5.4.2 and U-boot is 2020.04&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;kernel config&amp;nbsp; is imx_v6_v7_defconfig ,&amp;nbsp; wiht imx7d-sdb-gpmi-weim.dtb , i just added nand-ecc-mode="hw" n and&amp;nbsp; fsl,use-mininum-ecc&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;a board booted well and i can see messages which show nand&amp;nbsp; (see below)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;but in linux&amp;nbsp; when i mount nand with jffs or ubi&amp;nbsp; &amp;nbsp;i got ecc error&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;i don't know the Error cause is sw or hw issue ,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;any idea and advice will be of great help&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;thank you in advance ,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1) on mounting&amp;nbsp; jffs2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;mount -t jffs2 /dev/mtdblock2 /mnt&amp;nbsp; and copy some data ,i got ecc error&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 244.169534] jffs2: notice: (291) jffs2_get_inode_nodes: Node header CRC failed at 0x11cc20. {655a,ca3a,b4db27fc,afbcb3ed}&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 244.249511] jffs2: mtd-&amp;gt;read(0x320 bytes from 0x11fce0) returned ECC error&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 244.249541] jffs2: notice: (291) jffs2_get_inode_nodes: Node header CRC failed at 0x11fce0. {3a84,023e,249e0aee,81482350}&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 244.329488] jffs2: mtd-&amp;gt;read(0x184 bytes from 0xf2e7c) returned ECC error&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 244.329518] jffs2: notice: (291) jffs2_get_inode_nodes: Node header CRC failed at 0x0f2e7c. {ec8d,815f,4fe6e50f,b00bf645}&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 244.399514] jffs2: mtd-&amp;gt;read(0x6a0 bytes from 0xfa160) returned ECC error&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 244.399542] jffs2: notice: (291) jffs2_get_inode_nodes: Node header CRC failed at 0x0fa160. {0f08,25fa,115ee681,e1446179}&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:root@192:~" target="_blank"&gt;root@192:~#&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2)&amp;nbsp; on mount ubi, i got below kernel message&lt;/P&gt;&lt;P&gt;i just use ubiformat /ubiattach/mount .&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 291.254076] ubi0: background thread "ubi_bgt0d" started, PID 298&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;[&amp;nbsp; 314.548421] ubi0 warning: &lt;/STRONG&gt;&lt;STRONG&gt;ubi_io_read&lt;/STRONG&gt;&lt;STRONG&gt;: error -74 (ECC error) while reading 4096 bytes from PEB 2:4096, read only 4096 bytes, retry&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.549722] UBIFS (ubi0:0): Mounting in unauthenticated mode&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.551010] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 302&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.594967] UBIFS error (ubi0:0 pid 300): ubifs_read_node: bad node type (255 but expected 9)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.594999] UBIFS error (ubi0:0 pid 300): ubifs_read_node: bad node at LEB 12:264, LEB mapping status 0&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595017] Not a node, first 24 bytes:&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595032] 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ........................&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595056] CPU: 0 PID: 300 Comm: mount Not tainted 5.4.161-39915-g0021a0c8a58f-dirty #18&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595071] Hardware name: Freescale i.MX7 Dual (Device Tree)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595107] [&amp;lt;c01122a0&amp;gt;] (unwind_backtrace) from [&amp;lt;c010cbc8&amp;gt;] (show_stack+0x10/0x14)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595133] [&amp;lt;c010cbc8&amp;gt;] (show_stack) from [&amp;lt;c0def3c4&amp;gt;] (dump_stack+0xd0/0x104)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595159] [&amp;lt;c0def3c4&amp;gt;] (dump_stack) from [&amp;lt;c04664c8&amp;gt;] (ubifs_read_node+0x228/0x260)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595187] [&amp;lt;c04664c8&amp;gt;] (ubifs_read_node) from [&amp;lt;c046f6ac&amp;gt;] (dbg_old_index_check_init+0x64/0x94)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595213] [&amp;lt;c046f6ac&amp;gt;] (dbg_old_index_check_init) from [&amp;lt;c0462b24&amp;gt;] (ubifs_mount+0xf98/0x15ec)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595241] [&amp;lt;c0462b24&amp;gt;] (ubifs_mount) from [&amp;lt;c02e7670&amp;gt;] (legacy_get_tree+0x24/0x4c)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595268] [&amp;lt;c02e7670&amp;gt;] (legacy_get_tree) from [&amp;lt;c02a778c&amp;gt;] (vfs_get_tree+0x24/0xe8)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595293] [&amp;lt;c02a778c&amp;gt;] (vfs_get_tree) from [&amp;lt;c02d1b28&amp;gt;] (do_mount+0x8a8/0xbcc)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595316] [&amp;lt;c02d1b28&amp;gt;] (do_mount) from [&amp;lt;c02d2260&amp;gt;] (ksys_mount+0x88/0xb4)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595339] [&amp;lt;c02d2260&amp;gt;] (ksys_mount) from [&amp;lt;c0101000&amp;gt;] (ret_fast_syscall+0x0/0x28)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595355] Exception stack(0xd842ffa8 to 0xd842fff0)&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595376] ffa0:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00000000 b6eed90c 01049318 01049328 01049308 00000000&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595398] ffc0: 00000000 b6eed90c b6eee114 00000015 01049318 01049308 01049258 00000000&lt;/P&gt;&lt;P&gt;[&amp;nbsp; 314.595415] ffe0: b6eedfc4 beb68a18 b6ebe833 b6e49c7a&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;kernel boot message&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;[ 2.835671] imx ahci driver is registered.&lt;BR /&gt;[ 2.851340] nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xdc&lt;BR /&gt;[ 2.857722] nand: Macronix MX30LF4G28AC&lt;BR /&gt;[ 2.861691] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 112&lt;BR /&gt;[ 2.873112] Bad block table not found for chip 0&lt;BR /&gt;[ 2.878023] Bad block table found at page 262016, version 0x01&lt;BR /&gt;[ 2.884215] nand_read_bbt: bad block at 0x0000011e0000&lt;BR /&gt;[ 2.889468] nand_read_bbt: bad block at 0x00000b0a0000&lt;BR /&gt;[ 2.894638] nand_read_bbt: bad block at 0x000015a60000&lt;BR /&gt;[ 2.901535] Bad block table written to 0x00001ffe0000, version 0x01&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Nov 2022 03:29:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1556173#M197696</guid>
      <dc:creator>hyoungkikim</dc:creator>
      <dc:date>2022-11-18T03:29:57Z</dc:date>
    </item>
    <item>
      <title>Re: IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1557841#M197845</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/952"&gt;@hyoungkikim&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope you are doing well.&lt;/P&gt;
&lt;DIV id="bodyDisplay_0" class="lia-message-body lia-component-message-view-widget-body lia-component-body-signature-highlight-escalation lia-component-message-view-widget-body-signature-highlight-escalation"&gt;
&lt;DIV class="lia-message-body-content"&gt;
&lt;P&gt;It seems&amp;nbsp;Macronix MX30LF4G28AC NAND chip driver in new kernel is differ than in old one in point of ECC calculation.&lt;BR /&gt;So you need to re-format NAND structure with kobs-ng.&lt;/P&gt;
&lt;P&gt;Alternatively you can try to compile the driver from old kernel in new one.&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;
&lt;P&gt;Sanket Parekh&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 22 Nov 2022 13:16:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1557841#M197845</guid>
      <dc:creator>Sanket_Parekh</dc:creator>
      <dc:date>2022-11-22T13:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1558481#M197899</link>
      <description>&lt;P&gt;Hi&amp;nbsp; Sanket_Parehk&lt;/P&gt;&lt;P&gt;i tried images from L5.15.52-2.1.0_image_IMX6uL7D&amp;nbsp;&lt;/P&gt;&lt;P&gt;but&amp;nbsp; the result is the same ,&lt;/P&gt;&lt;P&gt;with kobj-ng i wrote u-boot to nand and&amp;nbsp; &amp;nbsp;&amp;nbsp;i store kernel and dtb by nand write cmd, and read back, and boot a borad with no problem&lt;/P&gt;&lt;P&gt;a strange things is&amp;nbsp; from u-boot&amp;nbsp; OOBSIZE is 112 byte ,but linux booting message showed OOBSIZE is 64&amp;nbsp;&lt;/P&gt;&lt;P&gt;and kernel couldn't find onfi nand&amp;nbsp;&lt;/P&gt;&lt;P&gt;i have no clue&amp;nbsp; it is about HW or SW&amp;nbsp; ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1&amp;nbsp; . from U-boot.&lt;/P&gt;&lt;P&gt;Normal Boot&lt;BR /&gt;Hit any key to stop autoboot: 0&lt;BR /&gt;=&amp;gt; nand info&lt;/P&gt;&lt;P&gt;Device 0: nand0, sector size 128 KiB&lt;BR /&gt;Page size 2048 b&lt;BR /&gt;OOB size 112 b&lt;BR /&gt;Erase size 131072 b&lt;BR /&gt;subpagesize 2048 b&lt;BR /&gt;options 0x40004200&lt;BR /&gt;bbt options 0x00068000&lt;BR /&gt;=&amp;gt;&lt;/P&gt;&lt;P&gt;2. booting message&lt;/P&gt;&lt;P&gt;[ 1.251221] imx ahci driver is registered.&lt;BR /&gt;[ 1.260274] Could not find a valid ONFI parameter page, trying bit-wise majority to recover it&lt;BR /&gt;[ 1.269039] ONFI parameter recovery failed, aborting&lt;BR /&gt;[ 1.274050] nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xdc&lt;BR /&gt;[ 1.280433] nand: Macronix NAND 512MiB 3,3V 8-bit&lt;BR /&gt;[ 1.285158] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64&lt;BR /&gt;[ 1.293187] Block protection check failed&lt;BR /&gt;[ 1.297879] Bad block table found at page 262080, version 0x01&lt;BR /&gt;[ 1.304180] Bad block table found at page 262016, version 0x01&lt;BR /&gt;[ 1.310208] nand_read_bbt: bad block at 0x0000011e0000&lt;BR /&gt;[ 1.315385] nand_read_bbt: bad block at 0x00000b0a0000&lt;BR /&gt;[ 1.320540] nand_read_bbt: bad block at 0x000015a60000&lt;BR /&gt;[ 1.325842] 5 cmdlinepart partitions found on MTD device gpmi-nand&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 11:18:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1558481#M197899</guid>
      <dc:creator>hyoungkikim</dc:creator>
      <dc:date>2022-11-23T11:18:44Z</dc:date>
    </item>
    <item>
      <title>Re: IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1558492#M197901</link>
      <description>&lt;P&gt;hi Sanket_Parekh&lt;/P&gt;&lt;P&gt;i downloaded LF_V5..15.42-2.1.0.image_IMX6UL7D&lt;/P&gt;&lt;P&gt;and&amp;nbsp; updated to u-boot-imx7dsabresd_nand.imx&amp;nbsp;&lt;/P&gt;&lt;P&gt;it booted well. and i download kernel and dtb , write to nand flash, and read back,&amp;nbsp;&lt;/P&gt;&lt;P&gt;successfully booted with that image&amp;nbsp;&lt;/P&gt;&lt;P&gt;but&amp;nbsp; the result is the same , i couldn't&amp;nbsp; use nand on linux&lt;/P&gt;&lt;P&gt;i have another questions&lt;/P&gt;&lt;P&gt;&amp;nbsp;on u-boot&amp;nbsp; OOBSIZE is 112 byte but kernel booting message shows oobsize is 64 byte&lt;/P&gt;&lt;P&gt;and there is a message about ONFI parameter fail&lt;/P&gt;&lt;P&gt;i am cofused it is a problem with hw or sw&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you&amp;nbsp;&lt;/P&gt;&lt;P&gt;1)&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hit any key to stop autoboot: 0&lt;BR /&gt;=&amp;gt; nand info&lt;/P&gt;&lt;P&gt;Device 0: nand0, sector size 128 KiB&lt;BR /&gt;Page size 2048 b&lt;BR /&gt;OOB size 112 b&lt;BR /&gt;Erase size 131072 b&lt;BR /&gt;subpagesize 2048 b&lt;BR /&gt;options 0x40004200&lt;BR /&gt;bbt options 0x00068000&lt;BR /&gt;=&amp;gt;&lt;/P&gt;&lt;P&gt;2) kernel booting message&lt;/P&gt;&lt;P&gt;[ 1.251221] imx ahci driver is registered.&lt;BR /&gt;[ 1.260274] Could not find a valid ONFI parameter page, trying bit-wise majority to recover it&lt;BR /&gt;[ 1.269039] ONFI parameter recovery failed, aborting&lt;BR /&gt;[ 1.274050] nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xdc&lt;BR /&gt;[ 1.280433] nand: Macronix NAND 512MiB 3,3V 8-bit&lt;BR /&gt;[ 1.285158] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64&lt;BR /&gt;[ 1.293187] Block protection check failed&lt;BR /&gt;[ 1.297879] Bad block table found at page 262080, version 0x01&lt;BR /&gt;[ 1.304180] Bad block table found at page 262016, version 0x01&lt;BR /&gt;[ 1.310208] nand_read_bbt: bad block at 0x0000011e0000&lt;BR /&gt;[ 1.315385] nand_read_bbt: bad block at 0x00000b0a0000&lt;BR /&gt;[ 1.320540] nand_read_bbt: bad block at 0x000015a60000&lt;BR /&gt;[ 1.325842] 5 cmdlinepart partitions found on MTD device gpmi-nand&lt;BR /&gt;[ 1.332032] Creating 5 MTD partitions on "gpmi-nand":&lt;BR /&gt;[ 1.337116] 0x000000000000-0x000004000000 : "nandboot"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 11:29:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1558492#M197901</guid>
      <dc:creator>hyoungkikim</dc:creator>
      <dc:date>2022-11-23T11:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1559193#M197948</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/952"&gt;@hyoungkikim&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you please try to perform the same experiment with Linux versions imx-4.14.98/imx-4.1.15?&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;
&lt;P&gt;Sanket Parekh&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2022 07:40:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1559193#M197948</guid>
      <dc:creator>Sanket_Parekh</dc:creator>
      <dc:date>2022-11-24T07:40:49Z</dc:date>
    </item>
    <item>
      <title>Re: IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1559352#M197960</link>
      <description>&lt;P&gt;Hi&amp;nbsp; SanKet_Parekh&lt;/P&gt;&lt;P&gt;i tested with L4.14.78_1_0_0_ga_image_MX7DSABRESD image&lt;/P&gt;&lt;P&gt;i worked , there is a message&amp;nbsp; of "&amp;nbsp; gpmi-nand 33002000.gpmi-nand: mode:5 ,failed in set feature."&lt;/P&gt;&lt;P&gt;but i mounted&amp;nbsp; a nand partition with ubifs&amp;nbsp;&lt;/P&gt;&lt;P&gt;and i found that in L5.15 Kernel , when&amp;nbsp; in&amp;nbsp; &amp;nbsp;nand_onfi_detect&amp;nbsp; function nand_read_param_page_op&amp;nbsp; return&amp;nbsp; data&amp;nbsp; which&amp;nbsp; the first 190 bytes are "FF"s and got valid data. ,&amp;nbsp; but&amp;nbsp; in&amp;nbsp; u-boot, it read valid page data ,&lt;/P&gt;&lt;P&gt;thank you&amp;nbsp; for your interest&amp;nbsp;&lt;/P&gt;&lt;P&gt;[ 1.246169] input: fxas2100x as /devices/soc0/soc/30800000.aips-bus/30a30000.i2c/i2c-1/1-0020/input/input1&lt;BR /&gt;[ 1.261442] fxas2100x 1-0020: fxas2100x device driver probe successfully&lt;BR /&gt;[ 1.275288] random: fast init done&lt;BR /&gt;[ 1.281192] nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xdc&lt;BR /&gt;[ 1.287577] nand: Macronix MX30LF4G28AC&lt;BR /&gt;[ 1.291422] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 112&lt;BR /&gt;[ 1.299445] gpmi-nand 33002000.gpmi-nand: mode:5 ,failed in set feature.&lt;BR /&gt;[ 1.306478] Bad block table found at page 262080, version 0x01&lt;BR /&gt;[ 1.312745] Bad block table found at page 262016, version 0x01&lt;BR /&gt;[ 1.318948] nand_read_bbt: bad block at 0x0000011e0000&lt;BR /&gt;[ 1.324118] nand_read_bbt: bad block at 0x00000b0a0000&lt;BR /&gt;[ 1.329314] nand_read_bbt: bad block at 0x000015a60000&lt;BR /&gt;[ 1.334786] 5 cmdlinepart partitions found on MTD device gpmi-nand&lt;BR /&gt;[ 1.340998] Creating 5 MTD partitions on "gpmi-nand":&lt;BR /&gt;[ 1.346081] 0x000000000000-0x000000080000 : "mx7-bcb"&lt;BR /&gt;[ 1.352048] 0x000000080000-0x000000200000 : "u-boot1"&lt;BR /&gt;[ 1.357942] 0x000000200000-0x000000380000 : "u-boot2"&lt;BR /&gt;[ 1.363794] 0x000000380000-0x000000400000 : "u-boot-env"&lt;BR /&gt;[ 1.369926] 0x000000400000-0x000020000000 : "ubi"&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2022 10:40:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1559352#M197960</guid>
      <dc:creator>hyoungkikim</dc:creator>
      <dc:date>2022-11-24T10:40:20Z</dc:date>
    </item>
    <item>
      <title>Re: IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1559815#M198001</link>
      <description>&lt;P&gt;Comparing gpmi-nand.c from 5.15 and 5.4 I noticed removed gpmi_copy_bits() routine. Call to it got replaced with&amp;nbsp;nand_extract_bits() calls with same arguments set. Looks like routines aren't doing the same work. Restoring gpmi_copy_bits and call to it seems fixing all problems.&lt;/P&gt;&lt;P&gt;Edward&lt;/P&gt;</description>
      <pubDate>Fri, 25 Nov 2022 08:19:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1559815#M198001</guid>
      <dc:creator>kef2</dc:creator>
      <dc:date>2022-11-25T08:19:32Z</dc:date>
    </item>
    <item>
      <title>Re: IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1559856#M198009</link>
      <description>Changes to bysy_timeout_cycles further make NAND unreadable:&lt;BR /&gt;&lt;BR /&gt;busy_timeout_ps = max(sdr-&amp;gt;tBERS_max, sdr-&amp;gt;tPROG_max);&lt;BR /&gt;busy_timeout_cycles = TO_CYCLES(busy_timeout_ps, period_ps);&lt;BR /&gt;&lt;BR /&gt;Older code works OK:&lt;BR /&gt;busy_timeout_cycles = TO_CYCLES(sdr-&amp;gt;tWB_max + sdr-&amp;gt;tR_max, period_ps);&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Nov 2022 09:05:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1559856#M198009</guid>
      <dc:creator>kef2</dc:creator>
      <dc:date>2022-11-25T09:05:31Z</dc:date>
    </item>
    <item>
      <title>Re: IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1561734#M198163</link>
      <description>&lt;P&gt;hi&amp;nbsp;&lt;SPAN&gt;kef2&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;i tested as you adviced but it didn't work&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;the kernel ( L4.14) worked well on&amp;nbsp; a NADN Flash but&amp;nbsp; a kernel (5.x.x) doesn't work which reads ID sucessfully but when&amp;nbsp; reading parameter pages , it&amp;nbsp; got&amp;nbsp; 190byte dummy 0xFF data before valid data&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;thank you&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2022 04:52:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1561734#M198163</guid>
      <dc:creator>hyoungkikim</dc:creator>
      <dc:date>2022-11-30T04:52:11Z</dc:date>
    </item>
    <item>
      <title>Re: IMX7D NAND ECC error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1564870#M198371</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi kef2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;i recompiled a kernel and&amp;nbsp; it worked&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;thank you&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Dec 2022 03:54:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX7D-NAND-ECC-error/m-p/1564870#M198371</guid>
      <dc:creator>hyoungkikim</dc:creator>
      <dc:date>2022-12-06T03:54:44Z</dc:date>
    </item>
  </channel>
</rss>

