This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

What changes for mesh dfu in nrf5_SDK_for_Mesh_v4.0.0?

Hello:

I am now working with nrf5_SDK_for_Mesh_v3.0.0 and I try to implement OTA for mesh dfu. However, I found that the v4.0.0 has a dfu_no_serial_nrf52832_xxAA_s132_7_0_1.emProject. Could you please tell what the difference is in the mesh dfu part in it and dfu_nrf52832_xxAA_s132_7_0_1.emProject? Does it mean using no serial version, I can do dfu wireless?

Thank you 

Jin

Parents
  • Hi, 

    The dfu_no_serial project is available on both Mesh SDK v3.0 and SDK v4.0 . It's not new in SDK v4.0

    The main difference in dfu_no_serial_nrf52 and the dfu_nrf52 is that the dfu_nrf52 has support for receiving the image via UART. When the dfu_no_serial can only receive the image via mesh. 

    Note that they are not the bootloader, they are the application. You still need the bootloader for the DFU process to work. 

Reply
  • Hi, 

    The dfu_no_serial project is available on both Mesh SDK v3.0 and SDK v4.0 . It's not new in SDK v4.0

    The main difference in dfu_no_serial_nrf52 and the dfu_nrf52 is that the dfu_nrf52 has support for receiving the image via UART. When the dfu_no_serial can only receive the image via mesh. 

    Note that they are not the bootloader, they are the application. You still need the bootloader for the DFU process to work. 

Children
No Data
Related