nRF52833 cannot interconnect and communicate with BLE chip of Realtek

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

Sigurd — Mon, 14 Nov 2022 11:18:32 GMT

[quote user="panypan"]In addition, a good news that the customer has solved this problem used ncs (modify base on : ncs\v2.0.0\nrf\samples\bluetooth\central_uart).[/quote]

Great! 😃

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

panypan — Mon, 14 Nov 2022 10:51:30 GMT

Hi Sigurd,

Sorry, I've changed this too.

In addition, a good news that the customer has solved this problem used ncs (modify base on : ncs\v2.0.0\nrf\samples\bluetooth\central_uart).

Thanks,

Pany

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

Sigurd — Mon, 14 Nov 2022 10:01:22 GMT

Try to change this:

uint32_t ble_hrs_c_init(ble_hrs_c_t * p_ble_hrs_c, ble_hrs_c_init_t * p_ble_hrs_c_init)
{
    VERIFY_PARAM_NOT_NULL(p_ble_hrs_c);
    VERIFY_PARAM_NOT_NULL(p_ble_hrs_c_init);

    ble_uuid_t hrs_uuid;

    hrs_uuid.type = BLE_UUID_TYPE_BLE;
    hrs_uuid.uuid = BLE_UUID_HEART_RATE_SERVICE;

    p_ble_hrs_c->evt_handler                 = p_ble_hrs_c_init->evt_handler;
    p_ble_hrs_c->error_handler               = p_ble_hrs_c_init->error_handler;
    p_ble_hrs_c->p_gatt_queue                = p_ble_hrs_c_init->p_gatt_queue;
    p_ble_hrs_c->conn_handle                 = BLE_CONN_HANDLE_INVALID;
    p_ble_hrs_c->peer_hrs_db.hrm_cccd_handle = BLE_GATT_HANDLE_INVALID;
    p_ble_hrs_c->peer_hrs_db.hrm_handle      = BLE_GATT_HANDLE_INVALID;

    return ble_db_discovery_evt_register(&hrs_uuid);
}

to this as well:

uint32_t ble_hrs_c_init(ble_hrs_c_t * p_ble_hrs_c, ble_hrs_c_init_t * p_ble_hrs_c_init)
{
    VERIFY_PARAM_NOT_NULL(p_ble_hrs_c);
    VERIFY_PARAM_NOT_NULL(p_ble_hrs_c_init);

    ble_uuid_t hrs_uuid;

    hrs_uuid.type = BLE_UUID_TYPE_BLE;
    hrs_uuid.uuid = 0xFF12;

    p_ble_hrs_c->evt_handler                 = p_ble_hrs_c_init->evt_handler;
    p_ble_hrs_c->error_handler               = p_ble_hrs_c_init->error_handler;
    p_ble_hrs_c->p_gatt_queue                = p_ble_hrs_c_init->p_gatt_queue;
    p_ble_hrs_c->conn_handle                 = BLE_CONN_HANDLE_INVALID;
    p_ble_hrs_c->peer_hrs_db.hrm_cccd_handle = BLE_GATT_HANDLE_INVALID;
    p_ble_hrs_c->peer_hrs_db.hrm_handle      = BLE_GATT_HANDLE_INVALID;

    return ble_db_discovery_evt_register(&hrs_uuid);
}

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

panypan — Fri, 11 Nov 2022 08:59:55 GMT

Hi,

Only change this:

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

Sigurd — Thu, 10 Nov 2022 15:43:50 GMT

Hi,

Did you do any other changes? e.g. in ble_hrs_c.c ?

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

panypan — Thu, 10 Nov 2022 12:53:43 GMT

Hi Sigurd,

Sorry for the late reply. The attachment is the main.c .

Pany

devzone.nordicsemi.com/.../35437422.main.c

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

Sigurd — Wed, 09 Nov 2022 16:18:04 GMT

Hi,

Could you attach your main.c file?

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

panypan — Tue, 08 Nov 2022 02:03:02 GMT

Hi sigurd,

The service (0xFF12) cannot be found after modifying according to your suggestions. The attachment is the output log.

Best regards,

Pany

devzone.nordicsemi.com/.../ble_5F00_app_5F00_hrs_5F00_c_5F00_0xFF12_5F00_log.txt

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

panypan — Mon, 07 Nov 2022 09:22:40 GMT

Hi Sigurd,

Thank you for your reply!

Yes, I also think so they have not registered it with the Bluetooth SIG.

I'll try your method and modify based on ble_app_hrs_c.

Best regards,

Pany

RE: nRF52833 cannot interconnect and communicate with BLE chip of Realtek

Sigurd — Sun, 06 Nov 2022 17:29:12 GMT

Hi,

[quote user=""]

UUID types: 128bit

UUID = {0xFB, 0x34, 0x9B, 0x5F, 0x80, 0x00, 0x00, 0x80, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00}

[/quote]

This is not a vendor defined 128-bit UUID, this is the base UUID used by the 16-bit UUIDs defined by Bluetooth SIG.

[quote user=""]0xFF12 [/quote]

I can't find 0xFF12 in the Assigned Numbers document here, https://www.bluetooth.com/specifications/assigned-numbers/ , so it's seems like they have not registered it with the Bluetooth SIG...

Try using this scan-filter:

    #define TARGET_UUID 0xFF12

ble_uuid_t uuid =
    {
        .uuid = TARGET_UUID,
        .type = BLE_UUID_TYPE_BLE,
    };

    err_code = nrf_ble_scan_filter_set(&m_scan,
                                       SCAN_UUID_FILTER,
                                       &uuid);
    APP_ERROR_CHECK(err_code);

And use e.g. ble_app_hrs_c as an template example on how to create a central that connects to a peripheral that have a 16-bit UUID service(BLE_UUID_TYPE_BLE).