<?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: SJA1110 TSN Qbv Issue in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1576426#M16219</link>
    <description>&lt;P&gt;LAS VEGAS, Jan. 06, 2020 (GLOBE NEWSWIRE) -- NXP Semiconductors N.V. (NASDAQ: NXPI), the world’s largest supplier of automotive semiconductors, has announced a multi-gigabit Ethernet switch designed to help automakers deliver the high-speed networks required for evolving connected vehicles. The NXP SJA1110 is the first automotive Ethernet switch with safety capabilities built in, offering integrated 100BASE-T1 PHYs, hardware-assisted security as well as multi-gigabit interfaces. Optimized for integration with NXP’s S32G vehicle network processor, the SJA1110 switch is also part of an overall networking solution which includes the VR5510 power management IC. Together, this solution addresses the biggest challenges facing vehicle networking today including scalability, safety, security and high-speed traffic engineering for more details here&amp;nbsp;&lt;A href="https://distinguished.io/companies/software-development" target="_self"&gt;top software development companies&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 03 Jan 2023 08:28:43 GMT</pubDate>
    <dc:creator>Razamehmood</dc:creator>
    <dc:date>2023-01-03T08:28:43Z</dc:date>
    <item>
      <title>SJA1110 TSN Qbv Issue</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1557743#M15921</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi everyone,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am testing the Qbv on SJA1110. I modify the example "switch_config_s32g_vnp_rdb" for testing.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I follow the Qbv example in document. But when I set the same config on port 4(SGMII) and port 6(100base-T1), I use iperf3 to test and get the difference result.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The 100base-T1 port behaves correctly and it can communicate every 8 seconds.&lt;/P&gt;&lt;P&gt;But the same config on SGMII port, it&amp;nbsp;communicate every 4 seconds and the bitrate is incorrect.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Does anybody have an idea for this?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there any detailed document about TSN on SJA1110?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ethan.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Nov 2022 10:19:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1557743#M15921</guid>
      <dc:creator>Ethan_L</dc:creator>
      <dc:date>2022-11-22T10:19:49Z</dc:date>
    </item>
    <item>
      <title>Re: SJA1110 TSN Qbv Issue</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1558476#M15944</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;could you please provide the switch configuration? We'll have a look into it then.&lt;/P&gt;
&lt;P&gt;BR, Petr&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 11:03:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1558476#M15944</guid>
      <dc:creator>PetrS</dc:creator>
      <dc:date>2022-11-23T11:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: SJA1110 TSN Qbv Issue</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1558965#M15953</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52961"&gt;@PetrS&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;The attachment is my &lt;SPAN&gt;switch configuration.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ethan.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2022 00:21:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1558965#M15953</guid>
      <dc:creator>Ethan_L</dc:creator>
      <dc:date>2022-11-24T00:21:07Z</dc:date>
    </item>
    <item>
      <title>Re: SJA1110 TSN Qbv Issue</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1561033#M15998</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;pleases see a feedback below I got from Apps engineer...&lt;/P&gt;
&lt;P&gt;I just checked the .mex file. I noticed they use the same TRIGGER_TIME (QBV Administrative Schedule Table) for both port 4 and port 6 and expect the same behavior. This will not work since TRIGGER_TIME is different depending on the port speed configuration. Since they use port 4 (which is 1Gbps) and port 6 (100Mbps) this can lead to different behavior.&lt;/P&gt;
&lt;P&gt;TRIGGER_TIME is quite well explained in our user manual (see attached screenshot).&lt;/P&gt;
&lt;P&gt;They need to change the TRIGGER_TIME of all entries of port 4 if they want to see the exact same behavior as on port 6.&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PetrS_0-1669697802699.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/202016i37DEDD059A7DB947/image-size/medium?v=v2&amp;amp;px=400" role="button" title="PetrS_0-1669697802699.png" alt="PetrS_0-1669697802699.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;BR, Petr&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 04:57:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1561033#M15998</guid>
      <dc:creator>PetrS</dc:creator>
      <dc:date>2022-11-29T04:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: SJA1110 TSN Qbv Issue</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1561082#M16000</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52961"&gt;@PetrS&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Got it, thank you very much.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 06:31:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1561082#M16000</guid>
      <dc:creator>Ethan_L</dc:creator>
      <dc:date>2022-11-29T06:31:25Z</dc:date>
    </item>
    <item>
      <title>Re: SJA1110 TSN Qbv Issue</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1576426#M16219</link>
      <description>&lt;P&gt;LAS VEGAS, Jan. 06, 2020 (GLOBE NEWSWIRE) -- NXP Semiconductors N.V. (NASDAQ: NXPI), the world’s largest supplier of automotive semiconductors, has announced a multi-gigabit Ethernet switch designed to help automakers deliver the high-speed networks required for evolving connected vehicles. The NXP SJA1110 is the first automotive Ethernet switch with safety capabilities built in, offering integrated 100BASE-T1 PHYs, hardware-assisted security as well as multi-gigabit interfaces. Optimized for integration with NXP’s S32G vehicle network processor, the SJA1110 switch is also part of an overall networking solution which includes the VR5510 power management IC. Together, this solution addresses the biggest challenges facing vehicle networking today including scalability, safety, security and high-speed traffic engineering for more details here&amp;nbsp;&lt;A href="https://distinguished.io/companies/software-development" target="_self"&gt;top software development companies&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 08:28:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/SJA1110-TSN-Qbv-Issue/m-p/1576426#M16219</guid>
      <dc:creator>Razamehmood</dc:creator>
      <dc:date>2023-01-03T08:28:43Z</dc:date>
    </item>
  </channel>
</rss>

