<?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のトピックS32K118Q048 LIN Stack- Break Delimiter</title>
    <link>https://community.nxp.com/t5/S32K/S32K118Q048-LIN-Stack-Break-Delimiter/m-p/2144218#M51505</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm currently working with the LIN stack on an NXP S32K118Q048 and aiming to increase the Break Field duration. Based on PicoScope measurements, the current Break + Delimiter length is approximately &lt;STRONG&gt;675 microseconds&lt;/STRONG&gt;, but I need to extend it to around &lt;STRONG&gt;940–945 microseconds&lt;/STRONG&gt; to ensure compatibility with a specific slave.&lt;/P&gt;&lt;P&gt;From the community posts, I understand that neither the RTD nor the hardware directly exposes a configuration for this. However, it was suggested that inserting a finite delay loop before sending the Sync byte could effectively increase the break duration.&lt;/P&gt;&lt;P&gt;The problem I'm facing is identifying &lt;STRONG&gt;where exactly&lt;/STRONG&gt; to insert this delay. I attempted modifying the Lpuart_Lin_Ip.c file but didn’t observe any effect.&lt;/P&gt;&lt;P&gt;I'm using:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;LIN Stack version&lt;/STRONG&gt;: 2.0&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;RTD version&lt;/STRONG&gt;: 3.0.0&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Could you please let me know the &lt;STRONG&gt;exact function name and file&lt;/STRONG&gt; where I can modify the break generation timing?&lt;BR /&gt;&lt;BR /&gt;regards,&lt;/P&gt;</description>
    <pubDate>Thu, 31 Jul 2025 06:36:43 GMT</pubDate>
    <dc:creator>yousefdessouki123</dc:creator>
    <dc:date>2025-07-31T06:36:43Z</dc:date>
    <item>
      <title>S32K118Q048 LIN Stack- Break Delimiter</title>
      <link>https://community.nxp.com/t5/S32K/S32K118Q048-LIN-Stack-Break-Delimiter/m-p/2144218#M51505</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm currently working with the LIN stack on an NXP S32K118Q048 and aiming to increase the Break Field duration. Based on PicoScope measurements, the current Break + Delimiter length is approximately &lt;STRONG&gt;675 microseconds&lt;/STRONG&gt;, but I need to extend it to around &lt;STRONG&gt;940–945 microseconds&lt;/STRONG&gt; to ensure compatibility with a specific slave.&lt;/P&gt;&lt;P&gt;From the community posts, I understand that neither the RTD nor the hardware directly exposes a configuration for this. However, it was suggested that inserting a finite delay loop before sending the Sync byte could effectively increase the break duration.&lt;/P&gt;&lt;P&gt;The problem I'm facing is identifying &lt;STRONG&gt;where exactly&lt;/STRONG&gt; to insert this delay. I attempted modifying the Lpuart_Lin_Ip.c file but didn’t observe any effect.&lt;/P&gt;&lt;P&gt;I'm using:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;LIN Stack version&lt;/STRONG&gt;: 2.0&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;RTD version&lt;/STRONG&gt;: 3.0.0&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Could you please let me know the &lt;STRONG&gt;exact function name and file&lt;/STRONG&gt; where I can modify the break generation timing?&lt;BR /&gt;&lt;BR /&gt;regards,&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jul 2025 06:36:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K118Q048-LIN-Stack-Break-Delimiter/m-p/2144218#M51505</guid>
      <dc:creator>yousefdessouki123</dc:creator>
      <dc:date>2025-07-31T06:36:43Z</dc:date>
    </item>
    <item>
      <title>Re: S32K118Q048 LIN Stack- Break Delimiter</title>
      <link>https://community.nxp.com/t5/S32K/S32K118Q048-LIN-Stack-Break-Delimiter/m-p/2144543#M51523</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/251159"&gt;@yousefdessouki123&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This works for me:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danielmartynek_0-1753965134941.png" style="width: 656px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/350490iFC5D9DCB9FF9AEFA/image-dimensions/656x218?v=v2" width="656" height="218" role="button" title="danielmartynek_0-1753965134941.png" alt="danielmartynek_0-1753965134941.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danielmartynek_2-1753965337445.png" style="width: 724px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/350492i9935EED5553801DC/image-dimensions/724x194?v=v2" width="724" height="194" role="button" title="danielmartynek_2-1753965337445.png" alt="danielmartynek_2-1753965337445.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;
&lt;H6 style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Any support, information, and technology (“Materials”) provided by NXP are provided AS IS, without any warranty express or&amp;nbsp;implied, and NXP disclaims all direct and indirect liability and damages in connection with the Material to the maximum extent&amp;nbsp;permitted by the applicable law. NXP accepts no liability for any assistance with applications or product design. &amp;nbsp;Materials&amp;nbsp;may only be used in connection with NXP products. Any feedback provided to NXP regarding the Materials may be used by&amp;nbsp;NXP without restriction.&lt;/H6&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jul 2025 12:35:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K118Q048-LIN-Stack-Break-Delimiter/m-p/2144543#M51523</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2025-07-31T12:35:58Z</dc:date>
    </item>
  </channel>
</rss>

