Change PHY mode to CODED while connected.

RE: Change PHY mode to CODED while connected.

Daniel — Wed, 24 Apr 2019 13:00:49 GMT

Oh wow. It is working now...

I always used my PCA10056 V0.9.0 2017.10 and V0.9.2 2017.27 and it always crashed while updating PHY to CODED.

NOW i'm using the PCA10056 V1.0.0 2018.45 and it works.. No problems while updating my PHY modes to 1M, 2M and CODED.

Not sure why it works now, I changed nothing. Maybe I can figure out the error, which occurs in the older versions.

Thanks for your help, haakonsh!

RE: Change PHY mode to CODED while connected.

Andy — Wed, 24 Apr 2019 09:18:01 GMT

0x11 isn't invalid data, it's busy.

From the documentation:

* @retval ::NRF_ERROR_BUSY Procedure is already in progress or not allowed at this time. Process pending events and wait for the pending procedure to complete and retry.

RE: Change PHY mode to CODED while connected.

haakonsh — Wed, 24 Apr 2019 08:40:41 GMT

That's strange. What version of the PCA10056 are you using?

NRF_BREAKPOINT_COND recides in the error handler, there should be an error code, line number, and file name available.

RE: Change PHY mode to CODED while connected.

Daniel — Thu, 18 Apr 2019 16:54:28 GMT

I also tested the nordic ble_app_att_mtu_throughput example with two nrf52840 DKs and it seems like I'm running into the same fatal error when changing the PHY mode to CODED.

The peripheral board causing this error..

RE: Change PHY mode to CODED while connected.

Daniel — Thu, 18 Apr 2019 12:44:49 GMT

Okay, found the error now.

err_code=0x000000011 as invalid data.

I fixed an error with my conn_handle parametre and now the phy is changing (I think).

At ble_evt_handler() I get the correct BLE_GAP_EVT_PHY_UPDATE event, logged PHY values are correct, but then the app is running into an error again -> NRF_BREAKPOINT_COND and NO error handler is triggered.

RE: Change PHY mode to CODED while connected.

haakonsh — Wed, 10 Apr 2019 14:06:59 GMT

I suggest you enter into a proper debug session and see what error info is passed to the error handler.

RE: Change PHY mode to CODED while connected.

Daniel — Tue, 09 Apr 2019 11:58:21 GMT

Hmm I don't know where to figure out which error it is without getting a ret_code.

I'm just connected via HTerm and see the logs.

Direct on sd_ble_gap_phy_update(), APP_ERROR_CHECK() never executes.

RE: Change PHY mode to CODED while connected.

Andy — Tue, 09 Apr 2019 11:55:37 GMT

If it crashes and restarts then it's going to an error handler somewhere. Is it crashing directly on sd_ble_gap_phy_update() or in the APP_ERROR_CHECK after that?

RE: Change PHY mode to CODED while connected.

Daniel — Tue, 09 Apr 2019 11:32:32 GMT

I get an app: Fatal error immediately after calling sd_ble_gap_phy_update(), so no error code is returned. App crashes and restarts.

RE: Change PHY mode to CODED while connected.

Andy — Mon, 08 Apr 2019 12:07:53 GMT

What error do you get?