<?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 Yocto Boot Problem - Custom Device Tree in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-Boot-Problem-Custom-Device-Tree/m-p/457377#M71509</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am developing a Yocto Linux kernel for a custom SBC based on the I.MX6Q. I have generated a device tree for the SBC and am executing 'bitbake core-image-base'. Everything appears to be good, but when I boot the image, it stops at the 'Starting kernel ...' message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have traced the issue to the early_init_dt_scan function call. The parameter being passed when the function is called does not point to my device tree but appears to be pointing at u-boot parameters instead. The device tree does build and looks correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are the contents being passed to the function:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="yocto.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/52017i3BD8EC5F38AC4D11/image-size/large?v=v2&amp;amp;px=999" role="button" title="yocto.png" alt="yocto.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the code checks for the proper DTS signature, it fails because the value is 5 instead of OF_DT_HEADER. Any idea why the data being passed is not the DTB file?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a customization step I am missing when adding a custom device tree?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Dec 2015 23:39:53 GMT</pubDate>
    <dc:creator>PaulDeMetrotion</dc:creator>
    <dc:date>2015-12-01T23:39:53Z</dc:date>
    <item>
      <title>Yocto Boot Problem - Custom Device Tree</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-Boot-Problem-Custom-Device-Tree/m-p/457377#M71509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am developing a Yocto Linux kernel for a custom SBC based on the I.MX6Q. I have generated a device tree for the SBC and am executing 'bitbake core-image-base'. Everything appears to be good, but when I boot the image, it stops at the 'Starting kernel ...' message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have traced the issue to the early_init_dt_scan function call. The parameter being passed when the function is called does not point to my device tree but appears to be pointing at u-boot parameters instead. The device tree does build and looks correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are the contents being passed to the function:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="yocto.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/52017i3BD8EC5F38AC4D11/image-size/large?v=v2&amp;amp;px=999" role="button" title="yocto.png" alt="yocto.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the code checks for the proper DTS signature, it fails because the value is 5 instead of OF_DT_HEADER. Any idea why the data being passed is not the DTB file?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a customization step I am missing when adding a custom device tree?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Dec 2015 23:39:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-Boot-Problem-Custom-Device-Tree/m-p/457377#M71509</guid>
      <dc:creator>PaulDeMetrotion</dc:creator>
      <dc:date>2015-12-01T23:39:53Z</dc:date>
    </item>
    <item>
      <title>Re: Yocto Boot Problem - Custom Device Tree</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-Boot-Problem-Custom-Device-Tree/m-p/457378#M71510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I really could use some help. Still have not resolved this issue. Somebody must have some experience customizing Yocto for a device that is not included by Freescale. Any advice is appreciated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I added my device tree file to the arch/arm/boot/dts directory and added this dtb file to the Makefile in the same directory. In my conf file I have the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#@TYPE: Machine&lt;/P&gt;&lt;P&gt;#@NAME: i.MX6Q SBC35-C398&lt;/P&gt;&lt;P&gt;#@SOC: i.MX6Q&lt;/P&gt;&lt;P&gt;#@DESCRIPTION: Machine configuration for i.MX6Q SBC35-C398&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;#@MAINTAINER: Paul DeMetrotion &amp;lt;&lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:pdemetrotion@winsystems.com"&gt;pdemetrotion@winsystems.com&lt;/A&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;require conf/machine/include/imx-base.inc&lt;/P&gt;&lt;P&gt;require conf/machine/include/tune-cortexa9.inc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SOC_FAMILY = "mx6:mx6q"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;KERNEL_DEVICETREE = "imx6q-c398.dtb"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.5;"&gt;UBOOT_CONFIG ??= "sd"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;UBOOT_CONFIG[sd] = "mx6qc398_config,sdcard"&lt;/P&gt;&lt;P&gt;UBOOT_CONFIG[sata] = "mx6qc398_sata_config"&lt;/P&gt;&lt;P&gt;UBOOT_CONFIG[mfgtool] = "mx6qc398_config"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SERIAL_CONSOLE = "115200 ttymxc0"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Am I missing something?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Dec 2015 21:48:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-Boot-Problem-Custom-Device-Tree/m-p/457378#M71510</guid>
      <dc:creator>PaulDeMetrotion</dc:creator>
      <dc:date>2015-12-02T21:48:34Z</dc:date>
    </item>
    <item>
      <title>Re: Yocto Boot Problem - Custom Device Tree</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-Boot-Problem-Custom-Device-Tree/m-p/457379#M71511</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is a document "i.MX_6_BSP_Porting_Guide.pdf" in the Linux BSP bundle. You may read it for reference.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Dec 2015 06:34:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-Boot-Problem-Custom-Device-Tree/m-p/457379#M71511</guid>
      <dc:creator>jimmychan</dc:creator>
      <dc:date>2015-12-04T06:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: Yocto Boot Problem - Custom Device Tree</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-Boot-Problem-Custom-Device-Tree/m-p/457380#M71512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This issue is resolved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Was not using bootz or passing the device tree blob file. The following environment variables fixed the problem:&lt;/P&gt;&lt;P&gt;"bootcmd_mmc=run bootargs_mmc; "&amp;nbsp;&amp;nbsp; \&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "fatload mmc 0:1 ${loadaddr} ${kernel}; " \&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "fatload mmc 0:1 ${fdt_addr} ${fdt_file}; " \&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "bootz ${loadaddr} - ${fdt_addr};\0" \&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Dec 2015 19:34:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-Boot-Problem-Custom-Device-Tree/m-p/457380#M71512</guid>
      <dc:creator>PaulDeMetrotion</dc:creator>
      <dc:date>2015-12-09T19:34:19Z</dc:date>
    </item>
  </channel>
</rss>

