nrf52832 serial dfu mode implementation

RE: nrf52832 serial dfu mode implementation

Vaibhav_Bansal — Thu, 27 Feb 2020 08:15:25 GMT

In above process I was doing follow the steps, but during execution of .dat file i go no response from the NRF, can you help me out with the possible reasons of no response and also there is no error with the packet transmission.

The procedure I had followed:

1. Set PRN - got success

2. Get MTU - got success

3. Create Object. - got success

4. Write data to object - got success

5. Calculate checksum - got success and verified

6. Execute - no response

RE: nrf52832 serial dfu mode implementation

Goudra — Fri, 18 Jan 2019 17:52:18 GMT

Hi,

Please let me know your suggestion for below query

https://devzone.nordicsemi.com/f/nordic-q-a/42731/nrf52-serial-dfu-file-loading-sequence

Thanks,

Basava.

RE: nrf52832 serial dfu mode implementation

Einar Thorsrud — Mon, 14 Jan 2019 14:23:51 GMT

Hi Basavanagouda,

That 0xC0 is the SLIP code for identifying the beginning and end of a packet frame. So that is only related to UART over USB.

Einar

RE: nrf52832 serial dfu mode implementation

Goudra — Fri, 11 Jan 2019 15:56:50 GMT

Hi Einar,

Thank you for the response and its helps us lot.

6. Where do you see that there is always a 0xC0 in the end of an init packet?

devzone.nordicsemi.com/.../btbin.htm

We captures data while sending example firmware from nrfutils to board. Each sent and rx packets are ending with 0xC0.

please check the end of the file you can see Blue and red colored data. Blue represents Tx data from the nrfutil and Red is Rx response from the device.

Thanks and regards,

Basavanagouda.

RE: nrf52832 serial dfu mode implementation

Einar Thorsrud — Fri, 11 Jan 2019 13:55:00 GMT

Hi Basavanagouda,

The whole serial DFU flow is shown in the sequence charts for the Serial transport layer.

1. There is no need to implement the ping packet. It can be useful for testing though, as you can use it to see if you have a working connection with the bootloader on the nRF.

2. Packet Receipt Notification (PRN) is used to acknowledge packet reception. It is not needed if you are using a reliable link (UART can probably be considered reliable here).

3. MTU is the maximum transmission unit (think of it as the maximum packet size). It is covered by the serial transport layer documentation. You can set a fixed number as long as you know that it is not too large for the device you are upgrading (which you can know if you are making both).

4. All opcodes are listed in a table in the DFU protocol documentation.

5. The .dat file contains the init packet, which is required. This contains version info etc. and is signed. The DFU process will only commence if the init packet validation is successful.

6. Where do you see that there is always a 0xC0 in the end of an init packet?

7. The firmware is transferred as raw binary (but split up). So no particular format as such.

8. PRN is not required.

9. No.