<?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>S32KのトピックS32K358: eDMA Trigger via GMAC PPS Module for Media Clock Generation</title>
    <link>https://community.nxp.com/t5/S32K/S32K358-eDMA-Trigger-via-GMAC-PPS-Module-for-Media-Clock/m-p/2143410#M51468</link>
    <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;I'm working on media clock generation using the GMAC PPS module and plan to use eDMA to update the target time (seconds and nanoseconds) dynamically. Here's a summary of my approach:&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Implementation Overview:&lt;/STRONG&gt;&lt;/H3&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;The GMAC PTP reference clock is configured at &lt;STRONG&gt;125 MHz&lt;/STRONG&gt;, which starts the system time.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The &lt;STRONG&gt;Target Time Seconds&lt;/STRONG&gt; and &lt;STRONG&gt;Nanoseconds&lt;/STRONG&gt; registers are updated to generate a pulse every second.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;PPS is configured in &lt;STRONG&gt;Media Clock Generation (MCGR) mode&lt;/STRONG&gt;, which should assert the mcgr_dma_req_o signal.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;I selected &lt;STRONG&gt;DMAMUX source 28 – “IEEE 1588 PTP timer ch[0]”&lt;/STRONG&gt;, assuming it maps to mcgr_dma_req_o[0] and thus triggers an eDMA peripheral request.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The TCD is set up to copy the next target time when triggered.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Observed Behavior:&lt;/STRONG&gt;&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;When the system time reaches or exceeds the configured target time, the &lt;STRONG&gt;TSTARGT0&lt;/STRONG&gt; bit in the MAC_Timestamp_Status register is correctly set — indicating that mcgr_dma_req_o[0] is asserted.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sathishkumar_sunmugavel_0-1753867248257.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/350215i805DE16B41600D34/image-size/medium?v=v2&amp;amp;px=400" role="button" title="sathishkumar_sunmugavel_0-1753867248257.png" alt="sathishkumar_sunmugavel_0-1753867248257.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;However, no DMA transfer is triggered; the current iteration count remains unchanged.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Questions:&lt;/STRONG&gt;&lt;/H3&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Is this method valid for generating periodic clock pulses using the PPS module and eDMA?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is the DMAMUX configuration (source 28: IEEE 1588 PTP timer ch[0]) correct for this scenario?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Does the assertion of mcgr_dma_req_o actually trigger an eDMA peripheral request?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The naming conventions seem inconsistent across resources:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;DMAMUX sheet: IEEE 1588 PTP timer ch[i]&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Reference Manual: mcgr_dma_req_o[i]&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;SDK Code: DMA_MUX_1_GMAC_0_PTP_TIMER_CH[i]&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Conclusion:&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;I would like to confirm: &lt;STRONG&gt;when the system time meets the configured target time, the mcgr_dma_req_o signal is asserted — is this signal routed to eDMA as a valid peripheral request?&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;I have attached the sample main.c file for reference. Please have a look and let me know what is going wrong.&lt;/P&gt;&lt;P&gt;Any insights would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Sathish.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Jul 2025 09:25:17 GMT</pubDate>
    <dc:creator>sathishkumar_sunmugavel</dc:creator>
    <dc:date>2025-07-30T09:25:17Z</dc:date>
    <item>
      <title>S32K358: eDMA Trigger via GMAC PPS Module for Media Clock Generation</title>
      <link>https://community.nxp.com/t5/S32K/S32K358-eDMA-Trigger-via-GMAC-PPS-Module-for-Media-Clock/m-p/2143410#M51468</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;I'm working on media clock generation using the GMAC PPS module and plan to use eDMA to update the target time (seconds and nanoseconds) dynamically. Here's a summary of my approach:&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Implementation Overview:&lt;/STRONG&gt;&lt;/H3&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;The GMAC PTP reference clock is configured at &lt;STRONG&gt;125 MHz&lt;/STRONG&gt;, which starts the system time.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The &lt;STRONG&gt;Target Time Seconds&lt;/STRONG&gt; and &lt;STRONG&gt;Nanoseconds&lt;/STRONG&gt; registers are updated to generate a pulse every second.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;PPS is configured in &lt;STRONG&gt;Media Clock Generation (MCGR) mode&lt;/STRONG&gt;, which should assert the mcgr_dma_req_o signal.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;I selected &lt;STRONG&gt;DMAMUX source 28 – “IEEE 1588 PTP timer ch[0]”&lt;/STRONG&gt;, assuming it maps to mcgr_dma_req_o[0] and thus triggers an eDMA peripheral request.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The TCD is set up to copy the next target time when triggered.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Observed Behavior:&lt;/STRONG&gt;&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;When the system time reaches or exceeds the configured target time, the &lt;STRONG&gt;TSTARGT0&lt;/STRONG&gt; bit in the MAC_Timestamp_Status register is correctly set — indicating that mcgr_dma_req_o[0] is asserted.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sathishkumar_sunmugavel_0-1753867248257.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/350215i805DE16B41600D34/image-size/medium?v=v2&amp;amp;px=400" role="button" title="sathishkumar_sunmugavel_0-1753867248257.png" alt="sathishkumar_sunmugavel_0-1753867248257.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;However, no DMA transfer is triggered; the current iteration count remains unchanged.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Questions:&lt;/STRONG&gt;&lt;/H3&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Is this method valid for generating periodic clock pulses using the PPS module and eDMA?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is the DMAMUX configuration (source 28: IEEE 1588 PTP timer ch[0]) correct for this scenario?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Does the assertion of mcgr_dma_req_o actually trigger an eDMA peripheral request?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;The naming conventions seem inconsistent across resources:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;DMAMUX sheet: IEEE 1588 PTP timer ch[i]&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Reference Manual: mcgr_dma_req_o[i]&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;SDK Code: DMA_MUX_1_GMAC_0_PTP_TIMER_CH[i]&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Conclusion:&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;I would like to confirm: &lt;STRONG&gt;when the system time meets the configured target time, the mcgr_dma_req_o signal is asserted — is this signal routed to eDMA as a valid peripheral request?&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;I have attached the sample main.c file for reference. Please have a look and let me know what is going wrong.&lt;/P&gt;&lt;P&gt;Any insights would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Sathish.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jul 2025 09:25:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K358-eDMA-Trigger-via-GMAC-PPS-Module-for-Media-Clock/m-p/2143410#M51468</guid>
      <dc:creator>sathishkumar_sunmugavel</dc:creator>
      <dc:date>2025-07-30T09:25:17Z</dc:date>
    </item>
    <item>
      <title>Re: S32K358: eDMA Trigger via GMAC PPS Module for Media Clock Generation</title>
      <link>https://community.nxp.com/t5/S32K/S32K358-eDMA-Trigger-via-GMAC-PPS-Module-for-Media-Clock/m-p/2144128#M51499</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/248322"&gt;@sathishkumar_sunmugavel&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I recommend to discuss this directly with NXP FAE assigned to Harman. Or you can create new case here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.nxp.com/s/?language=en_US" target="_blank"&gt;https://support.nxp.com/s/?language=en_US&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;... and the case will be forwarded to local FAE team.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for understanding.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jul 2025 04:29:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K358-eDMA-Trigger-via-GMAC-PPS-Module-for-Media-Clock/m-p/2144128#M51499</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2025-07-31T04:29:05Z</dc:date>
    </item>
  </channel>
</rss>

