<?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: LA1224 LS-DCS &amp;amp; TBGen in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/LA1224-LS-DCS-amp-TBGen/m-p/2366977#M16697</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;The key point is that TBGEN timed-interrupt timers 1–11 are VSPA trigger sources, not VSPA interrupt sources . Only Timed Interrupt Timer 0 can generate an MCU interrupt through &lt;CODE class=""&gt;INTSTAT[TI]&lt;/CODE&gt; and &lt;CODE class=""&gt;CNTRL1[TIIE]&lt;/CODE&gt; ; timers 1–11 only generate VSP platform triggers and set &lt;CODE class=""&gt;TISTAT[TITRIG1..11]&lt;/CODE&gt; . So if you configured TBGEN in FDD mode and are waiting for a TBGEN “interrupt” on a VSPA core, that expectation does not match with TBGEN/VSPA interface.&lt;/P&gt;
&lt;P&gt;For LA1224 4T4R, TBGEN timers 1–11 are VSPA trigger sources via &lt;CODE class=""&gt;ext_go&lt;/CODE&gt; rather than VSPA interrupt sources, so the most likely issue is trigger routing/enablement ( &lt;CODE class=""&gt;TMREN&lt;/CODE&gt; , correct TBGEN1/2 &lt;CODE class=""&gt;ext_go&lt;/CODE&gt; input, and &lt;CODE class=""&gt;TISTAT&lt;/CODE&gt; verification) rather than a missing VSPA ISR.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 18 May 2026 14:47:04 GMT</pubDate>
    <dc:creator>Bio_TICFSL</dc:creator>
    <dc:date>2026-05-18T14:47:04Z</dc:date>
    <item>
      <title>LA1224 LS-DCS &amp; TBGen</title>
      <link>https://community.nxp.com/t5/Layerscape/LA1224-LS-DCS-amp-TBGen/m-p/2366928#M16696</link>
      <description>&lt;P&gt;Hello!&lt;BR /&gt;Could you tell me how to enable continuous synchronous operation of 4T4R on the LA1224-RDB-LS?&lt;BR /&gt;I'm using 0-3 VSPA cores to run LS-DCS0 and LS-DCS1.&lt;BR /&gt;1DAC and 1ADC are running on each core.&lt;BR /&gt;I have interrupt handlers for TBGEN, and I configured TBGEN in FDD mode. But I'm not receiving interrupts from it on the VSPA.&lt;BR /&gt;I was able to run 2T2R synchronously, but in this case, either the ADC or DAC is running on each core.&lt;BR /&gt;Perhaps I haven't configured all the TBGEn timers?&lt;BR /&gt;I'm transmitting a single-tone signal generated using NCO with 8192 samples. I'm sure I generated the NCO parameters correctly.&lt;BR /&gt;But why do I see phase jumps on the ADC during loopback?&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2026 12:31:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LA1224-LS-DCS-amp-TBGen/m-p/2366928#M16696</guid>
      <dc:creator>flappy</dc:creator>
      <dc:date>2026-05-18T12:31:35Z</dc:date>
    </item>
    <item>
      <title>Re: LA1224 LS-DCS &amp; TBGen</title>
      <link>https://community.nxp.com/t5/Layerscape/LA1224-LS-DCS-amp-TBGen/m-p/2366977#M16697</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;The key point is that TBGEN timed-interrupt timers 1–11 are VSPA trigger sources, not VSPA interrupt sources . Only Timed Interrupt Timer 0 can generate an MCU interrupt through &lt;CODE class=""&gt;INTSTAT[TI]&lt;/CODE&gt; and &lt;CODE class=""&gt;CNTRL1[TIIE]&lt;/CODE&gt; ; timers 1–11 only generate VSP platform triggers and set &lt;CODE class=""&gt;TISTAT[TITRIG1..11]&lt;/CODE&gt; . So if you configured TBGEN in FDD mode and are waiting for a TBGEN “interrupt” on a VSPA core, that expectation does not match with TBGEN/VSPA interface.&lt;/P&gt;
&lt;P&gt;For LA1224 4T4R, TBGEN timers 1–11 are VSPA trigger sources via &lt;CODE class=""&gt;ext_go&lt;/CODE&gt; rather than VSPA interrupt sources, so the most likely issue is trigger routing/enablement ( &lt;CODE class=""&gt;TMREN&lt;/CODE&gt; , correct TBGEN1/2 &lt;CODE class=""&gt;ext_go&lt;/CODE&gt; input, and &lt;CODE class=""&gt;TISTAT&lt;/CODE&gt; verification) rather than a missing VSPA ISR.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2026 14:47:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LA1224-LS-DCS-amp-TBGen/m-p/2366977#M16697</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2026-05-18T14:47:04Z</dc:date>
    </item>
    <item>
      <title>Re: LA1224 LS-DCS &amp; TBGen</title>
      <link>https://community.nxp.com/t5/Layerscape/LA1224-LS-DCS-amp-TBGen/m-p/2369465#M16704</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/34846"&gt;@Bio_TICFSL&lt;/a&gt;&amp;nbsp;Thank you, the problem is solved&lt;/P&gt;</description>
      <pubDate>Thu, 21 May 2026 09:54:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LA1224-LS-DCS-amp-TBGen/m-p/2369465#M16704</guid>
      <dc:creator>flappy</dc:creator>
      <dc:date>2026-05-21T09:54:58Z</dc:date>
    </item>
  </channel>
</rss>

