When i use nrfutil to perform DFU it is passed, but when i send it through STM32 dev kit it Hash validation failed. but however i can see the CRC is correct.
When i use nrfutil to perform DFU it is passed, but when i send it through STM32 dev kit it Hash validation failed. but however i can see the CRC is correct.
Hi,
The question is a bit short on information, but I take it you have made your own serial DFU controller implementation running on the STM32, then? It is difficult to say what is the problem, but there must be a difference in the sequence when you use your implementation and when you use nrfutil. Have you compared them? What is the difference?
Hi Einar,
Yes we are trying to implement DFU from STM32 to nRF. When the same package is transferred through the PC using nrfutil, it is always successful. But when the same package is transferred from STM32 i see failure. but CRC is correct.
5. DFU fails with <warning> nrf_dfu_serial: DFU request completed with result: 0xB
I see. It looks correct to me, but obviously there is a problem somewhere. Can you dump the UART traffic when using both nrfutil and your implementation and diff it to see where it differs?
I checked the debug logs from nRF while performing DFU from PC and from STM, I see similar logs.
I enable verbose in nrfutil and checked and i found we're also following similar process.
Hi,
I see. Please upload the complete logs to this case, as it will be useful. However, what I was really interested in was a raw dump of the UART traffic (assuming you are using UART as DFU transport - please confirm). Comparing the dumps should hopefully show where there is a difference, and then we know where to look closer.