9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] OT: hard realtime, timing diagram GUI.
Date: Thu,  8 May 2014 07:16:13 -0700	[thread overview]
Message-ID: <4D93562F-DEE8-4C63-994F-94773D245546@bitblocks.com> (raw)
In-Reply-To: <5e71984e9a9daaadd76f605f45ad5999@quintile.net>

Would https://github.com/drom/wavedrom do? See the tutorial. Step 8 shows bezier arrows linking waveforms. And it seems to be actively developed. There is a command line version as well.

On May 8, 2014, at 5:52 AM, "Steve Simon" <steve@quintile.net> wrote:

>> I don't understand why realtime matters.
> 
> Only that such diagrams are more important in realtime systems.
> 
>> How do you want these events represented on the timing diagram?
> 
> I suspose a clock line, left to right, at the top.
> 
> events appear as signals, one below the other running paralle to the clock line.
> These  change state on a rising edge of a clock, and a different coloured bezier curve
> (with optional label) links an event to any events it triggers.
> 
> allow me to colour signals so interrupts and clock are clearly different
> and add labels to signals and I would be happy.
> 
> The idea is this diagram would be built by a cron job from regression tests every night
> and if the timings drifted in the system it should be quite easy to see where the time
> has been wasted.
> 
> Alternatively A GUI interface could be used - this might have advantages (cursors?)
> but really a PDF and page(1) would probably do.
> 
> Somthing like graphviz for timing diagrammes.
> 
> -Steve
> 



  parent reply	other threads:[~2014-05-08 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08  9:15 Steve Simon
2014-05-08 11:59 ` Bakul Shah
2014-05-08 12:52   ` Steve Simon
2014-05-08 13:55     ` lucio
2014-05-08 14:16     ` Bakul Shah [this message]
2014-05-08 14:53       ` Steve Simon
2014-05-08 15:47         ` Bakul Shah
2014-05-08 21:49 ` James A. Robinson
2014-05-08 15:19 Daryl M

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D93562F-DEE8-4C63-994F-94773D245546@bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).