<?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>Rapid IoTのトピックRe: SDK issue with SPI for RTC access ?</title>
    <link>https://community.nxp.com/t5/Rapid-IoT/SDK-issue-with-SPI-for-RTC-access/m-p/898080#M552</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eric,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;highly appreciate your support!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you, we already solved the SDK issue by utilization and separation of Athmosphere code as mentioned above and our RTC is now working.&lt;/P&gt;&lt;P&gt;Just in another thread provided some hints in order to prevent other users to seek as well, despite to little bit missing element for pcf in Athmosphere and gap in SDK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Again thank you!&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Stanislav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Apr 2019 07:42:11 GMT</pubDate>
    <dc:creator>cerny</dc:creator>
    <dc:date>2019-04-18T07:42:11Z</dc:date>
    <item>
      <title>SDK issue with SPI for RTC access ?</title>
      <link>https://community.nxp.com/t5/Rapid-IoT/SDK-issue-with-SPI-for-RTC-access/m-p/898078#M550</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #000000; font-size: 13px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Need periodically (MCUxpresso, SDK only) read out values from sensors and store to flash incuding time stamp.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="color: #000000; font-size: 13px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;RTC library - trying to use sensors/pcf2123.h from SDK,&amp;nbsp;but seems missing functions around SPI, which are required for callback:&lt;BR /&gt;pcf2123_fct.SPI_Read&lt;BR /&gt;pcf2123_fct.SPI_Write&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="color: #000000; font-size: 13px;"&gt;&lt;/P&gt;&lt;P style="color: #000000; font-size: 13px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;uint8_t (*SPI_Read)(uint8_t *writeBuf, uint8_t *readBuf, uint32_t readSize); /*!&amp;lt; External SPI read function */&lt;BR /&gt;uint8_t (*SPI_Write)(uint8_t *writeBuf, uint32_t writeSize); /*!&amp;lt; External SPI read function */&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="color: #000000; font-size: 13px;"&gt;&lt;/P&gt;&lt;P style="color: #000000; font-size: 13px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Could you please point out SDK functionality here ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="color: #000000; font-size: 13px;"&gt;&lt;/P&gt;&lt;P style="color: #000000; font-size: 13px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Thank you!&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="color: #000000; font-size: 13px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Stanislav&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Apr 2019 08:59:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Rapid-IoT/SDK-issue-with-SPI-for-RTC-access/m-p/898078#M550</guid>
      <dc:creator>cerny</dc:creator>
      <dc:date>2019-04-17T08:59:22Z</dc:date>
    </item>
    <item>
      <title>Re: SDK issue with SPI for RTC access ?</title>
      <link>https://community.nxp.com/t5/Rapid-IoT/SDK-issue-with-SPI-for-RTC-access/m-p/898079#M551</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a bit long one - It is true that PCF drivers in SDK are not self sufficient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RTC is used in Rapid IoT OOB application: When phone connects to kit, time is updated and then RTC is used to keep time up to date.&lt;/P&gt;&lt;P&gt;I advise you take a look on how it is being implemented on OOB example and adapt to your needs.&lt;/P&gt;&lt;P&gt;&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/61847i80A1E01DCD44465E/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;You shall find all API in datetime_mk64f.c as well as links to the other drivers you will need (spi.c, spi_mk64f.c...)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Apr 2019 07:31:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Rapid-IoT/SDK-issue-with-SPI-for-RTC-access/m-p/898079#M551</guid>
      <dc:creator>Eric_Ma</dc:creator>
      <dc:date>2019-04-18T07:31:57Z</dc:date>
    </item>
    <item>
      <title>Re: SDK issue with SPI for RTC access ?</title>
      <link>https://community.nxp.com/t5/Rapid-IoT/SDK-issue-with-SPI-for-RTC-access/m-p/898080#M552</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eric,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;highly appreciate your support!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you, we already solved the SDK issue by utilization and separation of Athmosphere code as mentioned above and our RTC is now working.&lt;/P&gt;&lt;P&gt;Just in another thread provided some hints in order to prevent other users to seek as well, despite to little bit missing element for pcf in Athmosphere and gap in SDK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Again thank you!&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Stanislav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Apr 2019 07:42:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Rapid-IoT/SDK-issue-with-SPI-for-RTC-access/m-p/898080#M552</guid>
      <dc:creator>cerny</dc:creator>
      <dc:date>2019-04-18T07:42:11Z</dc:date>
    </item>
  </channel>
</rss>

