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

[Kai777]

Hello,

    Fllow the guide of Configuring and performing DFU over Mesh,I am trying use dfu update my application program.After i program software device/bootloader/app(dfu example)/device page and then reset the target board.About 10 second later,i get assert 88972 from software device.But I can get map file of software device,so i can not location the assert.

Environment：

nrf52840, s140, nrf52-7,0,1

  Jlink Logs:

00> <t:          3>, main.c,  227, ----- Bluetooth Mesh DFU Example -----
00> <t:      10833>, nrf_mesh_dfu.c,  753, Version info: BL(ver, id): 0x01 0x01 SD: 0x00CA
00> <t:      10838>, nrf_mesh_dfu.c,  755, Version info: APP company: 0x00000059 id: 0x0001 version: 0x00000001
00> <t:      10862>, serial_handler_prov.c,  267, Generating encryption keypair...
00> <t:      15628>, main.c,  233, Initialization complete!
00> <t:      20335>, main.c,  254, Enabling serial interface...
00> <t:      20339>, mesh_app_utils.c,   66, Device UUID (raw): E299C627375747069B2463F3136E68DE
00> <t:      20343>, mesh_app_utils.c,   67, Device UUID : E299C627-3757-4706-9B24-63F3136E68DE
00> <t:      20355>, nrf_mesh_dfu.c,  554,   RADIO TX! SLOT 0, count 15, interval: periodic, handle: FFFE
00> <t:      20361>, nrf_mesh_dfu.c,  593,   SERIAL TX (type: 65534)
00> <t:      20369>, main.c,  262, DFU example started!
00> <t:     414490>, app_error_weak.c,   96, Softdevice assert: 88972:0

Appeal:

How can i get the map file match software devices?

how can i reslove it?

Thanks!

[Hung Bui]

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 

[Kai777]

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.

[Hung Bui]

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. 

[Kai777]

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.

[Hung Bui]

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. 

[Kai777]

Thandk you for your reply and suggestion.

I will do it