Not able to write 14 Bytes into Queued Writes module

RE: Not able to write 14 Bytes into Queued Writes module

Sigurd — Mon, 27 Apr 2020 06:27:20 GMT

[quote user="Caspar_Tsai"]I apply ble_cus.c, and ble_cus.h into my applicaton, and need to know the license for those two file.[/quote]

You can use the same license here as for the rest of the nRF5 SDK files.

/**
 * Copyright (c) 2016 - 2019, Nordic Semiconductor ASA
 *
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without modification,
 * are permitted provided that the following conditions are met:
 *
 * 1. Redistributions of source code must retain the above copyright notice, this
 *    list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form, except as embedded into a Nordic
 *    Semiconductor ASA integrated circuit in a product or a software update for
 *    such product, must reproduce the above copyright notice, this list of
 *    conditions and the following disclaimer in the documentation and/or other
 *    materials provided with the distribution.
 *
 * 3. Neither the name of Nordic Semiconductor ASA nor the names of its
 *    contributors may be used to endorse or promote products derived from this
 *    software without specific prior written permission.
 *
 * 4. This software, with or without modification, must only be used with a
 *    Nordic Semiconductor ASA integrated circuit.
 *
 * 5. Any software provided in binary form under this license must not be reverse
 *    engineered, decompiled, modified and/or disassembled.
 *
 * THIS SOFTWARE IS PROVIDED BY NORDIC SEMICONDUCTOR ASA "AS IS" AND ANY EXPRESS
 * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
 * OF MERCHANTABILITY, NONINFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE ARE
 * DISCLAIMED. IN NO EVENT SHALL NORDIC SEMICONDUCTOR ASA OR CONTRIBUTORS BE
 * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
 * GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
 * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 *
 */

RE: Not able to write 14 Bytes into Queued Writes module

Caspar_Tsai — Fri, 24 Apr 2020 09:20:17 GMT

Hi Sigurd,
1). I will check ble_app_hrs_rscs_relay() for more information.
2). Would you please tell me the license for both ble_cus.c, and ble_cus.h in github.com/.../custom_ble_service_example ?
I apply ble_cus.c, and ble_cus.h into my applicaton, and need to know the license for those two file.
If those files are GNU General Public License v3.0, then I am not able to use.

Many thanks.
Caspar

RE: Not able to write 14 Bytes into Queued Writes module

Sigurd — Tue, 14 Apr 2020 10:18:28 GMT

[quote user="Caspar_Tsai"]on_connect() function access null pointer in p_cus->evt_handler(p_cus, &evt); fatal error.[/quote]

Won't the ble_cus_on_ble_evt() just return, and not call on_connect() if the pointer is NULL ?

Snippet:

void ble_cus_on_ble_evt( ble_evt_t const * p_ble_evt, void * p_context)
{
    ble_cus_t * p_cus = (ble_cus_t *) p_context;
    
    NRF_LOG_INFO("BLE event received. Event type = %d\r\n", p_ble_evt->header.evt_id); 
    if (p_cus == NULL || p_ble_evt == NULL)
    {
        return;
    }
    
    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_CONNECTED:
            on_connect(p_cus, p_ble_evt);
            break;

[quote user="Caspar_Tsai"]The application is both central, and peripheral.role.[/quote]

If you are doing concurrent central and peripheral role, you might get some ideas on how to implement that by looking at the ble_app_hrs_rscs_relay() example in the nRF5 SDK.

[quote user="Caspar_Tsai"]Would you please share how to extract crash log, and stack dump from nRF52832 ? and the way to parse stack dump to call-stack ?[/quote]

To get all the information in the call-stack, remove compiler optimization. You should also set DEBUG as a preprocessor symbol.

RE: Not able to write 14 Bytes into Queued Writes module

Caspar_Tsai — Fri, 27 Mar 2020 22:48:33 GMT

Hi Sigurd,

Use ozone to debug, and find out the root cause is NULL pointer causes fatal error.
The application is both central, and peripheral.role.
Both central, and peripheral should have customer_ble_service, however only peripheral role do ble_cus_init(&m_cus, &cus_init);
Due to central-role does not do ble_cus_init(&m_cus, &cus_init), on_connect() function access null pointer in p_cus->evt_handler(p_cus, &evt); fatal error.

Would you please share how to extract crash log, and stack dump from nRF52832 ? and the way to parse stack dump to call-stack ?

Many thanks.
Caspar

RE: Not able to write 14 Bytes into Queued Writes module

Sigurd — Thu, 12 Mar 2020 15:08:54 GMT

Hi,

[quote userid="83078" url="~/f/nordic-q-a/56662/not-able-to-write-14-bytes-into-queued-writes-module/236060"]after caculate RAM(rwx) would be ORIGIN = 0x200028C2, LENGTH = D70E, however nrf_sdh_ble_enable() is 0x200028C0.
Would that be no problem for my app_mem_conf.ld define ?[/quote]

The nrf_sdh_ble_enable() returns the value you should use.

[quote userid="83078" url="~/f/nordic-q-a/56662/not-able-to-write-14-bytes-into-queued-writes-module/236060"]Need to debug why sd_ble_gap_connect() not work even though got NRF_SUCCESS.[/quote]

When sd_ble_gap_connect() returns NRF_SUCCESS, it will start to scan for the device to connect to. If the device is not found, or if it's not possible to connect to the device, it will continue to scan(until timeout, if enabled), and you will not get the the BLE_GAP_EVT_CONNECTED.

[quote userid="83078" url="~/f/nordic-q-a/56662/not-able-to-write-14-bytes-into-queued-writes-module/236216"]Attached ble_cus.zip (ble_wrap_15.c is my application already integrate[/quote]

The zip does not seem to have been attached, only ble_wrap_15.c. If are still having issues with this, please upload the whole project.

[quote userid="83078" url="~/f/nordic-q-a/56662/not-able-to-write-14-bytes-into-queued-writes-module/236216"]sd_ble_gap_connect() return NRF_SUCCESS, please check attached[/quote]

Do you get BLE_GAP_EVT_CONNECTED ?

RE: Not able to write 14 Bytes into Queued Writes module

Caspar_Tsai — Tue, 25 Feb 2020 10:44:58 GMT

Hi Sigurd,

1). After mark "BLE_CUS_DEF(m_cus)", sd_ble_gap_connect() works very well.
//BLE_CUS_DEF(m_cus); /**< Context for the Queued Write module.*/
It would be somewhere not configure properly, and would you please provide me what's item should configure well for intergeate github.com/.../custom_ble_service_example into my application ?

2). Attached ble_cus.zip (ble_wrap_15.c is my application already integratehttps://github.com/bjornspockeli/custom_ble_service_example )

3). sd_ble_gap_connect() return NRF_SUCCESS, please check attached devzone.nordicsemi.com/.../not_5F00_able_5F00_connect_5F00_0227.log
[2020-02-27 09:16:36] Debug : RESP_OK => ble_wrap_connect_to, sd_ble_gap_connect, err_code = 0

Many thanks.
Caspar

RE: Not able to write 14 Bytes into Queued Writes module

Caspar_Tsai — Mon, 24 Feb 2020 16:29:37 GMT

Hi Sigurd,

1). my application print out below logs
ble_stack_init, nrf_sdh_ble_default_cfg_set() = 0, ram_start = 200028C0
ble_stack_init, nrf_sdh_ble_enable() = 0, ram_start = 200028C0
Attached my application "app_mem_conf.ld"
UUID_COUNT = 2
RAM_REDUCE = 16 * UUID_COUNT = 32
MEMORY
{
FLASH (rx) : ORIGIN = 0x26000, LENGTH = 0x5d000
RAM (rwx) : ORIGIN = 0x20002890+RAM_REDUC, LENGTH = 0xD740-RAM_REDUC
}
after caculate RAM(rwx) would be ORIGIN = 0x200028C2, LENGTH = D70E, however nrf_sdh_ble_enable() is 0x200028C0.
Would that be no problem for my app_mem_conf.ld define ?
devzone.nordicsemi.com/.../app_5F00_mem_5F00_conf.ld
2). sd_ble_gap_connect() return NRF_SUCCESS, however my android nrfconnect application not receive any connect message,
Need to debug why sd_ble_gap_connect() not work even though got NRF_SUCCESS.
Did you have any suggestion to get more debug information ?

3). my applicatin scan_timeout is 0x0000 //disables timeout.

4). sd_ble_gap_connect() does not work, after intergate https://github.com/bjornspockeli/custom_ble_service_example into my application.

Many thanks.
Caspar

RE: Not able to write 14 Bytes into Queued Writes module

Sigurd — Mon, 24 Feb 2020 15:42:29 GMT

1) The function sd_ble_enable()/ nrf_sdh_ble_enable() will tell you how much RAM is required to enable the SoftDevice with the current SD configuration. Turn on logging, and the values should be printed in the log.

2) Did sd_ble_gap_connect() return any error-code ? You might also want to set a scan-timout in p_scan_params for sd_ble_gap_connect()

RE: Not able to write 14 Bytes into Queued Writes module

Caspar_Tsai — Mon, 24 Feb 2020 05:30:55 GMT

Hi Nordic,

I use github.com/.../custom_ble_service_example in my application to act as peripheral-role, and it works.
However, my application dose not able to connect other peripheral-role device, while my application do sd_ble_gap_connect to peripheral device.
1). Did you have any idea how many FLASH/RAM should increase while adding a vendor-specific UUID to the BLE stack results in the RAM requirement of the SoftDevice increasing, which we need to take into account ?
2). Did you have any suggestion the way to debug sd_ble_gap_connect not able to connect peripheral problem ?

Now, I'm trying to make RTT logging with J-Link RTT Viewer.

Many thanks.
Caspar

RE: Not able to write 14 Bytes into Queued Writes module

Caspar_Tsai — Thu, 06 Feb 2020 02:37:34 GMT

Hi Sigurd,

Currently, I just want to write a long characteristic in custom ble service.
I found this for reference. Is https://github.com/bjornspockeli/custom_ble_service_example suitable to integrate into my application ?
Would you please give me a reference example code for integration ?

Many thanks
Caspar

RE: Not able to write 14 Bytes into Queued Writes module

Sigurd — Mon, 20 Jan 2020 08:27:09 GMT

Hi,

Your application most likely entered the APP_ERROR_CHECK() with an error code somewhere. You need to debug your application to find the function that returned the error-code, and what error-code that was returned. You should also enable RTT logging(set NRF_LOG_BACKEND_RTT_ENABLED to 1 in sdk_config.h, you might also need to set NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED to 0), and see if you get any output in J-Link RTT Viewer, or Debug Terminal if you are using SES IDE.

Why are you using Queued write module for NUS? As mentioned in this post, queued writes only make sense if you want to synchronize writes to multiple characteristics, so that the change take effect simultaneously. If you just want to write to a long characteristic and have to split it over multiple writes, then you should write with offset instead. That is simpler and has less overhead.

RE: Not able to write 14 Bytes into Queued Writes module

Caspar_Tsai — Fri, 17 Jan 2020 13:46:19 GMT

Hi Nordic,

Wireshark log "0117.pcapng" attachedfor reference.

[Wireshark log information]
[Master Address: 73:e8:6b:a4:9e:9e (73:e8:6b:a4:9e:9e)] <- nrf_connect Android Application
[Slave Address: e6:e7:6e:cf:b4:c1 (e6:e7:6e:cf:b4:c1)] <- nrf52832 wtih my application

1). Master writes 13 Bytes into Slave successfully
[Write 13 Bytes][OK]

2). Master not able to write 14 Bytes into Slave, and lost connection
[Write 14 Bytes][NG]

[0117.pcapng]

devzone.nordicsemi.com/.../0117.pcapng

Many thanks.

Caspar

RE: Not able to write 14 Bytes into Queued Writes module

Caspar_Tsai — Fri, 17 Jan 2020 07:46:06 GMT

Hi Nordic,

My application do gatt_services_init (ble_wrap_15.c) to init qwr, and qwrs.
While nrf_connect write 14 Bytes data into qwr, nrf_connect got "[Server callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)"

Is there any methodology to understand why my application not able to handle 14 Bytes gatt write characteristics ?

"Log 2020-01-17 11_37_48.txt" [nrf_connect android application log]
V 11:37:28.334 Writing request to characteristic 6e400002-b5a3-f393-e0a9-e50e24dcca9e
D 11:37:28.334 gatt.writeCharacteristic(6e400002-b5a3-f393-e0a9-e50e24dcca9e, value=0x3132333435363738393031323334)
D 11:37:32.522 [Server callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
I 11:37:32.522 [Server] Device disconnected
E 11:37:32.538 Error 133 (0x85): GATT ERROR

Many thanks.
Caspar