<?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 QMAN lock-up when halting code execution in P-Series</title>
    <link>https://community.nxp.com/t5/P-Series/QMAN-lock-up-when-halting-code-execution/m-p/537035#M3352</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;We are currently working on an Ethernet-driver for the P4080 (rev. 3), during most conditions it runs well.&lt;/P&gt;&lt;P&gt;However we are having some problems when using a Lauterbach debugger to halt&amp;nbsp; code execution. If halting is done soon after initialization and there is traffic present on the network, it causes the QMAN to lock-up. &lt;/P&gt;&lt;P&gt;The configuration we’re using is somewhat simplified with 1 dTSEC and 2 SW portals for QMAN. Portal 0 is used for transmission and reception of frames, and portal 1 for tx confirmation. Both portals are used in push-mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By judging from the status registers, FMAN and dTSEC seems to run ok.&lt;/P&gt;&lt;P&gt;The lock-up of QMAN leads to that all its registers become unresponsive, which makes it impossible to read out the portal status from the command register.&lt;/P&gt;&lt;P&gt;There is no interrupt or other error bits set in the QMAN-registers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A snapshot of the registers in portal 0 is after lock-up has occurred is attached below.&lt;span class="lia-inline-image-display-wrapper" image-alt="Portal 0.PNG"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/9335i7100636773FC9A4E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Portal 0.PNG" alt="Portal 0.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Tobias&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Jul 2016 15:26:29 GMT</pubDate>
    <dc:creator>tobiashallberg</dc:creator>
    <dc:date>2016-07-04T15:26:29Z</dc:date>
    <item>
      <title>QMAN lock-up when halting code execution</title>
      <link>https://community.nxp.com/t5/P-Series/QMAN-lock-up-when-halting-code-execution/m-p/537035#M3352</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;We are currently working on an Ethernet-driver for the P4080 (rev. 3), during most conditions it runs well.&lt;/P&gt;&lt;P&gt;However we are having some problems when using a Lauterbach debugger to halt&amp;nbsp; code execution. If halting is done soon after initialization and there is traffic present on the network, it causes the QMAN to lock-up. &lt;/P&gt;&lt;P&gt;The configuration we’re using is somewhat simplified with 1 dTSEC and 2 SW portals for QMAN. Portal 0 is used for transmission and reception of frames, and portal 1 for tx confirmation. Both portals are used in push-mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By judging from the status registers, FMAN and dTSEC seems to run ok.&lt;/P&gt;&lt;P&gt;The lock-up of QMAN leads to that all its registers become unresponsive, which makes it impossible to read out the portal status from the command register.&lt;/P&gt;&lt;P&gt;There is no interrupt or other error bits set in the QMAN-registers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A snapshot of the registers in portal 0 is after lock-up has occurred is attached below.&lt;span class="lia-inline-image-display-wrapper" image-alt="Portal 0.PNG"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/9335i7100636773FC9A4E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Portal 0.PNG" alt="Portal 0.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Tobias&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Jul 2016 15:26:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/QMAN-lock-up-when-halting-code-execution/m-p/537035#M3352</guid>
      <dc:creator>tobiashallberg</dc:creator>
      <dc:date>2016-07-04T15:26:29Z</dc:date>
    </item>
  </channel>
</rss>

