Difference between DFU and Segger Studio Build and Run/Debug

[PauDC]

Hello,

I have a custom nrf52832 board with a SparkFun HX711 load cell.

I've developed my firmware using Segger Studio testing my data through a BLE connection with the option Build and Debug or Run. Let's call writing the firmware using Segger's Studio "Build and Run" functionality "method A".

Using method A I'm seeing my data correctly displayed.

Now I want to be able to update my firmware using buttonless DFU. So I followed Nordic's tutorial, avaiable here: Nordic's Secure DFU bootloader guide. Let's call writing the firmware via buttonless DFU "method B".

I managed to update the firmware via DFU correctly. But when sending data after using method B, I see the data I'm receiving is wrong. It's like I'm missing packets.

There's no difference between the code of the firmware between method A and B.

I'm going to attach an image for method A and B after what I see when the load cell is resting at a 100Hz rate.

Data displayed using method A:

Data displayed using method B:

Does this makes any sense? I do believe both method A and B outcome should be the same.

Thanks.

[PauDC]

Thanks Awneil and Edvin.

While debugging I saw an error in my code that somehow it only triggered when using method b.

Nevertheless I'm going to keep testing what both of you said, just to understand everything.

Thank you.