<?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: 56F84789 RAM problem in Digital Signal Controllers</title>
    <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56F84789-RAM-problem/m-p/435961#M564</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;It could be a silicon fault.&lt;/P&gt;&lt;P&gt;I have not heard of this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please, what are the data codes where the issue exists?&lt;/P&gt;&lt;P&gt;What percent of the units of this data code have the issue?&lt;/P&gt;&lt;P&gt;How many units have this issue?&lt;/P&gt;&lt;P&gt;What stage is the project for which these units are stocked in?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You many want to contact your local Freescale FAE for support on this issue as a next step.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Oct 2015 20:24:57 GMT</pubDate>
    <dc:creator>johnlwinters</dc:creator>
    <dc:date>2015-10-05T20:24:57Z</dc:date>
    <item>
      <title>56F84789 RAM problem</title>
      <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56F84789-RAM-problem/m-p/435960#M563</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have encountered a strange issue on certain 56F84789 chips. The last 4KW of RAM (0x3000-0x3FFF) is unusable. On read, each word is 0xFFFF. Attempting to write a word in that range has no effect.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We only find this problem with two specific date codes so far, all other date codes appear normal.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some questions:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Is this a silicon fault?&lt;/P&gt;&lt;P&gt;2) Are there any configuration bits that could stop part of RAM not working as expected?&lt;/P&gt;&lt;P&gt;3) Has anyone seen this type of problem?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Oct 2015 20:07:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Digital-Signal-Controllers/56F84789-RAM-problem/m-p/435960#M563</guid>
      <dc:creator>bobc</dc:creator>
      <dc:date>2015-10-05T20:07:48Z</dc:date>
    </item>
    <item>
      <title>Re: 56F84789 RAM problem</title>
      <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56F84789-RAM-problem/m-p/435961#M564</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;It could be a silicon fault.&lt;/P&gt;&lt;P&gt;I have not heard of this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please, what are the data codes where the issue exists?&lt;/P&gt;&lt;P&gt;What percent of the units of this data code have the issue?&lt;/P&gt;&lt;P&gt;How many units have this issue?&lt;/P&gt;&lt;P&gt;What stage is the project for which these units are stocked in?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You many want to contact your local Freescale FAE for support on this issue as a next step.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Oct 2015 20:24:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Digital-Signal-Controllers/56F84789-RAM-problem/m-p/435961#M564</guid>
      <dc:creator>johnlwinters</dc:creator>
      <dc:date>2015-10-05T20:24:57Z</dc:date>
    </item>
    <item>
      <title>Re: 56F84789 RAM problem</title>
      <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56F84789-RAM-problem/m-p/435962#M565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are at pre-production stage so there are a limited number of PCBs built. I've been looking through every board and it appears that the following two date codes exhibit the problem :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;QQAG1425H&lt;/P&gt;&lt;P&gt;QQAG1425J&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;with 100% rate, but there are only 6 chips with these date codes. All other date codes appear to be OK. We have several boards build into prototypes, I haven't been able to check those.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My colleague has raised an SR and contacted our local FAE, I will leave it with them and update if we get any news.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Oct 2015 09:06:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Digital-Signal-Controllers/56F84789-RAM-problem/m-p/435962#M565</guid>
      <dc:creator>bobc</dc:creator>
      <dc:date>2015-10-06T09:06:03Z</dc:date>
    </item>
  </channel>
</rss>

