<?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: Debugging U-Boot on iMX6 with BDI3000 in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-U-Boot-on-iMX6-with-BDI3000/m-p/401152#M59246</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Armand&lt;/P&gt;&lt;P&gt;After iMX6 reset there is a ROM code that runs&lt;/P&gt;&lt;P&gt;and while this code is running JTAG communication&lt;/P&gt;&lt;P&gt;is not possible. Therefore BDI can not halt at the&lt;/P&gt;&lt;P&gt;reset vector and it attempts to HALT as soon as&lt;/P&gt;&lt;P&gt;debug access is available.&lt;/P&gt;&lt;P&gt;If you need to debug from the very first instruction&lt;/P&gt;&lt;P&gt;you could replace the first instruction with an&lt;/P&gt;&lt;P&gt;infinite loop and you could then HALT while&lt;/P&gt;&lt;P&gt;it is looping there.&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;Sinan Akman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 May 2015 12:57:19 GMT</pubDate>
    <dc:creator>sinanakman</dc:creator>
    <dc:date>2015-05-05T12:57:19Z</dc:date>
    <item>
      <title>Debugging U-Boot on iMX6 with BDI3000</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-U-Boot-on-iMX6-with-BDI3000/m-p/401151#M59245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to debug U-Boot (version: imx_v2014.04_3.14.28_1.0.0_ga) for a custom board with a BDI3000.&lt;/P&gt;&lt;P&gt;So far I can connect to the target and I see the U-Boot code at the correct location, but after reset the PC is at 0x1ffa870c which is somewhere outside of U-Boot. Here the state after powering up th board with the BDI attached:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt; font-family: courier new,courier;"&gt;IMX6#0&amp;gt;info&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Core number&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 0&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Core state&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : debug mode (ARM)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Debug entry cause : Debug Request&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Current PC&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 0x1ffa870c&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt; font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Current CPSR&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 0x600001d3 (Supervisor)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to debug from the very first assembler instruction which gets loaded at address 0x17800000 but I don't know how to configure the BDI to achieve this. Does someone would have a BDI configuration file to share?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Armand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 May 2015 10:15:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-U-Boot-on-iMX6-with-BDI3000/m-p/401151#M59245</guid>
      <dc:creator>armandc_</dc:creator>
      <dc:date>2015-05-05T10:15:30Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging U-Boot on iMX6 with BDI3000</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-U-Boot-on-iMX6-with-BDI3000/m-p/401152#M59246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Armand&lt;/P&gt;&lt;P&gt;After iMX6 reset there is a ROM code that runs&lt;/P&gt;&lt;P&gt;and while this code is running JTAG communication&lt;/P&gt;&lt;P&gt;is not possible. Therefore BDI can not halt at the&lt;/P&gt;&lt;P&gt;reset vector and it attempts to HALT as soon as&lt;/P&gt;&lt;P&gt;debug access is available.&lt;/P&gt;&lt;P&gt;If you need to debug from the very first instruction&lt;/P&gt;&lt;P&gt;you could replace the first instruction with an&lt;/P&gt;&lt;P&gt;infinite loop and you could then HALT while&lt;/P&gt;&lt;P&gt;it is looping there.&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;Sinan Akman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 May 2015 12:57:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-U-Boot-on-iMX6-with-BDI3000/m-p/401152#M59246</guid>
      <dc:creator>sinanakman</dc:creator>
      <dc:date>2015-05-05T12:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging U-Boot on iMX6 with BDI3000</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-U-Boot-on-iMX6-with-BDI3000/m-p/401153#M59247</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Please refer to Chapter 1 (Porting U-Boot from an i.MX 6 Reference Board&lt;/P&gt;&lt;P&gt;to an i.MX 6 Custom Board) of “i.MX_6_BSP_Porting_Guide.pdf”in Linux documentation.&lt;/P&gt;&lt;P&gt;In particular, please pay attention on section1.4 (Debugging)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also the following may be helpful :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.denx.de/wiki/view/DULG/DebuggingUBoot" target="_blank"&gt;http://www.denx.de/wiki/view/DULG/DebuggingUBoot&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Yuri&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&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, 06 May 2015 08:19:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-U-Boot-on-iMX6-with-BDI3000/m-p/401153#M59247</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2015-05-06T08:19:12Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging U-Boot on iMX6 with BDI3000</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-U-Boot-on-iMX6-with-BDI3000/m-p/401154#M59248</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the clarification. I didn't realize that the JTAG cannot access the processor when the ROM code is executing. I reduced the delay after the reset in my BDI configuration which already helps, but the infinite loop is the real solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can now debug, thanks for your help.&lt;/P&gt;&lt;P&gt;Armand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 May 2015 09:46:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-U-Boot-on-iMX6-with-BDI3000/m-p/401154#M59248</guid>
      <dc:creator>armandc_</dc:creator>
      <dc:date>2015-05-06T09:46:52Z</dc:date>
    </item>
  </channel>
</rss>

