<?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>ble softdevice enable fail with bootloader</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127221/ble-softdevice-enable-fail-with-bootloader</link><description>I&amp;#39;m developing BLE code using the s140 + Nordic 52833 with nrf5 SDK. My flash contains the hex files for s140, the bootloader, and the app. I&amp;#39;ve encountered a strange issue: When I only flash s140 + the app, the softd evice stack initializes successfully</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 02 Mar 2026 09:26:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127221/ble-softdevice-enable-fail-with-bootloader" /><item><title>RE: ble softdevice enable fail with bootloader</title><link>https://devzone.nordicsemi.com/thread/562288?ContentTypeID=1</link><pubDate>Mon, 02 Mar 2026 09:26:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:10ee972d-2933-4e2c-8360-0660b555fd0d</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;You can work around this by&amp;nbsp;calling nrf_dfu_mbr_init_sd() at the start of main() in your application.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ble softdevice enable fail with bootloader</title><link>https://devzone.nordicsemi.com/thread/562286?ContentTypeID=1</link><pubDate>Mon, 02 Mar 2026 09:03:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:faffd33d-e441-4eb0-a57d-f7c5c165f4ff</guid><dc:creator>Liny</dc:creator><description>&lt;p&gt;Thank you for the assistance. I&amp;#39;ve verified that what you said is correct, but apart from that, are there any other solutions? Since my boot program is already burned into the chip and cannot be updated, I&amp;#39;m unable to fix this bug in the bootloader.&lt;br /&gt;&lt;span&gt;Best regards.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ble softdevice enable fail with bootloader</title><link>https://devzone.nordicsemi.com/thread/562275?ContentTypeID=1</link><pubDate>Mon, 02 Mar 2026 06:51:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c1b61af8-2837-4f09-bfee-57273f9ec04b</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;The issue is that the&amp;nbsp;SVCall_IRQn interrupt triggered by the Softdevice enable API doesn&amp;#39;t reach the Softdevice, but instead gets forwarded directly to the application.&amp;nbsp;This can happen if you have the&amp;nbsp;nrf_bootloader_app_start() jump directly to the main app instead of address 0x1000 where the softdevice starts.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please change&amp;nbsp;IMAGE_START_ADDR to &amp;quot;0x1000&amp;quot; and try again.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>