<?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中的主题 Re: PHY_665A causing DET</title>
    <link>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2104025#M49172</link>
    <description>&lt;P&gt;Hello Pratik,&lt;/P&gt;
&lt;P&gt;great. I am glad, that your issue is solved. Thank you for letting me know. I will inform the SW team.&lt;/P&gt;
&lt;P&gt;Have a nice day.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With Best Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Jozef&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 26 May 2025 03:58:28 GMT</pubDate>
    <dc:creator>JozefKozon</dc:creator>
    <dc:date>2025-05-26T03:58:28Z</dc:date>
    <item>
      <title>PHY_665A causing DET</title>
      <link>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2091034#M48401</link>
      <description>&lt;P&gt;Hello team,&lt;BR /&gt;&lt;BR /&gt;I am integrating TPL module for my project on SPI 1 and 2. I have configured SPI device as well as configured PHY_665A and BMS_Common, Bcc_772a, Bcc_774a components. But I am getting below error stack:&lt;BR /&gt;&lt;BR /&gt;Det_EndlessLoop()&lt;BR /&gt;Det_ReportError(:ModuleId = 255, :InstanceId = 0, :ApiId = 172, :ErrorId = 30)&lt;BR /&gt;Phy_665a_SpiVariantInit()&lt;BR /&gt;Phy_665a_Init(:McuIfProtocol = PHY_665A_SPI)&lt;BR /&gt;RE_ManageLED(:self = 0)&lt;BR /&gt;Os_Task_ApplicationTask()&lt;BR /&gt;Os_TrapIsrEpilogue()&lt;BR /&gt;&lt;BR /&gt;tried to debug everyway possible in PHY_665A but somehow I believe, when&amp;nbsp;Phy_665a_Init is called I am not able to enter SPI ISRs as well.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Let me know if any supporting project or files needed.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 02 May 2025 18:23:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2091034#M48401</guid>
      <dc:creator>pjadhav21</dc:creator>
      <dc:date>2025-05-02T18:23:03Z</dc:date>
    </item>
    <item>
      <title>Re: PHY_665A causing DET</title>
      <link>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2094581#M48612</link>
      <description>&lt;P&gt;Hello Pratik,&lt;/P&gt;
&lt;P&gt;I have posted the description of your issue to a SW team. So far I haven't received an answer. As soon as I will receive an answer, I will definitely reply to you.&lt;/P&gt;
&lt;P&gt;Thank you for your patience.&lt;/P&gt;
&lt;P&gt;With Best Regards,&lt;/P&gt;
&lt;P&gt;Jozef&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 10:51:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2094581#M48612</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2025-05-09T10:51:22Z</dc:date>
    </item>
    <item>
      <title>Re: PHY_665A causing DET</title>
      <link>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2098033#M48829</link>
      <description>&lt;P&gt;Hello Pratik,&lt;/P&gt;
&lt;P&gt;unfortunately there is still no answer from the software team. As soon as I will receive an one, I will definitely reply to you.&lt;/P&gt;
&lt;P&gt;Thank you for your patience.&lt;/P&gt;
&lt;P&gt;With Best Regards,&lt;/P&gt;
&lt;P&gt;Jozef&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2025 09:39:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2098033#M48829</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2025-05-15T09:39:02Z</dc:date>
    </item>
    <item>
      <title>Re: PHY_665A causing DET</title>
      <link>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2101261#M49033</link>
      <description>&lt;P&gt;Hello Pratik,&lt;/P&gt;
&lt;P&gt;I apologize for the delay. I have just checked our internal community, but there is still no answer from the SW team. I have just sent them a reminder. As soon as they will answer me, I will definitely reply to you.&lt;/P&gt;
&lt;P&gt;Thank you for your patience.&lt;/P&gt;
&lt;P&gt;With Best Regards,&lt;/P&gt;
&lt;P&gt;Jozef&lt;/P&gt;</description>
      <pubDate>Wed, 21 May 2025 06:48:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2101261#M49033</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2025-05-21T06:48:00Z</dc:date>
    </item>
    <item>
      <title>Re: PHY_665A causing DET</title>
      <link>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2102634#M49092</link>
      <description>&lt;P&gt;Hello Pratik,&lt;/P&gt;
&lt;P&gt;please see below another answer from the SW team I have just received.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;DESCRIPTION&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#0000FF"&gt;Please inform us about which version of BMS SDK and RTD drivers are you using.&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Please make sure to have all the MCAL-layer drivers initialized prior to Phy_665a initialization: (Icu, Mcu, Mcl, Spi, Gpt, OsIf, Platform, Port, Rm). You can use an Tresos/S32DS example as a reference.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#0000FF"&gt;Please make sure you have the interrupts configured as specified in the user manual and that the interrupt controller is initialized and working.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#0000FF"&gt;Spi driver shall be configured to work in asynchronous mode.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With Best Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Jozef&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 11:12:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2102634#M49092</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2025-05-22T11:12:54Z</dc:date>
    </item>
    <item>
      <title>Re: PHY_665A causing DET</title>
      <link>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2102635#M49093</link>
      <description>&lt;P&gt;Hello Pratik,&lt;/P&gt;
&lt;P&gt;please see below an answer from the SW team I have just received.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;DESCRIPTION&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#0000FF"&gt;&lt;SPAN&gt;It might be an initialization issue? Are the dependency drivers initialized (SPI, GPT,ICU, MCL, MCU).&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With Best Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Jozef&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 10:27:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2102635#M49093</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2025-05-22T10:27:14Z</dc:date>
    </item>
    <item>
      <title>Re: PHY_665A causing DET</title>
      <link>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2103815#M49161</link>
      <description>&lt;P&gt;Thank you so much for the response team. I was able to fix the issue, it was more of MCAL initialization sequence issue.&lt;/P&gt;</description>
      <pubDate>Sat, 24 May 2025 03:22:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2103815#M49161</guid>
      <dc:creator>pjadhav21</dc:creator>
      <dc:date>2025-05-24T03:22:06Z</dc:date>
    </item>
    <item>
      <title>Re: PHY_665A causing DET</title>
      <link>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2104025#M49172</link>
      <description>&lt;P&gt;Hello Pratik,&lt;/P&gt;
&lt;P&gt;great. I am glad, that your issue is solved. Thank you for letting me know. I will inform the SW team.&lt;/P&gt;
&lt;P&gt;Have a nice day.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With Best Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Jozef&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 26 May 2025 03:58:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/PHY-665A-causing-DET/m-p/2104025#M49172</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2025-05-26T03:58:28Z</dc:date>
    </item>
  </channel>
</rss>

