<?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: Can not boot up by MfgTool in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Can-not-boot-up-by-MfgTool/m-p/243648#M20738</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; You should special Linux version (updater) for the MFG. &lt;/P&gt;&lt;P&gt;Linux BSP provides the &lt;SPAN style="text-decoration: underline;"&gt;mfg firmware profile&lt;/SPAN&gt; for it. Under this profile special Linux &lt;/P&gt;&lt;P&gt;version is built; it is intended to be loaded by the MFG tool to DRAM of a target system&lt;/P&gt;&lt;P&gt;and interface with the MFG in order to get target images and write them to SD or NAND&lt;/P&gt;&lt;P&gt;during target system deployment. Please use Linux documentation how to build the firmware :&lt;BR /&gt;section 3.9 (Building Manufacturing Firmware) of "i.MX_6Dual6Quad_SABRE-SD_Linux_User's_Guide.pdf".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 Jan 2014 06:46:45 GMT</pubDate>
    <dc:creator>Yuri</dc:creator>
    <dc:date>2014-01-20T06:46:45Z</dc:date>
    <item>
      <title>Can not boot up by MfgTool</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Can-not-boot-up-by-MfgTool/m-p/243647#M20737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;My board is imx6q-sdb.&lt;/P&gt;&lt;P&gt;I have a question about how to make an uImage for MfgTool. &lt;BR /&gt;Before MfgTool burn image to flash, CPU will boot up first.&lt;/P&gt;&lt;P&gt;The MfgTool use two uImages,one for bootint up, another using to burn flash. &lt;/P&gt;&lt;P&gt;Now,I use the uImage which be compiled by myself.&lt;/P&gt;&lt;P&gt;When the MfgTool make the CPU boot up,it can not mount file system.&lt;/P&gt;&lt;P&gt;When I use the origin uImage include by MfgTool,CPU will start UTP when it finish initializing kernel.&lt;/P&gt;&lt;P&gt;Q:&lt;/P&gt;&lt;P&gt;What is UTP?&lt;/P&gt;&lt;P&gt;What do I need to modify my linux kernel?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UART print the blow information.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;Using origin uImage:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;......&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4&lt;/P&gt;&lt;P&gt;Bus freq driver module loaded&lt;/P&gt;&lt;P&gt;Bus freq driver Enabled&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;regulator_init_complete: PFUZE100_VGEN6: incomplete constraints, leaving on&lt;/P&gt;&lt;P&gt;regulator_init_complete: PFUZE100_VGEN3: incomplete constraints, leaving on&lt;/P&gt;&lt;P&gt;regulator_init_complete: PFUZE100_VGEN2: incomplete constraints, leaving on&lt;/P&gt;&lt;P&gt;regulator_init_complete: PFUZE100_VGEN1: incomplete constraints, leaving on&lt;/P&gt;&lt;P&gt;regulator_init_complete: SPKVDD: incomplete constraints, leaving on&lt;/P&gt;&lt;P&gt;snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)&lt;/P&gt;&lt;P&gt;Freeing init memory: 200K&lt;/P&gt;&lt;P&gt;Starting UTP&lt;/P&gt;&lt;P&gt;ln: /etc/mtab: File exists&lt;/P&gt;&lt;P&gt;disable turn off display&lt;/P&gt;&lt;P&gt;Starting the hotplug events dispatcher udevd&lt;/P&gt;&lt;P&gt;udevd (2001): /proc/2001/oom_adj is deprecated, please use /proc/2001/oom_score_&lt;/P&gt;&lt;P&gt;adj instead.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;Using my uImage:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;......&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;DVFS driver module loaded&lt;/P&gt;&lt;P&gt;regulator_init_complete: PFUZE100_VGEN6: incomplete constraints, leaving on&lt;/P&gt;&lt;P&gt;regulator_init_complete: PFUZE100_VGEN3: incomplete constraints, leaving on&lt;/P&gt;&lt;P&gt;regulator_init_complete: PFUZE100_VGEN2: incomplete constraints, leaving on&lt;/P&gt;&lt;P&gt;regulator_init_complete: PFUZE100_VGEN1: incomplete constraints, leaving on&lt;/P&gt;&lt;P&gt;snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)&lt;/P&gt;&lt;P&gt;List of all partitions:&lt;/P&gt;&lt;P&gt;1f00&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1024 mtdblock0&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;1f01&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 31744 mtdblock1&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;b300&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7757824 mmcblk0&amp;nbsp; driver: mmcblk&lt;/P&gt;&lt;P&gt;&amp;nbsp; b301&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7747584 mmcblk0p1 00000000-0000-0000-0000-000000000000&lt;/P&gt;&lt;P&gt;b310&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2048 mmcblk0boot1&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;b308&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2048 mmcblk0boot0&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;No filesystem could mount root, tried:&amp;nbsp; jffs2&lt;/P&gt;&lt;P&gt;Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)&lt;/P&gt;&lt;P&gt;[&amp;lt;80044854&amp;gt;] (unwind_backtrace+0x0/0xf8) from [&amp;lt;805067d4&amp;gt;] (panic+0x74/0x18c)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Jan 2014 03:57:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Can-not-boot-up-by-MfgTool/m-p/243647#M20737</guid>
      <dc:creator>carmilili</dc:creator>
      <dc:date>2014-01-20T03:57:45Z</dc:date>
    </item>
    <item>
      <title>Re: Can not boot up by MfgTool</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Can-not-boot-up-by-MfgTool/m-p/243648#M20738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; You should special Linux version (updater) for the MFG. &lt;/P&gt;&lt;P&gt;Linux BSP provides the &lt;SPAN style="text-decoration: underline;"&gt;mfg firmware profile&lt;/SPAN&gt; for it. Under this profile special Linux &lt;/P&gt;&lt;P&gt;version is built; it is intended to be loaded by the MFG tool to DRAM of a target system&lt;/P&gt;&lt;P&gt;and interface with the MFG in order to get target images and write them to SD or NAND&lt;/P&gt;&lt;P&gt;during target system deployment. Please use Linux documentation how to build the firmware :&lt;BR /&gt;section 3.9 (Building Manufacturing Firmware) of "i.MX_6Dual6Quad_SABRE-SD_Linux_User's_Guide.pdf".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Jan 2014 06:46:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Can-not-boot-up-by-MfgTool/m-p/243648#M20738</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2014-01-20T06:46:45Z</dc:date>
    </item>
  </channel>
</rss>

