You are browsing as a guest. Sign up (or log in) to start making projects!

11h 3m 36s logged

DEVLOG #48

The baseline finally passed its timing checks: about 5.47 ms uncertainty against the unchanged 50 ms limit. The next blocker is the peer link, where most captured peer frames couldn’t be used.

Wrong CSI layouts had been consuming the same budget as useful peer frames. I fixed the layout filtering and added fairer scheduling for peer traffic. The newer firmware reached RX1, but there’s still no complete two-way result.

RX4 restarted during its update and was still running V1 afterward. Later USB attempts never reached an app write, and its final boot mode wasn’t confirmed. The update’s reset cause remains unknown.

I also hardened the installer and file readers. The write path now uses the exact firmware bytes it verified, but the underlying inconsistent-read problem is still unexplained.

Next: confirm RX4’s state, complete the reviewed update, and repeat the peer pilot before the full two-way measurement.

0
59

Comments 0

No comments yet. Be the first!