<?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 Debugging RPMsg problem on i.MX93EVK in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-RPMsg-problem-on-i-MX93EVK/m-p/1860531#M223392</link>
    <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I'm trying to develop an RPMSG application to communicate between cortex A and cortex M of the i.MX93 EVK and be able to pass a data structure from cortex M to cortex A.&lt;/P&gt;&lt;P&gt;To develop it, I code on VS Code with the MCU Xpresso extension and use the GNU Arm toolchain. I use a SEGGER J Link probe to debug cortex M.&lt;BR /&gt;I am basing myself on the rpmsg_lite_pingpong_rtos demo provided in SDK_MCIMX93-EVK.&lt;/P&gt;&lt;P&gt;To be able to run in debug completely the RPMSG pingpong demonstration, I need to load the linux module imx_rpmsg_pingpong. I therefore set up debugging of the Cortex-M33 while the Cortex-A55 is under Linux, as specified in AN14120.&lt;/P&gt;&lt;P&gt;So I tried to debug the pingpong demo but I run into a problem: the program waits indefinitely in the rpmsg_lite_wait_for_link_up() function.&lt;/P&gt;&lt;P&gt;When I load on the cortex M the rpmsg_lite_pingpong_rtos.elf file built on VS Code, using remoteproc, it works perfectly. Only in debug mode do I encounter this problem.&lt;/P&gt;&lt;P&gt;I have seen on other forum topics the same problem encountered with IMX8MM cards, but after reading those topics, I have not been able to find a solution.&lt;/P&gt;&lt;P&gt;Could someone please explain why RPMsg doesn't work when debugged, and help me solve this ?&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
    <pubDate>Tue, 07 May 2024 12:25:40 GMT</pubDate>
    <dc:creator>rochambell</dc:creator>
    <dc:date>2024-05-07T12:25:40Z</dc:date>
    <item>
      <title>Debugging RPMsg problem on i.MX93EVK</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-RPMsg-problem-on-i-MX93EVK/m-p/1860531#M223392</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I'm trying to develop an RPMSG application to communicate between cortex A and cortex M of the i.MX93 EVK and be able to pass a data structure from cortex M to cortex A.&lt;/P&gt;&lt;P&gt;To develop it, I code on VS Code with the MCU Xpresso extension and use the GNU Arm toolchain. I use a SEGGER J Link probe to debug cortex M.&lt;BR /&gt;I am basing myself on the rpmsg_lite_pingpong_rtos demo provided in SDK_MCIMX93-EVK.&lt;/P&gt;&lt;P&gt;To be able to run in debug completely the RPMSG pingpong demonstration, I need to load the linux module imx_rpmsg_pingpong. I therefore set up debugging of the Cortex-M33 while the Cortex-A55 is under Linux, as specified in AN14120.&lt;/P&gt;&lt;P&gt;So I tried to debug the pingpong demo but I run into a problem: the program waits indefinitely in the rpmsg_lite_wait_for_link_up() function.&lt;/P&gt;&lt;P&gt;When I load on the cortex M the rpmsg_lite_pingpong_rtos.elf file built on VS Code, using remoteproc, it works perfectly. Only in debug mode do I encounter this problem.&lt;/P&gt;&lt;P&gt;I have seen on other forum topics the same problem encountered with IMX8MM cards, but after reading those topics, I have not been able to find a solution.&lt;/P&gt;&lt;P&gt;Could someone please explain why RPMsg doesn't work when debugged, and help me solve this ?&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2024 12:25:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-RPMsg-problem-on-i-MX93EVK/m-p/1860531#M223392</guid>
      <dc:creator>rochambell</dc:creator>
      <dc:date>2024-05-07T12:25:40Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging RPMsg problem on i.MX93EVK</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-RPMsg-problem-on-i-MX93EVK/m-p/1860809#M223419</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;you may refer to the following link:&lt;BR /&gt;&lt;A href="https://variwiki.com/index.php?title=MCUXpresso_VSCode" target="_blank"&gt;https://variwiki.com/index.php?title=MCUXpresso_VSCode&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Best regards/Saludos,&lt;BR /&gt;Aldo.&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2024 20:21:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-RPMsg-problem-on-i-MX93EVK/m-p/1860809#M223419</guid>
      <dc:creator>AldoG</dc:creator>
      <dc:date>2024-05-07T20:21:50Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging RPMsg problem on i.MX93EVK</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-RPMsg-problem-on-i-MX93EVK/m-p/1864478#M223636</link>
      <description>&lt;P&gt;Hello Aldo,&lt;/P&gt;&lt;P&gt;Thanks for your answer.&lt;/P&gt;&lt;P&gt;I have read some of the Variscite Wiki developers guides for MCUXpresso development with VSCode.&lt;BR /&gt;The link you give me is for DART-MX8M-MINI, it's the only guide that details the specific case of debugging RPMsg demos.&lt;/P&gt;&lt;P&gt;In the article, for the example, they&amp;nbsp;&lt;SPAN&gt;debug pingpong demo mapped in DDR.&lt;/SPAN&gt;&amp;nbsp;Is it necessary for the RPMsg demo to be mapped to DDR in order to debug its ?&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2024 13:34:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-RPMsg-problem-on-i-MX93EVK/m-p/1864478#M223636</guid>
      <dc:creator>rochambell</dc:creator>
      <dc:date>2024-05-13T13:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging RPMsg problem on i.MX93EVK</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Debugging-RPMsg-problem-on-i-MX93EVK/m-p/1865678#M223717</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;For this purpose even a guide for another processor should work, it only changes things like addresses, available peripherals, examples, etc.&lt;BR /&gt;&lt;BR /&gt;Also, please note that Ping-pong example is only available on DDR target.&lt;BR /&gt;&lt;BR /&gt;Best regards/Saludos,&lt;BR /&gt;Aldo.&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2024 20:46:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Debugging-RPMsg-problem-on-i-MX93EVK/m-p/1865678#M223717</guid>
      <dc:creator>AldoG</dc:creator>
      <dc:date>2024-05-14T20:46:55Z</dc:date>
    </item>
  </channel>
</rss>

