7 Commits

Author SHA1 Message Date
b76a97e394 Rename to "ST"
Name change due to confusion with the common programming verb "set".
2025-05-15 20:35:36 +02:00
0e068e764d Make rubout packet in output function optional 2025-05-15 20:08:37 +02:00
bf27293543 set_record.py: Add verbose tracing option
The commented out print statements tracking values arriving
are now switchable using the --trace flag.
2025-05-15 20:01:11 +02:00
0c7e730438 Finalize name change from PET to SET
There were still a few references to PET, which are corrected.
2025-05-14 21:10:19 +02:00
8b3a9ed381 README.md: Fix example program, elaborate on blurb
The example program (which is untested by the way) is corrected
to generate the desired sawtooth, and a more realistic
baudrate is chosen.

Blurb extended by supported signal types.
2025-05-14 20:59:02 +02:00
3ad06eeada set_record.py: Fixed input stream for Windows, omit null characters in string receive
This commit fixes two bugs, the first when recording
on Windows where the user is unable to stop the capture cleanly
and one regarding the VCD output being malformed due to null characters in strings.

Reading from the stdin buffer is generally better behaved on both platforms,
while not as performant. The user can now cancel the capture by terminating the source
program or issuing a keyboard interrupt.

The issue with string capture having trailing null characters is fixed,
which in the best case confuses GTKwave, or in the worst case segfaults it.
2025-05-14 20:49:25 +02:00
5c3473ff1f Initial release of Streaming Event Trace 2025-05-14 20:44:17 +02:00