Meizu M2 bricks nrf51822

RE: Meizu M2 bricks nrf51822

anna — Sat, 10 Mar 2018 07:48:02 GMT

Hi，I have the same problem with you .Can you do me a faver ??Thank you very much .

RE: Meizu M2 bricks nrf51822

Darrew — Thu, 28 Dec 2017 15:05:26 GMT

I have posted a follow-up question.

RE: Meizu M2 bricks nrf51822

Petter Myhre — Fri, 06 Oct 2017 09:25:25 GMT

It is very rare, I asked the other guys here, I they haven't experienced any phones using that address type.

RE: Meizu M2 bricks nrf51822

Sergey — Fri, 06 Oct 2017 07:38:37 GMT

Thank you for explaining!

It's bad, that we did not take into account the presence of this type of address on the phones. What is the tendency of using such types of addresses in BLE devices? Do they occur more often or less often?

RE: Meizu M2 bricks nrf51822

Petter Myhre — Wed, 04 Oct 2017 10:04:16 GMT

You cannot whitelist a random non-resolvable address. It is random, and you cannot resolve it. If you were to put the address into the whitelist, the device would change its address to something random, and then you would filter out an address of a known device.

RE: Meizu M2 bricks nrf51822

Sergey — Wed, 04 Oct 2017 09:51:56 GMT

Ideally i want to whitelist this device like everyone else (because our device works only in whitelist advertising). But is there such an opportunity?

I do not understand well the mechanism of operation of devices with this type of address, because this type not very commonly used and information on it is not much.

RE: Meizu M2 bricks nrf51822

Petter Myhre — Wed, 04 Oct 2017 08:54:14 GMT

Yes, BLE_ERROR_GAP_INVALID_BLE_ADDR is returned because BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_NON_RESOLVABLE is an invalid address type to have in a whitelist. What kind of behavior do you want when you have bonded with a device with this address type? Do you want to whitelist without this device? Do you want to whitelist at all?

RE: Meizu M2 bricks nrf51822

Sergey — Wed, 04 Oct 2017 07:58:07 GMT

If you want, i can send a .hex file with full flash memory of my chip (sd 130 V2 + app (standard Nordic_Keyboard) + bad bond data from Meizu M2).

RE: Meizu M2 bricks nrf51822

Sergey — Wed, 04 Oct 2017 07:56:07 GMT

I try to repeat this case in SDK12.3 (Nordic keyboard example). Now after bond with Meizu and reset, i catch a Error with code 0x3202 in function

pm_whitelist_get(whitelist_addrs, &addr_cnt,
                                    whitelist_irks,  &irk_cnt);

in BLE_ADV_EVT_WHITELIST_REQUEST event.

This is place in id_manager.c file, where error returns:

        if ((addr_type != BLE_GAP_ADDR_TYPE_PUBLIC) &&
        (addr_type != BLE_GAP_ADDR_TYPE_RANDOM_STATIC))
    {
        // The address shared by the peer during bonding can't be used for whitelisting.
        return BLE_ERROR_GAP_INVALID_BLE_ADDR;
    }

RE: Meizu M2 bricks nrf51822

Petter Myhre — Wed, 04 Oct 2017 06:34:35 GMT

This seems to be a bug in the device manager, see this, it should not return a whitelist with the address type BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_NON_RESOLVABLE in it, that doesn't really make sense. I seems it is fixed in Peer Manager in SDK 12, maybe you can use that or migrate to a newer SDK? Or port a newer library of Peer Manager back to SDK 11.

RE: Meizu M2 bricks nrf51822

Sergey — Tue, 03 Oct 2017 02:49:06 GMT

Yes, function sd_ble_gap_adv_start() return 0x07. Problem in whitelist.

adv_params.p_whitelist = &m_whitelist;

This string is from function ble_advertising_start. I attached to question screen of debugger window with variable m_whitelist after try to bond with Meizu M2 (and reset).

RE: Meizu M2 bricks nrf51822

Petter Myhre — Mon, 02 Oct 2017 11:20:56 GMT

The symptoms don't seem to be the same, but I guess it could be related. Which function is returning NRF_ERROR_INVALID_PARAM? sd_ble_gap_adv_start()? If so, which params are you giving to this function when NRF_ERROR_INVALID_PARAM is returned?