<?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 How to get the actual value from MPC574xG STM counter ? in MPC5xxx</title>
    <link>https://community.nxp.com/t5/MPC5xxx/How-to-get-the-actual-value-from-MPC574xG-STM-counter/m-p/768520#M11020</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear NXP Support,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we're using the STM module of the MPC574xG as the driver for an high resolution counter. The resolution of this counter should be one timer tick. Therefore we need to get the hardware counter value as accurate as possible.&lt;/P&gt;&lt;P&gt;In MPC5748G Reference Manual, Rev. 5, 12/2016 you describe the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOTE&lt;BR /&gt;Due to two clock sources and different clock domains, Values&lt;BR /&gt;in this field can lag behind the internal counter value for up to&lt;BR /&gt;six system plus eight counter clock cycles. Therefore, the value&lt;BR /&gt;read from this field immediately after may be lower than the&lt;BR /&gt;actual value of the internal counter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For us it is not quite clear what this means and how we can get the actual HW counter value.&lt;/P&gt;&lt;P&gt;E.g. is there a worst case scenario (e.g. add eight ticks to the read value...)?&lt;/P&gt;&lt;P&gt;The solution has to be independent from frequency configuration, because our customer can configure the core and peripherals according to his needs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance and best regards&lt;/P&gt;&lt;P&gt;Martin Schultheiß&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 Jan 2018 20:09:05 GMT</pubDate>
    <dc:creator>martinschulthei</dc:creator>
    <dc:date>2018-01-29T20:09:05Z</dc:date>
    <item>
      <title>How to get the actual value from MPC574xG STM counter ?</title>
      <link>https://community.nxp.com/t5/MPC5xxx/How-to-get-the-actual-value-from-MPC574xG-STM-counter/m-p/768520#M11020</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear NXP Support,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we're using the STM module of the MPC574xG as the driver for an high resolution counter. The resolution of this counter should be one timer tick. Therefore we need to get the hardware counter value as accurate as possible.&lt;/P&gt;&lt;P&gt;In MPC5748G Reference Manual, Rev. 5, 12/2016 you describe the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOTE&lt;BR /&gt;Due to two clock sources and different clock domains, Values&lt;BR /&gt;in this field can lag behind the internal counter value for up to&lt;BR /&gt;six system plus eight counter clock cycles. Therefore, the value&lt;BR /&gt;read from this field immediately after may be lower than the&lt;BR /&gt;actual value of the internal counter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For us it is not quite clear what this means and how we can get the actual HW counter value.&lt;/P&gt;&lt;P&gt;E.g. is there a worst case scenario (e.g. add eight ticks to the read value...)?&lt;/P&gt;&lt;P&gt;The solution has to be independent from frequency configuration, because our customer can configure the core and peripherals according to his needs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance and best regards&lt;/P&gt;&lt;P&gt;Martin Schultheiß&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Jan 2018 20:09:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/How-to-get-the-actual-value-from-MPC574xG-STM-counter/m-p/768520#M11020</guid>
      <dc:creator>martinschulthei</dc:creator>
      <dc:date>2018-01-29T20:09:05Z</dc:date>
    </item>
  </channel>
</rss>

