<?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 Re: Why don't the example PMIC OTP scripts program the I2C address? in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Why-don-t-the-example-PMIC-OTP-scripts-program-the-I2C-address/m-p/478840#M76138</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you very much! This answers my question.&lt;/P&gt;&lt;P&gt;-Ted&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Feb 2016 15:01:41 GMT</pubDate>
    <dc:creator>tedwolfe</dc:creator>
    <dc:date>2016-02-23T15:01:41Z</dc:date>
    <item>
      <title>Why don't the example PMIC OTP scripts program the I2C address?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Why-don-t-the-example-PMIC-OTP-scripts-program-the-I2C-address/m-p/478838#M76136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I was about to program the 'NP' version of the PF0100A PMIC devices using the KITPFGUI v4.0, but noticed that the example programming scripts (such as 'Example_Script(F0-Sample-Manual-ProgramECC).txt') downloaded with the GUI do not program the Extended Page1 OTP I2C ADDR register (address FF) containing the I2C address.&amp;nbsp; It seems to me that this resister should be programmed during OTP fuse programming, since the PMIC datasheet does not specify a default value for any of the Ext. Page1 registers including OTP I2C ADDR.&amp;nbsp; If the I2C address is not programmed, what I2C address is used to communicate to the PMIC via the I2C interface?&amp;nbsp; Why do the example programming scripts not bother to program the OTP I2C ADDR?&amp;nbsp; Is there some good reason for this, or is it just an oversight?&amp;nbsp; I noticed that the example given in AN4536 (see pg 4) does program this register with an I2C address value...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for your help,&lt;/P&gt;&lt;P&gt;Ted&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Feb 2016 16:25:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Why-don-t-the-example-PMIC-OTP-scripts-program-the-I2C-address/m-p/478838#M76136</guid>
      <dc:creator>tedwolfe</dc:creator>
      <dc:date>2016-02-22T16:25:56Z</dc:date>
    </item>
    <item>
      <title>Re: Why don't the example PMIC OTP scripts program the I2C address?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Why-don-t-the-example-PMIC-OTP-scripts-program-the-I2C-address/m-p/478839#M76137</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ted,&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi;"&gt;Yes, we don’t put the command of changing PMIC MMPF0100A OTP I2C Addr. in the example programming scripts, if I2C Addr. is not programmed, it’s 0x08 by default; generally customers can accept this default I2C Device Addr. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi;"&gt;You can add one command in the OTP script, as below red bold row, the OTP I2C Addr. is still 0x08, customer can change this "0x08" according to their request. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #00b050; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi;"&gt;WRITE_I2C:E0:0E // Power up DVS=25mV/16us, Seq CLK=2000us, PWRON config=0&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="mso-bidi-font-family: 'Times New Roman'; color: red; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-theme-font: minor-bidi; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin;"&gt;&lt;STRONG&gt;WRITE_I2C:FF:08 // I2C Device Address = 0x08&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #00b050; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi;"&gt;//-----------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #00b050; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi;"&gt;WRITE_I2C:E4:02 // FUSE POR=1 (This Enables OTP Programming)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #00b050; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi;"&gt;WRITE_I2C:E5:02 // FUSE POR=1 (This Enables OTP Programming)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #00b050; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi;"&gt;WRITE_I2C:E6:02 // FUSE POR=1 (This Enables OTP Programming)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi;"&gt;Sean&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Feb 2016 06:25:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Why-don-t-the-example-PMIC-OTP-scripts-program-the-I2C-address/m-p/478839#M76137</guid>
      <dc:creator>b36835</dc:creator>
      <dc:date>2016-02-23T06:25:39Z</dc:date>
    </item>
    <item>
      <title>Re: Why don't the example PMIC OTP scripts program the I2C address?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Why-don-t-the-example-PMIC-OTP-scripts-program-the-I2C-address/m-p/478840#M76138</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you very much! This answers my question.&lt;/P&gt;&lt;P&gt;-Ted&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Feb 2016 15:01:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Why-don-t-the-example-PMIC-OTP-scripts-program-the-I2C-address/m-p/478840#M76138</guid>
      <dc:creator>tedwolfe</dc:creator>
      <dc:date>2016-02-23T15:01:41Z</dc:date>
    </item>
  </channel>
</rss>

