Hi Fred, On Tue, Feb 05, 2019 at 02:25:43PM -0500, Copper Dr wrote: > I'm trying to figure out how to decode these disconnections. > > Reason 688 (0x02B0) and 573 (0x023D) > > I checked > http://mynewt.apache.org/latest/network/docs/ble_hs/ble_hs_return_codes.html > and the disconnect code does not make any sense. > > The 573 is the one I'm really interested in it happened just before 65,535 > commands were sent and is repeatable.
I agree - 688 (0x2b0) does not make sense. This is not a valid error code, so there must be some memory corruption or some other bug at play here. As you noticed, 573 (0x23d) is a legitimate error code: BLE_ERR_CONN_TERM_MIC. I don't know if there is a relation to the number 65535, but that would be an interesting bug! I will let one of the controller experts chime in. Chris > > > disconnect; reason=688 handle=1 our_ota_addr_type=0 > our_ota_addr=01:02:03:04:05:06 our_id_addr_type=0 > our_id_addr=01:02:03:04:05:06 peer_ota_addr_type=1 > peer_ota_addr=cb:a9:46:52:45:44 peer_id_addr_type=1 > peer_id_addr=cb:a9:46:52:45:44 conn_itvl=40 conn_latency=0 > supervision_timeout=256 encrypted=1 authenticated=1 bonded=1 > > disconnect; reason=573 handle=2 our_ota_addr_type=0 > our_ota_addr=01:02:03:04:05:06 our_id_addr_type=0 > our_id_addr=01:02:03:04:05:06 peer_ota_addr_type=1 > peer_ota_addr=cb:a9:42:31:30:30 peer_id_addr_type=1 > peer_id_addr=cb:a9:42:31:30:30 conn_itvl=40 conn_latency=0 > supervision_timeout=256 encrypted=1 authenticated=1 bonded=1 > > > Thanks, > > Fred Angstadt
