Mesh assert when using a Google Pixel 3 phone

[Andreas]

There is a mesh assert in our mesh application when using a Google Pixel 3 phone (Android 10). The error occurs as soon as the device connects for the first time in the nRF Mesh app.

<t:    60.250>, app_housekeeper.c,  329, Mesh assert at 0x000460E8 (:0)

Using addr2line I get this output:

$ addr2line -e concept.elf 0x000460E8
app_tvs_gatt.c:625 (discriminator 1)

Here is app_tvs_gatt.c, line 625:

NRF_MESH_ERROR_CHECK(sd_ble_gap_phy_update(p_ble_evt->evt.gap_evt.conn_handle, &phys));

When using a Samsung Galaxy S9 (Android 9) phone everything works without any problems.

The error seems to come from the softdevice. We are using s140_nrf52_7.0.1_softdevice.hex on an nRF52840_xxAA device.

NRF SDK: 16.0.0
Mesh SDK: 3.2.0

Is there any solution for this problem?

Regards,
Andreas

[Joakim Jakobsen]

Hi again.

The nRF Mesh app is mainly tested using the Pixel 3 on Android 10 so this should work out of the box.

Could you tell me what FW you are running on the nRF? Have you tested using an example from our nRF5 SDK for Mesh, i.e the light switch examples. Do you see any errors using our examples?

Regards,
Joakim

[Andreas]

Hi Joakim,

I could use light_switch_server_nrf52840_xxAA_s140_6_1_1.emProject without any problems using the same Pixel 3. The problem occurs while running our own application.

Regards,

Andreas

[Joakim Jakobsen]

Ok, so the problem shouldn't be the phone.

Before we investigate the assert, could you test using the supported combination of SDK versions?

nRF5 SDK for Mesh v.3.2.0 supports nRF5 SDK v.15.3.0 and I can see that you are using v.16.0.0. If you want to use nRF5 SDK v16.0.0, you should use nRF5 SDK for Mesh v.4.0.0.