I use example/dfu When trying mesh dfu, get assert 88972 from softwaredevice,how can i reslove it?

RE: I use example/dfu When trying mesh dfu, get assert 88972 from softwaredevice,how can i reslove it?

Kai777 — Tue, 14 Dec 2021 04:33:27 GMT

Thandk you for your reply and suggestion.

I will do it

RE: I use example/dfu When trying mesh dfu, get assert 88972 from softwaredevice,how can i reslove it?

Hung Bui — Mon, 13 Dec 2021 13:01:39 GMT

Hi Kai,

Does that reflect your development board LF crystal ? I don't think having the lower NRF_SDH_CLOCK_LF_ACCURACY would be the actual reason for the issue.

Please double check with the softdevice version mismatch.

RE: I use example/dfu When trying mesh dfu, get assert 88972 from softwaredevice,how can i reslove it?

Kai777 — Sun, 12 Dec 2021 13:30:01 GMT

in other development board(not nordic DK) I try to change

NRF_SDH_CLOCK_LF_ACCURACY

from 7 ->8 in sdk_config.h,the problem was resloved.

But i do not konw the reson.

RE: I use example/dfu When trying mesh dfu, get assert 88972 from softwaredevice,how can i reslove it?

Hung Bui — Fri, 03 Dec 2021 12:53:40 GMT

Hi Kai,

I suspect that it may be related to that you changed the S140 version but didn't update the application/bootloader. Please try to test again with S140 v7.2.0 and let us know which exact issue you have. Please give us all the command line script you used.

RE: I use example/dfu When trying mesh dfu, get assert 88972 from softwaredevice,how can i reslove it?

Kai777 — Fri, 03 Dec 2021 10:12:12 GMT

Hi Hung Bui.

Thanks for your reply.

the application/bootloader do not change and normal application(dfu) also exits(same problem).

I try use S140 v7.2.0,but i can not make mesh_dfu.zip with nrfutil

I found that the problem was related to our development board,may be something wrong with serial port.

RE: I use example/dfu When trying mesh dfu, get assert 88972 from softwaredevice,how can i reslove it?

Hung Bui — Thu, 02 Dec 2021 10:30:28 GMT

Hi Kai Qi,
Did you do any modification to the application and/or the bootloader ?
The assertion at 88972 suggests that it's a RADIO interrupt issue. Could be related to interrupt level configuration. Please make sure you followed the guide here.

Do you have any problem testing a normal application, without the bootloader ? Any reason you want to use S140 v7.0.1 instead of S140 v7.2.0 . I assume you have updated the application and bootloader so that it uses S140 v7.0.1 header files instead of S140 v7.2.0