<?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>i.MX Processors中的主题 Re: SNVS RTC fault on imx6q</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222848#M15098</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It seems your chips were not programmed with right fuse bit. Can you type "imxotp read 4" and let me know the value in u-boot ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 25 Jun 2013 01:58:31 GMT</pubDate>
    <dc:creator>RobinGong</dc:creator>
    <dc:date>2013-06-25T01:58:31Z</dc:date>
    <item>
      <title>SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222830#M15080</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;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;After changing another batch of imx6q chip, we found android system cannot boot done, it always hang at:&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;......&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;I/Zygote&amp;nbsp; ( 2151): ...preloaded 379 resources in 1771ms.&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;I/Zygote&amp;nbsp; ( 2151): ...preloaded 31 resources in 9ms.&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;D/dalvikvm( 2151): GC_EXPLICIT freed 29K, 1% free 6467K/6531K, paused 2ms+2ms&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;D/dalvikvm( 2151): GC_EXPLICIT freed 10K, 2% free 6457K/6531K, paused 1ms+1ms&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;D/dalvikvm( 2151): GC_EXPLICIT freed &amp;lt;1K, 2% free 6457K/6531K, paused 2ms+2ms&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;I/dalvikvm( 2151): System server process 2225 has been created&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;I/Zygote&amp;nbsp; ( 2151): Accepting command socket connections&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;D/SystemClock( 2225): Setting time of day to sec=86400&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;STRONG&gt;W/SystemServer( 2225): System clock is before 1970; setting to 1970.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;the batch number with this issue is:&lt;/P&gt;&lt;P&gt;MCIMX6Q6AVT10AC SBCF1315 KOREA YOCFSBU.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the following chip has no problem:&lt;/P&gt;&lt;P&gt;MCIMX6Q6AVT10AC SBAP1250 KOREA XXAPSBV.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Update] We used RTC stub instead of SNVS for test, and found system can boot up, but run very slowly. It is almost certainly SNVS is going wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anybody have any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jun 2013 06:30:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222830#M15080</guid>
      <dc:creator>lqw39</dc:creator>
      <dc:date>2013-06-17T06:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222831#M15081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Mr. Liu,&lt;/P&gt;&lt;P&gt;Based on above info which you had provided.&lt;/P&gt;&lt;P&gt;We can't get some conclusion.&lt;/P&gt;&lt;P&gt;Because the different chip batch will not bring any dfiierent.&lt;/P&gt;&lt;P&gt;But I have below suggestions fro you.&lt;/P&gt;&lt;P&gt;1. Please check your SW version, is it latest one and added all patched?&lt;/P&gt;&lt;P&gt;2. Please check power supply status and sequence.(VDDSNVS_IN should power up first.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hpoe above info can help you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jun 2013 08:00:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222831#M15081</guid>
      <dc:creator>LinWang</dc:creator>
      <dc:date>2013-06-21T08:00:05Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222832#M15082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have applied all patches listed on website, and use default power sequence of PFUZE100 (same with reference design, official BSP) .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW: system does not crash, just halt, and "android" animation still continues&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As I know, some batches of i.MX51 chip do not support security RTC module (or shielded?), so customers have to use RTC in PMIC (MC13892); unfortunately, we encountered this situation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jun 2013 08:29:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222832#M15082</guid>
      <dc:creator>lqw39</dc:creator>
      <dc:date>2013-06-21T08:29:32Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222833#M15083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Mr. Liu,&lt;/P&gt;&lt;P&gt;Can you show me your schematic?&lt;/P&gt;&lt;P&gt;BTW, I can't understand your below descriptions.&lt;/P&gt;&lt;P&gt;"[Update] We used RTC stub instead of SNVS for test" and "system does not crash, just halt, and "android" animation still continues"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All i.Mx6 chip with SRTC module, you can find related info in Datasheet.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jun 2013 09:44:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222833#M15083</guid>
      <dc:creator>LinWang</dc:creator>
      <dc:date>2013-06-21T09:44:25Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222834#M15084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We loaded a simulated RTC driver instead of SNVS RTC driver in kernel, and found system can run normally.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW: i.MX515 datasheet says SRTC is supported, but some or all of them shipped into China do not support SRTC, we have confirmed this issue with FAE of &lt;A href="http://www.wtmec.com/SC/index.htm" style="color: #017bba; text-decoration: underline; font-family: arial, sans-serif; font-size: 12px; background-color: #eeeeee;"&gt;WT Microelectronics Co. Ltd&lt;/A&gt;, which is one of the Freescale Distributor.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jun 2013 14:24:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222834#M15084</guid>
      <dc:creator>lqw39</dc:creator>
      <dc:date>2013-06-21T14:24:38Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222835#M15085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Mr. Liu,&lt;/P&gt;&lt;P&gt;Do you mean no issue after using your simulated RTC driver now?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i.Mx6 maybe different i.Mx515, Please confirm i.Mx6 status again.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Jun 2013 09:16:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222835#M15085</guid>
      <dc:creator>LinWang</dc:creator>
      <dc:date>2013-06-22T09:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222836#M15086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, android system works well after using simulated RTC driver; but media scanning becomes slow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We'll check other i.MX6 status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 01:54:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222836#M15086</guid>
      <dc:creator>lqw39</dc:creator>
      <dc:date>2013-06-24T01:54:21Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222837#M15087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;I believe media scaning only related with PLL or PFD clock source, please check if your simulated RTC driver modified related clock source!&lt;/P&gt;&lt;P&gt;Hope you can solve this issue quickly!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 02:15:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222837#M15087</guid>
      <dc:creator>LinWang</dc:creator>
      <dc:date>2013-06-24T02:15:42Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222838#M15088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Qinggwei, please click Correct Answer/Helpful Answer, if your question has been answered.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Yixing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 08:12:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222838#M15088</guid>
      <dc:creator>YixingKong</dc:creator>
      <dc:date>2013-06-24T08:12:24Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222839#M15089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. We have confirmed that clock source is right, and the simulated RTC does not change clock settings.&lt;/P&gt;&lt;P&gt;2. We cannot use simulated RTC in product since time cannot be kept after system power down; we MUST make SNVS RTC working.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some batches of imx6q chip do not support SRTC? &lt;/P&gt;&lt;P&gt;Shall we add new RTC chip into our hardware design?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 08:22:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222839#M15089</guid>
      <dc:creator>lqw39</dc:creator>
      <dc:date>2013-06-24T08:22:30Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222840#M15090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I know, RTC function is availabe in all i.Mx6 batches.&lt;/P&gt;&lt;P&gt;Please list your BSP version and pach list which you had added.&lt;/P&gt;&lt;P&gt;I will ask our SW engineer to help checking.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 08:29:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222840#M15090</guid>
      <dc:creator>LinWang</dc:creator>
      <dc:date>2013-06-24T08:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222841#M15091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have tried following BSP version:&lt;/P&gt;&lt;P&gt;1. R13.4&lt;/P&gt;&lt;P&gt;2. R13.41 + IMX6_R13.4.1.04_ANDROID_PATCH&lt;/P&gt;&lt;P&gt;3. JB-422_100&lt;/P&gt;&lt;P&gt;and every version have this issue on specific chip.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 08:42:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222841#M15091</guid>
      <dc:creator>lqw39</dc:creator>
      <dc:date>2013-06-24T08:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222842#M15092</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How many chip/board have this issue?&lt;/P&gt;&lt;P&gt;We need conifrm this isn't a single chip/board issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please share your schematic with me.&lt;/P&gt;&lt;P&gt;I like check it at same time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 08:47:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222842#M15092</guid>
      <dc:creator>LinWang</dc:creator>
      <dc:date>2013-06-24T08:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222843#M15093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All of the 10 pcs (with chip SN: &lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: #ffffff;"&gt;MCIMX6Q6AVT10AC SBCF1315 KOREA YOCFSBU&lt;/SPAN&gt;) have this issue.&lt;/P&gt;&lt;P&gt;And other boards (with chip SN: &lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: #ffffff;"&gt;MCIMX6Q6AVT10AC SBAP1250 KOREA XXAPSBV&lt;/SPAN&gt;) have no issue.&lt;/P&gt;&lt;P&gt;Two kinds of board have no difference except i.mx6q chip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We used the same design with SDP board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 09:00:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222843#M15093</guid>
      <dc:creator>lqw39</dc:creator>
      <dc:date>2013-06-24T09:00:53Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222844#M15094</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After checking with SW guy, our latest BSP is JB4.2.2_GA.&lt;/P&gt;&lt;P&gt;Please help to update to new version.&lt;/P&gt;&lt;P&gt;Your version is very old.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 09:19:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222844#M15094</guid>
      <dc:creator>LinWang</dc:creator>
      <dc:date>2013-06-24T09:19:55Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222845#M15095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am puzzled with your info!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have tried:&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;3. JB-422_100 (&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&amp;amp;nodeId=018rH3ZrDRB24A&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab" style="color: #017bba; text-decoration: underline; font-family: arial, sans-serif; font-size: 12px; background-color: #cccccc;"&gt;IMX6_JB422_100_ANDROID_SOURCE&lt;/A&gt;)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Which is the latest version in your website. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have the updated version which is not published?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know the link, thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2013 01:36:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222845#M15095</guid>
      <dc:creator>lqw39</dc:creator>
      <dc:date>2013-06-25T01:36:33Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222846#M15096</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please try latest BSP.&lt;/P&gt;&lt;P&gt;let me know the result.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2013 01:36:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222846#M15096</guid>
      <dc:creator>LinWang</dc:creator>
      <dc:date>2013-06-25T01:36:45Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222847#M15097</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I said above, we have tried the latest version we can get from website.&lt;/P&gt;&lt;P&gt;If you have newer version, please give me the link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2013 01:40:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222847#M15097</guid>
      <dc:creator>lqw39</dc:creator>
      <dc:date>2013-06-25T01:40:45Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222848#M15098</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It seems your chips were not programmed with right fuse bit. Can you type "imxotp read 4" and let me know the value in u-boot ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2013 01:58:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222848#M15098</guid>
      <dc:creator>RobinGong</dc:creator>
      <dc:date>2013-06-25T01:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: SNVS RTC fault on imx6q</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222849#M15099</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry, I miss your latest important info!&lt;/P&gt;&lt;P&gt;Suggestions:&lt;/P&gt;&lt;P&gt;1. Find a FSL domo board and mount issue chip "1315" on it an test.&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;2. Find local FSL support for help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would you please show your company's name and office location to us?&lt;/P&gt;&lt;P&gt;Thanks! &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2013 02:00:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SNVS-RTC-fault-on-imx6q/m-p/222849#M15099</guid>
      <dc:creator>LinWang</dc:creator>
      <dc:date>2013-06-25T02:00:36Z</dc:date>
    </item>
  </channel>
</rss>

