<?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>Kinetis MicrocontrollersのトピックProcessor Expert and Serial I2C EEPROMs</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Processor-Expert-and-Serial-I2C-EEPROMs/m-p/513418#M32499</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When using the Processor Expert component, I2C_LDD, to access a serial EEPROM, how,is the&lt;/P&gt;&lt;P&gt;device address specified? I am using an ST 24C16 chip. The device select code is the standard&lt;/P&gt;&lt;P&gt;0xA0, plus the 3 MSB address bits. The Processor Expert methods such as SelectSlaveDevice&lt;/P&gt;&lt;P&gt;require the device address as a parameter, But the generated code checks for an address &lt;/P&gt;&lt;P&gt;greater than 127 and flags an error if found. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 24C16 uses the 3 MSB address bits as a 2K block select. The memory address is the offset&lt;/P&gt;&lt;P&gt;within the 2K block. How is the device address specified to get the 0xA0 sent on the I2C bus?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Jun 2016 16:09:33 GMT</pubDate>
    <dc:creator>richardfox75</dc:creator>
    <dc:date>2016-06-02T16:09:33Z</dc:date>
    <item>
      <title>Processor Expert and Serial I2C EEPROMs</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Processor-Expert-and-Serial-I2C-EEPROMs/m-p/513418#M32499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When using the Processor Expert component, I2C_LDD, to access a serial EEPROM, how,is the&lt;/P&gt;&lt;P&gt;device address specified? I am using an ST 24C16 chip. The device select code is the standard&lt;/P&gt;&lt;P&gt;0xA0, plus the 3 MSB address bits. The Processor Expert methods such as SelectSlaveDevice&lt;/P&gt;&lt;P&gt;require the device address as a parameter, But the generated code checks for an address &lt;/P&gt;&lt;P&gt;greater than 127 and flags an error if found. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 24C16 uses the 3 MSB address bits as a 2K block select. The memory address is the offset&lt;/P&gt;&lt;P&gt;within the 2K block. How is the device address specified to get the 0xA0 sent on the I2C bus?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jun 2016 16:09:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Processor-Expert-and-Serial-I2C-EEPROMs/m-p/513418#M32499</guid>
      <dc:creator>richardfox75</dc:creator>
      <dc:date>2016-06-02T16:09:33Z</dc:date>
    </item>
    <item>
      <title>Re: Processor Expert and Serial I2C EEPROMs</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Processor-Expert-and-Serial-I2C-EEPROMs/m-p/513419#M32500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Richard,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; From the 24C16 datasheet, we can know that, the device select code is like following:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="9.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/59724i891DFD6E62246DE5/image-size/large?v=v2&amp;amp;px=999" role="button" title="9.jpg" alt="9.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="10.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/59802iAB172A0CA6AE773F/image-size/large?v=v2&amp;amp;px=999" role="button" title="10.jpg" alt="10.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; So, you can configure the device code+memory MSB addresses as the PE I2C target slave address, then write the I2C code, follow the Byte ADDR in the code, this Byte code, you don't need to add in the PE I2C address configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wish it helps you!&lt;/P&gt;&lt;P&gt;If you still have question, please contact me!&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Jingjing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Jun 2016 06:26:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Processor-Expert-and-Serial-I2C-EEPROMs/m-p/513419#M32500</guid>
      <dc:creator>kerryzhou</dc:creator>
      <dc:date>2016-06-03T06:26:28Z</dc:date>
    </item>
    <item>
      <title>Re: Processor Expert and Serial I2C EEPROMs</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Processor-Expert-and-Serial-I2C-EEPROMs/m-p/513420#M32501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Richard,&lt;/P&gt;&lt;P&gt;I do have an example (plus a Processor Expert component) for the 24A series of EEPROMS, see &lt;A href="https://mcuoneclipse.com/2013/08/18/driver-for-microchip-24xx-serial-eeprom/" title="https://mcuoneclipse.com/2013/08/18/driver-for-microchip-24xx-serial-eeprom/"&gt;https://mcuoneclipse.com/2013/08/18/driver-for-microchip-24xx-serial-eeprom/&lt;/A&gt; .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think your ST chip is compatible with the Micrchip one. That component supports multiple different devices, including the '16' one:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/59950i6A832FED9870CC8C/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Jun 2016 06:37:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Processor-Expert-and-Serial-I2C-EEPROMs/m-p/513420#M32501</guid>
      <dc:creator>BlackNight</dc:creator>
      <dc:date>2016-06-03T06:37:47Z</dc:date>
    </item>
    <item>
      <title>Re: Processor Expert and Serial I2C EEPROMs</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Processor-Expert-and-Serial-I2C-EEPROMs/m-p/513421#M32502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Erich,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the e-mail response. I used your 24xx component. The code works&lt;/P&gt;&lt;P&gt;correctly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dick Fox&lt;/P&gt;&lt;P&gt;Firmware  Engineer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NATIONAL CONTROLS CORPORATION BUSINESS UNIT&lt;/P&gt;&lt;P&gt;INSTRUMENTATION AND SPECIALTY CONTROLS DIVISION&lt;/P&gt;&lt;P&gt;1725 Western Dr | West Chicago, IL 60185 | &lt;A href="http://www.ametekncc.com" target="test_blank"&gt;http://www.ametekncc.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Phone: (630)621-3118 | email: Dick Fox@ametek.com&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Jun 2016 12:50:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Processor-Expert-and-Serial-I2C-EEPROMs/m-p/513421#M32502</guid>
      <dc:creator>richardfox75</dc:creator>
      <dc:date>2016-06-03T12:50:04Z</dc:date>
    </item>
  </channel>
</rss>

