The crc4 from the "read byte" response is a later problem. As it is now, the crc doesn't work anymore in my fork.
But one problem at the time.
]]>1) normal iteration is 99.1us
2) when sending, it follows bit frames, ie 100us (ONE) 60us (ZERO)
this is my problem at the moment, to verify this claims in the paper...
I just can't get your trace to match up with these statements from the papers
19 = obsfuscated
04 = lsfr xor (legic prng)
1D = plain text
If I understand You correctly, the transmit 0x01 - response 0x1d ?
zerobased RAND, receive 0x19
Been trying to make the legic code better, got some the tracelog out with stuff which helps in understanding this very simple protocol. I still don't get it when the prng skips forward, when sending its bit-period (100us/60us) and when not sending is (100us well 99.1us according to documents). But is "not sending" the pause between frames?!?
]]>