<?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のトピックSerial downloader jump error</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Serial-downloader-jump-error/m-p/678160#M104655</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we are working on a custom board based on i.MX6 quad plus.&lt;/P&gt;&lt;P&gt;The board is working well, but about 10 % of our prototypes share the same problem: they do not boot.&lt;/P&gt;&lt;P&gt;When connected by means of a USB cable to a Ubuntu development machine all the boards are enumerated as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bus 001 Device 028: ID 15a2:0054 Freescale Semiconductor, Inc. i.MX 6Dual/6Quad SystemOnChip in RecoveryMode&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So we would like to investigate the failure cause and the first step is to load a firmware by USB: when we load u-boot by means of Serial Downloader Protocol (imx_usb_loader) we have some difference.&lt;/P&gt;&lt;P&gt;Loading and booting works well on the "good" boards but fails on the "jump" command on the "faulty" boards (see log). We see the difference by looking at u-boot&amp;nbsp;output on the board serial console.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at imx_usb_loader source code seems like loading u-boot in RAM is working (RAM content is verified against original file after load) but the jump command fails.&lt;/P&gt;&lt;P&gt;Any idea about the problem origin?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Carlo&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;imx_usb_loader output: working boards&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;#&amp;nbsp;./imx_usb &lt;BR /&gt;config file &amp;lt;.//imx_usb.conf&amp;gt;&lt;BR /&gt;[...]&lt;BR /&gt;config file &amp;lt;.//mx6_usb_work.conf&amp;gt;&lt;BR /&gt;parse .//mx6_usb_work.conf&lt;BR /&gt;Interface 0 claimed&lt;BR /&gt;HAB security state: development mode (0x56787856)&lt;BR /&gt;== work item&lt;BR /&gt;filename u-boot.imx&lt;BR /&gt;load_size 0 bytes&lt;BR /&gt;load_addr 0x13f00000&lt;BR /&gt;dcd 1&lt;BR /&gt;clear_dcd 0&lt;BR /&gt;plug 1&lt;BR /&gt;jump_mode 0&lt;BR /&gt;jump_addr 0x00000000&lt;BR /&gt;== end work item&lt;BR /&gt;loading DCD table @0x910000&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt;&amp;lt;-184, 1024 bytes&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;succeeded (status 0x128a8a12)&lt;BR /&gt;HAB security state: development mode (0x56787856)&lt;BR /&gt;== work item&lt;BR /&gt;filename u-boot.imx&lt;BR /&gt;load_size 0 bytes&lt;BR /&gt;load_addr 0x13f00000&lt;BR /&gt;dcd 0&lt;BR /&gt;clear_dcd 1&lt;BR /&gt;plug 0&lt;BR /&gt;jump_mode 2&lt;BR /&gt;jump_addr 0x00000000&lt;BR /&gt;== end work item&lt;BR /&gt;clear dcd_ptr=0x177ff42c&lt;/P&gt;&lt;P&gt;loading binary file(u-boot.imx) to 177ff400, skip=0, fsize=6ec00 type=aa&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt;&amp;lt;453632, 453632 bytes&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;succeeded (status 0x88888888)&lt;BR /&gt;jumping to 0x177ff400&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;imx_usb_loader output: faulty&amp;nbsp;boards&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;[the same as in working boards, but the last lines are]&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;jumping to 0x177ff400&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;j4 in err=0, last_trans=64 &amp;nbsp;33 22 0a 00&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Jun 2017 14:12:49 GMT</pubDate>
    <dc:creator>carlotomasin</dc:creator>
    <dc:date>2017-06-07T14:12:49Z</dc:date>
    <item>
      <title>Serial downloader jump error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Serial-downloader-jump-error/m-p/678160#M104655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we are working on a custom board based on i.MX6 quad plus.&lt;/P&gt;&lt;P&gt;The board is working well, but about 10 % of our prototypes share the same problem: they do not boot.&lt;/P&gt;&lt;P&gt;When connected by means of a USB cable to a Ubuntu development machine all the boards are enumerated as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bus 001 Device 028: ID 15a2:0054 Freescale Semiconductor, Inc. i.MX 6Dual/6Quad SystemOnChip in RecoveryMode&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So we would like to investigate the failure cause and the first step is to load a firmware by USB: when we load u-boot by means of Serial Downloader Protocol (imx_usb_loader) we have some difference.&lt;/P&gt;&lt;P&gt;Loading and booting works well on the "good" boards but fails on the "jump" command on the "faulty" boards (see log). We see the difference by looking at u-boot&amp;nbsp;output on the board serial console.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at imx_usb_loader source code seems like loading u-boot in RAM is working (RAM content is verified against original file after load) but the jump command fails.&lt;/P&gt;&lt;P&gt;Any idea about the problem origin?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Carlo&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;imx_usb_loader output: working boards&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;#&amp;nbsp;./imx_usb &lt;BR /&gt;config file &amp;lt;.//imx_usb.conf&amp;gt;&lt;BR /&gt;[...]&lt;BR /&gt;config file &amp;lt;.//mx6_usb_work.conf&amp;gt;&lt;BR /&gt;parse .//mx6_usb_work.conf&lt;BR /&gt;Interface 0 claimed&lt;BR /&gt;HAB security state: development mode (0x56787856)&lt;BR /&gt;== work item&lt;BR /&gt;filename u-boot.imx&lt;BR /&gt;load_size 0 bytes&lt;BR /&gt;load_addr 0x13f00000&lt;BR /&gt;dcd 1&lt;BR /&gt;clear_dcd 0&lt;BR /&gt;plug 1&lt;BR /&gt;jump_mode 0&lt;BR /&gt;jump_addr 0x00000000&lt;BR /&gt;== end work item&lt;BR /&gt;loading DCD table @0x910000&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt;&amp;lt;-184, 1024 bytes&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;succeeded (status 0x128a8a12)&lt;BR /&gt;HAB security state: development mode (0x56787856)&lt;BR /&gt;== work item&lt;BR /&gt;filename u-boot.imx&lt;BR /&gt;load_size 0 bytes&lt;BR /&gt;load_addr 0x13f00000&lt;BR /&gt;dcd 0&lt;BR /&gt;clear_dcd 1&lt;BR /&gt;plug 0&lt;BR /&gt;jump_mode 2&lt;BR /&gt;jump_addr 0x00000000&lt;BR /&gt;== end work item&lt;BR /&gt;clear dcd_ptr=0x177ff42c&lt;/P&gt;&lt;P&gt;loading binary file(u-boot.imx) to 177ff400, skip=0, fsize=6ec00 type=aa&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt;&amp;lt;453632, 453632 bytes&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;succeeded (status 0x88888888)&lt;BR /&gt;jumping to 0x177ff400&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;imx_usb_loader output: faulty&amp;nbsp;boards&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;[the same as in working boards, but the last lines are]&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;jumping to 0x177ff400&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;j4 in err=0, last_trans=64 &amp;nbsp;33 22 0a 00&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jun 2017 14:12:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Serial-downloader-jump-error/m-p/678160#M104655</guid>
      <dc:creator>carlotomasin</dc:creator>
      <dc:date>2017-06-07T14:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: Serial downloader jump error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Serial-downloader-jump-error/m-p/678161#M104656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Carlo&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;seems address for loading u-boot in RAM is ddr, so&lt;/P&gt;&lt;P&gt;may be recoomended to run ddr test and update dcd with new&lt;/P&gt;&lt;P&gt;calibration coefficients.&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://community.freescale.com/docs/DOC-105652" title="https://community.freescale.com/docs/DOC-105652"&gt;https://community.freescale.com/docs/DOC-105652&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jun 2017 23:29:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Serial-downloader-jump-error/m-p/678161#M104656</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2017-06-07T23:29:25Z</dc:date>
    </item>
    <item>
      <title>Re: Serial downloader jump error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Serial-downloader-jump-error/m-p/678162#M104657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;unfortunately the DDR test tool always fails calibration on "faulty" boards so it is not a calibration problem at all.&lt;/P&gt;&lt;P&gt;Now we are investigating by means of X-rays to check the connections of the SOC to the PCB. We think that some signal from SOC to DDR is not working properly due to some bad join.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Carlo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jun 2017 07:01:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Serial-downloader-jump-error/m-p/678162#M104657</guid>
      <dc:creator>carlotomasin</dc:creator>
      <dc:date>2017-06-26T07:01:36Z</dc:date>
    </item>
  </channel>
</rss>

