<?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>MCUXpresso GeneralのトピックDebugging I.MX RT 1050 with MCUXpresso</title>
    <link>https://community.nxp.com/t5/MCUXpresso-General/Debugging-I-MX-RT-1050-with-MCUXpresso/m-p/824226#M936</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I read that MCUXpresso does not support software breakpoints for code placed in Flash (e.g. QSPI NOR Flash). Is this true?&lt;/P&gt;&lt;P&gt;This can be a significant limitation (when available HW breakpoints are not enough), since we would like to use XIP from QSPI Flash, and code size will be significantly bigger than internal RAM size.&lt;/P&gt;&lt;P&gt;I read that Segger tools can place SW break points in Flash (it is a matter of being able to rewrite flash sectors), is there any plan to include this feature in next MCUXpresso release(s) ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Dec 2018 17:24:51 GMT</pubDate>
    <dc:creator>adicarlo</dc:creator>
    <dc:date>2018-12-21T17:24:51Z</dc:date>
    <item>
      <title>Debugging I.MX RT 1050 with MCUXpresso</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/Debugging-I-MX-RT-1050-with-MCUXpresso/m-p/824226#M936</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I read that MCUXpresso does not support software breakpoints for code placed in Flash (e.g. QSPI NOR Flash). Is this true?&lt;/P&gt;&lt;P&gt;This can be a significant limitation (when available HW breakpoints are not enough), since we would like to use XIP from QSPI Flash, and code size will be significantly bigger than internal RAM size.&lt;/P&gt;&lt;P&gt;I read that Segger tools can place SW break points in Flash (it is a matter of being able to rewrite flash sectors), is there any plan to include this feature in next MCUXpresso release(s) ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Dec 2018 17:24:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/Debugging-I-MX-RT-1050-with-MCUXpresso/m-p/824226#M936</guid>
      <dc:creator>adicarlo</dc:creator>
      <dc:date>2018-12-21T17:24:51Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging I.MX RT 1050 with MCUXpresso</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/Debugging-I-MX-RT-1050-with-MCUXpresso/m-p/824227#M937</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;'Software breakpoints in flash' (&lt;A class="link-titled" href="https://mcuoneclipse.com/2012/07/29/software-and-hardware-breakpoints/" title="https://mcuoneclipse.com/2012/07/29/software-and-hardware-breakpoints/"&gt;Software and Hardware Breakpoints | MCU on Eclipse&lt;/A&gt;) are currently only supported with the SEGGER J-Link debug probes which are supported in the MCUXpresso IDE. But this is not available say with the LinkServer and the P&amp;amp;E debug probes: for these as you say it will use hardware breakpoints. The i.MX RT has a decent number of HW breakpoints, so this might not be a real limitiation. Or just use a J-Link with MCUXpresso IDE if you really want to use this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jan 2019 09:00:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/Debugging-I-MX-RT-1050-with-MCUXpresso/m-p/824227#M937</guid>
      <dc:creator>BlackNight</dc:creator>
      <dc:date>2019-01-02T09:00:15Z</dc:date>
    </item>
  </channel>
</rss>

