Mesh DFU Fail

Question

Hi ! 
 I use SDK:15.3.0 ,Mesh v3.2.0 and have tried official dfu example which is ok.However, When after I enable marco "MESH_FEATURE_PB_GATT_ENABLED=1 MESH_FEATURE_GATT_PROXY_ENABLED=1" and INIT functions --gap_params_init();conn_params_init(); in Main() ,rebuild ok ,Try serial mesh dfu again ,there is alwalys interupt to stop in the process.The details as follow: 
 What I do:

Fullscreen 
 preparations.txt 
 Download 
 
 Step 1: Generate a DFU file with nrfutil
nrfutil dfu genpkg --application E:Project/Mesh_v3.2.0/nrf5_SDK_for_Mesh_v3.2.0_src/examples/dfu_test/build/dfu_test_nrf52832_xxAA_s132_6.1.1_Debug/dfu_test_nrf52832_xxAA_s132_6.1.1.hex --company-id 0x00000059 --application-id 1 --application-version 11 --key-file private_key.txt --sd-req 0x00B7 --mesh dfu_test.zip

Step 2: Generate a DFU file with nrfutil
"public_key":"9d11e0467262333673dbc6d6fa96795f128bd4970764fe38d9feb07615c3674924cb76362d83ffa7bfe48d9c78c23303509718ed3f9a9a39f5e1b812539cbad3"
(note:just add public_key to json)
python device_page_generator.py -d nrf52832_xxAA -sd "s132_6.1.1"

Step 3: Erase chip memory and flash SoftDevice on all devices
Note Steps 3 to 6 must be executed in order.

Nrfjprog --family nRF52 --program E:Project/Mesh_v3.2.0/nrf5_SDK_for_Mesh_v3.2.0_src/bin/softdevice/s132_nrf52_6.1.1_softdevice.hex --chiperase

Step 4: Flash the serial bootloader on all devices
nrfjprog --family nRF52 --program E:/Project/Mesh_v3.2.0/nrf5_SDK_for_Mesh_v3.2.0_src/bin/bootloader/gccarmemb/mesh_bootloader_serial_gccarmemb_nrf52832_xxAA.hex

Step 5: Flash the first application on all devices
nrfjprog --family nRF52 --program E:/Project/Mesh_v3.2.0/nrf5_SDK_for_Mesh_v3.2.0_src/examples/dfu_test/build/dfu_test_nrf52832_xxAA_s132_6.1.1_Debug/dfu_test_nrf52832_xxAA_s132_6.1.1.hex

Step 6: Flash the device page on all devices and reset the device
nrfjprog --family nRF52 --program E:/Project/Mesh_v3.2.0/nrf5_SDK_for_Mesh_v3.2.0_src/tools/dfu/bin/device_page_nrf52832_xxAA_s132_6.1.1.hex
nrfjprog --family nRF52 --reset

//=======================================================================================//

Transferring the DFU archive over serial with nrfutil:

nrfutil --verbose dfu serial -pkg C:/Users/35273/dfu_test.zip -p com6 -b 115200 --mesh

The Result:

Fullscreen 
 Fail.txt 
 Download 
 
 C:\Users\35273>nrfutil --verbose dfu serial -pkg C:/Users/35273/dfu_test.zip -p com6 -b 115200 --mesh
Upgrading target on com6 with DFU package C:\Users\35273\dfu_test.zip. Flow control is disabled.
Flushing com-port...
Opened com-port
Starting DFU upgrade of type 4, SoftDevice size: 0, bootloader size: 0, application size: 130272
Sending DFU start packet, afterwards we wait for the flash on target to be initialized before continuing.
PC -> target: 0502aabbccdd
target -> PC: 0582aabbccdd
Got echo response
Sending DFU init packet
PC -> target: 1378fdff040fd684dc4e5900000001000b000000
target -> PC: 16a6045900000001000b00000059000000010009000000
target -> PC: 03847800
PC -> target: 1378fdff040fd684dc4e5900000001000b000000
target -> PC: 03847800
PC -> target: 1478fcff0000d684dc4effffffff387f000040000c
target -> PC: 0da201045900000001000b000000
target -> PC: 03847800
Sending firmware file
 [------------------------------------] 1% 00:11:56PC -> target: 1978fcff0100d684dc4e00f0002071630200596302005b630200
target -> PC: 03847800
PC -> target: 1978fcff0200d684dc4e5d6302005f6302006163020000000000
.....
PC -> target: 1978fcff2400d684dc4e3149324a00f03ef831483249324a00f0
target -> PC: 03847800
PC -> target: 1978fcff2500d684dc4e39f832483249334a00f034f832483349
target -> PC: 03847800
PC -> target: 1978fcff2600d684dc4e334a00f02ff833483349344a00f02af8
PC -> target: 1978fcff2600d684dc4e334a00f02ff833483349344a00f02af8
target -> PC: 03847887
PC -> target: 1978fcff2600d684dc4e334a00f02ff833483349344a00f02af8
PC -> target: 1978fcff2600d684dc4e334a00f02ff833483349344a00f02af8
target -> PC: 03844a82
PC -> target: 1978fcff2600d684dc4e334a00f02ff833483349344a00f02af8


Failed to upgrade target. Error is: Device returned status code ERROR_INVALID_DATA (135) on a DFU data packet.

Possible causes:
- bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
- baud rate or flow control is not the same as in the target bootloader.
- target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.
Closing serial port...

I have been confused for a long time .So Publish this for help ,Thanks in advance.