<?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>LPC MicrocontrollersのトピックRe: LPC55S66 rev.1 going to busfault on debugging</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S66-rev-1-going-to-busfault-on-debugging/m-p/972282#M38464</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Felipe,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as you can see here&amp;nbsp;&lt;A href="https://community.nxp.com/message/1195953"&gt;https://community.nxp.com/message/1195953&lt;/A&gt;&amp;nbsp; it toke me quiet a time to get this data from NXP. It would be nice if you could verify this behaviour. It is happening with both examples from the LPC55S66 SDK2.6.2 as with own generated files. Running it on a LPC55S69 solves the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 12 Sep 2019 12:53:29 GMT</pubDate>
    <dc:creator>dingelen</dc:creator>
    <dc:date>2019-09-12T12:53:29Z</dc:date>
    <item>
      <title>LPC55S66 rev.1 going to busfault on debugging</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S66-rev-1-going-to-busfault-on-debugging/m-p/972280#M38462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;has anyone else experineced the LPC55S66 rev.1 on debugging with SWD going immediatly to a bus-fault, not entering the ResetISR?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Same code in a LPC55S69 does work correct. I've already tried several chips all with the same error, the LPC55S69 always works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Versions IDE 11.0.1, SDK 2.6.2, Segger J-Link, using the standard empty project from SDK or the SDK examples.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Sep 2019 13:40:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S66-rev-1-going-to-busfault-on-debugging/m-p/972280#M38462</guid>
      <dc:creator>dingelen</dc:creator>
      <dc:date>2019-09-10T13:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: LPC55S66 rev.1 going to busfault on debugging</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S66-rev-1-going-to-busfault-on-debugging/m-p/972281#M38463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Tom,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you try to enter into ISP mode before trying to debug? In addition, please have in mind LPC55S66 has smaller flash and SRAM than LPC55S69. Is there any chance your application is consuming all the resources? Please check image below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/87675iF6D6DADE9A07F74F/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Felipe&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2019 21:28:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S66-rev-1-going-to-busfault-on-debugging/m-p/972281#M38463</guid>
      <dc:creator>FelipeGarcia</dc:creator>
      <dc:date>2019-09-11T21:28:01Z</dc:date>
    </item>
    <item>
      <title>Re: LPC55S66 rev.1 going to busfault on debugging</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S66-rev-1-going-to-busfault-on-debugging/m-p/972282#M38464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Felipe,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as you can see here&amp;nbsp;&lt;A href="https://community.nxp.com/message/1195953"&gt;https://community.nxp.com/message/1195953&lt;/A&gt;&amp;nbsp; it toke me quiet a time to get this data from NXP. It would be nice if you could verify this behaviour. It is happening with both examples from the LPC55S66 SDK2.6.2 as with own generated files. Running it on a LPC55S69 solves the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Sep 2019 12:53:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S66-rev-1-going-to-busfault-on-debugging/m-p/972282#M38464</guid>
      <dc:creator>dingelen</dc:creator>
      <dc:date>2019-09-12T12:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: LPC55S66 rev.1 going to busfault on debugging</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S66-rev-1-going-to-busfault-on-debugging/m-p/972283#M38465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This issue has been solved with SDK 2.6.3&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Oct 2019 09:30:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S66-rev-1-going-to-busfault-on-debugging/m-p/972283#M38465</guid>
      <dc:creator>dingelen</dc:creator>
      <dc:date>2019-10-04T09:30:59Z</dc:date>
    </item>
  </channel>
</rss>

