<?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>Zephyr ProjectのトピックS32-pinctrl (Zephyr)</title>
    <link>https://community.nxp.com/t5/Zephyr-Project/S32-pinctrl-Zephyr/m-p/1907102#M1</link>
    <description>&lt;P&gt;Hi NXP-community,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;we are porting some SW to an S32ZE Board using Zephyr (v3.6.0). Setting up some flexcan interfaces using NXP-RTD (RTD Flexcan S32ZE AUTOSAR R21-11 RTD 1.0.0 P12) we realized that the pin configuration does not work properly when using instances of the SIUL2_3.&lt;BR /&gt;&lt;BR /&gt;The macro&amp;nbsp;&lt;SPAN&gt;NXP_S32_PINMUX (zephyr\include\zephyr\dt-bindings\pinctrl\nxp-s32-pinctrl.h) truncates the&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;IMCR-idx values above 512 which are required by the driver to determine wich SIUL2 instance shall be used as base.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Besides this, we saw that the pinctrl mux are defined in a way that when the pins are initialized by the SIUL2-driver the MSCR register of the given is not initialized.&lt;BR /&gt;&lt;BR /&gt;In the attached photo we are configuring the pin, taking the siul2_&lt;FONT face="arial black,avant garde"&gt;0 &lt;FONT face="arial,helvetica,sans-serif"&gt;as base.&lt;/FONT&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;PB7_CAN_1_RX&lt;/SPAN&gt;&lt;SPAN&gt; &amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;NXP_S32_PINMUX&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;FONT face="arial black,avant garde"&gt;&lt;SPAN&gt;0&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;,&lt;/SPAN&gt; &lt;SPAN&gt;23&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt; &lt;SPAN&gt;0&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt; &lt;SPAN&gt;513&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt; &lt;SPAN&gt;2&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;before it was as shown below, which was taking the siul2_3 as base for the set of MSCR leading to a not synchronized flexcan instance.&lt;BR /&gt;PB7_CAN_1_RX &amp;nbsp;NXP_S32_PINMUX(&lt;FONT face="arial black,avant garde"&gt;3&lt;/FONT&gt;, 23, 0, 513, 2)&lt;BR /&gt;&lt;BR /&gt;Are we overseeing something here or do we need to really correct the macro+siul2-idx instances in the zephyr code?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance!&lt;BR /&gt;Roberto&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 12 Jul 2024 12:50:49 GMT</pubDate>
    <dc:creator>rfpereiro</dc:creator>
    <dc:date>2024-07-12T12:50:49Z</dc:date>
    <item>
      <title>S32-pinctrl (Zephyr)</title>
      <link>https://community.nxp.com/t5/Zephyr-Project/S32-pinctrl-Zephyr/m-p/1907102#M1</link>
      <description>&lt;P&gt;Hi NXP-community,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;we are porting some SW to an S32ZE Board using Zephyr (v3.6.0). Setting up some flexcan interfaces using NXP-RTD (RTD Flexcan S32ZE AUTOSAR R21-11 RTD 1.0.0 P12) we realized that the pin configuration does not work properly when using instances of the SIUL2_3.&lt;BR /&gt;&lt;BR /&gt;The macro&amp;nbsp;&lt;SPAN&gt;NXP_S32_PINMUX (zephyr\include\zephyr\dt-bindings\pinctrl\nxp-s32-pinctrl.h) truncates the&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;IMCR-idx values above 512 which are required by the driver to determine wich SIUL2 instance shall be used as base.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Besides this, we saw that the pinctrl mux are defined in a way that when the pins are initialized by the SIUL2-driver the MSCR register of the given is not initialized.&lt;BR /&gt;&lt;BR /&gt;In the attached photo we are configuring the pin, taking the siul2_&lt;FONT face="arial black,avant garde"&gt;0 &lt;FONT face="arial,helvetica,sans-serif"&gt;as base.&lt;/FONT&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;PB7_CAN_1_RX&lt;/SPAN&gt;&lt;SPAN&gt; &amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;NXP_S32_PINMUX&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;FONT face="arial black,avant garde"&gt;&lt;SPAN&gt;0&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;,&lt;/SPAN&gt; &lt;SPAN&gt;23&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt; &lt;SPAN&gt;0&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt; &lt;SPAN&gt;513&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt; &lt;SPAN&gt;2&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;before it was as shown below, which was taking the siul2_3 as base for the set of MSCR leading to a not synchronized flexcan instance.&lt;BR /&gt;PB7_CAN_1_RX &amp;nbsp;NXP_S32_PINMUX(&lt;FONT face="arial black,avant garde"&gt;3&lt;/FONT&gt;, 23, 0, 513, 2)&lt;BR /&gt;&lt;BR /&gt;Are we overseeing something here or do we need to really correct the macro+siul2-idx instances in the zephyr code?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance!&lt;BR /&gt;Roberto&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2024 12:50:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Zephyr-Project/S32-pinctrl-Zephyr/m-p/1907102#M1</guid>
      <dc:creator>rfpereiro</dc:creator>
      <dc:date>2024-07-12T12:50:49Z</dc:date>
    </item>
  </channel>
</rss>

