Closed Swulf closed 11 years ago
I see from your other issue that you're using a BusPirate. As far as I know, the BP does not support triggers, so that might well explain why this is happening...
Hi Jan,
Thanks for replying to me!
I didn't have RLE enabled - it was configured as in the attached image...
Thanks,
Swulf
On 5/16/2013 10:38 AM, Jan Willem Janssen wrote:
Did you by any chance enable the RLE-option during capture? If so, that could be a probably cause of this...
— Reply to this email directly or view it on GitHub https://github.com/jawi/ols/issues/169#issuecomment-18016657.
Ohh, well that would explain it.
I have ordered the Dangerous Prototypes Logic Sniffer board (http://www.seeedstudio.com/depot/preorder-open-workbench-logic-sniffer-p-612.html?cPath=75) so I hope it will work with that!
The original OBLS has proper trigger support; be sure to update it to the latest firmware (the "DemonCore") as it will give the best results...
Hi,
I am using OLS v0.9.6.1 with the Bus Pirate (v3.6 I think).
Maybe I am misunderstanding something fundamental,and I apologize if there is an OLS forum I should be asking this in...
I don't seem to understand the behaviour of the triggering system. I am examining SPI data monitored by the Bus Pirate. I have a Simple trigger monitoring the SPI /CS line as shown here:
and I see the result below for a typical run
I seem to be unable to see the triggering event itself or any time before that. Maybe I am wrong but I thought that the time '0.0' in the image above would have corresponded to the trigger event (i.e. the CS line changing state and causing the capture to start). Instead the events are all shown occurring before that, and I can't even see the actual triggering event. What I would like to do is to see the triggering event at time 0.0 and events before and after.
Am I doing something wrong?
Thanks again for a very useful piece of software!
Swulf