<?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のトピックs32k312_emios-bctu-adc hardware triggering</title>
    <link>https://community.nxp.com/t5/S32K/s32k312-emios-bctu-adc-hardware-triggering/m-p/1929081#M39178</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/100054"&gt;@Irina_Costachescu&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I need to configure ADC in hardware triggering mode for PWM synchronous motor current measurement, i am using s32k312 micro,&lt;BR /&gt;&lt;BR /&gt;I configured adc in HW triggered mode, but i am confused in the areas like setting TRGMUX and triggers for the BCTU and ADC.&lt;BR /&gt;I configured the PWM in OPWFMB (need to configure in variable period and dutycycle emios0_ch1)&amp;nbsp;&lt;BR /&gt;Currently my triggering link is like: to trigger BCTU i created&amp;nbsp;BCTU_EMIOS_0_4 trigger source(for internal trigger for BCTU) and to trigger ADC i created&amp;nbsp;BCTU_Trg23 trigger source.&lt;BR /&gt;But in the BctuHwUnit configuration section i'm still confused with the settings like BCTU List items, Is it really needed in my case since i use only one adc unit as hardware triggering mode for reading the signals (which contains 4 signals total in that HwUnit, in which one of the signal is used for motor current measurement rest of them is not time dependent like rest of the signals converts like back-to-back mode for that scatter gather config is done for channel linking).&lt;BR /&gt;In my requirement for e&lt;SPAN&gt;very 50µs (max. 100µs) a current value needs to be measured. Within an ISR the PID regulator is called to adjust the PWM based on the updated current measurement.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;s32k1&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Aug 2024 11:13:44 GMT</pubDate>
    <dc:creator>S32k1</dc:creator>
    <dc:date>2024-08-09T11:13:44Z</dc:date>
    <item>
      <title>s32k312_emios-bctu-adc hardware triggering</title>
      <link>https://community.nxp.com/t5/S32K/s32k312-emios-bctu-adc-hardware-triggering/m-p/1929081#M39178</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/100054"&gt;@Irina_Costachescu&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I need to configure ADC in hardware triggering mode for PWM synchronous motor current measurement, i am using s32k312 micro,&lt;BR /&gt;&lt;BR /&gt;I configured adc in HW triggered mode, but i am confused in the areas like setting TRGMUX and triggers for the BCTU and ADC.&lt;BR /&gt;I configured the PWM in OPWFMB (need to configure in variable period and dutycycle emios0_ch1)&amp;nbsp;&lt;BR /&gt;Currently my triggering link is like: to trigger BCTU i created&amp;nbsp;BCTU_EMIOS_0_4 trigger source(for internal trigger for BCTU) and to trigger ADC i created&amp;nbsp;BCTU_Trg23 trigger source.&lt;BR /&gt;But in the BctuHwUnit configuration section i'm still confused with the settings like BCTU List items, Is it really needed in my case since i use only one adc unit as hardware triggering mode for reading the signals (which contains 4 signals total in that HwUnit, in which one of the signal is used for motor current measurement rest of them is not time dependent like rest of the signals converts like back-to-back mode for that scatter gather config is done for channel linking).&lt;BR /&gt;In my requirement for e&lt;SPAN&gt;very 50µs (max. 100µs) a current value needs to be measured. Within an ISR the PID regulator is called to adjust the PWM based on the updated current measurement.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;s32k1&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2024 11:13:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/s32k312-emios-bctu-adc-hardware-triggering/m-p/1929081#M39178</guid>
      <dc:creator>S32k1</dc:creator>
      <dc:date>2024-08-09T11:13:44Z</dc:date>
    </item>
    <item>
      <title>Re: s32k312_emios-bctu-adc hardware triggering</title>
      <link>https://community.nxp.com/t5/S32K/s32k312-emios-bctu-adc-hardware-triggering/m-p/1929430#M39211</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thank you so much for your interest in our products and for using our community.&lt;/P&gt;
&lt;P&gt;There is no the specific module synchronization that you require for the S32K312. But you could refer to &lt;EM&gt;Adc_Sar_Bctu_Ip_example_S32K312&lt;/EM&gt; and &lt;EM&gt;Emios_Pwm_Ip_Example_S32K312&lt;/EM&gt; that are included in S32DS 3.4 with RTD 2.x.x. You can have multiple IDEs.&lt;/P&gt;
&lt;P&gt;Additionally, you could refer to the &lt;EM&gt;4.2.4. Analogue data capturing&lt;/EM&gt; section from &lt;EM&gt;AN13767&lt;/EM&gt; and its respective &lt;EM&gt;Application Software&lt;/EM&gt; in &lt;A href="https://www.nxp.com/design/design-center/development-boards-and-designs/automotive-motor-control-solutions/s32k344-brushless-direct-current-and-permanent-magnet-synchronous-motor-control-development-kit:MCSPTE1AK344" target="_blank" rel="noopener"&gt;MCSPTE1AK344&lt;/A&gt; page:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="_Leo__0-1723233070367.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/292808i9A0465A07BD77538/image-size/medium?v=v2&amp;amp;px=400" role="button" title="_Leo__0-1723233070367.png" alt="_Leo__0-1723233070367.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;_Leo__0-1723233070367.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Hope it helps you.&lt;/P&gt;
&lt;P&gt;Have a nice day!&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2024 19:53:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/s32k312-emios-bctu-adc-hardware-triggering/m-p/1929430#M39211</guid>
      <dc:creator>_Leo_</dc:creator>
      <dc:date>2024-08-09T19:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: s32k312_emios-bctu-adc hardware triggering</title>
      <link>https://community.nxp.com/t5/S32K/s32k312-emios-bctu-adc-hardware-triggering/m-p/1980193#M42434</link>
      <description>&lt;P&gt;Hi Community,&lt;/P&gt;&lt;P&gt;I have configured Adc in bctu control mode and the conversion of the channels are happening.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In order to measure the adc at the mid point of pwm active dutycyle,&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Configure the Dummy PWM Signal&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The dummy PWM signal is correctly set to half the period of the original PWM signal. This will help you achieve the desired delay for midpoint measurement.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Set Up TRGMUX&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Configured the TRGMUX to route the eMIOS channel (e.g.,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;TRGMUX_IP_INPUT_EMIOS0_IPP_CH3) to the BCTU trigger input (TRGMUX_IP_OUTPUT_BCTU_TRG23).&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Trigger BCTU&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Used the dummy PWM signal to trigger the BCTU at the midpoint of the original PWM signal’s on-time.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;BCTU to ADC&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The BCTU is configured to start the ADC conversion upon receiving the trigger.&lt;BR /&gt;&lt;BR /&gt;Also when ever there is any pwm dutycycle update I need to change the delay point in such a way that it should be at the mid of pwm active dutycycle, for that i have used Bctu Tigger notification callback to update the trigger point.&lt;BR /&gt;&lt;BR /&gt;But when i output the result in DSO the signal waves are showing not as expected. Yellow - PWM Output&amp;nbsp;&lt;BR /&gt;Green&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;- BCTU trigger( should be at the mid point), also for some signals it is missing.&lt;STRONG&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="S32k1_0-1729685686033.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/306420i73D362B850ADE88B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="S32k1_0-1729685686033.png" alt="S32k1_0-1729685686033.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;S32k1_0-1729685686033.png&lt;/span&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 23 Oct 2024 12:14:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/s32k312-emios-bctu-adc-hardware-triggering/m-p/1980193#M42434</guid>
      <dc:creator>S32k1</dc:creator>
      <dc:date>2024-10-23T12:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: s32k312_emios-bctu-adc hardware triggering</title>
      <link>https://community.nxp.com/t5/S32K/s32k312-emios-bctu-adc-hardware-triggering/m-p/2294452#M56136</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please share the resolution for such issue. I am facing a similar issue where the ADC trigger is delayed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jan 2026 16:57:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/s32k312-emios-bctu-adc-hardware-triggering/m-p/2294452#M56136</guid>
      <dc:creator>aditya_barve</dc:creator>
      <dc:date>2026-01-15T16:57:33Z</dc:date>
    </item>
  </channel>
</rss>

