Custom Service Issue

RE: Custom Service Issue

operator — Fri, 10 Mar 2017 19:07:31 GMT

Turns out services_init() needs to be called before advertising_init when doing it this way which makes sense when using a custom service...

All appears to be working now!

RE: Custom Service Issue

operator — Fri, 10 Mar 2017 18:53:23 GMT

Hello Petter and thank you for the reply.

I left the ble_enable_params.gatts_enable_params.attr_tab_size set to 0x900 and am debugging with the default memory size settings listed above.

I have optimization set to Level 0 (-O0) in my C/C++ settings and set some break points around if (app_ram_base != ram_start).

err_code equals 0x00000004 ram_start is 0x20002168 and app_ram_base becomes 0x200024F8 I also created a variable ram_size and set it equal to ram_end_address_get() - app_ram_base.

ram_end_address_get is called and returns 0x20010000 as ram_end_address.

My ram_size variable becomes 0x0000DB08

So I go back and set my IRAM Start to 0x200024F8 and IRAM size to 0x0000DB08

Sure enough, soft_device_enable() returns err_code 0x00000000, which I believe is NRF_SUCCESS.

Unfortunately, now ble_advertising_init is returning 0x07 I have tried using:

advdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
advdata.uuids_complete.p_uuids  = m_adv_uuids;
[...]
err_code = ble_advertising_init(&advdata, NULL, &options, on_adv_evt, NULL);

as well as:

ble_advdata_t          scanrsp;
[...]
memset(&scanrsp, 0, sizeof(scanrsp));
scanrsp.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
scanrsp.uuids_complete.p_uuids  = m_adv_uuids;
[...]
err_code = ble_advertising_init(&advdata, &scanrsp, &options, on_adv_evt, NULL);

Any thoughts on what might be causing this?

RE: Custom Service Issue

Petter Myhre — Fri, 10 Mar 2017 10:08:16 GMT

Please examine softdevice_enable(). Here ram_start equals the linker value of the RAM starting point of the application. app_ram_base is set to ram_start and is given to the SoftDevice through sd_ble_enable().

The SoftDevice will compare the value of app_ram_base with the RAM it actually needs, if too little RAM has been provided sd_ble_enable() will return NRF_ERROR_NO_MEM and app_ram_base will will be the required RAM starting point of the application.

You can check the value of the app_ram_base by using the debugger (turn off optimizations), or by printing:

    NRF_LOG_WARNING("sd_ble_enable: RAM start should be adjusted to 0x%x\r\n",
            app_ram_base);
    NRF_LOG_WARNING("RAM size should be adjusted to 0x%x \r\n",
            ram_end_address_get() - app_ram_base);