<?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のトピックMCAL and Drivers together</title>
    <link>https://community.nxp.com/t5/S32K/MCAL-and-Drivers-together/m-p/1746384#M28155</link>
    <description>&lt;P&gt;Can I use both Lpspi driver (non-autosar) and Spi (autosar) MCAL in the same project? For instance, can I use Lpspi driver functions for LPSPI5 and Spi MCAL functions for other LPSPI (except 5), or is it going to create conflicts in trying to configure both in one main.c?&lt;/P&gt;</description>
    <pubDate>Wed, 25 Oct 2023 21:23:46 GMT</pubDate>
    <dc:creator>psarkar</dc:creator>
    <dc:date>2023-10-25T21:23:46Z</dc:date>
    <item>
      <title>MCAL and Drivers together</title>
      <link>https://community.nxp.com/t5/S32K/MCAL-and-Drivers-together/m-p/1746384#M28155</link>
      <description>&lt;P&gt;Can I use both Lpspi driver (non-autosar) and Spi (autosar) MCAL in the same project? For instance, can I use Lpspi driver functions for LPSPI5 and Spi MCAL functions for other LPSPI (except 5), or is it going to create conflicts in trying to configure both in one main.c?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Oct 2023 21:23:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/MCAL-and-Drivers-together/m-p/1746384#M28155</guid>
      <dc:creator>psarkar</dc:creator>
      <dc:date>2023-10-25T21:23:46Z</dc:date>
    </item>
    <item>
      <title>Re: MCAL and Drivers together</title>
      <link>https://community.nxp.com/t5/S32K/MCAL-and-Drivers-together/m-p/1746515#M28167</link>
      <description>&lt;P&gt;&lt;A href="mailto:Hi@psarkar" target="_blank"&gt;Hi@psarkar&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Some limitations of mixing MCAL and Driver&lt;/P&gt;
&lt;P&gt;1.It is forbidden to use the same hardware instance in HLD and LLD (E.g. if SPI1 is used in HLD context, it cannot be used also through IPL)&lt;/P&gt;
&lt;P&gt;2.IP layer doesn’t provide Tresos configuration. It can be configured only on Design Studio (CT).&lt;/P&gt;
&lt;P&gt;3.&lt;U&gt;&lt;STRONG&gt;IP layer cannot be used in Autosar applications, as it does not satisfy ASR compliance constraints (DEM, DET, Multicore). IP layer should not be seen as a CDD&lt;/STRONG&gt;&lt;/U&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;for example,you can use SPI5 at the MCAL layer and SPI4 at the driver layer. This will not cause an error when configuring using S32 DS, but this is actually not in compliance with the specification.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So it is not recommended to do this&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2023 03:00:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/MCAL-and-Drivers-together/m-p/1746515#M28167</guid>
      <dc:creator>Senlent</dc:creator>
      <dc:date>2023-10-26T03:00:53Z</dc:date>
    </item>
  </channel>
</rss>

