<?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>LayerscapeのトピックDifference between LS1021AXN7MQB and LS1021ASE7MQB</title>
    <link>https://community.nxp.com/t5/Layerscape/Difference-between-LS1021AXN7MQB-and-LS1021ASE7MQB/m-p/1481001#M10773</link>
    <description>&lt;P&gt;We are facing JTAG connection issues with LS1021AXN7MQB used in out board. But not with LS1021ASE7MQB used in NXP TWR EVK board.&lt;BR /&gt;&lt;BR /&gt;We're using third party JTAG probe and not CW TAP. They provide single configuration file which is working with EVK but not with our board. So I was wondering if anything has to be changed in configuration file between LS1021AXN7MQB and LS1021ASE7MQB.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Jun 2022 07:24:37 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2022-06-28T07:24:37Z</dc:date>
    <item>
      <title>Difference between LS1021AXN7MQB and LS1021ASE7MQB</title>
      <link>https://community.nxp.com/t5/Layerscape/Difference-between-LS1021AXN7MQB-and-LS1021ASE7MQB/m-p/1481001#M10773</link>
      <description>&lt;P&gt;We are facing JTAG connection issues with LS1021AXN7MQB used in out board. But not with LS1021ASE7MQB used in NXP TWR EVK board.&lt;BR /&gt;&lt;BR /&gt;We're using third party JTAG probe and not CW TAP. They provide single configuration file which is working with EVK but not with our board. So I was wondering if anything has to be changed in configuration file between LS1021AXN7MQB and LS1021ASE7MQB.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 07:24:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Difference-between-LS1021AXN7MQB-and-LS1021ASE7MQB/m-p/1481001#M10773</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-06-28T07:24:37Z</dc:date>
    </item>
  </channel>
</rss>

