<?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: YAFFS2 filesystem and UBIFS writing issue with IMX283 processor in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150876#M1084</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Mike, what is the limit of nand flash size which could be used without problem, with the current BP version?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Mar 2011 14:25:06 GMT</pubDate>
    <dc:creator>AhmetYUCE</dc:creator>
    <dc:date>2011-03-17T14:25:06Z</dc:date>
    <item>
      <title>YAFFS2 filesystem and UBIFS writing issue with IMX283 processor</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150874#M1082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;&amp;nbsp; We are using linux-2.6.35 released BSP. We are trying to bring up YAFFS2 on that .We mounted YAFFS2 and copied files system on the mount directory, so much of bad blocks are getting created. We tried using nand-write command nandwrite –a –o /dev/mtd1 nand.yaffs2 then it is crashing and we are getting the following messages&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;bad block at d3e0000, 1 block(s) gpmi-nfc gpmi-nfc.0: This driver doesn't support&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;t writing the OOB&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;from d3e0000 will be ski------------[ cut here ]------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;pped&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Writing data to blWARNING: at drivers/mtd/nand/gpmi-nfc/gpmi-nfc-mil.c:1014 mil_&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;ecc_write_oob+0x68/0xe8()&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;ock 1696 at offset 0xd40Modules linked in:0000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Bad block at d4000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;00, 1 block(s) from d400Backtrace: 000 will be skipped&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Wri&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;ting data to block 1697 [&amp;lt;c00354a8&amp;gt;] (dump_backtrace+0x0/0x114) from [&amp;lt;c0412fa0&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;] (dump_stack+0x18/0x1c)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;at offset 0xd420000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Bad r7:00000009 block at d420000, 1 blo r6:000003f6ck(s) from d420000 will&amp;nbsp; r5:c&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;0293e6cbe skipped&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Writing data r4:00000000 to block 1698 at offset&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;&amp;nbsp;0xd440000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Bad block at[&amp;lt;c0412f88&amp;gt;] (dump_stack+0x0/0x1c) from [&amp;lt;c004d69c&amp;gt;] (warn_slowpath_&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;common+0x54/0x6c)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;&amp;nbsp;d440000, 1 block(s) fro[&amp;lt;c004d648&amp;gt;] (warn_slowpath_common+0x0/0x6c) from [&amp;lt;c004&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;d6d8&amp;gt;] (warn_slowpath_null+0x24/0x2c)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;m d440000 will be skipped r9:000e2880d&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Writing data to block r8:0000000b 1699 at offset 0xd46000 r7:0001d7800&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Bad block at d460000, r6:c0595ad0 1 block(s) from d460000 r5:c77a41e8 will be skipped&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;&amp;nbsp;&amp;nbsp;Is there any patch for gpmi-nfc driver to support &amp;nbsp;this?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;&amp;nbsp;We even tried with nandwrite –a –p /dev/mtd1 nand.yaffs2. It is showing as writing success, but if we mount the filesystem, we are able to see only lost+ found directory. We created .yaffs2 image by using mkyaffs2 utils.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;We even tried with UBIFS, once it is getting attached and we could able mount and copy filesystem into it, but if we detach ubi and attach again the we are getting the following errors&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;UBI error: ubi_scan_add_used: two LEBs with same sequence number 4&lt;BR /&gt;ubiattach: error!: cannot attach mtd1&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; error 22 (Invalid argument)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;Along with this we even tried nand write in u-boot. We are getting the following error.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;nand write 0x42000000 0 0x30000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;NAND write: device 0 offset 0x0, size 0x30000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;[send_page] DMA error&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;[send_page] DMA error&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;[send_page] DMA error&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;[send_page] DMA error&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;[send_page] DMA error&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;[send_page] DMA error&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;[send_page] DMA error&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;196608 bytes written: OK&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;As per the below mail post they are telling that nand driver is not ported for imx283 in the linux 2.6.35 BSP. &amp;nbsp;But in the reference manual it is told that gpmi-nfc is the driver for NAND. We need to get the proper clarification on this. &amp;nbsp;Please help us to resolve this issue as early as possible&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.spinics.net/lists/u-boot-v2/msg02497.html" title="http://www.spinics.net/lists/u-boot-v2/msg02497.html"&gt;&lt;SPAN style="font-family: 'Courier New'; font-size: 2; "&gt;&lt;/SPAN&gt;&lt;/A&gt;&lt;A href="http://www.spinics.net/lists/u-boot-v2/msg02497.html" target="test_blank"&gt;http://www.spinics.net/lists/u-boot-v2/msg02497.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New'; font-size: 2; "&gt;Thanks and Regards&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New'; font-size: 2; "&gt;Deepthi&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626F; font-family: Arial; font-size: 1; "&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Mar 2011 03:57:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150874#M1082</guid>
      <dc:creator>deepthikiran</dc:creator>
      <dc:date>2011-03-15T03:57:15Z</dc:date>
    </item>
    <item>
      <title>Re: YAFFS2 filesystem and UBIFS writing issue with IMX283 processor</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150875#M1083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I ran into this problem also using ubifs. It turned out to be a bug in the NAND flash driver. I was able to get it working with a smaller size NAND device, but larger devices show the bug. It has been reported to Freescale and verified by their support team. I don't know how soon a solution will be available.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2011 01:52:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150875#M1083</guid>
      <dc:creator>iMxGuy</dc:creator>
      <dc:date>2011-03-17T01:52:40Z</dc:date>
    </item>
    <item>
      <title>Re: YAFFS2 filesystem and UBIFS writing issue with IMX283 processor</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150876#M1084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Mike, what is the limit of nand flash size which could be used without problem, with the current BP version?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2011 14:25:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150876#M1084</guid>
      <dc:creator>AhmetYUCE</dc:creator>
      <dc:date>2011-03-17T14:25:06Z</dc:date>
    </item>
    <item>
      <title>Re: YAFFS2 filesystem and UBIFS writing issue with IMX283 processor</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150877#M1085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;BSP version, sorry.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2011 14:25:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150877#M1085</guid>
      <dc:creator>AhmetYUCE</dc:creator>
      <dc:date>2011-03-17T14:25:39Z</dc:date>
    </item>
    <item>
      <title>Re: YAFFS2 filesystem and UBIFS writing issue with IMX283 processor</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150878#M1086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It looks like chips under 512MB will work but I only tested this one device. The 1GB size chip did not work for me.&lt;BR /&gt; &lt;BR /&gt;This chip works&lt;/P&gt;&lt;P&gt;&lt;BR /&gt; NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-b)&lt;BR /&gt;-----------------------------&lt;BR /&gt;NAND Flash Device Information&lt;BR /&gt;-----------------------------&lt;BR /&gt;Manufacturer : Samsung (0xec)&lt;BR /&gt;Device Code : 0xdc&lt;BR /&gt;Cell Technology : SLC&lt;BR /&gt;Chip Size : 512 MiB&lt;BR /&gt;Pages per Block : 64&lt;BR /&gt;Page Geometry : 2048+64&lt;BR /&gt;ECC Strength : 4 bits&lt;BR /&gt;ECC Size : 512 B&lt;BR /&gt;Data Setup Time : 15 ns&lt;BR /&gt;Data Hold Time : 12 ns&lt;BR /&gt;Address Setup Time: 25 ns&lt;BR /&gt;GPMI Sample Delay : 6 ns&lt;BR /&gt;tREA : Unknown&lt;BR /&gt;tRLOH : Unknown&lt;BR /&gt;tRHOH : Unknown&lt;BR /&gt;Description : K9F4G08&lt;BR /&gt;-----------------&lt;BR /&gt;Physical Geometry&lt;BR /&gt;-----------------&lt;BR /&gt;Chip Count : 1&lt;BR /&gt;Page Data Size in Bytes: 2048 (0x800)&lt;BR /&gt;Page OOB Size in Bytes : 64&lt;BR /&gt;Block Size in Bytes : 131072 (0x20000)&lt;BR /&gt;Block Size in Pages : 64 (0x40)&lt;BR /&gt;Chip Size in Bytes : 536870912 (0x20000000)&lt;BR /&gt;Chip Size in Pages : 262144 (0x40000)&lt;BR /&gt;Chip Size in Blocks : 4096 (0x1000)&lt;BR /&gt;Medium Size in Bytes : 536870912 (0x20000000)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;This chip does not work&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)&lt;BR /&gt;-----------------------------&lt;BR /&gt;NAND Flash Device Information&lt;BR /&gt;-----------------------------&lt;BR /&gt;Manufacturer : Micron (0x2c)&lt;BR /&gt;Device Code : 0xd3&lt;BR /&gt;Cell Technology : SLC&lt;BR /&gt;Chip Size : 1 GiB&lt;BR /&gt;Pages per Block : 64&lt;BR /&gt;Page Geometry : 2048+64&lt;BR /&gt;ECC Strength : 4 bits&lt;BR /&gt;ECC Size : 512 B&lt;BR /&gt;Data Setup Time : 25 ns&lt;BR /&gt;Data Hold Time : 15 ns&lt;BR /&gt;Address Setup Time: 10 ns&lt;BR /&gt;GPMI Sample Delay : 6 ns&lt;BR /&gt;tREA : Unknown&lt;BR /&gt;tRLOH : Unknown&lt;BR /&gt;tRHOH : Unknown&lt;BR /&gt;Description : MT29F8G08FABWG&lt;BR /&gt;-----------------&lt;BR /&gt;Physical Geometry&lt;BR /&gt;-----------------&lt;BR /&gt;Chip Count : 1&lt;BR /&gt;Page Data Size in Bytes: 2048 (0x800)&lt;BR /&gt;Page OOB Size in Bytes : 64&lt;BR /&gt;Block Size in Bytes : 131072 (0x20000)&lt;BR /&gt;Block Size in Pages : 64 (0x40)&lt;BR /&gt;Chip Size in Bytes : 1073741824 (0x40000000)&lt;BR /&gt;Chip Size in Pages : 524288 (0x80000)&lt;BR /&gt;Chip Size in Blocks : 8192 (0x2000)&lt;BR /&gt;Medium Size in Bytes : 1073741824 (0x40000000)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2011 15:40:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150878#M1086</guid>
      <dc:creator>iMxGuy</dc:creator>
      <dc:date>2011-03-17T15:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: YAFFS2 filesystem and UBIFS writing issue with IMX283 processor</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150879#M1087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mike,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I see you were able to get to some level of success with using ubifs&amp;nbsp;as your root filesystem format on NAND.&lt;/P&gt;&lt;P&gt;Using the i.MX28_Linux_BSP_Userguide.pdf&amp;nbsp;for assistance with this, I cant seem to be able to mount the file system:&lt;/P&gt;&lt;P&gt;I get the following error printout:&lt;/P&gt;&lt;P&gt;UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs0", error -19&lt;BR /&gt;VFS: Cannot open root device "ubi0:rootfs0" or unknown-block(0,0)&lt;BR /&gt;Please append a correct "root=" boot option; here are the available partitions:&lt;BR /&gt;1f00&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20480 mtdblock0 (driver?)&lt;BR /&gt;1f01&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 110592 mtdblock1 (driver?)&lt;BR /&gt;Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)&lt;/P&gt;&lt;P&gt;I am using the default boot command:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 2; "&gt;noinitrd console=ttyAM0,115200 ubi.mtd=1 root=ubi0:rootfs0 rootfstype=ubifs rw gpmi&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When flashing the NAND on my i.MX28 EVK, I assumed I was to flash the output of the ltib build for ubifs - rootfs.uifs.img as follows:&lt;/P&gt;&lt;P&gt;nandwrite /dev/mtd1 rootfs.ubifs.img,&lt;/P&gt;&lt;P&gt;after flashing the kernel and bootlet:&lt;/P&gt;&lt;P&gt;kobs-ng init -v imx28_ivt_linux.sb&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there an error in this procedure or a missing step somewhere?&lt;/P&gt;&lt;P&gt;Any help on this would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;FYI: I have been able to get a .ext3 formatted root&amp;nbsp;filesystem to mount successfully, so I think the underlying drivers are all OK.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Robert G&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;CITE&gt;Mike Morrell said:&lt;/CITE&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;DIV&gt;I ran into this problem also using ubifs. It turned out to be a bug in the NAND flash driver. I was able to get it working with a smaller size NAND device, but larger devices show the bug. It has been reported to Freescale and verified by their support team. I don't know how soon a solution will be available.&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 May 2011 18:37:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150879#M1087</guid>
      <dc:creator>RobertMGirard</dc:creator>
      <dc:date>2011-05-13T18:37:08Z</dc:date>
    </item>
    <item>
      <title>Re: YAFFS2 filesystem and UBIFS writing issue with IMX283 processor</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150880#M1088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Are you able to boot u-boot from Samsung K9F4G08 NAND.&lt;/P&gt;&lt;P&gt;If yes,what version of u-boot and did you changed anything in u-boot to boot from NAND.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm also using Samsung K9F4G08 NAND 1GB but i'm not able to boot from NAND.&lt;/P&gt;&lt;P&gt;Previously i had Micron NAND and i was able to boot from it.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;hitlin37&lt;BR /&gt; &lt;BR /&gt; &lt;CITE&gt;Mike Morrell said:&lt;/CITE&gt;&lt;/P&gt;&lt;BLOCKQUOTE cite="http://imxcommunity.org/forum/topics/yaffs2-filesystem-and-ubifs?commentId=4103961%3AComment%3A6953#4103961Comment6953"&gt;&lt;DIV&gt;&lt;DIV class="xg_user_generated"&gt;&lt;P&gt;It looks like chips under 512MB will work but I only tested this one device. The 1GB size chip did not work for me.&lt;BR /&gt; &lt;BR /&gt; This chip works&lt;/P&gt;&lt;P&gt;&lt;BR /&gt; NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-b)&lt;BR /&gt; -----------------------------&lt;BR /&gt; NAND Flash Device Information&lt;BR /&gt; -----------------------------&lt;BR /&gt; Manufacturer : Samsung (0xec)&lt;BR /&gt; Device Code : 0xdc&lt;BR /&gt; Cell Technology : SLC&lt;BR /&gt; Chip Size : 512 MiB&lt;BR /&gt; Pages per Block : 64&lt;BR /&gt; Page Geometry : 2048+64&lt;BR /&gt; ECC Strength : 4 bits&lt;BR /&gt; ECC Size : 512 B&lt;BR /&gt; Data Setup Time : 15 ns&lt;BR /&gt; Data Hold Time : 12 ns&lt;BR /&gt; Address Setup Time: 25 ns&lt;BR /&gt; GPMI Sample Delay : 6 ns&lt;BR /&gt; tREA : Unknown&lt;BR /&gt; tRLOH : Unknown&lt;BR /&gt; tRHOH : Unknown&lt;BR /&gt; Description : K9F4G08&lt;BR /&gt; -----------------&lt;BR /&gt; Physical Geometry&lt;BR /&gt; -----------------&lt;BR /&gt; Chip Count : 1&lt;BR /&gt; Page Data Size in Bytes: 2048 (0x800)&lt;BR /&gt; Page OOB Size in Bytes : 64&lt;BR /&gt; Block Size in Bytes : 131072 (0x20000)&lt;BR /&gt; Block Size in Pages : 64 (0x40)&lt;BR /&gt; Chip Size in Bytes : 536870912 (0x20000000)&lt;BR /&gt; Chip Size in Pages : 262144 (0x40000)&lt;BR /&gt; Chip Size in Blocks : 4096 (0x1000)&lt;BR /&gt; Medium Size in Bytes : 536870912 (0x20000000)&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; This chip does not work&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)&lt;BR /&gt; -----------------------------&lt;BR /&gt; NAND Flash Device Information&lt;BR /&gt; -----------------------------&lt;BR /&gt; Manufacturer : Micron (0x2c)&lt;BR /&gt; Device Code : 0xd3&lt;BR /&gt; Cell Technology : SLC&lt;BR /&gt; Chip Size : 1 GiB&lt;BR /&gt; Pages per Block : 64&lt;BR /&gt; Page Geometry : 2048+64&lt;BR /&gt; ECC Strength : 4 bits&lt;BR /&gt; ECC Size : 512 B&lt;BR /&gt; Data Setup Time : 25 ns&lt;BR /&gt; Data Hold Time : 15 ns&lt;BR /&gt; Address Setup Time: 10 ns&lt;BR /&gt; GPMI Sample Delay : 6 ns&lt;BR /&gt; tREA : Unknown&lt;BR /&gt; tRLOH : Unknown&lt;BR /&gt; tRHOH : Unknown&lt;BR /&gt; Description : MT29F8G08FABWG&lt;BR /&gt; -----------------&lt;BR /&gt; Physical Geometry&lt;BR /&gt; -----------------&lt;BR /&gt; Chip Count : 1&lt;BR /&gt; Page Data Size in Bytes: 2048 (0x800)&lt;BR /&gt; Page OOB Size in Bytes : 64&lt;BR /&gt; Block Size in Bytes : 131072 (0x20000)&lt;BR /&gt; Block Size in Pages : 64 (0x40)&lt;BR /&gt; Chip Size in Bytes : 1073741824 (0x40000000)&lt;BR /&gt; Chip Size in Pages : 524288 (0x80000)&lt;BR /&gt; Chip Size in Blocks : 8192 (0x2000)&lt;BR /&gt; Medium Size in Bytes : 1073741824 (0x40000000)&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jan 2012 13:56:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150880#M1088</guid>
      <dc:creator>hitlin37</dc:creator>
      <dc:date>2012-01-03T13:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: YAFFS2 filesystem and UBIFS writing issue with IMX283 processor</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150881#M1089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Can anyone confirm that there's a trouble when using some NAND of 512MiB?? I'm using a SLC NAND from Hynix and I get the same error messages than Robert.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Thx. BR,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Fernando&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Nov 2012 12:50:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/YAFFS2-filesystem-and-UBIFS-writing-issue-with-IMX283-processor/m-p/150881#M1089</guid>
      <dc:creator>fluiss</dc:creator>
      <dc:date>2012-11-07T12:50:32Z</dc:date>
    </item>
  </channel>
</rss>

