I want to insert a DFU module through BLE in my old ble project to upgrade my nrf5340 image

[zhouhaifang]

    i have look for many DFU examples in NCS1.5.0 , but samples are Abstract ，and can not to start . a ble test  app in phone have a menu that  can  send file to nrf5340 through ble ,  when ble of nrf5340 receive this file  ,file can as  a new image.

[zhouhaifang]

Simon thank you!!

 i place v1.5.1 directly in diak D ,all error like "can not find files"  disappear . I have tested your project . i first load D:\v1.5.1\nrf\samples\bluetooth\peripheral_uart\build\hci_rpmsg\zephyr\merged_CPUNET.hex in nrf5340 net core ,then load merged.hex in nrf5340 app core .run the program ,find that nrf5340 can use BLE  send uart data to app .but when app   send data to nrf5340 through ble ,nrf5340 reset.

[Simon]

zhouhaifang said:

i place v1.5.1 directly in diak D ,all error like "can not find files"  disappear . I have tested your project . i first load D:\v1.5.1\nrf\samples\bluetooth\peripheral_uart\build\hci_rpmsg\zephyr\merged_CPUNET.hex in nrf5340 net core ,then load merged.hex in nrf5340 app core .run the program ,find that nrf5340 can use BLE  send uart data to app .but when app   send data to nrf5340 through ble ,nrf5340 reset.

I read your reply earlier today, then I got back to this ticket now and answered it right away without reading the reply again (I forgot the question and assumed you still struggled with the DFU). Sorry about that. But it seems like you were asking about something else: nRF5340 Resets when the app sends data to it.

I will look into this issue tomorrow

[Simon]

zhouhaifang said:

send uart data to app .but when app   send data to nrf5340 through ble ,nrf5340 reset.

I was not able to reproduce this. I did the following:

• Apply the patch to NCS v1.5.1
• Build and flash the peripheral_uart project
  • west build -b nrf5340dk_nrf5340_cpuapp && west flash
• Open a putty terminal window and reset the chip

• Connect to it from the phone and open the RX Characteristic:

• Then I can see the same message in the terminal, and the chip didn't reset

Best regards,

Simon