Large data transfer over ble.

RE: Large data transfer over ble.

Simonr — Wed, 15 Jan 2020 14:39:18 GMT

Hi Thomas

The error codes can be looked up using ble_err.h and nrf_error.h. Error 0x3002 is BLE_ERROR_INVALID_CONN_HANDLE and defined as being an invalid connect handle. NRF_ERROR_STK_BASE_NUM is defined as 0x3000 in nrf_error.h.

Have you edited the ble_app_pwr_profiling example to be connectable or is it just advertising and not connecting to a central? I think it would be easier to avoid these connection errors if you based your project in an example that is already using connectable advertising by default.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Wed, 15 Jan 2020 10:42:58 GMT

I also sometimes get an error from m_event_handler(&app_uart_event); within a uart event handler in app_uart_fifo.c. In the case of NRF_DRV_UART_EVT_TX_DONE. This error code is 1.

I am thinking this is due to data being sent to the uart and it not being processed until the main loop is restarted.

This error run from the:

main: advertising_mod: err_code = sd_ble_gap_adv_stop(m_adv_handle);
ble_gap.h: SVCALL(SD_BLE_GAP_ADV_STOP, uint32_t, sd_ble_gap_adv_stop(uint8_t adv_handle));
nrfx_uarte.c: uarte_irq_handler : p_cb->handler(&event, p_cb->p_context); //This is aborting the transfer
nrfx_uarte.c: uarte_evt_handler : m_handlers[inst_idx](&event, m_contexts[inst_idx]);
app_uart_fifo.c : uart_event_handler: m_event_handler(&app_uart_event)
Then app error handler_bare

I do however get some data out before this error runs:

RE: Large data transfer over ble.

Thomas — Wed, 15 Jan 2020 10:33:06 GMT

I get an error code on sd_ble_gap_disconnect

err_code 3002. Is there somewhere I can look up these error codes?

RE: Large data transfer over ble.

Simonr — Tue, 14 Jan 2020 14:17:22 GMT

Do you have any error code to go on this time around? I'm guessing that the UART events aren't handled properly since your project isn't using UART originally, but it's hard to say what exactly is going wrong without any error code or log.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Tue, 14 Jan 2020 10:41:15 GMT

Hi Simon,

Cheers for that, it makes perfect sense. So I have now changed, my ble_evt_handler with the disconnected case to:

case BLE_GAP_EVT_DISCONNECTED:
            err_code = sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
            err_code = ble_advertising_restart_without_whitelist(&advertising_mod);
                if (err_code != NRF_ERROR_INVALID_STATE)
                {
                    APP_ERROR_CHECK(err_code);
                }
                GATT_CONNECTED = false;//Enable the live advertising
            break;

This is similar to the UART example you suggested. However, I changed the parameter to advertising_mod from m_advertising. This was due to a compile error stating it was undefined and recommending advertising_mod.

This still causes a fatal error on disconnect. This error comes from the uarte_evt_handler going to the fifo m_event_handler(&app_uart_event);

This happens a few seconds after I press disconnect on the app.

I have also tried using advertising_start();

That functionality looks like below:

static void advertising_start(void)
{
    ret_code_t err_code;

    err_code = sd_ble_gap_adv_start(m_adv_handle, APP_BLE_CONN_CFG_TAG);
    APP_ERROR_CHECK(err_code);
}

However, this does also not work.

RE: Large data transfer over ble.

Simonr — Tue, 14 Jan 2020 09:40:59 GMT

Hi Thomas

Seeing as you're using the ble_app_pwr_profiling example, how are you handling the BLE_GAP_EVT_DISCONNECTED in your ble_evt_handler? By default, the ble_app_pwr_profiling example is handling it by going to system OFF mode upon a disconnection, which might be why your device doesn't start advertising upon a disconnect. Try handling the disconnect event like the ble_app_uart example does, as that example does start advertising automatically upon a disconnect.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Mon, 13 Jan 2020 15:23:24 GMT

Hi Simon,

Sorry the confusion let me clarify.

I can advertise whilst no connection is active and have changing adverts that works fine.

Then from the main NRF connect screen when I see the list of devices I have the option to connect to the device as you would expect. From there I can see the services with the device.

However, when I then disconnect from this my advert does not come back and I get the aforementioned fatal error.

I want my advertising to restart on a disconnect. I am not sure why this is not the case.

In my main code I have the following:

 while (true)
    {
        if(GATT_CONNECTED == false)
        {
          // Get next gyte from FIFO
          while (app_uart_get(&c) != NRF_SUCCESS);
          string[pos] = c;

          // Assume that all strings end with \n. If end, print and start over.
          if (string[pos] == '\n')
          {
              string[pos+1] = '\0';
              NRF_LOG_INFO("Received string: \"%s\"", string);
              sscanf( string, "%*d , %d , %*d , %d ", &T1_data_1,&T2_data_1);
              NRF_LOG_INFO("T1 is:\"%d\"", T1_data_1);
              NRF_LOG_INFO("T2 is:\"%d\"", T2_data_1);
              pos = 0;
              counter++;
              idle_state_handle();
              data_changed = true;
              //converted_number =  toBinary(T1_data_1);
              if(data_changed==true)
              {
                advertising_mod(counter,T1_data_1,T2_data_1,00,00,70,80,70,80);//Only have two temperature sensors
                data_changed = false;
              }
          }
          else
          {
              pos++;
            
          }
       }
       else// GATT_CONNECTED = true
       {
           idle_state_handle();
       }
    }

GATT_CONNECTED is a boolean I have created. I set this to true in the ble_evt_handler within the case BLE_GAP_EVT_CONNECTED case. And I also set it to false on the disconnected case.

I am not sure why the advert itself does not restart. Note I am using a modified ble_app_pwr_profiling example.

RE: Large data transfer over ble.

Simonr — Mon, 13 Jan 2020 14:22:08 GMT

Hi Thomas

[quote user="ThomasMorris"]Then when press connect nothing is populated within the services menu also, I am chucking the data out to a RTT viewer. When I press connect I stop my live advertising Via a boolean that is set from the ble_evt_handler connected state. Then I can see the services.[/quote]

I'm not entirely sure what you mean here. Do you have to press connect twice for the device to connect to your central properly? The fact that it stops advertising when you connect makes sense, as it is connecting and won't be able to advertise during that process, as the nRF52 series only has one radio.

As for the disconnect you are seeing, BLE_GATTS_EVT_TIMEOUT means that a peer failed to respond to an ATT request in time, and that makes the central disconnect from your peripheral. So somewhere your peripheral is ignoring an ATT request from the central which causes this disconnect. You can see ble_gatts_evt_timeout_t for more information on this disconnect reason.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Mon, 13 Jan 2020 11:26:58 GMT

Hi Simon,

I have looked through the ble_app_pwr_profiling example. I have gotten it to work with my advertising that updates once per second from data coming in via UART.

However, whilst this works. Using the nordic semi conductor app (NRF connect). The device comes up with the live data and a connection is available.

The way my code works at the moment is as follows:

init the advert via button press (connectable)
Wait for UART string data (received once per second)
Update the advert (Run advertising_mod function see below)
Loop

Then when press connect nothing is populated within the services menu also, I am chucking the data out to a RTT viewer. When I press connect I stop my live advertising Via a boolean that is set from the ble_evt_handler connected state. Then I can see the services. But, when I disconnect I get fatal error.

This runs from BLE_GATTS_EVT_TIMEOUT APP

Advertising Mod: Note m_beacon is just for storing my data values inside of.

static void advertising_mod(int count, int T1_value,int T2_value,
                                       int t3_value_1,int t3_value_2, int p1_value_1, int p1_value_2,
                                       int p2_value_1,int p2_value_2)
{
    uint32_t      err_code;
    ble_advdata_t advdata;
    uint8_t       flags = BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED;
    
    int t1_value_1 = (T1_value >>8) & 0XFF;//MSB shifting
    int t1_value_2 = T1_value & 0XFF;//LSB

    int t2_value_1 = (T2_value >> 8) & 0XFF;//MSB
    int t2_value_2 = T2_value & 0XFF;//LSB

    ble_advdata_manuf_data_t manuf_specific_data;
    m_beacon_info[0]=(unsigned char) count;
    m_beacon_info[1]=(unsigned char) t1_value_1;
    m_beacon_info[2]=(unsigned char) t1_value_2;
    m_beacon_info[3]=(unsigned char) t2_value_1;
    m_beacon_info[4]=(unsigned char) t2_value_2;
    m_beacon_info[5]=(unsigned char) t3_value_1;
    m_beacon_info[6]=(unsigned char) t3_value_2;
    m_beacon_info[7]=(unsigned char) p1_value_1;
    m_beacon_info[8]=(unsigned char) p1_value_2;
    m_beacon_info[9]=(unsigned char) p2_value_1;
    m_beacon_info[10]=(unsigned char) p2_value_2;
   
    manuf_specific_data.company_identifier = COMPANY_IDENTIFIER;
    manuf_specific_data.data.p_data = (uint8_t *) m_beacon_info;
    manuf_specific_data.data.size   = APP_BEACON_INFO_LENGTH;

    // Build and set advertising data.
    memset(&advdata, 0, sizeof(advdata));

    advdata.name_type             = BLE_ADVDATA_NO_NAME;
    advdata.flags                 = flags;
    advdata.p_manuf_specific_data = &manuf_specific_data;

    // Initialize advertising parameters (used when starting advertising).
    memset(&m_adv_params, 0, sizeof(m_adv_params));

    m_adv_params.properties.type = BLE_GAP_ADV_TYPE_CONNECTABLE_SCANNABLE_UNDIRECTED;
    //m_adv_params.properties.type = BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;
    m_adv_params.p_peer_addr     = NULL;    // Undirected advertisement.
    m_adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    m_adv_params.interval        = CONNECTABLE_ADV_INTERVAL;
    m_adv_params.duration        = APP_ADV_DURATION;       // 30 Second adverts
    m_adv_params.primary_phy     = BLE_GAP_PHY_1MBPS;

    err_code = ble_advdata_encode(&advdata, m_adv_data.adv_data.p_data, &m_adv_data.adv_data.len);
    APP_ERROR_CHECK(err_code);

    err_code = sd_ble_gap_adv_stop(m_adv_handle);
    APP_ERROR_CHECK(err_code);

    err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &m_adv_params);
    APP_ERROR_CHECK(err_code);

    err_code = sd_ble_gap_adv_start(m_adv_handle, APP_BLE_CONN_CFG_TAG);
    APP_ERROR_CHECK(err_code);
}

The error comes from err_code = sd_ble_gap_disconnect(p_ble_evt->evt.gatts_evt.conn_handle,
BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);

But, I am not sure why.

Thanks,

Thomas

RE: Large data transfer over ble.

Simonr — Fri, 10 Jan 2020 14:13:55 GMT

I believe the ble_app_pwr_profiling example uses the sd_ble_gap_adv_set_configure function in order to set up two different advertising buffers, however, we don't have an example for updating advertising data regularly like you want to.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Fri, 10 Jan 2020 13:19:48 GMT

Also is there any example code where this is used?

RE: Large data transfer over ble.

Thomas — Thu, 09 Jan 2020 14:32:33 GMT

Ok I'll have a look.

But the old way I did it was start an ad then stop and start another. I presume the : SVCALL(SD_BLE_GAP_ADV_SET_CONFIGURE, uint32_t, sd_ble_gap_adv_set_configure(uint8_t *p_adv_handle, ble_gap_adv_data_t const *p_adv_data, ble_gap_adv_params_t const *p_adv_params));

Is used to update it rather than stop and start it again.

RE: Large data transfer over ble.

Simonr — Thu, 09 Jan 2020 14:23:29 GMT

Hi Thomas

Okay, thank you for explaining what you want to do. I urge you to check out the sd_ble_gap_adv_set_configure function on line 1887 in ble_gap.h at C:\nordicsemi\SDK\nRF5_SDK_16.0.0_98a08e2\components\softdevice\s140\headers\ where configuring an additional advertising set is described. In order to update advertising data while advertising, new advertising buffers must be provided, as you can't change the one you're using while advertising, which is likely what causes the error.

So you'll have to alternate between what advertising buffer you're updating each time in order to keep up a continuous advertisement.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Thu, 09 Jan 2020 08:21:00 GMT

Hi Simon,

Basically the app functionality I want is this:

Read sensor data which, in previous code uses RTT and UART(Working on other project)
Store this sensor data to an external SD (not yet done)
Output once per second an advertisement with the sensor data within the advertisement packet
Be able to receive connections from a ble application to:
- Set the time
- Request logged data from the board via sd card

Also I am using s140 p10056

I am now using the gatt example. I have got a fixed advertisement using the app_adv.c and passing in my fixed variables for the advertisement packet. Now I want to have this data update every second from data comming inform the UART.

My first question is how do I update this? Below is my code

main:

int main(void)
{
    //Int values
    T1_data_1 = 0;T1_data_2 = 0;T2_data_1 = 0;T2_data_2 = 0;T3_data_1 = 0;
    T3_data_2 = 0;P1_data_1 = 0;P1_data_2 = 0;P2_data_1 = 0;P2_data_2 = 0;
    // Initialize.
    modules_init();

    // Start execution.
    NRF_LOG_INFO("GATT Service client started.");
    advertising_start(m_erase_bonds);

    // Enter main loop.
  
    counter++;//Int value
    advertising_update(counter,T1_data_1,T2_data_1,00,00,70,80,70,80);
    for (;;)
    {
        idle_state_handle();
    }
    
}

Advertising Init:

void advertising_init(void)
{
    ret_code_t             err_code;
    ble_advertising_init_t init;

    memset(&init, 0, sizeof(init));
    //Manufacturer data
    ble_advdata_manuf_data_t                  manuf_data; //Variable to hold manufacturer specific data
    uint8_t data[]                            = "test"; //Our data to advertise
   
    manuf_data.company_identifier             =  0x0487; //Centricas company ID
    manuf_data.data.p_data                    = m_beacon_info;
    //manuf_data.data.p_data                    = data;
    //manuf_data.data.size = sizeof((uint8_t *) m_beacon_info);
    //manuf_data.data.size                      = sizeof(data);
    manuf_data.data.size                      = 11;
    
    init.advdata.p_manuf_specific_data = &manuf_data;
    //

    init.advdata.name_type            = BLE_ADVDATA_FULL_NAME;
    //init.advdata.short_name_len = 6; // Advertise only first 6 letters of name
    init.advdata.include_appearance   = true;
    init.advdata.flags                = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
    

    init.config.ble_adv_fast_enabled  = true;
    init.config.ble_adv_fast_interval = ADV_INTERVAL;
    init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;

    init.evt_handler = on_adv_evt;

    err_code = ble_advertising_init(&m_advertising, &init);
    APP_ERROR_CHECK(err_code);

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

Finally my update code:

When this code is run it goes to app error weak. I cant trace the error from debugging the error handler though. I happens after init.evt_handler = on_adv_evt;

void advertising_update(int count, int T1_value,int T2_value,
                                       int t3_value_1,int t3_value_2, int p1_value_1, int p1_value_2,
                                       int p2_value_1,int p2_value_2)
{
    ret_code_t             err_code;
    ble_advertising_init_t init;

    int t1_value_1 = (T1_value >>8) & 0XFF;//MSB shifting
    int t1_value_2 = T1_value & 0XFF;//LSB

    int t2_value_1 = (T2_value >> 8) & 0XFF;//MSB
    int t2_value_2 = T2_value & 0XFF;//LSB

    m_beacon_info[0]=(unsigned char) count;
    m_beacon_info[1]=(unsigned char) t1_value_1;
    m_beacon_info[2]=(unsigned char) t1_value_2;
    m_beacon_info[3]=(unsigned char) t2_value_1;
    m_beacon_info[4]=(unsigned char) t2_value_2;
    m_beacon_info[5]=(unsigned char) t3_value_1;
    m_beacon_info[6]=(unsigned char) t3_value_2;
    m_beacon_info[7]=(unsigned char) p1_value_1;
    m_beacon_info[8]=(unsigned char) p1_value_2;
    m_beacon_info[9]=(unsigned char) p2_value_1;
    m_beacon_info[10]=(unsigned char) p2_value_2;

    memset(&init, 0, sizeof(init));
    //Manufacturer data
    ble_advdata_manuf_data_t                  manuf_data; //Variable to hold manufacturer specific data
 
    manuf_data.company_identifier             =  0x0487; //Centricas company ID
    manuf_data.data.p_data                    = m_beacon_info;
    
    manuf_data.data.size                      = 11;
    
    init.advdata.p_manuf_specific_data = &manuf_data;

    init.advdata.name_type            = BLE_ADVDATA_FULL_NAME;
    //init.advdata.short_name_len = 6; // Advertise only first 6 letters of name
    init.advdata.include_appearance   = true;
    init.advdata.flags                = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
    
    init.config.ble_adv_fast_enabled  = true;
    init.config.ble_adv_fast_interval = ADV_INTERVAL;
    init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;

    init.evt_handler = on_adv_evt;

    err_code = ble_advertising_init(&m_advertising, &init);
    APP_ERROR_CHECK(err_code);   

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

Thanks,

Thomas

RE: Large data transfer over ble.

Simonr — Thu, 09 Jan 2020 07:56:17 GMT

Errors from the sd_ble_gap_adv_start should be returning an error message, like NRF_ERROR_INVALID_STATE, etc. These can be seen in ble_gap.h in C:\nordicsemi\SDK\nRF5_SDK_16.0.0_98a08e2\components\softdevice\s132\headers\ble_gap.h. I suggest you use the same advertising init function as in one of the examples already using connections in order to set up a "default" advertising that we know works.

Do you want something like a service (for example the battery value) that updates between each advertisement as part of your advertising packet? To do so, you will likely have to use scan response packets, as the size of the advertisement itself is rather limited. You will then have to enable service data in both the advertisement packet and the scan response packet. You can check out this case and the guide Joakim links to for more information on how to use scan response packets.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Wed, 08 Jan 2020 14:34:06 GMT

Oddly changing BLE_GAP_ADV_TYPE_CONNECTABLE_SCANNABLE_UNDIRECTED to BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED

Causes:

err_code = sd_ble_gap_adv_start(m_adv_handle, APP_BLE_CONN_CFG_TAG);
APP_ERROR_CHECK(err_code);

To pass an error code 12.

Also where is a look up table for error codes?

Also is it possible to have a ble advert e.g. something that changes every second with data in it, whilst being connectable for other features?

RE: Large data transfer over ble.

Simonr — Wed, 08 Jan 2020 13:55:25 GMT

You need to change the advertising params to make the device connectable and (usually) scannable by changing the m_adv_params.properties.type to something like BLE_GAP_ADV_TYPE_CONNECTABLE_SCANNABLE_UNDIRECTED.

You can check out the ble_advertising_init function in ble_advertising.c to see the default advertising parameters used in most of the connectable examples in the SDK. Note that the gatts example uses the app_adv.c file to set up the advertising (where it again calls ble_advertising_init).

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Wed, 08 Jan 2020 13:27:16 GMT

Thanks SImon,

I've resolved that issue now thanks.

Another question. As my project previously advertises data how do I add the connect-ability functionality too this?

This is my present advertisement init routine.

static void live_advertising_init(void)
{
    uint32_t      err_code;
    ble_advdata_t advdata;
    uint8_t       flags = BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED;

    ble_advdata_manuf_data_t manuf_specific_data;

    manuf_specific_data.company_identifier = APP_COMPANY_IDENTIFIER;
    manuf_specific_data.data.p_data = (uint8_t *) m_beacon_info;
    manuf_specific_data.data.size   = APP_BEACON_INFO_LENGTH;

    // Build and set advertising data.
    memset(&advdata, 0, sizeof(advdata));
    //Advertisement information

    advdata.name_type             = BLE_ADVDATA_NO_NAME;
    advdata.flags                 = flags;
    advdata.p_manuf_specific_data = &manuf_specific_data;
    /*Old setup

    advdata.name_type             = BLE_ADVDATA_NO_NAME;
    advdata.flags                 = flags;
    advdata.p_manuf_specific_data = &manuf_specific_data;
    */

    // Initialize advertising parameters (used when starting advertising).
    memset(&m_adv_params, 0, sizeof(m_adv_params));

    m_adv_params.properties.type = BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;
    m_adv_params.p_peer_addr     = NULL;    // Undirected advertisement.
    m_adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    m_adv_params.interval        = NON_CONNECTABLE_ADV_INTERVAL;
    m_adv_params.duration        = 0;       // Never time out.

    err_code = ble_advdata_encode(&advdata, m_adv_data.adv_data.p_data, &m_adv_data.adv_data.len);
    APP_ERROR_CHECK(err_code);

    err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &m_adv_params);
    APP_ERROR_CHECK(err_code);
}

I want it so when I am connected I can connect to the Gatt services and then notifications after that.

The advertising_init in the GATT example is

void advertising_init(void)
{
    ret_code_t             err_code;
    ble_advertising_init_t init;

    memset(&init, 0, sizeof(init));


    init.advdata.name_type            = BLE_ADVDATA_FULL_NAME;
    init.advdata.include_appearance   = true;
    init.advdata.flags                = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;

    init.config.ble_adv_fast_enabled  = true;
    init.config.ble_adv_fast_interval = ADV_INTERVAL;
    init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;

    init.evt_handler = on_adv_evt;

    err_code = ble_advertising_init(&m_advertising, &init);
    APP_ERROR_CHECK(err_code);

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

But, when I make the basic change of making the name from BLE_ADVDATA_NO_NAME to BLE_ADVDATA_FULL_NAME it no longer advertises. As an error is thrown on ble_advdata_encode.

I might therefore, start again with the GATT example and import my code over. But the underlying question is how do I have a dumb advertisement which broadcasts but, is connectable to the Gatt?

RE: Large data transfer over ble.

Simonr — Wed, 08 Jan 2020 12:48:03 GMT

In this case, SEGGER should give you an indication of what you should allocate your RAM to in the error message. To see how you do change the RAM and Flash memory start addresses and sizes, please check out this guide on the matter.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Wed, 08 Jan 2020 09:03:06 GMT

Hi Simon,

I've used my project as I feel it is more complex and, too a long time to set up.

However, I have just debugged my program stepping through the main when it gets to ble_stack_init.

It runs the line of code nrf_sdh_ble_enable. Running through this gives

NRF_LOG_WARNING("Insufficient RAM allocated for the SoftDevice.");

        NRF_LOG_WARNING("Change the RAM start location from 0x%x to 0x%x.",
                        app_ram_start_link, *p_app_ram_start);
        NRF_LOG_WARNING("Maximum RAM size for application is 0x%x.",
                        ram_end_address_get() - (*p_app_ram_start));

Which I presume means the ram allocated is not large enough.

How do I resolve this?

Thanks,

Thomas

Edit note : I am using Segger error code is 0x00000004

RE: Large data transfer over ble.

Simonr — Wed, 08 Jan 2020 08:59:44 GMT

Hi Thomas

Here is the general approach to combine two projects:

1. Start with the more complex one. If your project is very large, then that's the right way to start, but if it's just the beacon project with a few adjustments, I think starting out with the GATT example will be the best course of action.

2. Add the required .c files and the necessary include paths to your project.

3. Add required includes and code to your main.c file.

4. Modify the sdk_config.h file to enable the necessary configurations. Refer to the other project and compare the sdk_config.h files to see what's needed.

5. Compile the application.
a) If there are errors/warnings, go back to point 2 and resolve the errors before building again. This is very likely to repeat itself several times.

6. Test application.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Tue, 07 Jan 2020 15:04:10 GMT

Hi Simon,

I am adding the nordic gatt example code to my own project. I am at the point of including the include files and when I build it complies however, my previous code does not work. At this point I have only included the includes and a few definitions non of the functions (within the main)

My code (Previous functionality does this)

Takes in UART sensor data via RTT pin connections 26-29
Creates a ble advertisement
Each second modifies the ble advertisement and outputs last read data to the advert
It also spits out the sensor values to the RTT terminal

Now when I have added the GATT example includes, libraries, services, ble to the project and, changed the sdk_config.h so that no linker and compilation errors occur. Now my RTT viewer does not get populated and, no advertisement is made.

Could this be due to an issue in my sdk_config.h with some functionality for the GATT stopping my RTT and or, my adverts?

One definite change is that:

#define BLE_ADVERTISING_ENABLED 1//0

This line of code in my project is 0 and, in the GATT example it is 1. To compile it needs to be enabled.

RE: Large data transfer over ble.

Simonr — Tue, 07 Jan 2020 09:39:21 GMT

Yes, the approach, although the thread is somewhat dated, is still the correct one. You might want to look at some of our newer examples (ble_app_uart for example) as well as the blog post I linked to in my previous reply for some tips on how to optimize the Bluetooth transfer to use the throughput and methods available in Bluetooth 5.0.

Best regards,

Simon

RE: Large data transfer over ble.

Thomas — Mon, 06 Jan 2020 14:45:28 GMT

Hi Simonr,

I don't think I am pushing the limits as I don't need it to be all done in a single second. Although faster is better. Would you say my outlined approach is correct though?

RE: Large data transfer over ble.

Simonr — Mon, 06 Jan 2020 13:53:26 GMT

It seems to me like you might be pushing the upper limit of what you will be able to transfer using BLE here. I suggest you take a look at this blog post, which shows you how to achieve maximum throughput, and also provides source code for a project doing this.

Best regards,

Simon