Non-packet events from Cynthion USB analyzer#227
Non-packet events from Cynthion USB analyzer#227miek merged 10 commits intogreatscottgadgets:mainfrom
Conversation
780decc to
c733ba1
Compare
73ed600 to
ee8296f
Compare
722ee07 to
dba8910
Compare
64654cd to
839d048
Compare
d473721 to
aa34ecb
Compare
|
This will need a rebase, but I'd like to get #234 merged before I do that. |
8936f57 to
cb258cb
Compare
|
Rebased on #242. Let's merge that one first. |
cb258cb to
4b6d150
Compare
a085822 to
4daa5d4
Compare
4daa5d4 to
53e31a5
Compare
|
I managed to get this to crash just now and it seems to be reliably reproducible. The setup is a Praline plugged in, speed set to auto, target power turned off with both turn on at capture start & turn off at capture end enabled. I hit capture, let it capture the enumeration, then when I hit stop it crashes with: |
|
Thank you, good catch! I was able to reproduce that crash with the same setup. After working around the crash, by replacing the subtraction that causes the underflow and panic with a A bit more thinking later I realised that I needed to add a |
This PR adds support for non-packet events that may be captured by Cynthion or other USB packet analyzers.
The scope here is limited to events related to the USB capture process itself, or that occur on the USB bus. This implies that these events have a clearly defined position within the stream of captured USB packets.
Events that occur independently of the USB bus, such as logic signals changing on the Cynthion PMOD ports, or voltage/current data points captured from the PAC1954 chip, are out of scope for this event mechanism because they can e.g. occur mid-packet, and therefore require independent timestamping and indexing.
The proposed set of initially supported events is:
These correspond to work in progress on the Cynthion analyzer gateware to detect and emit these events.
TODO:
Will close #118 when complete.