<?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>softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/17205/softdevice-enable-in-application-crash-if-it-has-already-initialized-in-bootloader</link><description>Hi, 
 On a system reset, we want a mechanism to stay in bootloader for a short period before jumping in application. This way, if something is wrong in application that prevent communication, we still have a way to fallback in the bootloader. Our system</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 21 Nov 2016 14:16:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/17205/softdevice-enable-in-application-crash-if-it-has-already-initialized-in-bootloader" /><item><title>RE: softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/thread/66100?ContentTypeID=1</link><pubDate>Mon, 21 Nov 2016 14:16:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89cde0fa-9154-4242-9eaa-2fb946bfc388</guid><dc:creator>Marc</dc:creator><description>&lt;p&gt;Yes but I use my workaround as described in my last paragraph.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/thread/66099?ContentTypeID=1</link><pubDate>Mon, 21 Nov 2016 08:16:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2a999422-17eb-4d95-a0cf-c1187c4a3f8a</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@mamarceau: Are you still experiencing this issue?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/thread/66098?ContentTypeID=1</link><pubDate>Thu, 20 Oct 2016 18:17:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6da54a4-194a-4092-b477-7180e93f76c0</guid><dc:creator>Marc</dc:creator><description>&lt;p&gt;I&amp;#39;ll see If I could create a stripped project bootloader/app that reproduce this. As for the base addresses, it is done in nrf_ble_dfu.c:765     err_code = sd_softdevice_vector_table_base_set(BOOTLOADER_START_ADDR);
and nrf_bootloader_app_start.c:172 err_code = sd_softdevice_vector_table_base_set(start_addr);&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/thread/66097?ContentTypeID=1</link><pubDate>Thu, 20 Oct 2016 17:46:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:34c2d46c-783a-4c80-9dc5-91ef5acb60ae</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;did you set the vectar table in MBR and forgot to change it back to softdevice base address? I am just trying to think loud all the options that could cause this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/thread/66096?ContentTypeID=1</link><pubDate>Thu, 20 Oct 2016 17:42:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e646b1b6-6dcd-478a-a275-efa2e9008a6d</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;can you step and see if the SVC instruction causes the hardfault or does this happen inside the softdevice`?
Does your application_fault handler gets called?
I think we need to investigate it more, can you help me reproduce it at my desk by uploading project or some files, if you cannot upload here then please open a ticket in mypage in support and i will take it over.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/thread/66095?ContentTypeID=1</link><pubDate>Thu, 20 Oct 2016 16:05:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5d4557b6-7481-4057-82be-85aa12018c2b</guid><dc:creator>Marc</dc:creator><description>&lt;p&gt;Just tried to add nrf_delay_ms(20) (also tried 100ms) between the sd disable and application jump and still doesn&amp;#39;t work.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/thread/66094?ContentTypeID=1</link><pubDate>Thu, 20 Oct 2016 15:57:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2c5ddca-050d-46a3-b47f-3af4585400fd</guid><dc:creator>Marc</dc:creator><description>&lt;p&gt;Yes, 100% reproductible. If I enter in bootloader and directly jump to application, it works. If I initialize sd and ble and then I jump in app, regardless if I disable sd before jump, it fails. I use the example code, I never switch to RC clock. Let me try the 20ms delay.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/thread/66093?ContentTypeID=1</link><pubDate>Thu, 20 Oct 2016 15:42:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:216b54f9-9335-4fcb-95f8-fe2cab9371b5</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;The title for this question says that app crashes on softdevice_enable if it is already enabled. But your code shows that it is disabled in bootloader before it jumps to app.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softdevice enable in Application crash if it has already initialized in bootloader</title><link>https://devzone.nordicsemi.com/thread/66092?ContentTypeID=1</link><pubDate>Thu, 20 Oct 2016 15:39:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7c34f9d-69ec-4060-8b19-f571c325ee80</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;is this 100% reproduceable? are you using internal RC for LFCLK? what happens if you add like 20ms delay after softdevice_disable and then jump to the application?  I am just wondering if there were still any calibration on going when you do softdevice_disable, because calibration is done asynchronously within softdevice and notified with power interrupts internally.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>