<?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: i.MX6 Manufacturing Tool Issue in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6-Manufacturing-Tool-Issue/m-p/288173#M34364</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I get my first response right after I fixed the problem. The solution was simple but not specified in the Manufacturing Tool Firmware Development Guide. The document should specify that the uuc and mtd-utils packages should be included in the kernel build. This may be obvious but I missed it. Once I selected these packages, the archive file initramfs.cpio.gz.uboot was usable during the manufacturing process.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Feb 2014 17:43:39 GMT</pubDate>
    <dc:creator>PaulDeMetrotion</dc:creator>
    <dc:date>2014-02-12T17:43:39Z</dc:date>
    <item>
      <title>i.MX6 Manufacturing Tool Issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6-Manufacturing-Tool-Issue/m-p/288170#M34361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am working on a custom device that uses the i.MX6Q processor. I am trying to use the Manufacturing Tool version 4.1.0 to program an SPI-NOR device on an SPI bus. I use LTIB to generate u-boot and uImage binaries without any problems. I also generate the initramfs.cpio.gz.uboot file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I use the initramfs.cpio.gz.uboot file included with the manufacturing tool release, I can program our device without any problem. If I try to use the initramfs file built by LTIB, I cannot use the manufacturing tool. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following is a portion of the console output where the boot fails. Any idea why the root device being searched for is not included? Is there a build setting that I need to change?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mxc_dvfs_core_probe&lt;/P&gt;&lt;P&gt;DVFS driver module loaded&lt;/P&gt;&lt;P&gt;snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 03:06:22 UTC (11182)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;VFS: Cannot open root device "(null)" or unknown-block(0,0)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Please append a correct "root=" boot option; here are the available partitions:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1f00&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 512 mtdblock0&amp;nbsp; (driver?)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1f01&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; 8 mtdblock1&amp;nbsp; (driver?)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1f02&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3520 mtdblock2&amp;nbsp; (driver?)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Unable to handle kernel NULL pointer dereference at virtual address 00000027&lt;/P&gt;&lt;P&gt;pgd = e71a8000&lt;/P&gt;&lt;P&gt;[00000027] *pgd=7712a831, *pte=00000000, *ppte=00000000&lt;/P&gt;&lt;P&gt;Internal error: Oops: 17 [#1] PREEMPT SMP&lt;/P&gt;&lt;P&gt;Modules linked in:&lt;/P&gt;&lt;P&gt;CPU: 3&amp;nbsp;&amp;nbsp;&amp;nbsp; Not tainted&amp;nbsp; (3.0.35-2666-gbdde708 #44)&lt;/P&gt;&lt;P&gt;PC is at fget+0x40/0xbc&lt;/P&gt;&lt;P&gt;LR is at fget+0x20/0xbc&lt;/P&gt;&lt;P&gt;pc : [&amp;lt;800e44bc&amp;gt;]&amp;nbsp;&amp;nbsp;&amp;nbsp; lr : [&amp;lt;800e449c&amp;gt;]&amp;nbsp;&amp;nbsp;&amp;nbsp; psr: a0000013&lt;/P&gt;&lt;P&gt;sp : e7181f30&amp;nbsp; ip : 10c53c7d&amp;nbsp; fp : 00000000&lt;/P&gt;&lt;P&gt;r10: 00000000&amp;nbsp; r9 : e7180000&amp;nbsp; r8 : 8003b184&lt;/P&gt;&lt;P&gt;r7 : 000000c5&amp;nbsp; r6 : 00000011&amp;nbsp; r5 : e9c4ee00&amp;nbsp; r4 : ffffffff&lt;/P&gt;&lt;P&gt;r3 : e74f1008&amp;nbsp; r2 : 00000100&amp;nbsp; r1 : e7181f50&amp;nbsp; r0 : 00000001&lt;/P&gt;&lt;P&gt;Flags: NzCv&amp;nbsp; IRQs on&amp;nbsp; FIQs on&amp;nbsp; Mode SVC_32&amp;nbsp; ISA ARM&amp;nbsp; Segment user&lt;/P&gt;&lt;P&gt;Control: 10c53c7d&amp;nbsp; Table: 771a804a&amp;nbsp; DAC: 00000015&lt;/P&gt;&lt;P&gt;Process env (pid: 4342, stack limit = 0xe71802f0)&lt;/P&gt;&lt;P&gt;Stack: (0xe7181f30 to 0xe7182000)&lt;/P&gt;&lt;P&gt;1f20:&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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00000001 7ee8abf0 e7181f50 800e7620&lt;/P&gt;&lt;P&gt;1f40: 00000001 7ee8abf0 ffffffff 800e7814 e9d61d80 60000013 00000001 2aae9000&lt;/P&gt;&lt;P&gt;1f60: 2aae9000 e7180000 00000005 00000000 e7180000 00000000 7ee8aaac 800d1fdc&lt;/P&gt;&lt;P&gt;1f80: 08100875 0002ab82 e9c4ee40 e9bb8000 2aae9560 00000018 2aac4724 0000040f&lt;/P&gt;&lt;P&gt;1fa0: 2ad645d0 8003b000 2ad645d0 ffffffff 00000001 7ee8abf0 7ee8abf0 00000001&lt;/P&gt;&lt;P&gt;1fc0: 2ad645d0 ffffffff 00000011 000000c5 0000011e 00000000 2aae9000 00000000&lt;/P&gt;&lt;P&gt;1fe0: 2ac9ccf0 7ee8abe4 2ac9a1c8 2acf6034 20000010 00000001 79ffc811 79ffcc11&lt;/P&gt;&lt;P&gt;[&amp;lt;800e44bc&amp;gt;] (fget+0x40/0xbc) from [&amp;lt;800e7620&amp;gt;] (vfs_fstat+0xc/0x3c)&lt;/P&gt;&lt;P&gt;[&amp;lt;800e7620&amp;gt;] (vfs_fstat+0xc/0x3c) from [&amp;lt;800e7814&amp;gt;] (sys_fstat64+0x14/0x30)&lt;/P&gt;&lt;P&gt;[&amp;lt;800e7814&amp;gt;] (sys_fstat64+0x14/0x30) from [&amp;lt;8003b000&amp;gt;] (ret_fast_syscall+0x0/0x30)&lt;/P&gt;&lt;P&gt;Code: e5933004 e7934104 e3540000 0a000017 (e5943028)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Feb 2014 16:34:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6-Manufacturing-Tool-Issue/m-p/288170#M34361</guid>
      <dc:creator>PaulDeMetrotion</dc:creator>
      <dc:date>2014-02-10T16:34:51Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6 Manufacturing Tool Issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6-Manufacturing-Tool-Issue/m-p/288171#M34362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have attached a file that shows the difference between the two console outputs. The top one shows a successful boot with the original initramfs file and the bottom one shows the boot failure with the custom built initramfs file.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="otg.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/42680i98FCC38711F9C0AC/image-size/large?v=v2&amp;amp;px=999" role="button" title="otg.png" alt="otg.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Feb 2014 14:54:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6-Manufacturing-Tool-Issue/m-p/288171#M34362</guid>
      <dc:creator>PaulDeMetrotion</dc:creator>
      <dc:date>2014-02-12T14:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6 Manufacturing Tool Issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6-Manufacturing-Tool-Issue/m-p/288172#M34363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should post the full boot log. There is not enough information here. There are many things that might have gone wrong like:&lt;/P&gt;&lt;P&gt;* Your u-boot doesn't boot to initramfs&lt;/P&gt;&lt;P&gt;* Incorrect address for initramfs&lt;/P&gt;&lt;P&gt;* Problem with the initramfs configuration or files&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a first thing, I would check if /init is pointing to the right place like /bin/busybox. Avoid using relative paths like ../bin/busybox.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Feb 2014 17:09:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6-Manufacturing-Tool-Issue/m-p/288172#M34363</guid>
      <dc:creator>KursadOney</dc:creator>
      <dc:date>2014-02-12T17:09:41Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6 Manufacturing Tool Issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6-Manufacturing-Tool-Issue/m-p/288173#M34364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I get my first response right after I fixed the problem. The solution was simple but not specified in the Manufacturing Tool Firmware Development Guide. The document should specify that the uuc and mtd-utils packages should be included in the kernel build. This may be obvious but I missed it. Once I selected these packages, the archive file initramfs.cpio.gz.uboot was usable during the manufacturing process.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Feb 2014 17:43:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6-Manufacturing-Tool-Issue/m-p/288173#M34364</guid>
      <dc:creator>PaulDeMetrotion</dc:creator>
      <dc:date>2014-02-12T17:43:39Z</dc:date>
    </item>
  </channel>
</rss>

