<?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>nRF9160 DK hardware exception</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/49058/nrf9160-dk-hardware-exception</link><description>Dear Nordic Support, 
 When I got my nRF9160 DK, I ran the getting started successfully then I followed the instruction from the 2 below links: 
 https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/getting-started</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 27 Aug 2019 13:19:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/49058/nrf9160-dk-hardware-exception" /><item><title>RE: nRF9160 DK hardware exception</title><link>https://devzone.nordicsemi.com/thread/206404?ContentTypeID=1</link><pubDate>Tue, 27 Aug 2019 13:19:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fabfc7d7-2f88-4cd3-9170-b6d5fdecdf80</guid><dc:creator>Duy</dc:creator><description>&lt;p&gt;Update: I loaded the&amp;nbsp;&lt;strong&gt;spm&lt;/strong&gt; with&amp;nbsp;&lt;strong&gt;nrf9160_pca10090&lt;/strong&gt; then I load the&amp;nbsp;&lt;strong&gt;zenphyr&lt;/strong&gt;&lt;strong&gt;.hex&lt;/strong&gt; file of my application using the&amp;nbsp;&lt;strong&gt;nrf9160_pca10090&lt;/strong&gt;&lt;strong&gt;ns&lt;/strong&gt;. This works fine for all tags.&lt;/p&gt;
&lt;p&gt;Hello &lt;a href="https://devzone.nordicsemi.com/members/sigurdon"&gt;Sigurd&lt;/a&gt;, I think this should be updated in the getting started guide. I had to spent hours to realize this &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 DK hardware exception</title><link>https://devzone.nordicsemi.com/thread/195422?ContentTypeID=1</link><pubDate>Fri, 28 Jun 2019 15:56:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:851f834a-ced1-4e19-9d32-6298b0158f98</guid><dc:creator>Duy</dc:creator><description>&lt;p&gt;Hello Vish. I got it work with&amp;nbsp;&lt;strong&gt;v0.4.0&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 DK hardware exception</title><link>https://devzone.nordicsemi.com/thread/195343?ContentTypeID=1</link><pubDate>Fri, 28 Jun 2019 10:52:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:270c2655-3f8e-4fe9-9294-f3a12b59ebb2</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;If you were not able to flash the modem fw, then try to flash the at_client sample to the nRF9160,&amp;nbsp;and then try to flash the modem fw again. And as Vish mentioned, please also use v0.4.0 tag.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 DK hardware exception</title><link>https://devzone.nordicsemi.com/thread/195220?ContentTypeID=1</link><pubDate>Thu, 27 Jun 2019 17:53:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a40f0572-02c4-43aa-8cff-3e5437b3fd18</guid><dc:creator>Vish</dc:creator><description>&lt;p&gt;I suppose you are using the latest on master. Try v0.4.0 . Asset tracker works well on that. &lt;a href="https://devzone.nordicsemi.com/members/sigurdon"&gt;Sigurd&lt;/a&gt; It might be worth mentioning the specific tag version this on Getting Started Assistant in nRF Connect. Its mentioned that the master might be unstable , but people always tend to use the latest..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 DK hardware exception</title><link>https://devzone.nordicsemi.com/thread/195215?ContentTypeID=1</link><pubDate>Thu, 27 Jun 2019 17:18:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f289ddc-8141-418e-b090-c8ea092647de</guid><dc:creator>Duy</dc:creator><description>&lt;p&gt;This person also has the same issue:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/49041/nrf9160-faulting-instruction-address-0x3648-fatal-fault-in-isr-spinning/195207"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/49041/nrf9160-faulting-instruction-address-0x3648-fatal-fault-in-isr-spinning/195207&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 DK hardware exception</title><link>https://devzone.nordicsemi.com/thread/195198?ContentTypeID=1</link><pubDate>Thu, 27 Jun 2019 14:45:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:81995dbf-5f6d-4bae-9979-98fc72e50bae</guid><dc:creator>Duy</dc:creator><description>&lt;p&gt;Thank you for your reply.&lt;/p&gt;
&lt;p&gt;Yes, I did it after I uploaded the firmware but same error.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;And when I Erased All the nRF9160, I couldn&amp;#39;t update the latest modem FW version.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 DK hardware exception</title><link>https://devzone.nordicsemi.com/thread/195185?ContentTypeID=1</link><pubDate>Thu, 27 Jun 2019 14:00:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:841d4134-1f33-4780-810a-62ec529119b2</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Try to update to the latest modem fw version, found here:&amp;nbsp;&lt;a href="https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs"&gt;https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>