<?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>i.MX ProcessorsのトピックI.MX6 U-Boot hang while it boot linux kernel</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910313#M137140</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="text-align: center;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;U-Boot Version: u-boot-fslc&amp;nbsp; 2017.11-fslc&amp;nbsp;&amp;nbsp;&lt;A href="https://github.com/Freescale/u-boot-fslc/commit/a07698f0bfdb2887b617399643acd659c6e75138"&gt;https://github.com/Freescale/u-boot-fslc/commit/a07698f0bfdb2887b617399643acd659c6e75138&lt;/A&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;Board: i.mx6ul&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;It can boot successfully until I add some debug information in boot process by printf function just like in the patch in attachments.&amp;nbsp; After adding some printf, U-Boot bootz command can't parse the dtb successfully, and then hang. The detailed error messages :&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P&gt;=&amp;gt; load mmc 1:1 0x83000000 imx6ul-14x14-evk.dtb&lt;BR /&gt;reading imx6ul-14x14-evk.dtb&lt;BR /&gt;37104 bytes read in 19 ms (1.9 MiB/s)&lt;BR /&gt;=&amp;gt; load mmc 1:1 0x82000000 zImage&lt;BR /&gt;reading zImage&lt;BR /&gt;7436328 bytes read in 337 ms (21 MiB/s)&lt;BR /&gt;=&amp;gt; bootz 0x82000000 - 0x83000000&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:612&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:641&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:655&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:664&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:715&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:721&lt;BR /&gt;## Flattened Device Tree blob at 83000000&lt;BR /&gt; Booting using the fdt blob at 0x83000000&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:612&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:641&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:655&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:664&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:692&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/arch/arm/lib/bootm.c:417&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/arch/arm/lib/bootm.c:224&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image.c:1508&lt;BR /&gt; Using Device Tree in place at 83000000, end 8300c0ef&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:194&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:196&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image.c:1515&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:467&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:472&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt;subnode: chosen: FDT_ERR_BADSTRUCTURE&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt;ERROR: /chosen node create failed&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt; - must RESET the board to recover.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;FDT creation failed! hanging...### ERROR ### Please RESET the board ###&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;It seems that the memory of dtb (0x83000000 ) is corrupted due to my some printf.&amp;nbsp; That's&amp;nbsp;unbelievable. Could anyone help me on this?&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;Thanks in advance,&lt;/P&gt;&lt;P style="text-align: left;"&gt;Jinliang&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Jul 2019 15:03:14 GMT</pubDate>
    <dc:creator>jinliang_li</dc:creator>
    <dc:date>2019-07-26T15:03:14Z</dc:date>
    <item>
      <title>I.MX6 U-Boot hang while it boot linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910313#M137140</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="text-align: center;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;U-Boot Version: u-boot-fslc&amp;nbsp; 2017.11-fslc&amp;nbsp;&amp;nbsp;&lt;A href="https://github.com/Freescale/u-boot-fslc/commit/a07698f0bfdb2887b617399643acd659c6e75138"&gt;https://github.com/Freescale/u-boot-fslc/commit/a07698f0bfdb2887b617399643acd659c6e75138&lt;/A&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;Board: i.mx6ul&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;It can boot successfully until I add some debug information in boot process by printf function just like in the patch in attachments.&amp;nbsp; After adding some printf, U-Boot bootz command can't parse the dtb successfully, and then hang. The detailed error messages :&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P&gt;=&amp;gt; load mmc 1:1 0x83000000 imx6ul-14x14-evk.dtb&lt;BR /&gt;reading imx6ul-14x14-evk.dtb&lt;BR /&gt;37104 bytes read in 19 ms (1.9 MiB/s)&lt;BR /&gt;=&amp;gt; load mmc 1:1 0x82000000 zImage&lt;BR /&gt;reading zImage&lt;BR /&gt;7436328 bytes read in 337 ms (21 MiB/s)&lt;BR /&gt;=&amp;gt; bootz 0x82000000 - 0x83000000&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:612&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:641&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:655&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:664&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:715&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:721&lt;BR /&gt;## Flattened Device Tree blob at 83000000&lt;BR /&gt; Booting using the fdt blob at 0x83000000&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:612&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:641&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:655&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:664&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/bootm.c:692&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/arch/arm/lib/bootm.c:417&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/arch/arm/lib/bootm.c:224&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image.c:1508&lt;BR /&gt; Using Device Tree in place at 83000000, end 8300c0ef&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:194&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:196&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image.c:1515&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:467&lt;BR /&gt;DONKEY:/path/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:472&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt;subnode: chosen: FDT_ERR_BADSTRUCTURE&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt;ERROR: /chosen node create failed&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt; - must RESET the board to recover.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;FDT creation failed! hanging...### ERROR ### Please RESET the board ###&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;It seems that the memory of dtb (0x83000000 ) is corrupted due to my some printf.&amp;nbsp; That's&amp;nbsp;unbelievable. Could anyone help me on this?&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;Thanks in advance,&lt;/P&gt;&lt;P style="text-align: left;"&gt;Jinliang&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Jul 2019 15:03:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910313#M137140</guid>
      <dc:creator>jinliang_li</dc:creator>
      <dc:date>2019-07-26T15:03:14Z</dc:date>
    </item>
    <item>
      <title>Re: I.MX6 U-Boot hang while it boot linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910314#M137141</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Usually printf() can't impact system boot. Would you narrow down the issue with removing some printf() and check which printf caused the issue? Did you call printf before UART is initialized?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jul 2019 05:26:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910314#M137141</guid>
      <dc:creator>justin_jiang</dc:creator>
      <dc:date>2019-07-30T05:26:15Z</dc:date>
    </item>
    <item>
      <title>Re: I.MX6 U-Boot hang while it boot linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910315#M137142</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To reproduce this issue,&amp;nbsp; the minimum debug messages needed to be kept as&amp;nbsp;0001-Keep-minimum-debug-messages.patch.&amp;nbsp; Keep printf functions in&amp;nbsp;common/fdt_support.c,&amp;nbsp;common/image-fdt.c,&amp;nbsp;common/image.c. It can work well if I only keep printf functions in&amp;nbsp;&lt;SPAN&gt;common/fdt_support.c or&amp;nbsp;common/image-fdt.c,&amp;nbsp;&lt;SPAN&gt;common/image.c .&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;So it can not to be determined which exactlly printf function cause the issue.&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;And when I add or remove some printf functions,&amp;nbsp; the error messages may be different, however it always hang at parsing dtb.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;Sometimes, it hang here&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;U-Boot SPL 2017.11+fslc+ga07698f (Jul 30 2019 - 19:34:57)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Trying to boot from MMC1&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;U-Boot 2017.11+fslc+ga07698f (Jul 30 2019 - 19:34:57 +0800)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;CPU: Freescale i.MX6UL rev1.1 528 MHz (running at 396 MHz)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;CPU: Industrial temperature grade (-40C to 105C)Reset cause: POR&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Board: MX6UL 14x14 EVK&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;I2C: ready&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DRAM: 512 MiB&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;MMC: FSL_SDHC: 0, FSL_SDHC: 1&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;*** Warning - bad CRC, using default environment&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Video: 480x272x24&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;In: serial&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Out: serial&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Err: serial&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Net: , FEC1&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Hit any key to stop autoboot: 0&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;switch to partitions #0, OK&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;mmc1 is current device&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;switch to partitions #0, OK&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;mmc1 is current device&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;** Unable to read file boot.scr **&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;reading zImage&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;7409120 bytes read in 336 ms (21 MiB/s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Booting from mmc ...&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;reading imx6ul-14x14-evk.dtb&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;37104 bytes read in 18 ms (2 MiB/s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;## Flattened Device Tree blob at 83000000&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt; Booting using the fdt blob at 0x83000000&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DONKEY:/path/alios-release/dev_linux_module2/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image.c:1508&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt; Using Device Tree in place at 83000000, end 8300c0ef&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DONKEY:/path/alios-release/dev_linux_module2/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:194&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DONKEY:/path/alios-release/dev_linux_module2/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:196&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DONKEY:/path/alios-release/dev_linux_module2/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image.c:1515&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DONKEY:/path/alios-release/dev_linux_module2/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:467&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DONKEY:/path/alios-release/dev_linux_module2/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/image-fdt.c:472&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DONKEY:/path/alios-release/dev_linux_module2/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/fdt_support.c:284&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DONKEY:/path/alios-release/dev_linux_module2/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-r0/git/common/fdt_support.c:291&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DONKEY:/path/alios-release/dev_linux_module2/build/tmp/work/imx6ulevk-alios-linux-gnueabi/u-boot-fslc/v2017.11+gitAUTOINC+a07698f0bf-0/git/common/fdt_support.c:115:offset:0 n&lt;/EM&gt;&lt;EM&gt;ame:chosen&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;Sometimes, it throw a "data abort"/"undefined instruction" execption.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;data abort&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;pc : [&amp;lt;9ff9f10e&amp;gt;] lr : [&amp;lt;9ff9efcf&amp;gt;]&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;reloc pc : [&amp;lt;8782710e&amp;gt;] lr : [&amp;lt;87826fcf&amp;gt;]&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;sp : 9ef77858 ip : 00000000 fp : 9ff78cc9&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;r10: 00000007 r9 : 9ef77eb8 r8 : 00000000&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;r7 : 9ffaa327 r6 : 83000000 r5 : 9ef77874 r4 : fffffff5&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;r3 : 0000001a r2 : 00008690 r1 : 00000064 r0 : 00000009&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Flags: nzCv IRQs off FIQs off Mode SVC_32&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Resetting CPU ...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;resetting ...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;However the pc pointer maybe different.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other informations:&lt;/P&gt;&lt;P&gt;1. It can work well if I enable all debug message,&amp;nbsp; define debug in include/common.h.&lt;/P&gt;&lt;P&gt;2. I dumped and compared the memory of dtb with the working one, they are same.&lt;/P&gt;&lt;P&gt;3. printf is used after UART initialized.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jul 2019 12:15:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910315#M137142</guid>
      <dc:creator>jinliang_li</dc:creator>
      <dc:date>2019-07-30T12:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: I.MX6 U-Boot hang while it boot linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910316#M137143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;A _jive_internal="true" class="" data-content-finding="Community" data-userid="345405" data-username="jinliang.li@linux.alibaba.com" href="https://community.nxp.com/people/jinliang.li@linux.alibaba.com"&gt;Jinliang Li&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please try to use u-boot supported by NXP which can be built from the attached Yocto User Guide? &lt;/P&gt;&lt;P&gt;I have compiled the uboot with applying your patch, kernel &amp;amp; DTB from the attached Yocto User Guide and I did not come across any error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Shivani&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jul 2019 13:05:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910316#M137143</guid>
      <dc:creator>shivanipatel</dc:creator>
      <dc:date>2019-07-30T13:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: I.MX6 U-Boot hang while it boot linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910317#M137144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I also used the yocto meta-freescale,&amp;nbsp;&lt;A class="link-titled" href="https://github.com/Freescale/meta-freescale" title="https://github.com/Freescale/meta-freescale"&gt;GitHub - Freescale/meta-freescale: Layer containing NXP hardware support metadata&lt;/A&gt;&amp;nbsp;. And the u-boot version is&amp;nbsp;u-boot-fslc_2017.11 .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jul 2019 02:47:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910317#M137144</guid>
      <dc:creator>jinliang_li</dc:creator>
      <dc:date>2019-07-31T02:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: I.MX6 U-Boot hang while it boot linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910318#M137145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Justin,&lt;/P&gt;&lt;P&gt;Do you have any other suggestion?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jul 2019 06:08:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910318#M137145</guid>
      <dc:creator>jinliang_li</dc:creator>
      <dc:date>2019-07-31T06:08:56Z</dc:date>
    </item>
    <item>
      <title>Re: I.MX6 U-Boot hang while it boot linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910319#M137146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Shivani Patel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which u-boot version are you using?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jul 2019 07:19:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910319#M137146</guid>
      <dc:creator>jinliang_li</dc:creator>
      <dc:date>2019-07-31T07:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: I.MX6 U-Boot hang while it boot linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910320#M137147</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just tested the u-boot-fslc 2018.11+fslc， 2017.09+fslc, 2018.01+fslc,&amp;nbsp; they all&amp;nbsp;can work well.&amp;nbsp; Is there any known issue in u-boot 2017.11+fslc?&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/JiangJustin"&gt;JiangJustin&lt;/A&gt;&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/shivanipatel"&gt;shivanipatel&lt;/A&gt;&lt;/P&gt;&lt;P&gt;That's too hard to debug such issue in u-boot.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jul 2019 12:45:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-MX6-U-Boot-hang-while-it-boot-linux-kernel/m-p/910320#M137147</guid>
      <dc:creator>jinliang_li</dc:creator>
      <dc:date>2019-07-31T12:45:49Z</dc:date>
    </item>
  </channel>
</rss>

