<?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: HCS08QRUG Question about slaveAddress in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/HCS08QRUG-Question-about-slaveAddress/m-p/174241#M12000</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;Hello Tim,&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;A simple way of handling an IIC slave address would be to #define a macro&amp;nbsp;having the value required for the particular external device.&amp;nbsp; The macro name can then be used as a constant when sending the address byte.&amp;nbsp; An issue will be whether the value defined by the macro is already&amp;nbsp;left-shifted,&amp;nbsp;to allow the inclusion of the read/write bit.&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;Regards,&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;Mac&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Dec 2007 09:28:36 GMT</pubDate>
    <dc:creator>bigmac</dc:creator>
    <dc:date>2007-12-20T09:28:36Z</dc:date>
    <item>
      <title>HCS08QRUG Question about slaveAddress</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/HCS08QRUG-Question-about-slaveAddress/m-p/174238#M11997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Hi folks,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Starting to get up to speed on C &amp;amp; iic, and have been playing with the HCS08QRUG&lt;/DIV&gt;&lt;DIV&gt;software.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;My test project is to talk to a 'simple' RTC from Maxim, and am modifying the routines&lt;/DIV&gt;&lt;DIV&gt;given to make it happen.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;For the life of me, I cannot see where in the example code the slave's address is&lt;/DIV&gt;&lt;DIV&gt;declared. (or even selfAddress).&amp;nbsp;&amp;nbsp;I can&amp;nbsp;see how it is manipulated &amp;amp; then placed in&lt;/DIV&gt;&lt;DIV&gt;the IICD register.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;This is probably something very basic, but if anyone has a minute, maybe they&lt;/DIV&gt;&lt;DIV&gt;can point me in the right direction.&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;Thanks!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Tim&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Dec 2007 13:08:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/HCS08QRUG-Question-about-slaveAddress/m-p/174238#M11997</guid>
      <dc:creator>UtopiaTim</dc:creator>
      <dc:date>2007-12-19T13:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: HCS08QRUG Question about slaveAddress</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/HCS08QRUG-Question-about-slaveAddress/m-p/174239#M11998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;BTW,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Seems it would be a good thing for someone at Freescale to write a simple&lt;/DIV&gt;&lt;DIV&gt;example program that has the micro as the Master, and have it talk to a commonly&lt;/DIV&gt;&lt;DIV&gt;available IIC peripheral (not a&amp;nbsp;memory, or other micro pretending to be an IIC part).&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Just something simple, not with master/slave options/kitchen sink/etc ! &lt;IMG alt=":smileysurprised:" class="emoticon emoticon-smileysurprised" id="smileysurprised" src="http://freescale.i.lithium.com/i/smilies/16x16_smiley-surprised.gif" title="Smiley Surprised" /&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Sometimes trying to sift out all the options &amp;amp; ap notes is a bit tough.&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;Thanks,&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;Tim&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Dec 2007 13:28:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/HCS08QRUG-Question-about-slaveAddress/m-p/174239#M11998</guid>
      <dc:creator>UtopiaTim</dc:creator>
      <dc:date>2007-12-19T13:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: HCS08QRUG Question about slaveAddress</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/HCS08QRUG-Question-about-slaveAddress/m-p/174240#M11999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Actually, code to talk I2C is all over the place. But from your posting, what would probably help you the most would be a sample datastream that would show how the part interacts with the master/host.&lt;BR /&gt;&lt;BR /&gt;When I designed one of my devices, I has to talk to the DS1307 RTC part, and I had a choice of two Freescale parts. One didn't have I2C built in, and that was the one I was probably going to use, so I just hooked it up using the same pins just in case and wrote my code so that it manually did the I2C.&lt;BR /&gt;&lt;BR /&gt;Hmm, I could post my notes as to how I got it to work, but I don't have them handy (they are commented in my source). However, I DO seem to remember that the slave address was 7 bits, not 8, and shifted 1 bit place. As a result, if you are looking at the datastream, and expect to see the address stream by, you'll miss it because of the offset.&lt;BR /&gt;&lt;BR /&gt;I2C is actually pretty simple, once you get the mindset. I actually found it more complex and befuddeling to try to go back and incorporate the hardware I2C support than to just leave my routines in place.&lt;BR /&gt;&lt;BR /&gt;Mike&lt;BR /&gt;&lt;BR /&gt;Message Edited by mke_et on &lt;SPAN class="date_text"&gt;2007-12-19&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;01:50 PM&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Dec 2007 02:47:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/HCS08QRUG-Question-about-slaveAddress/m-p/174240#M11999</guid>
      <dc:creator>mke_et</dc:creator>
      <dc:date>2007-12-20T02:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: HCS08QRUG Question about slaveAddress</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/HCS08QRUG-Question-about-slaveAddress/m-p/174241#M12000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;Hello Tim,&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;A simple way of handling an IIC slave address would be to #define a macro&amp;nbsp;having the value required for the particular external device.&amp;nbsp; The macro name can then be used as a constant when sending the address byte.&amp;nbsp; An issue will be whether the value defined by the macro is already&amp;nbsp;left-shifted,&amp;nbsp;to allow the inclusion of the read/write bit.&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;Regards,&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;Mac&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT size="2"&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Dec 2007 09:28:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/HCS08QRUG-Question-about-slaveAddress/m-p/174241#M12000</guid>
      <dc:creator>bigmac</dc:creator>
      <dc:date>2007-12-20T09:28:36Z</dc:date>
    </item>
  </channel>
</rss>

