Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

Einar Thorsrud — Mon, 20 May 2019 07:50:20 GMT

Hi,

It looks like you have everything covered there. You can refer to Adding Buttonless Secure DFU Service to a BLE application for more information.

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Fri, 17 May 2019 03:04:21 GMT

Hi,

Thank you very much,I don't know what happened,but sometimes I can accomplish the dfu service directly, and now I want to know what code I must add in the main.c,Is this the following?

1.Implement the DFU event handler
static void ble_dfu_buttonless_evt_handler(ble_dfu_buttonless_evt_type_t event)
{
switch (event)
{
case BLE_DFU_EVT_BOOTLOADER_ENTER_PREPARE:
NRF_LOG_INFO("Device is preparing to enter bootloader mode\r\n");
break;
case BLE_DFU_EVT_BOOTLOADER_ENTER:
NRF_LOG_INFO("Device will enter bootloader mode\r\n");
break;
case BLE_DFU_EVT_BOOTLOADER_ENTER_FAILED:
NRF_LOG_ERROR("Device will enter bootloader mode\r\n");
break;
default:
NRF_LOG_INFO("Unknown event from ble_dfu.\r\n");
break;
}
}

2.Enabling power management auto shutdown retry
#ifndef NRF_PWR_MGMT_CONFIG_AUTO_SHUTDOWN_RETRY
#define NRF_PWR_MGMT_CONFIG_AUTO_SHUTDOWN_RETRY 1
#endif

3. Implement the power management
static bool app_shutdown_handler(nrf_pwr_mgmt_evt_t event)
{
switch (event)
{
case NRF_PWR_MGMT_EVT_PREPARE_DFU:
NRF_LOG_INFO("Power management wants to reset to DFU mode\r\n"); 
// Change this code to tailor to your reset strategy.
// Returning false here means that the device is not ready to jump to DFU mode yet.
// 
// Here is an example using a variable to delay resetting the device:
if (!m_ready_for_reset)
{
return false;
}
break;
default:
// Implement any of the other events available from the power management module:
// -NRF_PWR_MGMT_EVT_PREPARE_SYSOFF
// -NRF_PWR_MGMT_EVT_PREPARE_WAKEUP
// -NRF_PWR_MGMT_EVT_PREPARE_RESET
return true;
}
NRF_LOG_INFO("Power management allowed to reset to DFU mode\r\n");
return true;
}


4. Initializing the Buttonless Secure DFU Service
static void services_init(void)
{
...
ble_dfu_buttonless_init_t dfus_init =
{
.evt_handler = ble_dfu_buttonless_evt_handler
};
err_code = ble_dfu_buttonless_init(&dfus_init);
APP_ERROR_CHECK(err_code);
...
}

Because I'm not sure whether I can use it in other application simply,or I need change a lot of things if I want to add dfu in another application.Looking forward to your reply.

best regards

zhong,

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

Einar Thorsrud — Mon, 06 May 2019 11:46:34 GMT

Hi,

1. This seems to be RTT log from the application. Is the bootloader running? Another way of making sure that the RTT log of the debug bootloader is printed is to disable RTT logging in the application. This way you know there is no "residue" RTT buffer from the application in RAM. Also remember that it only the debug bootloader that has RTT logging.

2. The phone shows that there are no DFU characteristics. This indicates that neither the bootloader nor an application with the buttonless DFU service is running. Can you double check?

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Sun, 05 May 2019 08:12:45 GMT

Hi,

I try to disconnect the RTT viewer and connect again after entering DFU mode.but nothing I can find,

and then I try the dfu in another phone(android),unfortunately,even if I open the RTT ,The dfu fail too.

It's the information in RTT viewer and in the phone:

1.RTT viewer

Process: JLinkExe

<debug> nrf_sdh: State request: 0x00000000

<debug> nrf_sdh: State change: 0x00000000

<debug> nrf_sdh: State change: 0x00000001

<debug> nrf_sdh_ble: RAM starts at 0x20002AA8

<info> app: Debug logging for UART over RTT started.

<debug> nrf_sdh_ble: BLE event: 0x10.

<debug> nrf_ble_gatt: Requesting to update ATT MTU to 247 bytes on connection 0x0.

<debug> nrf_ble_gatt: Updating data length to 251 on connection 0x0.

<info> app: Connected

<debug> nrf_sdh_ble: BLE event: 0x3A.

<debug> nrf_ble_gatt: ATT MTU updated to 247 bytes on connection 0x0 (response).

<info> app: Data len is set to 0xF4(244)

<debug> app: ATT MTU exchange completed. central 0xF7 peripheral 0xF7

<debug> nrf_sdh_ble: BLE event: 0x24.

<debug> nrf_ble_gatt: Data length updated to 27 on connection 0x0.

<debug> nrf_ble_gatt: max_rx_octets: 27

<debug> nrf_ble_gatt: max_tx_octets: 27

<debug> nrf_ble_gatt: max_rx_time: 328

<debug> nrf_ble_gatt: max_tx_time: 328

<debug> app: ATT MTU exchange completed. central 0xF7 peripheral 0xF7

<debug> nrf_sdh_ble: BLE event: 0x12.

2.in the phone

what' the matter?

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

Einar Thorsrud — Tue, 30 Apr 2019 13:32:59 GMT

Hi,

This RTT log only covers the application. That is an unfortunate consequence of the RTT viewer only searching for the RTT buffer once, as described here and here. Can you try to disconnect the RTT viewer and connect again after entering DFU mode? That way you should get the bootloader RTT output. (alternatively, you could make sure that the RTT buffer of the application and bootloader is in the same memory address).

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Tue, 30 Apr 2019 07:54:33 GMT

Hi,

It's the log file:

<debug> nrf_sdh: State request: 0x00000000

<debug> nrf_sdh: State change: 0x00000000

<debug> nrf_sdh: State change: 0x00000001

<debug> nrf_sdh_ble: RAM starts at 0x20002AA8

<info> app: Debug logging for UART over RTT started.

<debug> nrf_sdh_ble: BLE event: 0x10.

<debug> nrf_ble_gatt: Requesting to update ATT MTU to 247 bytes on connection 0x0.

<debug> nrf_ble_gatt: Updating data length to 251 on connection 0x0.

<info> app: Connected

<debug> nrf_sdh_ble: BLE event: 0x3A.

0xF7

x0.

<debug> nrf_sdh: State request: 0x00000000

<debug> nrf_sdh: State change: 0x00000000

<debug> nrf_sdh: State change: 0x00000001

<debug> nrf_sdh_ble: RAM starts at 0x20002AA8

<info> app: Debug logging for UART over RTT started.

<debug> nrf_sdh_ble: BLE event: 0x10.

<debug> nrf_ble_gatt: Requesting to update ATT MTU to 247 bytes on connection 0x0.

<debug> nrf_ble_gatt: Updating data length to 251 on connection 0x0.

<info> app: Connected

<debug> nrf_sdh_ble: BLE event: 0x3A.

<debug> nrf_ble_gatt: ATT MTU updated to 185 bytes on connection 0x0 (response).

<info> app: Data len is set to 0xB6(182)

<debug> app: ATT MTU exchange completed. central 0xF7 peripheral 0xF7

<debug> nrf_sdh_ble: BLE event: 0x24.

<debug> nrf_ble_gatt: Data length updated to 251 on connection 0x0.

<debug> nrf_ble_gatt: max_rx_octets: 251

<debug> nrf_ble_gatt: max_tx_octets: 251

<debug> nrf_ble_gatt: max_rx_time: 2120

<debug> nrf_ble_gatt: max_tx_time: 2120

<debug> app: ATT MTU exchange completed. central 0xF7 peripheral 0xF7

<debug> nrf_sdh_ble: BLE event: 0x23.

<debug> nrf_ble_gatt: Peer on connection 0x0 requested a data length of 251 bytes.

<debug> nrf_ble_gatt: Updating data length to 251 on connection 0x0.

<debug> nrf_sdh_ble: BLE event: 0x24.

<debug> nrf_ble_gatt: Data length updated to 251 on connection 0x0.

<debug> nrf_ble_gatt: max_rx_octets: 251

<debug> nrf_ble_gatt: max_tx_octets: 251

<debug> nrf_ble_gatt: max_rx_time: 2120

<debug> nrf_ble_gatt: max_tx_time: 2120

<debug> app: ATT MTU exchange completed. central 0xF7 peripheral 0xF7

<debug> nrf_sdh_ble: BLE event: 0x50.

<debug> nrf_sdh_ble: BLE event: 0x52.

<debug> nrf_sdh_ble: BLE event: 0x50.

<info> app: Received indication state 1

<debug> nrf_sdh_ble: BLE event: 0x51.

<debug> nrf_sdh_ble: BLE event: 0x53.

<info> app: Device is preparing to enter bootloader mode.

<debug> app: Disconnected connection handle 0

<info> app: Disconnected 1 links.

<debug> app: In ble_dfu_buttonless_bootloader_start_finalize

<info> app: Device will enter bootloader mode.

<info> app: Power management wants to reset to DFU mode.

<info> app: Power management allowed to reset to DFU mode.

and I can finish dfu when I open the RTT mode,but If I don't use RTT to test.It won't finish the dfu Just like before（always in 100%），Is it normal？（app“nrf connect”in iphone）.

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

Einar Thorsrud — Mon, 29 Apr 2019 10:56:30 GMT

Hi,

There is no RTT output here, just printouts from JLinkExe. You also need to connect to JLinkExe via telnet, as described in the end in the post I linked to.

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Sun, 28 Apr 2019 06:55:18 GMT

Hi,

It's the log file with the bootloader_debug only:

###RTT Client: ************************************************************

###RTT Client: * SEGGER Microcontroller GmbH *

###RTT Client: * Solutions for real time microcontroller applications *

###RTT Client: ************************************************************

###RTT Client: * *

###RTT Client: * www.segger.com Support: support@segger.com *

###RTT Client: * *

###RTT Client: ************************************************************

###RTT Client: * *

###RTT Client: * SEGGER J-Link RTT Client Compiled Mar 22 2019 17:28:45 *

###RTT Client: * *

###RTT Client: ************************************************************

###RTT Client: -----------------------------------------------

###RTT Client: Connecting to J-Link RTT Server via localhost:19021 Connected.

SEGGER J-Link V6.40 - Real time terminal output

J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15 V1.0, SN=683732423

Process: emStudio

and this is the log file with bootloader,settings,softdevice and app:

###RTT Client: ************************************************************

###RTT Client: * SEGGER Microcontroller GmbH *

###RTT Client: * Solutions for real time microcontroller applications *

###RTT Client: ************************************************************

###RTT Client: * *

###RTT Client: * www.segger.com Support: support@segger.com *

###RTT Client: * *

###RTT Client: ************************************************************

###RTT Client: * *

###RTT Client: * SEGGER J-Link RTT Client Compiled Mar 22 2019 17:28:45 *

###RTT Client: * *

###RTT Client: ************************************************************

###RTT Client: -----------------------------------------------

###RTT Client: Connecting to J-Link RTT Server via localhost:19021 Connected.

SEGGER J-Link V6.44c - Real time terminal output

J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15 V1.0, SN=683732423

Process: JLinkExe

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Sun, 28 Apr 2019 05:35:11 GMT

Hi,

I try this and I get these things:

JLinkRTTClient

###RTT Client: ************************************************************

###RTT Client: * SEGGER Microcontroller GmbH *

###RTT Client: * Solutions for real time microcontroller applications *

###RTT Client: ************************************************************

###RTT Client: * *

###RTT Client: * www.segger.com Support: support@segger.com *

###RTT Client: * *

###RTT Client: ************************************************************

###RTT Client: * *

###RTT Client: * SEGGER J-Link RTT Client Compiled Mar 22 2019 17:28:45 *

###RTT Client: * *

###RTT Client: ************************************************************

###RTT Client: -----------------------------------------------

###RTT Client: Connecting to J-Link RTT Server via localhost:19021 Connected.

SEGGER J-Link V6.44c - Real time terminal output

J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15 V1.0, SN=683732423

Process: JLinkExe

Where can I find the exact file?and I try to change the application-version at 2,The same situation occured ,and I simply use the DfuTarg,It failed too.What should I do next?

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

Einar Thorsrud — Fri, 26 Apr 2019 10:47:58 GMT

Hi,

Yes, you can use RTT logging on Mac as well, but it is a bit less user friendly. You can follow the same basic instructions as for Linux, for instance from this post.

Your nrfutil command looks mostly OK. However, you should increase the application-version, as the bootloader will prevent you to upgrade to the same or lower version number (unless NRF_DFU_APP_DOWNGRADE_PREVENTION is set to 0 in the bootloaders sdk_config.h).

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Fri, 26 Apr 2019 09:27:24 GMT

Hi Einar,

ok,so I can do it in mac os? I will do it, by the way,maybe my update-zip.file is incorrecct.It's my process:

1.get the output file.hex in example hrs.and named "app_new.hex"

2.use command:

nrfutil pkg generate --application app_new.hex --application-version 1 --application-version-string "1.0.0" --hw-version 52 --sd-req 0xB6 --sd-id 0xB6 --softdevice s140_nrf52_6.1.1_softdevice.hex --key-file priv.pem FW.zip

and I download the zipfile and use it.

Is there any problem?looking forward to your reply.

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

Einar Thorsrud — Fri, 26 Apr 2019 09:20:40 GMT

Hi,

The debug bootlaoder use RTT logging by default, so you just need to connect a J-link debugger (unless you use the DK, which has one onboard) and start the J-Link RTT Viewer. This should have allready been installed on your computer, assuming you use Windows and have installed nRF5 Command Line Tools.

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Fri, 26 Apr 2019 06:12:27 GMT

Hi,Einar,

I tested with a debug bootloader,it's named DfuTarg,but the same situation occured,it's always in 100% and then back to the orignal service(dfuTarg), and now i'm using the macos and I don't know how to get the RTT log. could you please tell me how to get the RTT log and I will update it quickly.

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

Einar Thorsrud — Thu, 25 Apr 2019 09:26:48 GMT

Hi Zhong,

I see. Since you are able to transfer the image, you have successfully entered DFU mode in the bootloader. Therefor this issue is not related to the DFU service.

Can you test with a debug bootloader, and upload the RTT log to this case? The bootloader has extensive logging, so the log should hopefully tell us more about what is going on.

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Thu, 25 Apr 2019 02:32:58 GMT

Hi Einar,

I fail in last step.I want to use dfu service to update.The progress bar is becoming 100% and nothing happened,The update file I use is blinky_example.I think if I can start OTA service.maybe it's not the problem about the update file,so what should I do?like the image, it can't be finished,and then it will return to the original service(UART service with dfu service) automatically,Thanks for your patient.

best regards

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

Einar Thorsrud — Tue, 23 Apr 2019 13:50:59 GMT

Hi,

This thread started with correcting the memory configuration of the application and SoftDevice, to allow you to add more services. That seems to not be the current issue?

If you don't get any errors but still don't see the DFU service there are two possible reasons that comes to mind:

You do not actually initialize the DFU service. Can you verify that you do, and possibly upload your code so that I can check it?
Another possible explanation is that even if you have added the DFU service is might not show up in your phone as it may have cached the services. In that case you could remove the device from your phone and toggle airplane mode on and off before reconnecting. This way you know that it will perform a new service discovery.

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Thu, 18 Apr 2019 07:59:56 GMT

hello,AndreasF,

I try it again, and it also only shows the UART service,could you please help me find the solution?Thanks a lot.

best regrads,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Thu, 18 Apr 2019 02:48:52 GMT

hello,AndreasF,

I changed my section placement marcos by the warning:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x100000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x40000

FLASH_START=0x26000

FLASH_SIZE=0xda000

RAM_START=0x20002aa8

RAM_SIZE=0x3d558

and then I "build and run" in order to get the output.hex.After this,I make the setting file and mix the settings.hex,app.hex,softdevice.hex and bootloader.hex by using the code below:

nrfutil settings generate --family NRF52840 --application app.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 settings.hex

mergehex --merge bootloader.hex s140_nrf52_6.1.1_softdevice.hex --output production_final1.hex

mergehex --merge production_final1.hex app.hex --output production_final2.hex

mergehex --merge production_final2.hex settings.hex --output production_final.hex

nrfjprog --eraseall -f NRF52

nrfjprog -f NRF52 --program "production_final.hex" --verify  

nrfjprog --reset -f NRF52

finally I can connect the nrf52840 which is named "UART service" by my phone,but I can only find that there is only a service named UART service,I can't find the dfu service, what should I do?

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Thu, 18 Apr 2019 02:05:15 GMT

hello,AndreasF,

I try it,and then I receive the message like this:

 nrf_sdh_ble: Insufficient RAM allocated for the SoftDevice.

 nrf_sdh_ble: Change the RAM start location from 0x20002A98 to 0x20002AA8.

 nrf_sdh_ble: Maximum RAM size for application is 0x3D558.

 nrf_sdh_ble: sd_ble_enable() returned NRF_ERROR_NO_MEM.

 app: ERROR 4 [NRF_ERROR_NO_MEM] at /Users/zz/Desktop/stage5a/heatzy_pilote/BLE_Projects/nRF5_SDK_15.3.0_59ac345/examples/ble_peripheral/ble_app_uart/main.c:508

PC at: 0x0002EC1B

so,how to change the section placement marcos?I use the soft6.1.1 and sdk 15.3.0,This is my setting(I set by the tutorial:https://devzone.nordicsemi.com/tutorials/b/getting-started/posts/adjustment-of-ram-and-flash-memory),I don't know the exact mean about FLASH_PH_START and FLASH_PH_SIZE.etc

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x100000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x40000

FLASH_START=0x26000

FLASH_SIZE=0xda000

RAM_START=0x20002a98

RAM_SIZE=0x3d568

so I just change the RAM_START and RAM_SIZE?or I should also change other things like FLASH_PH_START or FLASH_START. Look forward to your reply.

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

AndreasF — Wed, 17 Apr 2019 10:15:22 GMT

Hi zhong.

Have you added the source files and header files?

[quote user="zhong"][/quote]

1.Add source file
Add a folder nRF_DFU to the project and add the following files:

<sdk>\components\ble\ble_services\ble_dfu\ble_dfu.c
<sdk>\components\ble\ble_services\ble_dfu\ble_dfu_bonded.c
<sdk>\components\ble\ble_services\ble_dfu\ble_dfu_unbonded.c
<sdk>\components\libraries\bootloader\dfu\nrf_dfu_svci.c

Have you defined m_ready_for_reset?

Best regards,

Andreas

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Wed, 17 Apr 2019 10:00:20 GMT

hello,AndreasF

I do the thing in the infocenter guide,I add the code and set

NRF_PWR_MGMT_CONFIG_AUTO_SHUTDOWN_RETRY 1 

and there are some errors in the image

which files should I add?

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Wed, 17 Apr 2019 09:16:54 GMT

hello,AndreasF

I will try the Infocentor Guide,what diffrerence entre the dfu_buttonless service and dfu_secure_buttonless service?so I just should do the things step by step by "add secure_buttonless_dfu service in ble application"? now I am using the tutorial for this website.http://www.sunyouqun.com/2018/04/nordic-ble-dfu-4-buttonless-app/

it's Chinese and other person was success in using it, all the changes are shown in the form of pictures. Now I explain the work I have done.

first，Open the <sdk>\examples\ble_peripheral\ble_app_hrs project to make sure the project works

1.Add source file
Add a folder nRF_DFU to the project and add the following files:

2.Add Include directory
Find User Include Directories in the project configuration window and add the following path:

../../../../../../components/libraries/bootloader
../../../../../../components/libraries/bootloader/ble_dfu
../../../../../../components/libraries/bootloader/dfu
../../../../../../components/libraries/svc
If you use SEGGER Embedded Studio, you need to pay extra attention to the spaces at the end of these paths, which may result in not being recognized correctly.

3.Add macro switch
Find Preprocessor Definitions in the Project Configuration window and add the following items:

NRF_DFU_SVCI_ENABLED
NRF_DFU_TRANSPORT_BLE=1
BL_SETTINGS_ACCESS_ONLY

4.Configuring sdk_config
In sdk_config.h, make the following changes:

BLE_DFU_ENABLED = 1
NRF_SDH_BLE_VS_UUID_COUNT += 1

5.Add header file
Add the following header file to main.c:

#include "nrf_dfu_ble_svci_bond_sharing.h"
#include "nrf_svci_async_function.h"
#include "nrf_svci_async_handler.h"
#include "ble_dfu.h"
#include "nrf_power.h"
#include "nrf_bootloader_info.h"

6.Add code
Open the main.c of the Buttonless sample project and copy the following functions into the main.c of the current project:

Add Buttonless DFU Service:

static bool app_shutdown_handler(nrf_pwr_mgmt_evt_t event){};
NRF_PWR_MGMT_HANDLER_REGISTER(app_shutdown_handler, 0);
static void buttonless_dfu_sdh_state_observer(nrf_sdh_state_evt_t state, void * p_context){};
NRF_SDH_STATE_OBSERVER(m_buttonless_dfu_state_obs, 0) = {};
static void ble_dfu_evt_handler(ble_dfu_buttonless_evt_type_t event){};

Add the DFU service at the end of the main.c/services_init function:

ble_dfu_buttonless_init_t dfus_init = {0};

// Initialize the async SVCI interface to bootloader.
err_code = ble_dfu_buttonless_async_svci_init();
APP_ERROR_CHECK(err_code);

dfus_init.evt_handler = ble_dfu_evt_handler;

err_code = ble_dfu_buttonless_init(&dfus_init);
APP_ERROR_CHECK(err_code);

7.Adjust memory address
Follow the steps above and walk down, you can already compile. Burn Softdevice and Application, open the serial port tool, you should see the log message prompts that the memory address and memory size need to be adjusted.

（In this step, I didn't see any information on the serial port, so I don't know how to modify the RAM, maybe the memory of nrf52840 is enough）

Then I can compile and get the app.hex file

8.Bootloader settings

I confirmed that I used the correct version of softdevice and bootloader (s140_nrf52_6.1.1_softdevice.hex and complie the file in sdk15.3.0/example/dfu/secure_bootloader/pca10056 folder to get the bootloader.hex), and then got the final hex file by the following command.

nrfutil settings generate --family NRF52840 --application app.hex --application-version 3 --bootloader-version 2 --bl-settings-version 1 settings.hex

mergehex --merge bootloader.hex s140_nrf52_6.1.1_softdevice.hex --output production_final1.hex

mergehex --merge production_final1.hex app.hex --output production_final2.hex

mergehex --merge production_final2.hex settings.hex --output production_final.hex

nrfjprog --eraseall -f NRF52

nrfjprog -f NRF52 --program "production_final.hex" --verify

nrfjprog --reset -f NRF52

That's all the things I have done,I don't know where is the problem which cause the situation that I can't allocated RAM.Look forward to your reply~

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

AndreasF — Wed, 17 Apr 2019 08:48:42 GMT

Hi.

I think the error "Stopped by vector catch" is related to a Hardfault.

How did you add the dfu_buttonless Service? Did you follow the Infocenter Guide?

Perhaps this Hardfault occurs because the dfu_buttonless Service is not configured correctly.

Best regards,

Andreas

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

zhong — Wed, 17 Apr 2019 07:58:50 GMT

Hi AndreasF,

I try the chapter 8 or 9 in this tutorial,but there a problem occurs,

1.In chapter 8

First,I set the RAM like this in configuration debug,like this image.(sdk15.3.0,softdevice6.1.1)

and then I change the define in sdk_config.h which are shown in chapter 8.after I cancel all the breakpoint and click "go" in option "debug",but it's nothing in debug terminal,like the image.

Finally I click "go" once more,it shows"stopped by vector catch"

2.in chapter 9

In this way ,I set a breakpoint in line" ret_code_t ret_code = sd_ble_enable(p_app_ram_start);" shown in chapter 9, and then I click "go" in option"debug" once time ,the result like this image:

and then I click"go" once more,The debug never jump into the breakpoint which I set and it was blocked wtih"stopped by vector catch",like the image:

So what should I do?and if there are some tutorial which can tell me how to allocate RAM when I want to add a new service in a example(add dfu_buttonless service is better),Look forward to your help,thanks!

best regards,

zhong

RE: Problem 'stopped by vector catch' in allocating RAM when I added a new ble service" (nrf52840 sdk15.3.0)

AndreasF — Wed, 17 Apr 2019 07:10:16 GMT

Hi zhong.

For the issue with Restricted Memory Range, please read this.

For adjustment of RAM, please read this tutorial and look at chapter 8 or 9.

Best regards,

Andreas