OTA over serial failure| sdk 15.2

[Somesh Burkule]

Hello Everyone,

I am using nrf52832 and sdk 15.2 for ota over serial. I have made bootloader for OTA over UART and tested same with nrfutil using my dfu package file. firmware is upgraded successfully and  working fine.

Now I need to upgrade firmware using host MCU. I tried sending dfu package file( .zip ) to nrf52832 over UART using slip librairy to upgrade firmware but it is not working.

Is there any compulsion to send Ping packet, PNR, MTU Packet, init packet, application and bootloader separately over UART?

Can we send directly dfu package created through nrfutil to nrf52832 from other MCU over UART?

Kindly suggest me right approach.

[Edvin]

Hello,

 

Now I need to upgrade firmware using host MCU. I tried sending dfu package file( .zip ) to nrf52832 over UART using slip librairy to upgrade firmware but it is not working.

 From this, I interpret that you want to drag'n'drop from a computer, isn't that right? Is that the final way you want to do it? Or do you want to program the nRF From a microcontroller on a PCB? 

What HW are you running on? Is it a DK, or is it a custom PCB?

BR,

Edvin

[Somesh Burkule]

No, I don't want drag and drop from computer. I want upgrade nrf from other MCU through UART. I have custom PCB. Kindly help for the same.

[Edvin]

Then you need to follow the same behavior as nrfutil does. This protocol is described in the documentation on infocenter here and here, and probably more in detail in the github repository for nrfutil. 

That are the protocols that you need to use to transfer a new application to the nRF via the serial bootloader.

BR,
Edvin

[Somesh Burkule]

I am following UART DFU Master code given here and implemented but not getting results.

is there any documentaion for the same code?

I am using baud rate 115200, HW flow control disabled. sending image.hex file as per MTU size.

[Edvin]

Can you describe for me how you proceeded? Please note that this is not an official example from Nordic. You can use it as a reference, but there is no guarantee that it works. You should really familiarize yourself with the uart protocol that nrfutil uses, and understand what is happening in the example that you link to.

 

Somesh Burkule said:

but not getting results.

 What is happening? Does it run at all? does it start the DFU? Does it finish?

does it work if you transfer the same image via nrfutil?

BR,

Edvin

[Somesh Burkule]

I have made code in c same as given example. first sending init packet and then image but not getting any response from nrf. I also written simple UART ping packet and sent over UART but receiving garbage data continuously. 

As I uploaded dfu package through nrfutil it works.

Can we send directly DFU package file through UART?

[Edvin]

Somesh Burkule said:

Can we send directly DFU package file through UART?

 

You need the init packet first, if that was the question.

I suggest that you rather dig into why it doesn't respond to the ping request. Have you tried to perform the DFU with different number of --verbose in the command? It will print more info the more "--verbose" commands you use in the DFU command.

e.g.:

nrfutil --verbose --verbose --verbose --verbose dfu serial -pkg dfu_image.zip -p COM48 -b 115200

will print all the data going over the UART.

Have you tried to analyze the UART coming from your master? Is there any data on the line? Is it anything coming back on the UART RX? Are both sides using the same baudrate?

BR,

Edvin

[Somesh Burkule]

Yes I will check for ping request response. also with different verbose in command.

there is data on Tx line of master but on Rx, there is garbage data coming contunuously. baud rate also same on both side.

[Somesh Burkule]

Does it require hardware flow control enabled?

[Edvin]

If your bootloader requires it. It is recommended, since the bootloader needs to save all the data to flash. Since this takes some time, you either need to use flow control, or you need to have some delay between the packets, so that the nRF has time to save all the data.