<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Broken bit in RAM region</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22403/broken-bit-in-ram-region</link><description>Hi, Nordic!
We have two PDK-NRF52840 and custom boards with NRF52840 chips.
2 from 5 chips have a broken bit in RAM. This is different places.
For example:
 
 Is this problem only for preview chip? Will You make manufactoring tests for serial chips</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 30 May 2017 12:16:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22403/broken-bit-in-ram-region" /><item><title>RE: Broken bit in RAM region</title><link>https://devzone.nordicsemi.com/thread/88120?ContentTypeID=1</link><pubDate>Tue, 30 May 2017 12:16:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:595440d8-4758-4d86-aaf5-0fad06669050</guid><dc:creator>Vlad Mokhnachov</dc:creator><description>&lt;p&gt;What means this test? I erase all memory(RAM and Flash). After I read all memory bytes.(I made this test not once)
First chip have a broken byte at  0x200137EB
Second chip have a broken byte at 0x2003D801&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broken bit in RAM region</title><link>https://devzone.nordicsemi.com/thread/88119?ContentTypeID=1</link><pubDate>Tue, 30 May 2017 11:54:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f93fb016-7c96-4d99-a31f-ebafe17213a1</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Also could you try to test with just &amp;quot;while(1);&amp;quot; in main()  ? Seems that the RAM address is inside the stack area?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broken bit in RAM region</title><link>https://devzone.nordicsemi.com/thread/88121?ContentTypeID=1</link><pubDate>Tue, 30 May 2017 11:47:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:abe1c6ad-c3c1-47df-b031-539e213b7442</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Could you please create a support case on our &lt;a href="https://www.nordicsemi.com/eng/nordic/mypage"&gt;MyPage&lt;/a&gt; ? We need more information about the chips and to get the chips here (you will have a replacement). Please provide  link to this thread. Also please take a close-up photo of the chips.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broken bit in RAM region</title><link>https://devzone.nordicsemi.com/thread/88118?ContentTypeID=1</link><pubDate>Tue, 30 May 2017 11:34:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4bd6a34a-7144-4ebc-bf05-8ebaac44b155</guid><dc:creator>Vlad Mokhnachov</dc:creator><description>&lt;p&gt;Problem with variable in debug mode was a reason for experiments with J-Link Commander.
It&amp;#39;s happen on your PDK board and on our board. New chip on the same board works good.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broken bit in RAM region</title><link>https://devzone.nordicsemi.com/thread/88117?ContentTypeID=1</link><pubDate>Tue, 30 May 2017 10:39:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89e4038a-12fa-4e76-857a-7237f02f992a</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Vlad :  The preview chips should be tested. It pretty strange that you see the error on 2 out of 5. Where are the 2 defected chip mounted ? It&amp;#39;s on our PDK or on your board ?&lt;/p&gt;
&lt;p&gt;Could you try to run the chip in debug mode, add a break point and try to change the RAM value at that address? Or create a small code to directly change RAM value at that address ? Just to verify it&amp;#39;s not the issue with J-Link Commander.&lt;/p&gt;
&lt;p&gt;If you still see the issue, I would suggest you to create a case on our support portal (MyPage), we would need to get hold of the chips for further investigation.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>