<?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>Device crashes during advertising for custom boards</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/107507/device-crashes-during-advertising-for-custom-boards</link><description>Hello, 
 I&amp;#39;m getting crashes instantly when device attempts to advertise. The same code running on NRF52 DK has no problems. 
 Here&amp;#39;s the crash log: 
 
 [00:00:01.105,407] &amp;lt;inf&amp;gt; sdc_hci_driver: SoftDevice Controller build revision: 58 5d 8b 31 54 67 00</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 23 Jan 2024 05:33:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/107507/device-crashes-during-advertising-for-custom-boards" /><item><title>RE: Device crashes during advertising for custom boards</title><link>https://devzone.nordicsemi.com/thread/465472?ContentTypeID=1</link><pubDate>Tue, 23 Jan 2024 05:33:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2bcf03c3-1b33-4d25-b4e3-aa85d5547d77</guid><dc:creator>Joe F.</dc:creator><description>&lt;p&gt;solved, first issue due to xc2 shorted to 3v0, second issue due to bad ble configs. Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device crashes during advertising for custom boards</title><link>https://devzone.nordicsemi.com/thread/464986?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2024 09:54:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e24fef7-f3c7-4081-aa52-325364b0f198</guid><dc:creator>Joe F.</dc:creator><description>&lt;p&gt;I&amp;#39;m pretty new with zephyr and nrf52, could it be possible that the chip&amp;#39;s missing some stack that I can maybe flash on?&lt;/p&gt;
&lt;p&gt;EDIT: I guess I would first like to know what these errors mean, like if it points to any areas of the hardware that is an issue, like maybe unpowered bus or modem?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device crashes during advertising for custom boards</title><link>https://devzone.nordicsemi.com/thread/464979?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2024 09:46:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d252e014-fdd9-43ef-a4ea-e2d060052873</guid><dc:creator>Joe F.</dc:creator><description>&lt;p&gt;got another error message, it does appear there is a hardware issue, just not sure whether it&amp;#39;s specific to the NRF52832 or an assembly issue:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1705657532419v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;*** Booting Zephyr OS build v2.6.0-rc1-ncs1&amp;nbsp; ***&lt;br /&gt;Created adv: 0x20002a84&lt;br /&gt;Bluetooth initialized&lt;br /&gt;&lt;br /&gt;[00:00:03.171,905] &amp;lt;err&amp;gt; os: ***** USAGE FAULT *****&lt;br /&gt;[00:00:03.171,905] &amp;lt;err&amp;gt; os:&amp;nbsp;&amp;nbsp; Unaligned memory access&lt;br /&gt;[00:00:03.171,936] &amp;lt;err&amp;gt; os: r0/a1:&amp;nbsp; 0x0001494d&amp;nbsp; r1/a2:&amp;nbsp; 0x00000020&amp;nbsp; r2/a3:&amp;nbsp; 0x00000001&lt;br /&gt;[00:00:03.171,936] &amp;lt;err&amp;gt; os: r3/a4:&amp;nbsp; 0x00000001 r12/ip:&amp;nbsp; 0x20001af8 r14/lr:&amp;nbsp; 0x00019dd7&lt;br /&gt;[00:00:03.171,936] &amp;lt;err&amp;gt; os:&amp;nbsp; xpsr:&amp;nbsp; 0x21000200&lt;br /&gt;[00:00:03.171,936] &amp;lt;err&amp;gt; os: Faulting instruction address (r15/pc): 0x0002259c&lt;br /&gt;[00:00:03.171,936] &amp;lt;err&amp;gt; os: &amp;gt;&amp;gt;&amp;gt; ZEPHYR FATAL ERROR 0: CPU exception on CPU 0&lt;br /&gt;[00:00:03.171,936] &amp;lt;err&amp;gt; os: Current thread: 0x200027a8 (unknown)&lt;br /&gt;[00:00:04.150,207] &amp;lt;err&amp;gt; fatal_error: Resetting system&lt;br /&gt;*** Booting Zephyr OS build v2.6.0-rc1-ncs1&amp;nbsp; ***&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device crashes during advertising for custom boards</title><link>https://devzone.nordicsemi.com/thread/464940?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2024 04:57:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50c47ae4-cab6-4b40-8634-a94e8d41ec94</guid><dc:creator>Joe F.</dc:creator><description>&lt;p&gt;Yes this project is on v1.6.0&lt;img style="max-height:71px;max-width:255px;" height="71" src="https://devzone.nordicsemi.com/resized-image/__size/510x142/__key/communityserver-discussions-components-files/4/pastedimage1705637100275v1.png" width="255" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We haven&amp;#39;t done any radio testing, but I have tested with one of the examples, peripheral_uart, and got the same issue:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;*** Booting Zephyr OS build v2.6.0-rc1-ncs1&amp;nbsp; ***&lt;br /&gt;[00:00:00.004,669] &amp;lt;inf&amp;gt; peripheral_uart: Bluetooth zz&lt;br /&gt;Starting Nordic UART serv[00:00:05.004,974] &amp;lt;dbg&amp;gt; fs_nvs.nvs_recover_last_ate: Recovering last ate from sector 0&lt;br /&gt;[00:00:05.010,986] &amp;lt;inf&amp;gt; fs_nvs: 6 Sectors of 4096 bytes&lt;br /&gt;[00:00:05.010,986] &amp;lt;inf&amp;gt; fs_nvs: alloc wra: 0, fd8&lt;br /&gt;[00:00:05.010,986] &amp;lt;inf&amp;gt; fs_nvs: data wra: 0, 1c&lt;br /&gt;[00:00:05.011,138] &amp;lt;inf&amp;gt; sdc_hci_driver: SoftDevice Controller build revision:&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 58 5d 8b 31 54 67 00 e9&amp;nbsp; b8 4a a7 df a9 9c e4 1c |X].1Tg.. .J......&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; b3 0b ce 74&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |...t&lt;br /&gt;[00:00:05.015,441] &amp;lt;inf&amp;gt; bt_hci_core: No ID address. App must call settings_load()&lt;br /&gt;[00:00:05.015,472] &amp;lt;inf&amp;gt; peripheral_uart: Bluetooth initialized&lt;br /&gt;[00:00:05.022,064] &amp;lt;err&amp;gt; mpsl_init: MPSL ASSERT: 112, 2177&lt;br /&gt;[00:00:05.022,064] &amp;lt;err&amp;gt; os: ***** HARD FAULT *****&lt;br /&gt;[00:00:05.022,094] &amp;lt;err&amp;gt; os:&amp;nbsp;&amp;nbsp; Fault escalation (see below)&lt;br /&gt;[00:00:05.022,125] &amp;lt;err&amp;gt; os: r0/a1:&amp;nbsp; 0x00000003&amp;nbsp; r1/a2:&amp;nbsp; 0x00000000&amp;nbsp; r2/a3:&amp;nbsp; 0x200015c8&lt;br /&gt;[00:00:05.022,125] &amp;lt;err&amp;gt; os: r3/a4:&amp;nbsp; 0x00000008 r12/ip:&amp;nbsp; 0x20000dd4 r14/lr:&amp;nbsp; 0x0001191b&lt;br /&gt;[00:00:05.022,125] &amp;lt;err&amp;gt; os:&amp;nbsp; xpsr:&amp;nbsp; 0x41000018&lt;br /&gt;[00:00:05.022,125] &amp;lt;err&amp;gt; os: Faulting instruction address (r15/pc): 0x0001ee0e&lt;br /&gt;[00:00:05.022,155] &amp;lt;err&amp;gt; os: &amp;gt;&amp;gt;&amp;gt; ZEPHYR FATAL ERROR 0: CPU exception on CPU 0&lt;br /&gt;[00:00:05.022,155] &amp;lt;err&amp;gt; os: Fault during interrupt handling&lt;br /&gt;&lt;br /&gt;[00:00:05.022,155] &amp;lt;err&amp;gt; os: Current thread: 0x20001ea8 (unknown)&lt;br /&gt;[00:00:06.495,788] &amp;lt;err&amp;gt; fatal_error: Resetting system&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;How would I run the radio test and what should I look for?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device crashes during advertising for custom boards</title><link>https://devzone.nordicsemi.com/thread/464755?ContentTypeID=1</link><pubDate>Thu, 18 Jan 2024 10:20:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:db04fe62-c225-4a1d-912e-9b76b73a6099</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;From the path it may seem as you are using a very old nRF Connect SDK (latest is v2.5.1), can you just confirm you are indeed using v1.6.0 before we look into this? Have you run any radio test and similar just to confirm that the board is working?&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>