<?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 Firmware update using NRF Connect SDK alongside Zephyr RTOS on VS Code.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/96455/ble-firmware-update-using-nrf-connect-sdk-alongside-zephyr-rtos-on-vs-code</link><description>I am trying to implement a firmware update feature via BLE to my already existing application whereby nrf52840 is connecting to an android device via BLE and is sucsessfully sending and receiving data. 
 I was trying to follow this: https://developer</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Feb 2023 12:19:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/96455/ble-firmware-update-using-nrf-connect-sdk-alongside-zephyr-rtos-on-vs-code" /><item><title>RE: BLE Firmware update using NRF Connect SDK alongside Zephyr RTOS on VS Code.</title><link>https://devzone.nordicsemi.com/thread/408853?ContentTypeID=1</link><pubDate>Wed, 08 Feb 2023 12:19:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4d898c7a-dafe-4291-a12a-2dbc1ee8ab8b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi again,&lt;/p&gt;
&lt;p&gt;Could you give some more detail on how long it takes ? When you integrate MCUBoot , it will boot first and may do some verification but it shouldn&amp;#39;t take a significant time (few hundred ms).Have you checked the log to see at which step it spend it time. You should be able to see the MCUboot log.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you have done a DFU , then MCUboot will have to swap the image and the process may take time depends on the size of the image (can be 30 40 seconds)&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Have you tried to test with smp_svr to see if the example have the same problem ?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Firmware update using NRF Connect SDK alongside Zephyr RTOS on VS Code.</title><link>https://devzone.nordicsemi.com/thread/408846?ContentTypeID=1</link><pubDate>Wed, 08 Feb 2023 12:02:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3d4e32d7-85b9-40de-8972-95516fe9b74e</guid><dc:creator>Chris_1</dc:creator><description>&lt;p&gt;Many Thanks for your reply. I managed to get it working however, it is taking a very long time to start after system reset. Is there a way to fix this ?&lt;/p&gt;
&lt;p&gt;My current proj.conf file is as follows:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;#CONFIG_BT_DEBUG_LOG=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;#CONFIG_BT_MAX_CONN=1&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;#CONFIG_BT_L2CAP_TX_BUF_COUNT=5&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BT_PERIPHERAL&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BT_DEVICE_NAME&lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt;&amp;quot;My_DeviceBT_TEST_HJ840&amp;quot;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;#CONFIG_BT_DEVICE_APPEARANCE=962&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;CONFIG_HEAP_MEM_POOL_SIZE&lt;/span&gt;&lt;span&gt;=4096&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;#CONFIG_BT_CTLR_TX_PWR_MINUS_40=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;#CONFIG_DK_LIBRARY=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;# This example requires more workqueue stack&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE&lt;/span&gt;&lt;span&gt;=4096&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_PM_CPU_OPS&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL&lt;/span&gt;&lt;span&gt;=n&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_CLOCK_CONTROL_NRF_K32SRC_50PPM&lt;/span&gt;&lt;span&gt;=n&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;##CONFIG_TIMESLICING=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;#CONFIG_TIMESLICE_SIZE=50000&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;#CONFIG_TIMESLICE_PRIORITY=0&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;CONFIG_GPIO&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;CONFIG_I2C&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_I2C_NRFX&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_SPI&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;# Enable mcumgr.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MCUMGR&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;# Enable most core commands.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MCUMGR_CMD_IMG_MGMT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MCUMGR_CMD_OS_MGMT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;# Ensure an MCUboot-compatible binary is generated.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BOOTLOADER_MCUBOOT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;# Allow for large Bluetooth data packets.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BT_L2CAP_TX_MTU&lt;/span&gt;&lt;span&gt;=252&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BT_BUF_ACL_RX_SIZE&lt;/span&gt;&lt;span&gt;=256&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;# Enable the Bluetooth (unauthenticated) and shell mcumgr transports.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MCUMGR_SMP_BT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MCUMGR_SMP_BT_AUTHEN&lt;/span&gt;&lt;span&gt;=n&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Firmware update using NRF Connect SDK alongside Zephyr RTOS on VS Code.</title><link>https://devzone.nordicsemi.com/thread/408842?ContentTypeID=1</link><pubDate>Wed, 08 Feb 2023 11:56:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a682c283-62bd-44da-9969-e616ae3bf73b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Christopher,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please follow our guide &lt;a href="https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/ncs-dfu"&gt;here &lt;/a&gt;on how to integrate the SMP service in your application.&amp;nbsp;&lt;br /&gt;Basically you need to enable the CONFIG_s and then call&amp;nbsp;smp_bt_register() to register the service.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>