<?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 SJA1105 PIN problem in AUTOSAR SW-C</title>
    <link>https://community.nxp.com/t5/AUTOSAR-SW-C/SJA1105-PIN-problem/m-p/1015053#M2</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Connection accessory diagram: CPU A is responsible for driver loading of SJA1105, CPU A and CPU B are connected to SJA1105 through RGMII, MAC2MAC.&lt;BR /&gt;2. When the system is running, CPU A and B can ping normally.&lt;BR /&gt;3. Reboot CPU B. After CPU B restarts, it cannot ping, but CPU A can still ping.&lt;BR /&gt;How to solve this problem?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Mar 2020 06:52:23 GMT</pubDate>
    <dc:creator>gavinguo</dc:creator>
    <dc:date>2020-03-25T06:52:23Z</dc:date>
    <item>
      <title>SJA1105 PIN problem</title>
      <link>https://community.nxp.com/t5/AUTOSAR-SW-C/SJA1105-PIN-problem/m-p/1015053#M2</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Connection accessory diagram: CPU A is responsible for driver loading of SJA1105, CPU A and CPU B are connected to SJA1105 through RGMII, MAC2MAC.&lt;BR /&gt;2. When the system is running, CPU A and B can ping normally.&lt;BR /&gt;3. Reboot CPU B. After CPU B restarts, it cannot ping, but CPU A can still ping.&lt;BR /&gt;How to solve this problem?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Mar 2020 06:52:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/AUTOSAR-SW-C/SJA1105-PIN-problem/m-p/1015053#M2</guid>
      <dc:creator>gavinguo</dc:creator>
      <dc:date>2020-03-25T06:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: SJA1105 PIN problem</title>
      <link>https://community.nxp.com/t5/AUTOSAR-SW-C/SJA1105-PIN-problem/m-p/1015054#M3</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/gavinguo"&gt;gavinguo&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not think we can help with such information here. This community space is about MATLAB/Simulink related topics. Perhaps you can try to get in touch with the NXP Support via a Ticket:&amp;nbsp;&lt;A class="link-titled" href="https://www.nxp.com/support/support:SUPPORTHOME" title="https://www.nxp.com/support/support:SUPPORTHOME"&gt;Support | NXP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Mar 2020 07:18:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/AUTOSAR-SW-C/SJA1105-PIN-problem/m-p/1015054#M3</guid>
      <dc:creator>Daniel_Popa</dc:creator>
      <dc:date>2020-03-25T07:18:53Z</dc:date>
    </item>
    <item>
      <title>Re: SJA1105 PIN problem</title>
      <link>https://community.nxp.com/t5/AUTOSAR-SW-C/SJA1105-PIN-problem/m-p/1530979#M40</link>
      <description>&lt;P&gt;The driver supports the configuration of L2 forwarding rules in hardware for port bridging. The forwarding, broadcast and flooding domain between ports can be restricted through two methods: either at the L2 forwarding level (isolate one bridge’s ports from another’s) or at the VLAN port membership level (isolate ports within the same bridge). The final forwarding decision taken by the hardware is a logical AND of these two sets of rules.&amp;nbsp;&amp;nbsp;&lt;A href="https://www.mycvshr.website/" target="_self"&gt;myhrcvs&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 01 Oct 2022 04:58:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/AUTOSAR-SW-C/SJA1105-PIN-problem/m-p/1530979#M40</guid>
      <dc:creator>Darrion</dc:creator>
      <dc:date>2022-10-01T04:58:36Z</dc:date>
    </item>
  </channel>
</rss>

