Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

load streaming JSON #25

Open
drom opened this issue Sep 9, 2022 · 4 comments
Open

load streaming JSON #25

drom opened this issue Sep 9, 2022 · 4 comments

Comments

@drom
Copy link
Member

drom commented Sep 9, 2022

Load streaming JSON messages:

https://en.wikipedia.org/wiki/JSON_streaming

Standard fields:

  • t -- time stamp (in time units compatible with VCD) optional field. If omitted, t is current time stamp
  • n -- signal name

Immediate events

...
{"t":2334534, "n":"MY_WRITE", ...}
...

Sequence (transaction)

...
{"t0":345345, "t1":34564556, "n":"SEQ_NAME", "n1":"END_BAR", "n0":"BEGIN_FOO", ....}
...
@mslijepc
Copy link

mslijepc commented Sep 26, 2022

for the read and writes, I can do sequence

e.g. for read

{"t0":123, "t1":234, "t2":235, "t3":236, "n":"READ_TRANS", "n0":"BegReqE", "n1":"EndReqE", "n2":"rresp_t", "n3":"rresp_t_end"}

For signal:

{"t":123, "n":"r_valid, start", "MSG": "initial value"}
{"t":125, "n ":"r_valid, end", "MSG": "beginning of loop"}
{"t":125, "n":"r_valid, start"}

Ok?

@mslijepc
Copy link

should we name differently signals from different adapters? they will be in different files

@drom
Copy link
Member Author

drom commented Sep 27, 2022

@tannewt
Copy link

tannewt commented Nov 1, 2022

This would be great to connect to logic analyzer hardware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants