Allow single HLA to generate multiple bubble tracks

Voters 16

V
R
S
J
T
E
+ 10 voters
J
A
F
B
T
C
S
C
M

Open
Subscribe

Tim

Original request below:
discuss.saleae.com/t/spi-flash-analyzer-and-enhancements/765/7

Description:
"Any idea if we’ll be able to add multiple tracks of bubbles? I’d love to output the raw bytes on separate tracks. I’d prefer to have multiple tracks from a single HLA. That way the settings are shared for the HLA."

Current Workaround:
You can use multiple instances of the same HLA to accomplish the same goal. This idea would be more of a "quality-of-life" feature so that you could skip this step and easily manage settings via a single HLA.

Use case:
"Generally, I’d like to have different bubble tracks for different things. One for the commands, one for the raw data (more like what the SPI LLA gives) and one for errors. That would allow one to better survey the full analysis. (Like easily finding errors.)"

30-03-2021 -

Activity Newest / Oldest

Martin

I work with RF data. If you allow to use more than one "row" of frames i would be able to show more useful data.
For example, One big frame to show the duration of all the pulses.
Other row for bit number, which is useful when you want to find one particular bit between 24, without having to count.
Other row for each bit value.
Other row for each byte value.
Other row for the actual decoded data of the RF signal.

Tim

(#62155)
"I only put frames on the clock channel because that was the only way to do multiple frame channels. If there are any plans to support overlapping frames as requested in this discussion topic, I have some interest in that."

Peter Jaquiery

I don't think the title matches the description. I see both as desirable features, but they are quite different.

1/ Allow a single HLA to use data from multiple inputs and low level analyzers (implied by the title)
2/ Allow a single HLA to generate bubble text for multiple input traces (implied by the description)

I have a feeling 1/ has been addressed by and Idea already.

Tim

Thanks! I just updated it, and also added more notes on the current workaround and use case