BitBob
August 28, 2026, 7:12pm
2
This seems similar to my post (issue #2: One Shot Trigger Problems ) … you might be able work around the one shot trigger issue by extending the holdoff, as long as your capture buffer/transfer time is less than the holdoff time. If sampling at maximum sample rates and capturing multiple channels, you might not be able to get it to trigger & stop.
I was running into some problems trying to decode a quad-SPI flash memory device.
Specifically, I was trying to configure a ‘one shot’ capture of the entire power-up transaction, but running into two problems:
The digital data packet loss on derived digital signals (even though all analog data was captured successfully)
The ‘one shot’ trigger failed to actually STOP the capture properly
Background: Initial serial communications is ~ 5 MHz SPI, but switches to ~20 MHz QSPI mode. The SPI is n…
Meanwhile, regarding:
… are the gaps all ~12ms wide at start of capture?
If so, I think it is a known issue, per:
Hi All,
Everytime I use a digital channel in a free running capture there seems to always be a drop in communication (or something) towards the beginning of the capture. This seems to happen towards the beginning of the capture and has a tendency to throw of the SPI decode (SPI with no CS) and can’t be easily recovered since deleting data before/after a point in the capture is not yet possible with the Logic MSO app (deleting data before/after tended to resolve framing issues on the logic pro). …
And
Logic MSO just arrived today but not getting it to do what I need. I saw some of the prior questions in the forum that explain what I need - single shot with controlled capture length (pre and post trigger) from a digital input(s) is not available yet.
I think this older forum post covers my use case: Single Shot Recording duration settings and few other questions - #2 by timreyes
in which case this is sort of a me too post - though I’m trying to work around it by using the scope to trigger.
…