03-28-2015, 09:13 AM
For the first data bit I simply put in a 0 or a 1 ... 00000000 or 00000001 into the buffer.
For each data bit after that I shift what I have left ... 00000000 or 00000010 ... and then OR in a 1 if need be ... 00000001 or 00000011
Next bit [assuming there was a 1 in the previous bit] ... 00000001 or 00000011 shifted becomes 00000010 or 00000110 and after the OR ...
When you look at the 24 bit string it would be exactly like the scope trace with time going from the [left] high order bits to the [right] low order bits.
Only getting a "Ready" is strange. That suggests that the interrupt does not increment the capturedBurstCounter. That's strange because it should be incremented ... assuming nothing is going wrong with the timing ... based on the clock transitions and has nothing to do with the data line.
Maybe I should take a drive up there and we do this in real time
For each data bit after that I shift what I have left ... 00000000 or 00000010 ... and then OR in a 1 if need be ... 00000001 or 00000011
Next bit [assuming there was a 1 in the previous bit] ... 00000001 or 00000011 shifted becomes 00000010 or 00000110 and after the OR ...
When you look at the 24 bit string it would be exactly like the scope trace with time going from the [left] high order bits to the [right] low order bits.
Only getting a "Ready" is strange. That suggests that the interrupt does not increment the capturedBurstCounter. That's strange because it should be incremented ... assuming nothing is going wrong with the timing ... based on the clock transitions and has nothing to do with the data line.
Maybe I should take a drive up there and we do this in real time