Define optimal synchronization (start) bytes for link layer

[jadamcrain]

The best start bytes should have a low probability of occurring in other parts of the protocol.

How about:

0b10101010 == 0xAA
0b01010101 == 0x55

So start characters would be [0xAA, 0x55]

thoughts?

[blytkerchan]

0xa5 is a classic- worth considering rlc

…

-- I am Ronald's iPhone and I approve this message (now that I've edited it extensively using autocorrect) When a measure becomes a target, it ceases to be a good measure. —Goodhart’s law

On Mar 10, 2017, at 12:20, Adam Crain ***@***.***> wrote: The best start bytes should have a low probability of occurring in other parts of the protocol. How about: 0b10101010 == 0xAA 0b01010101 == 0x55 So start characters would be [0xAA, 0x55] thoughts? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jadamcrain]

0x5AA5 if you flip the nibbles and append

Let the bikeshed continue! =)

[blytkerchan]

Yes, it has the advantage of being very easy to recognize on a scope and hard to get wrong by shifting one bit. Less of an issue these days, but still worth a mention 🙂 rlc

…

-- I am Ronald's iPhone and I approve this message (now that I've edited it extensively using autocorrect) When a measure becomes a target, it ceases to be a good measure. —Goodhart’s law

On Mar 10, 2017, at 12:37, Adam Crain ***@***.***> wrote: 0x5AA5 if you flip the nibbles and append — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.