DWM3000 TX timestamp byte stays the same during the entire operation

[Pianista]

I got similar problem using DMW3000 and ds_twr exmaples.
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.
My topic:

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

Something is wrong with your timestamps that you are reading out of the final message. Poll_rx to Resp_tx works out as about 34 million or around 530us, that seems like a reasonable value. The final_rx value also looks sensible given poll_rx and resp_tx. But Poll_tx to Resp_rx are 418 million apart or about 6.5 ms, far too long. Similarly the gap from resp_rx to final_tx is completely wrong. Poll_tx to final_tx also looks a little high, I’d expect it to be almost the same as poll_rx to final_…