Random and very high values of distance between DMW3000 using STM32G4 nucleo

[Pianista]

Thank you for the tip,
I checked a frames sending from initiator to responder on the last round and here what I got:
Here is a TX final message which is prepared by initiator:

And here is a message which responder got:

Using red color I marked bytes which have a timestamps from initiator. I checked that initiator include good bytes to msg and this is ok. But responder read from RX_BUFFER bad bytes of timestamps . I also see that first byte of timestamp form initiator have always 0x01.
Some similar problem got c0-hunterz in this topic:

DWM3000 TX timestamp byte stays the same during the entire operation

Hello, I am currently working with DWM3000 and I am trying to test the different modes of operation. When in RX, the module retrieves the frames as expected and I can extract the timestamps, which look fine to me, as they increment on a similar scale (the TX is transmitted periodically). On the other side though, the TX has some issues. The frame is sent correctly, no issues there, but when trying to read the TX timestamp (via dwm_readtxtimestamp()), the first byte in the timestamp buffer seem t…

P.S. I debug all process and read the timestamps by STMCubeIDE and put them to the formula. Calculated distance was good. The problem is probably in sending/receiving or reading from RX_BUFFER in responder or some little configuration. But still don’t know where search a problem