<?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: Timer vs Timer Input (via XBAR)? in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Timer-vs-Timer-Input-via-XBAR/m-p/2255336#M35798</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I'll address the difference between IOMUX timer accessible via GPIO pins versus timer input via XBAR on the RT1020-series chip.&lt;BR /&gt;&lt;BR /&gt;The difference between TMR1_TIMER0 via GPIO_SD_B0_00 and TMR1_TIMER0 at GPIO_AD_B1_09 via XBAR involves two different routing methods for timer signals:&lt;BR /&gt;&lt;BR /&gt;1. Direct Timer Connection (IOMUX):&lt;BR /&gt;When using TMR1_TIMER0 via GPIO_SD_B0_00, you're accessing the timer directly through the IOMUX (Input/Output Multiplexer). This represents the default/direct path where the timer functionality is hardwired to specific GPIO pins. You simply configure the pin mux setting to select the timer function (typically ALT mode 1, 2, etc.).&lt;BR /&gt;&lt;BR /&gt;2. XBAR Routing Method:&lt;BR /&gt;When using TMR1_TIMER0 at GPIO_AD_B1_09 via XBAR, you're utilizing the Cross Bar (XBAR) peripheral to route the timer signal to a different pin. This provides flexibility when the default timer pins are occupied by other critical functions (like SEMC, ENET, or SD card interfaces).&lt;BR /&gt;&lt;BR /&gt;You would choose XBAR routing when:&lt;BR /&gt;- The default timer pins are already used by other essential peripherals&lt;BR /&gt;- You need to route multiple signals to a single peripheral&lt;BR /&gt;- You need to connect a pin to both GPIO functionality and timer input simultaneously&lt;BR /&gt;- You need flexible input/output signal routing without hardware modifications&lt;BR /&gt;&lt;BR /&gt;The direct IOMUX method is simpler to implement but less flexible in pin selection. The XBAR method requires additional configuration but offers greater flexibility when default pins are unavailable.&lt;BR /&gt;&lt;BR /&gt;For your fan tachometer application, the XBAR approach would be beneficial if the default TMR1_TIMER0 pins conflict with other peripherals you're using. Implementation requires enabling XBAR clock, configuring pins for XBAR function, and properly setting XBAR routing registers to map inputs to outputs.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 04 Dec 2025 13:44:10 GMT</pubDate>
    <dc:creator>Bio_TICFSL</dc:creator>
    <dc:date>2025-12-04T13:44:10Z</dc:date>
    <item>
      <title>Timer vs Timer Input (via XBAR)?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Timer-vs-Timer-Input-via-XBAR/m-p/2254332#M35785</link>
      <description>&lt;P&gt;I'm trying to read tachometer outputs from a computer fan using an NXP RT1020-series chip but am confused with the difference between IOMUX timer accessible via GPIO pins (i.e. TMR1_TIMER0 via GPIO_SD_B0_00) versus timer input via XBAR (i.e. TMR1_TIMER0 at GPIO_AD_B1_09 via XBAR). Is there a difference between the two methods and when would one chose one option over the other?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Dec 2025 15:45:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Timer-vs-Timer-Input-via-XBAR/m-p/2254332#M35785</guid>
      <dc:creator>dcc_1234</dc:creator>
      <dc:date>2025-12-03T15:45:48Z</dc:date>
    </item>
    <item>
      <title>Re: Timer vs Timer Input (via XBAR)?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Timer-vs-Timer-Input-via-XBAR/m-p/2255336#M35798</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I'll address the difference between IOMUX timer accessible via GPIO pins versus timer input via XBAR on the RT1020-series chip.&lt;BR /&gt;&lt;BR /&gt;The difference between TMR1_TIMER0 via GPIO_SD_B0_00 and TMR1_TIMER0 at GPIO_AD_B1_09 via XBAR involves two different routing methods for timer signals:&lt;BR /&gt;&lt;BR /&gt;1. Direct Timer Connection (IOMUX):&lt;BR /&gt;When using TMR1_TIMER0 via GPIO_SD_B0_00, you're accessing the timer directly through the IOMUX (Input/Output Multiplexer). This represents the default/direct path where the timer functionality is hardwired to specific GPIO pins. You simply configure the pin mux setting to select the timer function (typically ALT mode 1, 2, etc.).&lt;BR /&gt;&lt;BR /&gt;2. XBAR Routing Method:&lt;BR /&gt;When using TMR1_TIMER0 at GPIO_AD_B1_09 via XBAR, you're utilizing the Cross Bar (XBAR) peripheral to route the timer signal to a different pin. This provides flexibility when the default timer pins are occupied by other critical functions (like SEMC, ENET, or SD card interfaces).&lt;BR /&gt;&lt;BR /&gt;You would choose XBAR routing when:&lt;BR /&gt;- The default timer pins are already used by other essential peripherals&lt;BR /&gt;- You need to route multiple signals to a single peripheral&lt;BR /&gt;- You need to connect a pin to both GPIO functionality and timer input simultaneously&lt;BR /&gt;- You need flexible input/output signal routing without hardware modifications&lt;BR /&gt;&lt;BR /&gt;The direct IOMUX method is simpler to implement but less flexible in pin selection. The XBAR method requires additional configuration but offers greater flexibility when default pins are unavailable.&lt;BR /&gt;&lt;BR /&gt;For your fan tachometer application, the XBAR approach would be beneficial if the default TMR1_TIMER0 pins conflict with other peripherals you're using. Implementation requires enabling XBAR clock, configuring pins for XBAR function, and properly setting XBAR routing registers to map inputs to outputs.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 13:44:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Timer-vs-Timer-Input-via-XBAR/m-p/2255336#M35798</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2025-12-04T13:44:10Z</dc:date>
    </item>
  </channel>
</rss>

