How to submit bugs on the pc-ble-driver?

RE: How to submit bugs on the pc-ble-driver?

Einar Thorsrud — Thu, 15 Oct 2020 08:12:48 GMT

Yes, this is unfortunately not fixed yet. There is a ticket open for it though, so it should be updated at some point.

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Wed, 14 Oct 2020 10:20:43 GMT

I have just downloaded version 4.1.2. They did not fix the documentation.

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Fri, 17 Apr 2020 17:31:13 GMT

If I could get a working project I could help debug this.

RE: How to submit bugs on the pc-ble-driver?

Einar Thorsrud — Fri, 17 Apr 2020 15:17:51 GMT

Hi,

[quote user="brianreinhold"]Does any engineer writing the pc-ble-driver HAVE a VS project that I could get?[/quote]

No, not according to the answer I have gotten when I asked.

[quote user="brianreinhold"]More serious at this stage is solving the problem that I cannot reset the CCCDs from the saved info. This prevents compliant collectors from getting measurements on bonded reconnects and prevents me from doing service changed invocations.[/quote]

This was reported as a bug internally, but it hs not been resolved yet, unfortunately.

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Thu, 16 Apr 2020 11:56:32 GMT

Does any engineer writing the pc-ble-driver HAVE a VS project that I could get? More serious at this stage is solving the problem that I cannot reset the CCCDs from the saved info. This prevents compliant collectors from getting measurements on bonded reconnects and prevents me from doing service changed invocations.

The redistributable problem I have solved. I finally found all 67 dlls I needed to copy with the exe.

RE: How to submit bugs on the pc-ble-driver?

Einar Thorsrud — Thu, 16 Apr 2020 09:51:20 GMT

I understand. However, the pc-ble-driver is cross-platform and therefore we use a cross-platform built system for it.

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Sat, 11 Apr 2020 14:58:43 GMT

According to what I read in the instructions, after I download tons of third party packages and clog up my paths with all these requirements, the line you give above will build the library, not make a VS project. I want a VS project for two reasons, to build a static library that has no microsoft redistributables (the one available requires them) so I can compile a static exe without the need for an end user to install redistributables, and I want to try and debug two serious problems with the driver, one of which makes it non compliant with the BTLE standards.

The cost is great and I want to be absolutely sure that doing such will give me a VS project. Then I can go through the efforts of trying to clean up the mess left by the installs (such installs never clean up completely; that's a price one always needs to pay).

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Tue, 10 Mar 2020 13:40:54 GMT

I was hoping someone had a completed project. I tried those instructions some time ago and gave up after two weeks. It required that one download a voluminous amount of third party software which I really don't want to do. That garbage never really cleans up after itself when you try to uninstall it.

RE: How to submit bugs on the pc-ble-driver?

Einar Thorsrud — Tue, 10 Mar 2020 12:52:02 GMT

Hi,

You can generate a VS project by following this guide, but use the cmake generator for Visual Studio instead of Ninja, like this:

cmake .. -G "Visual Studio 15 2017 Win64"

(I do not have any updates on the issue itself.)

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Tue, 10 Mar 2020 08:25:51 GMT

Any news on an update? Perhaps a pre-written VS project to build the driver myself?

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Wed, 19 Feb 2020 18:14:42 GMT

It is possible someone there can configure the pc-ble-driver as a Visual Studio project so I can debug some of these issues myself? Someone there must have one!

RE: How to submit bugs on the pc-ble-driver?

Einar Thorsrud — Wed, 19 Feb 2020 15:11:20 GMT

I see. I have reported it internally so that it can be fixed in a future release.

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Tue, 18 Feb 2020 12:26:28 GMT

I am talking about the read. I don't need this feature for a write. This is an issue I get when the client READS one of my characteristics!

RE: How to submit bugs on the pc-ble-driver?

Einar Thorsrud — Tue, 18 Feb 2020 09:12:43 GMT

[quote user="brianreinhold"]

This is from the ble_gatts.h file supplied with the latest build of the pc-ble-driver available on line. Since the method has the 'adapter_t' parameter, it is clearly for the driver.

The latest version available is nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib

[/quote]

I see. But this note is valid for READ, not for WRITE. For write, there is a relevant comment in the declaration of ble_gatts_authorize_params_t:

  uint8_t           update : 1;         /**< If set, data supplied in p_data will be used to update the attribute value.
                                             Please note that for @ref BLE_GATTS_AUTHORIZE_TYPE_WRITE operations this bit must always be set,
                                             as the data to be written needs to be stored and later provided by the application. */

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Mon, 17 Feb 2020 12:50:47 GMT

The only documentation that exists is from the the h-files

/**@brief Respond to a Read/Write authorization request.
 *
 * @note This call should only be used as a response to a @ref BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST event issued to the application.
 *
 * @mscs
 * @mmsc{@ref BLE_GATTS_QUEUED_WRITE_NOBUF_AUTH_MSC}
 * @mmsc{@ref BLE_GATTS_QUEUED_WRITE_BUF_AUTH_MSC}
 * @mmsc{@ref BLE_GATTS_QUEUED_WRITE_NOBUF_NOAUTH_MSC}
 * @mmsc{@ref BLE_GATTS_READ_REQ_AUTH_MSC}
 * @mmsc{@ref BLE_GATTS_WRITE_REQ_AUTH_MSC}
 * @mmsc{@ref BLE_GATTS_QUEUED_WRITE_QUEUE_FULL_MSC}
 * @mmsc{@ref BLE_GATTS_QUEUED_WRITE_PEER_CANCEL_MSC}
 * @endmscs
 *
 * @param[in] conn_handle                 Connection handle.
 * @param[in] p_rw_authorize_reply_params Pointer to a structure with the attribute provided by the application.
 *
 * @note @ref ble_gatts_authorize_params_t::p_data is ignored when this function is used to respond
 *       to a @ref BLE_GATTS_AUTHORIZE_TYPE_READ event if @ref ble_gatts_authorize_params_t::update
 *       is set to 0.
 *
 * @retval ::NRF_SUCCESS               Successfully queued a response to the peer, and in the case of a write operation, Attribute Table updated.
 * @retval ::BLE_ERROR_INVALID_CONN_HANDLE Invalid Connection Handle.
 * @retval ::NRF_ERROR_BUSY            The stack is busy, process pending events and retry.
 * @retval ::NRF_ERROR_INVALID_ADDR    Invalid pointer supplied.
 * @retval ::NRF_ERROR_INVALID_STATE   Invalid Connection State or no authorization request pending.
 * @retval ::NRF_ERROR_INVALID_PARAM   Authorization op invalid,
 *                                         handle supplied does not match requested handle,
 *                                         or invalid data to be written provided by the application.
 * @retval ::NRF_ERROR_TIMEOUT There has been a GATT procedure timeout. No new GATT procedure can be performed without reestablishing the connection.
 */
SVCALL(SD_BLE_GATTS_RW_AUTHORIZE_REPLY, uint32_t, sd_ble_gatts_rw_authorize_reply(adapter_t *adapter, uint16_t conn_handle, ble_gatts_rw_authorize_reply_params_t const *p_rw_authorize_reply_params));

This is from the ble_gatts.h file supplied with the latest build of the pc-ble-driver available on line. Since the method has the 'adapter_t' parameter, it is clearly for the driver.

The latest version available is nrf-ble-driver-sd_api_v6-mt-static-4_1_1.lib

The documentation may be incorrect, but that is all I have to go by. However, its an easy work-a-round, just put in the value and be done with it. However, not being able to reset the CCCDs is a critical issue that I cannot work around. I cannot write them myself though I wish I could right now!

RE: How to submit bugs on the pc-ble-driver?

Einar Thorsrud — Mon, 17 Feb 2020 12:23:25 GMT

Hi,

[quote user="brianreinhold"]the documentation on the BLE_GATTS_AUTHORIZE_TYPE_WRITE states that IF I set the update parameter to 0 then I need not set the value; the current value is to be used.[/quote]

Where do you see that? Which pc-ble-driver version and which SoftDevice version do you use?

RE: How to submit bugs on the pc-ble-driver?

brianreinhold — Fri, 14 Feb 2020 14:47:02 GMT

First, the documentation on the BLE_GATTS_AUTHORIZE_TYPE_WRITE states that IF I set the update parameter to 0 then I need not set the value; the current value is to be used. However, that is not the behavior. If I do NOT set the value, the client read does not work. Fortunately the bug is not too serious, because I can just set the value to the current value. It does not prevent me from performing the operations I need to do and interoperating with clients

RE: How to submit bugs on the pc-ble-driver?

Einar Thorsrud — Fri, 14 Feb 2020 14:36:51 GMT

Hi,

1. I suggest we continue in this thread regarding the issue with sd_ble_gatts_sys_attr_set().

2. In what context do you see this? If only for BLE_GATTS_AUTHORIZE_TYPE_WRITE, then this is expected and in line with the API documentation.

[quote user=""]I have posted these problems to the forum for some time now but its probably better to post them directly to the pc-ble-driver development team. Looked on git-hub but could not find a way to do it.[/quote]

Bugs for the pc-ble-driver should be reported here on DevZone.