<?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>BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11853/bl600-nus-service-and-dfu-support</link><description>Hello, 
 I am using BL600A module and Nordic softdevice and SDK9.0. The system is having NUS service and TX and RX characteristic. Now I have a requirement for firmware upgrade OTA. 
 My question is, Can I use DFU and bootloader without affecting the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 19 Feb 2016 09:41:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11853/bl600-nus-service-and-dfu-support" /><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44913?ContentTypeID=1</link><pubDate>Fri, 19 Feb 2016 09:41:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc54fb07-b293-4e3f-a6db-e933ec2de7aa</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;The issue is fixed currently. I tested with android phone and then tested with MCP, now it is uploading without error. I think it is the issue with MCP. And also while uploading it is consuming more CPU resource.
Yes I am using the latest MCP i.e., 3.10.0.14
Thank you for the support.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44912?ContentTypeID=1</link><pubDate>Fri, 19 Feb 2016 09:37:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15a10f77-4412-4a69-87c8-51c6242d6876</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Are you using the latest version of MCP, and is error message still &amp;quot;no dfu service&amp;quot;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44900?ContentTypeID=1</link><pubDate>Fri, 19 Feb 2016 04:41:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:22b82d4c-cb4b-47f7-a2b6-06a2b5630825</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Update: I tested the same .zip file using nRF toolbox from android phone, and it is uploading successfully. The problem persists with only MCP.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44911?ContentTypeID=1</link><pubDate>Thu, 18 Feb 2016 09:52:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:46df119a-4584-437b-9473-f7b85fbc7380</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;I tested with clean and fresh SDK but the error persists. Is this correct to generate the zip file for the application:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;C:\Program Files\Nordic Semiconductor\Master Control Panel\3.10.0.14\nrf&amp;gt;nrfutil
.exe dfu genpkg --application E:\nRF51_SDK_9.0.0_2e23562\examples\ble_peripheral
\ble_app_hrs\pca10028\s110_with_dfu\arm5_no_packs_build\nrf51422_xxac_s110.hex
--application-version 0xffffffff --dev-type 0xffff --dev-revision 0xffff --sd-re
q 0x64 E:\nRF51_SDK_9.0.0_2e23562\test.zip
Zip created at E:\nRF51_SDK_9.0.0_2e23562\test.zip&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Am I doing mistake in generating the zip file?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44910?ContentTypeID=1</link><pubDate>Thu, 18 Feb 2016 09:27:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ab29da6b-e6b2-420b-8f96-8924c9a2fffa</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Yes it should work without any modifications. Reason I asked you to try the pre-compiled one was to ensure that there wasn&amp;#39;t a config/code change that could cause the error you saw. Please  try the same project from a clean SDK, and see if it works then.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44909?ContentTypeID=1</link><pubDate>Thu, 18 Feb 2016 09:16:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ac4e5f2c-7bd8-43c2-8bb7-55e199816e31</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;No, I was compiling the project located in &lt;em&gt;\nRF51_SDK_9.0.0_2e23562\examples\ble_peripheral\ble_app_hrs\pca10028\s110_with_dfu\arm5_no_packs&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Now I tested with the file mentioned by you and yes I am not getting any errors and firmware upgrading.
What is the difference between these two files? As suggested in nordic document, we have to use hrs_with_dfu, Right?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44908?ContentTypeID=1</link><pubDate>Thu, 18 Feb 2016 08:59:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:380a5c9c-5baa-4803-992b-13c1d702665e</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Are you using the hrm_dfu example in the following directory &amp;quot;\nRF51_SDK_9.0.0\examples\dfu\ble_dfu_send_hex\test_images_update\dfu_test_app_hrm_s110.zip&amp;quot;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44907?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 12:35:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bd94579e-b5d5-43e5-87f1-654af499d78c</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Yes. After changing it is advertising :) Still not getting why it was not working previously when I changed the RAM address.
Now I tried to flash the hrs_dfu hex file over DFU, but getting error &lt;strong&gt;device doesnot have the required DFU service&lt;/strong&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44906?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 12:19:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:16e7751f-7d75-4587-bfae-973e7768021b</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Please check the updated hex file. Yes the file was loaded in the programming log. When I checked in nrf_studio it is displaying 3 partitions: SD , Application and Bootloader.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44905?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 11:39:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:476de22e-b3eb-4251-b850-e14fac5082a4</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;The .hex you sent is loading data to RAM above 16K, but assume you changed it after you sent it to me? Did you verify that the file was loaded in the programming log, to ensure you&amp;#39;re not running the old one?  This is the only reason I can think of that should cause hardfault in dfu_ble_peer_data_get&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44904?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 11:30:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ff158963-7299-4c5e-b0df-149f3637e45b</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;For testing purpose, I am testing on Evaluation board: NRF51822QFAAG0 which has 256KB flash and 16KB RAM. So for 16KB of RAM, I had changed the IRAM1 and IRAM settings as discussed in one of the thread in forum, but it is also not working.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44903?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 11:27:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3f01b15-82f9-41e3-9310-eb44cbe22328</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Guess the BL600A has 16K of RAM then. Changing the RAM settings in target options  should fix this:&lt;/p&gt;
&lt;p&gt;IRAM1: 0x20002c00   0x1380
IRAM2: 0x20003F80  0x80&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44902?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 11:09:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd12dac4-3aa0-49b9-8e5b-6b8c32ae7824</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Hi Vidar, if I just flash the program using F8 in Keil, I am getting the error : &lt;strong&gt;Reading flash area to program to guarantee it is erased.
Checking that the area to write is not protected.
Programing device.&lt;/strong&gt;.
Then I tried to debug the code, breakpoint is hitting main and when I execute, hardfault is occuring for CRC16 in the following code snippet:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;uint32_t dfu_ble_peer_data_get(dfu_ble_peer_data_t * p_peer_data)
{
uint16_t crc;

if (p_peer_data == NULL)
{
    return NRF_ERROR_NULL;
}

crc = crc16_compute((uint8_t *)&amp;amp;m_peer_data, sizeof(m_peer_data), NULL);
if (crc != m_peer_data_crc)
{
    return NRF_ERROR_INVALID_DATA;
}
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44901?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 10:21:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9227b3b0-db85-4278-911c-192c25ea86b0</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Can&amp;#39;t read the register content in the screenshot you sent, but the code appears to be stuck in the hardfault handler inside the MBR. Please attach the .hex/.axf file you&amp;#39;re using.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44899?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 07:11:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ac4d8a8-3b5d-42f3-98ce-5d7f770aca4c</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Please add a screenshot of the register view when you debug the code:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start a new debug session and start execution, then stop  after few seconds to take the screenshot.&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44898?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 04:57:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0744298f-46e4-43c8-b95c-7cb887ecd4a8</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;No, it is not coming to main. Arguments for the external tool is &lt;em&gt;--family NRF51 --program &amp;quot;#H&amp;quot;&lt;/em&gt; and the address is as below:&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/bootloader.bmp" alt="image description" /&gt;&lt;/p&gt;
&lt;p&gt;Update: This is a screenshot after debugging.&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/bootloader_5F00_dual.bmp" alt="image description" /&gt;
Hex file is : &lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/4251.nrf51422_5F00_xxac.hex"&gt;nrf51422_xxac.hex&lt;/a&gt;
Axf file: &lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/nrf51422_5F00_xxac.axf"&gt;nrf51422_xxac.axf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This is the hex and axf file after changing the RAM registers:
&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/6765.nrf51422_5F00_xxac.hex"&gt;nrf51422_xxac.hex&lt;/a&gt;
&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/2100.nrf51422_5F00_xxac.axf"&gt;nrf51422_xxac.axf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This is the screenshot taken after executing and stopping:
&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/dfu.bmp" alt="image description" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44897?ContentTypeID=1</link><pubDate>Tue, 16 Feb 2016 14:10:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c3ad4a77-000f-4590-acdf-8669c7544fa9</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Yes, the device should advertise as &amp;quot;dfutarg&amp;quot; when SD+BL is programmed. Have you tried to attach a debugger and see if main in the bootloader is reached?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44896?ContentTypeID=1</link><pubDate>Mon, 15 Feb 2016 12:34:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:23ed4b2c-9f76-47e8-99a3-f5cca93418fd</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Hello Vidar, before flashing application using Jtag or DFU bootloader, should we able to see the dfu device advertising?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44895?ContentTypeID=1</link><pubDate>Mon, 15 Feb 2016 07:37:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5364beec-7d73-40cd-a6c7-7eb0c54ae0fd</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Program is most likely running from the bootloader. Please have a look at answer &amp;#39;E&amp;#39; in this &lt;a href="https://devzone.nordicsemi.com/blogs/685/common-faq-on-dfu/"&gt;FAQ&lt;/a&gt; for more details.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44894?ContentTypeID=1</link><pubDate>Sat, 13 Feb 2016 13:40:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f4e6b20-8771-4a7b-a46f-00711a4a3ee1</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Update: As I have an evaluation kit, I will go with buttonless DFU . Now I flashed Softdevice, Bootloader application and then ble_hrs application. But breakpoint is not hitting main of ble_hrs. What can be the cause?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44893?ContentTypeID=1</link><pubDate>Sat, 13 Feb 2016 13:15:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e01fbbdc-484e-4bb6-9e16-5ad3d8f6bc80</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Hi Vidar, Thank you for the link. I flashed Softdevice and then ble_hrs application but got error when I did firmware upgrade using DFU.
Now I got to know that I have to flash bootloader and need to change the programming tool as mentioned &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk51.v10.0.0%2Fbledfu_example_running.html&amp;amp;anchor=bledfu_example_running_test"&gt;here&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;But where can I get &lt;strong&gt;dfu_dual_bank_ble_SoftDevice_pca10028&lt;/strong&gt; example project in SDK 9.0?&lt;/p&gt;
&lt;p&gt;Regards,
Sowmya&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BL600 NUS service and DFU support</title><link>https://devzone.nordicsemi.com/thread/44892?ContentTypeID=1</link><pubDate>Sat, 13 Feb 2016 11:03:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:816050eb-6613-499b-8682-2bb88dd4582e</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You don&amp;#39;t have to do anything to your existing application if you have a board button or similar that you can use to enter DFU mode (press button while resetting kit). The other alternative is to extend your existing application to support &amp;quot;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk51.v10.0.0/bledfu_application.html?cp=4_0_1_4_3_1_2"&gt;buttonless&lt;/a&gt;&amp;quot; entry. Neither of these approaches will affect the existing NUS service.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>