<?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>High Performance Analog Front End InterfacesのトピックBinary and hexadecimal address mismatch for PCAL6524</title>
    <link>https://community.nxp.com/t5/High-Performance-Analog-Front/Binary-and-hexadecimal-address-mismatch-for-PCAL6524/m-p/2060665#M19</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am running on an issue on the I2C bus addresses for the PCAL6524. The address in binary does not match the address in hexadecimal. i.e: 0100000 should give us 0x20 but it is saying 0x40 in the chip datasheet (p7/70). Can you guys clarify on what is going on?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pcal6524.PNG" style="width: 490px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/327794iDF609ADBED045376/image-size/large?v=v2&amp;amp;px=999" role="button" title="pcal6524.PNG" alt="pcal6524.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Mar 2025 17:47:38 GMT</pubDate>
    <dc:creator>sbah</dc:creator>
    <dc:date>2025-03-12T17:47:38Z</dc:date>
    <item>
      <title>Binary and hexadecimal address mismatch for PCAL6524</title>
      <link>https://community.nxp.com/t5/High-Performance-Analog-Front/Binary-and-hexadecimal-address-mismatch-for-PCAL6524/m-p/2060665#M19</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am running on an issue on the I2C bus addresses for the PCAL6524. The address in binary does not match the address in hexadecimal. i.e: 0100000 should give us 0x20 but it is saying 0x40 in the chip datasheet (p7/70). Can you guys clarify on what is going on?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="pcal6524.PNG" style="width: 490px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/327794iDF609ADBED045376/image-size/large?v=v2&amp;amp;px=999" role="button" title="pcal6524.PNG" alt="pcal6524.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Mar 2025 17:47:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/High-Performance-Analog-Front/Binary-and-hexadecimal-address-mismatch-for-PCAL6524/m-p/2060665#M19</guid>
      <dc:creator>sbah</dc:creator>
      <dc:date>2025-03-12T17:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: Binary and hexadecimal address mismatch for PCAL6524</title>
      <link>https://community.nxp.com/t5/High-Performance-Analog-Front/Binary-and-hexadecimal-address-mismatch-for-PCAL6524/m-p/2060693#M20</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The address in hexadecimal is actually the full 8-bit write slave address (R/W bit = 0).&lt;/P&gt;
&lt;P&gt;PCAL6524 has fix value for A6 – A2 as “01000”, and programmable A1-A0 settings (depending on what is connected to ADDR pin).&lt;/P&gt;
&lt;P&gt;If for example ADDR = VSS, then PCAL6524 uses 0x44 (“0100010” + “0”) for I2C write slave address, and 0x45 (“0100010” + “1”) for I2C read slave address.&lt;/P&gt;
&lt;P&gt;If for example ADDR = VDD, then PCAL6524 uses 0x46 (“0100011” + “0”) for I2C write slave address, and 0x47 (“0100011” + “1”) for I2C read slave address.&lt;/P&gt;
&lt;P&gt;BRs, Tomas&lt;/P&gt;</description>
      <pubDate>Wed, 12 Mar 2025 19:24:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/High-Performance-Analog-Front/Binary-and-hexadecimal-address-mismatch-for-PCAL6524/m-p/2060693#M20</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2025-03-12T19:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: Binary and hexadecimal address mismatch for PCAL6524</title>
      <link>https://community.nxp.com/t5/High-Performance-Analog-Front/Binary-and-hexadecimal-address-mismatch-for-PCAL6524/m-p/2060695#M21</link>
      <description>Hi Thomas, thank you for the clarification.&lt;BR /&gt;&lt;BR /&gt;However, there is only one ADDR pin. It does give A1 and A0 bits different values depending on what is connected to it: SCL, SDA, GND and VS.</description>
      <pubDate>Wed, 12 Mar 2025 19:08:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/High-Performance-Analog-Front/Binary-and-hexadecimal-address-mismatch-for-PCAL6524/m-p/2060695#M21</guid>
      <dc:creator>sbah</dc:creator>
      <dc:date>2025-03-12T19:08:11Z</dc:date>
    </item>
    <item>
      <title>Re: Binary and hexadecimal address mismatch for PCAL6524</title>
      <link>https://community.nxp.com/t5/High-Performance-Analog-Front/Binary-and-hexadecimal-address-mismatch-for-PCAL6524/m-p/2061011#M23</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Yes, A1 and A0 are not HW address pins, which is quite common in other devices, but 2 bits whose value depends on the connection of the ADDR pin as shown in Table 4.&lt;/P&gt;
&lt;P&gt;BR, Tomas&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2025 07:08:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/High-Performance-Analog-Front/Binary-and-hexadecimal-address-mismatch-for-PCAL6524/m-p/2061011#M23</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2025-03-13T07:08:12Z</dc:date>
    </item>
  </channel>
</rss>

