I have managed to get the SPI decoding to work with a clock at 200khz, but at 2 Mhz the decoding seems to have missed the packet.
it recognises the start, but misses the clock. although this is clearly visible in the trace.
at 200khz the decoding works fine, but the end of the last byte is missed, (the CS line goes high, but the data bubble continues on)
in the attached file the 4 signals are:
D0, CS
D1, SDI
D2, SD0
D3, SCLk
from the waveforms at 5.44us
should decode as:
SDO, AB,00,00,00
SDI, 00,00,00,29
I have passed the information and traces on to the development team for investigation.
While I am waiting for a definitive answer from then, and looking at the trace, I would suggest that it is not correctly locking onto the clock so can you try a few different timebases to see if it helps decode any part of the signal correctly.
Hi,
I tried a number of different timebases.. this was one of the first things I thought may have caused problems, but to no avail..
I have some other work to get on with for the next day or so, but will hopefully get back to this afterwards.
I look forward to getting some response from the dev team..
We have tried this on the latest beta release and by removing the serial decode settings and then adding them back but setting a falling edge clock, MSB first, we are able to decode 01, 03, 05 as a repeating sequence.
Is this what you would expect for the 20120620-0004.psdata file on D2, SD0