<?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 [IMX8X] Interruption between A35 and M4 (user) core in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IMX8X-Interruption-between-A35-and-M4-user-core/m-p/1681985#M208706</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;To set up the context, I am using the IMX8XQXP product in order to develop a communication based on the messagery unit between the A35 and M4 core.&amp;nbsp;&lt;BR /&gt;I precise that I am programming in bare-metal on A35 core, and FreeRTOS on M4 one.&amp;nbsp;&lt;BR /&gt;I started from the demonstration, that I found in the MCU Xpresso SDK, e.g the rpmsg or the power-down one.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I observe with the help of my Lauterbach probe, that I manage to create a general interruption, send from MU5_B (M4 side) to MU5_A (A35 side), the &lt;STRONG&gt;GIE[3]&lt;/STRONG&gt; register is on "&lt;STRONG&gt;pending&lt;/STRONG&gt;" on the side A of the channel.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Nevertheless, I didn't manage to treat the interruption on the A35 side. From the reference manual, I've seen that &lt;STRONG&gt;MU5_INT_A&lt;/STRONG&gt; is attach to the IRQ vector 216. Thus, I manage to program the "&lt;STRONG&gt;enable&lt;/STRONG&gt;" register of the &lt;STRONG&gt;GIC-500&lt;/STRONG&gt; corresponding to the IRQ 216 but nothing append.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Finally, I manage to active with the help of the Lauterbach probe in order to validate that my handler and my activation of the interruption is well done on the A35.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there something else to do, to attach the good IRQ to MU5_A in the GIC engine ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you advance.&amp;nbsp;&lt;BR /&gt;Vincent PALERMINI&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jul 2023 11:27:11 GMT</pubDate>
    <dc:creator>VPalermini</dc:creator>
    <dc:date>2023-07-05T11:27:11Z</dc:date>
    <item>
      <title>[IMX8X] Interruption between A35 and M4 (user) core</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX8X-Interruption-between-A35-and-M4-user-core/m-p/1681985#M208706</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;To set up the context, I am using the IMX8XQXP product in order to develop a communication based on the messagery unit between the A35 and M4 core.&amp;nbsp;&lt;BR /&gt;I precise that I am programming in bare-metal on A35 core, and FreeRTOS on M4 one.&amp;nbsp;&lt;BR /&gt;I started from the demonstration, that I found in the MCU Xpresso SDK, e.g the rpmsg or the power-down one.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I observe with the help of my Lauterbach probe, that I manage to create a general interruption, send from MU5_B (M4 side) to MU5_A (A35 side), the &lt;STRONG&gt;GIE[3]&lt;/STRONG&gt; register is on "&lt;STRONG&gt;pending&lt;/STRONG&gt;" on the side A of the channel.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Nevertheless, I didn't manage to treat the interruption on the A35 side. From the reference manual, I've seen that &lt;STRONG&gt;MU5_INT_A&lt;/STRONG&gt; is attach to the IRQ vector 216. Thus, I manage to program the "&lt;STRONG&gt;enable&lt;/STRONG&gt;" register of the &lt;STRONG&gt;GIC-500&lt;/STRONG&gt; corresponding to the IRQ 216 but nothing append.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Finally, I manage to active with the help of the Lauterbach probe in order to validate that my handler and my activation of the interruption is well done on the A35.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there something else to do, to attach the good IRQ to MU5_A in the GIC engine ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you advance.&amp;nbsp;&lt;BR /&gt;Vincent PALERMINI&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2023 11:27:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX8X-Interruption-between-A35-and-M4-user-core/m-p/1681985#M208706</guid>
      <dc:creator>VPalermini</dc:creator>
      <dc:date>2023-07-05T11:27:11Z</dc:date>
    </item>
    <item>
      <title>Re: [IMX8X] Interruption between A35 and M4 (user) core</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX8X-Interruption-between-A35-and-M4-user-core/m-p/1683896#M208869</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/213963"&gt;@VPalermini&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope you are doing well&lt;/P&gt;
&lt;P&gt;The interrupt process is detailed in section 18.8.2.8 Interrupt Messaging Protocols of the Reference Manual IMX8DQXPRM.&lt;/P&gt;
&lt;P&gt;For more information, kindly refer to the discussion from the thread below for the same query.&lt;BR /&gt;&lt;A href="https://community.nxp.com/t5/i-MX-Processors/How-to-trigger-software-interrupt-from-iMX8-A35-to-M4/td-p/1002384" target="_blank"&gt;https://community.nxp.com/t5/i-MX-Processors/How-to-trigger-software-interrupt-from-iMX8-A35-to-M4/td-p/1002384&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;Sanket Parekh&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2023 10:22:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX8X-Interruption-between-A35-and-M4-user-core/m-p/1683896#M208869</guid>
      <dc:creator>Sanket_Parekh</dc:creator>
      <dc:date>2023-07-07T10:22:06Z</dc:date>
    </item>
  </channel>
</rss>

