<?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 OTP configuration in FS85 in Power Management</title>
    <link>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916330#M407</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi NXP team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For FS85 PMIC, Is it possible to configure the following OTP registers through FS85 driver during init :&lt;/P&gt;&lt;P&gt;1.&amp;nbsp;WD_SELECTION bit of&amp;nbsp;OTP_CFG_ASIL register for challenger mode&lt;/P&gt;&lt;P&gt;2. &amp;nbsp;FLT_RECOVERY_EN bit of&amp;nbsp;&amp;nbsp;OTP_CFG_I2C register for disabling the fault recovery strategy&lt;/P&gt;&lt;P&gt;3.&amp;nbsp;&lt;SPAN&gt;Autoretry_infinite&amp;nbsp; &amp;nbsp;and&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Autoretry_en bits of&amp;nbsp;OTP_CFG_SM_2 register&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If not how these OTP registers shall be configured?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding point3 : Will the&amp;nbsp;FS85&amp;nbsp;move to DEEP_FS when fault error counter reaches maximum?&lt;/P&gt;&lt;P&gt;(According to FS85 data sheet, Exit of DEEP-FS mode is only possible by WAKE1 = 0 or after 4 s if the autoretry feature&lt;BR /&gt;is activated by OTP_Autorety_en bit. The number of autroretry can be limited to 15 or infinite depending on OTP_Autoretry_infinite bit.)&lt;/P&gt;&lt;P&gt;So after recovering from DEEP_FS when wake1 = 1, the main state machine will start transition to normal mode. I would like to know the state to which FS_state machine will transit or in other words how will&amp;nbsp;&lt;SPAN&gt;FS_state machine behave? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;(Note :The FS85 is connected to MCU for watchdog purpose)&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Aug 2019 08:41:05 GMT</pubDate>
    <dc:creator>haby_a</dc:creator>
    <dc:date>2019-08-28T08:41:05Z</dc:date>
    <item>
      <title>OTP configuration in FS85</title>
      <link>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916330#M407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi NXP team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For FS85 PMIC, Is it possible to configure the following OTP registers through FS85 driver during init :&lt;/P&gt;&lt;P&gt;1.&amp;nbsp;WD_SELECTION bit of&amp;nbsp;OTP_CFG_ASIL register for challenger mode&lt;/P&gt;&lt;P&gt;2. &amp;nbsp;FLT_RECOVERY_EN bit of&amp;nbsp;&amp;nbsp;OTP_CFG_I2C register for disabling the fault recovery strategy&lt;/P&gt;&lt;P&gt;3.&amp;nbsp;&lt;SPAN&gt;Autoretry_infinite&amp;nbsp; &amp;nbsp;and&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Autoretry_en bits of&amp;nbsp;OTP_CFG_SM_2 register&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If not how these OTP registers shall be configured?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding point3 : Will the&amp;nbsp;FS85&amp;nbsp;move to DEEP_FS when fault error counter reaches maximum?&lt;/P&gt;&lt;P&gt;(According to FS85 data sheet, Exit of DEEP-FS mode is only possible by WAKE1 = 0 or after 4 s if the autoretry feature&lt;BR /&gt;is activated by OTP_Autorety_en bit. The number of autroretry can be limited to 15 or infinite depending on OTP_Autoretry_infinite bit.)&lt;/P&gt;&lt;P&gt;So after recovering from DEEP_FS when wake1 = 1, the main state machine will start transition to normal mode. I would like to know the state to which FS_state machine will transit or in other words how will&amp;nbsp;&lt;SPAN&gt;FS_state machine behave? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;(Note :The FS85 is connected to MCU for watchdog purpose)&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Aug 2019 08:41:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916330#M407</guid>
      <dc:creator>haby_a</dc:creator>
      <dc:date>2019-08-28T08:41:05Z</dc:date>
    </item>
    <item>
      <title>Re: OTP configuration in FS85</title>
      <link>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916331#M408</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Haby,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fail-safe OTP_REGISTERS&amp;nbsp;registers cannot be changed later during the INIT_FS phase.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From Main OTP_REGISTERS, only regulators behavior in case of TSD, VPRE and VBOOST slew rate parameters can be changed later as shown in the FS84/85 Datasheet rev. 3.1 and below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/82236iBB0A2228E3954977/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So to answer your questions in detail:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. No. The Watchdog mode (Simple or Challenger) cannot be changed later during the INIT_FS phase.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;FS85 watchdog must be configured to "Challenger WD" by OTP (WD_SELECTION = 1)&amp;nbsp;for ASIL C or D safety applications.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;During the INIT_FS phase the MCU can configure the Watchdog monitoring using the FS_I_WD_CFG&lt;/P&gt;&lt;P&gt;register:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Watchdog Error Counter Limit with WD_ERR_LIMIT[1:0] bits&lt;/LI&gt;&lt;LI&gt;Watchdog Refresh Counter Limit with WD_RFR_LIMIT[1:0] bits&lt;/LI&gt;&lt;LI&gt;Watchdog impact on RSTB and FS0B with WD_FS_IMPACT[1:0] bits&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Watchdog Window Period and Watchdog Window Duty Cycle can be changed not only during the INIT_FS phase, but also later during the Normal mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. No. The Fault recovery strategy cannot be changed later during the INIT_FS phase.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the FS85 is used in combination with NXP S32x 16nm MCU and the FCCU monitoring is enabled, the FS85 Fault Recovery feature should be enabled by OTP using FLT_RECOVERY_EN OTP bit to benefit from the MCU Fault recovery strategy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. No. Both Autoretry_infinite and Autoretry_en cannot be changed later during the INIT_FS phase.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When the Fault Error Counter reaches its maximum value, the FS85 goes to Deep Fail-Safe phase if it is activated by OTP. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A few more words about OTP configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- It is system integrator's responsibility to define the OTP configuration desired for its safety application.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Only A0 parts are non-programmed OTP configurations. They can be programmed&amp;nbsp;&lt;SPAN&gt;using the &lt;A href="https://www.nxp.com/design/development-boards/analog-toolbox/fs84-fs85-safety-sbc-programming-board:KITFS85SKTEVM"&gt;KITFS85SKTEVM&lt;/A&gt;&lt;/SPAN&gt;&amp;nbsp;programming board (&lt;SPAN&gt;&lt;A href="https://www.nxp.com/docs/en/user-guide/UM11183.pdf"&gt;UM11183&lt;/A&gt;&lt;/SPAN&gt;) or&amp;nbsp;&lt;A href="https://www.nxp.com/part/KITFS85FRDMEVM" style="color: #2989c5; text-decoration: none;"&gt;KITFS85FRDMEVM&lt;/A&gt;&amp;nbsp;evaluation board (&lt;A href="https://www.nxp.com/docs/en/user-guide/UM11157.pdf"&gt;UM11157&lt;/A&gt;)&lt;SPAN&gt;. &lt;/SPAN&gt;&lt;SPAN&gt;However, this is only for debug and development to find/evaluate the&amp;nbsp;optimal configuration. Final OTP programming for parts in production can be requested either from NXP or some distributors depending on the volume.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- There are several pre-programmed OTP configurations available as shown in the datasheet (Table 2).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Tomas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV style="color: #51626f; border: 0px; font-size: 14px;"&gt;&lt;DIV class="" style="border: 0px; font-weight: inherit; margin: 20px 0px;"&gt;&lt;P style="border: 0px; font-weight: inherit;"&gt;&lt;SPAN style="border: 1pt none windowtext; font-weight: inherit; font-size: 9pt; padding: 0in;"&gt;&lt;EM&gt;PS:&amp;nbsp;If my answer helps to solve your question, please mark it as "Correct" or “Helpful”. Thank you.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Aug 2019 09:24:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916331#M408</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2019-08-29T09:24:25Z</dc:date>
    </item>
    <item>
      <title>Re: OTP configuration in FS85</title>
      <link>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916332#M409</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Tomas.&lt;/P&gt;&lt;P&gt;Please help me with this question as well&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Final OTP programming for parts in production can be requested either from NXP or some distributors depending on the volume. Does this mean during the production of IC, the configuration of OTP registers need to be done ?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Also I would like to know,&amp;nbsp;&lt;SPAN&gt;after recovering from DEEP_FS when wake1 = 1, the main state machine will start transition to normal mode. I would like to know the state to which FS_state machine will transit or in other words how will&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="border: 0px;"&gt;FS_state machine behave?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Aug 2019 11:32:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916332#M409</guid>
      <dc:creator>haby_a</dc:creator>
      <dc:date>2019-08-29T11:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: OTP configuration in FS85</title>
      <link>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916333#M410</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Haby,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, NXP or selected distributors must do the OTP programming for parts in production. OTP programming by customers (typically using the &lt;A href="https://www.nxp.com/design/development-boards/analog-toolbox/fs84-fs85-safety-sbc-programming-board:KITFS85SKTEVM"&gt;KITFS85SKTEVM&lt;/A&gt;)&amp;nbsp;is allowed only for engineering purpose during development to validate the OTP configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/84272iA70CB350A2462921/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_4.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/84457iA56A9AEBAE4F2B74/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_4.png" alt="pastedImage_4.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for your second question,&amp;nbsp;I need to double check it with the design team, but it should be the same&amp;nbsp;as the typical power up phase. When the ABIST1 is done, RSTB and PGOOD pins are released and the initialization of the device is opened for another new 256 ms.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Tomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Aug 2019 08:45:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916333#M410</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2019-08-30T08:45:34Z</dc:date>
    </item>
    <item>
      <title>Re: OTP configuration in FS85</title>
      <link>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916334#M411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Tomas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to read the OTP registers during run time?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Haby&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Oct 2019 06:14:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/OTP-configuration-in-FS85/m-p/916334#M411</guid>
      <dc:creator>haby_a</dc:creator>
      <dc:date>2019-10-10T06:14:34Z</dc:date>
    </item>
  </channel>
</rss>

