<?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のトピックRe: KL25 and DALLAS iButton (1-Wire)</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL25-and-DALLAS-iButton-1-Wire/m-p/492220#M30409</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have had very clean results with the DS2483 I2C-to-onewire 'master' device to supply 'perfect' one-wire control, using one I2C interface and an internal-timer to wait-out each resultant one-wire process.&amp;nbsp; To cut my overhead I also built an interrupt-driven I2C process and next-level state machine to complete entire one-wire transactions with minimal processor use.&amp;nbsp; This all runs 'in the background' because I have 'realtime work' to get done, and that does add a certain amount of complexity...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message me for details.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 27 Feb 2016 01:45:36 GMT</pubDate>
    <dc:creator>egoodii</dc:creator>
    <dc:date>2016-02-27T01:45:36Z</dc:date>
    <item>
      <title>KL25 and DALLAS iButton (1-Wire)</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL25-and-DALLAS-iButton-1-Wire/m-p/492217#M30406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to handle 1-Wire signal from iButton using UART0 in 1-Wire mode (something like ISO7816) or not?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2016 13:49:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL25-and-DALLAS-iButton-1-Wire/m-p/492217#M30406</guid>
      <dc:creator>SergeMaslenniko</dc:creator>
      <dc:date>2016-02-26T13:49:58Z</dc:date>
    </item>
    <item>
      <title>Re: KL25 and DALLAS iButton (1-Wire)</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL25-and-DALLAS-iButton-1-Wire/m-p/492218#M30407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Serge,&lt;/P&gt;&lt;P&gt;The Dallas Button requires different communication protocol as can be managed by UART0. Please see the communication details on web:&lt;/P&gt;&lt;P&gt;&lt;A href="https://en.wikipedia.org/wiki/1-Wire" title="https://en.wikipedia.org/wiki/1-Wire"&gt;1-Wire - Wikipedia, the free encyclopedia&lt;/A&gt;&amp;nbsp; . It is possible to use standard GPIO method with timer to communicate with 1-Wire Slave.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it could help, but you are welcome for next support.&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Stano.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2016 14:51:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL25-and-DALLAS-iButton-1-Wire/m-p/492218#M30407</guid>
      <dc:creator>Stano</dc:creator>
      <dc:date>2016-02-26T14:51:07Z</dc:date>
    </item>
    <item>
      <title>Re: KL25 and DALLAS iButton (1-Wire)</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL25-and-DALLAS-iButton-1-Wire/m-p/492219#M30408</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Serge,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have a TPM timer (with 3 or 4 channels) and two DMA channels available, the Dallas/Maxim 1-wire bus master can also be implemented as discussed here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/384485"&gt;Dallas iButton High Resolution Delays with No Preemption&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Although this link is to a question in the MQX software section, the timer based solution described there was developed and tested using a KL26 micro.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Zeljko&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2016 22:19:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL25-and-DALLAS-iButton-1-Wire/m-p/492219#M30408</guid>
      <dc:creator>zeljko_stefanovic</dc:creator>
      <dc:date>2016-02-26T22:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: KL25 and DALLAS iButton (1-Wire)</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL25-and-DALLAS-iButton-1-Wire/m-p/492220#M30409</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have had very clean results with the DS2483 I2C-to-onewire 'master' device to supply 'perfect' one-wire control, using one I2C interface and an internal-timer to wait-out each resultant one-wire process.&amp;nbsp; To cut my overhead I also built an interrupt-driven I2C process and next-level state machine to complete entire one-wire transactions with minimal processor use.&amp;nbsp; This all runs 'in the background' because I have 'realtime work' to get done, and that does add a certain amount of complexity...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message me for details.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Feb 2016 01:45:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL25-and-DALLAS-iButton-1-Wire/m-p/492220#M30409</guid>
      <dc:creator>egoodii</dc:creator>
      <dc:date>2016-02-27T01:45:36Z</dc:date>
    </item>
  </channel>
</rss>

