<?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: P&amp;amp;E Multilink Debug in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/P-amp-E-Multilink-Debug/m-p/1844372#M29739</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I did more testing on this:&lt;/P&gt;&lt;P&gt;1) If I change to fuse mode and stop running emwin_gui_demo, I can program hello world again. Then I can program and run emwin_gui_demo again. Then stop working because of gui_demo&lt;/P&gt;&lt;P&gt;2) I tried the different graphic demo, like "lvgl demo" and got the same result.&lt;/P&gt;&lt;P&gt;I think it is related to graphic demo, but I do not know which part causes this?&lt;/P&gt;&lt;P&gt;Can anyone help me to fix it?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Christie&lt;/P&gt;</description>
    <pubDate>Wed, 10 Apr 2024 20:21:32 GMT</pubDate>
    <dc:creator>a8Chcx</dc:creator>
    <dc:date>2024-04-10T20:21:32Z</dc:date>
    <item>
      <title>P&amp;E Multilink Debug</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/P-amp-E-Multilink-Debug/m-p/1843364#M29718</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am using RT1064 and&amp;nbsp;"P&amp;amp;E Mutilink USB"&amp;nbsp;to debug my project.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) I can program internal flash over JTAG(J21) and run Hello_world again and again without any problem.&lt;/P&gt;&lt;P&gt;2) When I program emwin_gui_demo over JTAG and works fine at the first time. Then JTAG stop working. Even I go back to try "hello world" and always get error "Error in services launch sequence&lt;BR /&gt;PEmicro GDB Launch Failure : The GDB Server was not able to establish a connection to the target processor. Please check your connections and power. Verify that the launch settings in the Debug Configuration are accurate."&lt;/P&gt;&lt;P&gt;Can anybody help me fix this problem because I can't test anything fro now?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Christie&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2024 20:13:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/P-amp-E-Multilink-Debug/m-p/1843364#M29718</guid>
      <dc:creator>a8Chcx</dc:creator>
      <dc:date>2024-04-09T20:13:27Z</dc:date>
    </item>
    <item>
      <title>Re: P&amp;E Multilink Debug</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/P-amp-E-Multilink-Debug/m-p/1844372#M29739</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I did more testing on this:&lt;/P&gt;&lt;P&gt;1) If I change to fuse mode and stop running emwin_gui_demo, I can program hello world again. Then I can program and run emwin_gui_demo again. Then stop working because of gui_demo&lt;/P&gt;&lt;P&gt;2) I tried the different graphic demo, like "lvgl demo" and got the same result.&lt;/P&gt;&lt;P&gt;I think it is related to graphic demo, but I do not know which part causes this?&lt;/P&gt;&lt;P&gt;Can anyone help me to fix it?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Christie&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2024 20:21:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/P-amp-E-Multilink-Debug/m-p/1844372#M29739</guid>
      <dc:creator>a8Chcx</dc:creator>
      <dc:date>2024-04-10T20:21:32Z</dc:date>
    </item>
    <item>
      <title>Re: P&amp;E Multilink Debug</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/P-amp-E-Multilink-Debug/m-p/1845452#M29759</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I did more testing and found:&lt;/P&gt;&lt;P&gt;JTAG_nTRST(pin3 of JTAG) and&amp;nbsp;LCD_TOUCH_INT are using the same IO from MCU.&lt;/P&gt;&lt;P&gt;When initializing "LCD_TOUCH_INT" to 0, it causes P&amp;amp;E debug stop working.&lt;/P&gt;&lt;P&gt;Can anybody confirm if it is true and let me know how to fix it?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Christie&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 19:43:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/P-amp-E-Multilink-Debug/m-p/1845452#M29759</guid>
      <dc:creator>a8Chcx</dc:creator>
      <dc:date>2024-04-11T19:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: P&amp;E Multilink Debug</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/P-amp-E-Multilink-Debug/m-p/1847065#M29797</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/14098"&gt;@a8Chcx&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; This issue is normally caused by the abnormal code is downloaded to the flash, then the chip can't detect the valid FCB.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Normally, you can enter the serial download mode, then do the mass erase to resolve the issues.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Please refer to my post:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/RT-board-recovery-for-debugger-connect-issues/ta-p/1635260" target="_blank"&gt;https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/RT-board-recovery-for-debugger-connect-issues/ta-p/1635260&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Wish it helps you!&lt;/P&gt;
&lt;P&gt;If you still have question about it, please kindly let me know.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Kerry&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2024 10:35:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/P-amp-E-Multilink-Debug/m-p/1847065#M29797</guid>
      <dc:creator>kerryzhou</dc:creator>
      <dc:date>2024-04-15T10:35:32Z</dc:date>
    </item>
  </channel>
</rss>

