<?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 Cannot flash complete NAND in one go in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Cannot-flash-complete-NAND-in-one-go/m-p/235144#M18529</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a problem flashing NAND on MX53 (SABRE-AI). After I flash bootloader with kobs-ng and then the kernel right after, everything seems to go okay (readback from flash is correct), but after rebooting, I can see that kernel is corrupt (some bytes have flipped to 0xff). After re-writing kernel-only, then it will appear correct after reboot. Why cannot I write complete NAND in one go, is it even supposed to work? From the forums or application notes I didn't find anything concerning this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are the commands I've been using:&lt;/P&gt;&lt;P&gt;# flash_erase /dev/mtd0 0 0&lt;/P&gt;&lt;P&gt;# kobs-ng init --chip_0_device_path=/dev/mtd0 uboot.bin&lt;/P&gt;&lt;P&gt;# flash_erase /dev/mtd1 0 0&lt;/P&gt;&lt;P&gt;# nandwrite -p /dev/mtd1 kernel.bin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have verified the behavior with two different NAND models: MT29F2G08 and S34ML01G2. My kernel version is 2.6.35.3.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Feb 2014 09:14:56 GMT</pubDate>
    <dc:creator>henri_bragge</dc:creator>
    <dc:date>2014-02-14T09:14:56Z</dc:date>
    <item>
      <title>Cannot flash complete NAND in one go</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Cannot-flash-complete-NAND-in-one-go/m-p/235144#M18529</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a problem flashing NAND on MX53 (SABRE-AI). After I flash bootloader with kobs-ng and then the kernel right after, everything seems to go okay (readback from flash is correct), but after rebooting, I can see that kernel is corrupt (some bytes have flipped to 0xff). After re-writing kernel-only, then it will appear correct after reboot. Why cannot I write complete NAND in one go, is it even supposed to work? From the forums or application notes I didn't find anything concerning this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are the commands I've been using:&lt;/P&gt;&lt;P&gt;# flash_erase /dev/mtd0 0 0&lt;/P&gt;&lt;P&gt;# kobs-ng init --chip_0_device_path=/dev/mtd0 uboot.bin&lt;/P&gt;&lt;P&gt;# flash_erase /dev/mtd1 0 0&lt;/P&gt;&lt;P&gt;# nandwrite -p /dev/mtd1 kernel.bin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have verified the behavior with two different NAND models: MT29F2G08 and S34ML01G2. My kernel version is 2.6.35.3.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Feb 2014 09:14:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Cannot-flash-complete-NAND-in-one-go/m-p/235144#M18529</guid>
      <dc:creator>henri_bragge</dc:creator>
      <dc:date>2014-02-14T09:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot flash complete NAND in one go</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Cannot-flash-complete-NAND-in-one-go/m-p/235145#M18530</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, Henri!&lt;/P&gt;&lt;P&gt;Follow my work sequency for write Linux and U-Boot on NAND:&lt;/P&gt;&lt;P&gt;// U-Boot&lt;/P&gt;&lt;P&gt;TARGET=`grep bootloader /proc/mtd | cut -d ':' -f1`&lt;/P&gt;&lt;P&gt;echo "Write U-Boot on NAND /dev/$TARGET"&lt;/P&gt;&lt;P&gt;/root/flash_erase /dev/$TARGET 0 0&lt;/P&gt;&lt;P&gt;echo 1 &amp;gt; /sys/devices/platform/mxc_nandv2_flash.0/ignorebad&lt;/P&gt;&lt;P&gt;/root/kobs-ng init --chip_0_device_path=/dev/$TARGET $UBOOT&lt;/P&gt;&lt;P&gt;echo 0 &amp;gt; /sys/devices/platform/mxc_nandv2_flash.0/ignorebad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;// Linux&lt;/P&gt;&lt;P&gt;TARGET=`grep -m 1 kernel /proc/mtd | cut -d ':' -f1`&lt;/P&gt;&lt;P&gt;echo "Write Linux on NAND /dev/$TARGET"&lt;/P&gt;&lt;P&gt;/root/flash_erase /dev/$TARGET 0 0&lt;/P&gt;&lt;P&gt;/root/nandwrite -mp /dev/$TARGET $LINUX&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this help you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Feb 2014 10:38:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Cannot-flash-complete-NAND-in-one-go/m-p/235145#M18530</guid>
      <dc:creator>BrilliantovKiri</dc:creator>
      <dc:date>2014-02-17T10:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot flash complete NAND in one go</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Cannot-flash-complete-NAND-in-one-go/m-p/235146#M18531</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kirill, thanks for your answer. The commands worked otherwise, but unfortunately didn't solve the problem. After reboot I still get errors like this when diffing hexdumps of the original file and NAND:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;-00002fd0&amp;nbsp; 03 00&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;+00002fd0&amp;nbsp; ff 00&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-000037d0&amp;nbsp; 00 09&lt;/P&gt;&lt;P&gt;+000037d0&amp;nbsp; ff 09&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But your answer confirmed me that it should be possible and my commands are OK. There could be something wrong with my custom-built kernel or mtd-tools, I will probably try to rule that out next.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Henri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2014 11:56:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Cannot-flash-complete-NAND-in-one-go/m-p/235146#M18531</guid>
      <dc:creator>henri_bragge</dc:creator>
      <dc:date>2014-02-18T11:56:00Z</dc:date>
    </item>
  </channel>
</rss>

