From mboxrd@z Thu Jan  1 00:00:00 1970
References: <5e71984e9a9daaadd76f605f45ad5999@quintile.net>
From: Bakul Shah <bakul@bitblocks.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <5e71984e9a9daaadd76f605f45ad5999@quintile.net>
Message-Id: <4D93562F-DEE8-4C63-994F-94773D245546@bitblocks.com>
Date: Thu,  8 May 2014 07:16:13 -0700
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: [9fans] OT: hard realtime, timing diagram GUI.
Topicbox-Message-UUID: e3344b0c-ead8-11e9-9d60-3106f5b1d025

Would https://github.com/drom/wavedrom do? See the tutorial. Step 8 shows be=
zier arrows linking waveforms. And it seems to be actively developed. There i=
s 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.
>=20
> Only that such diagrams are more important in realtime systems.
>=20
>> How do you want these events represented on the timing diagram?
>=20
> I suspose a clock line, left to right, at the top.
>=20
> 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 b=
ezier curve
> (with optional label) links an event to any events it triggers.
>=20
> allow me to colour signals so interrupts and clock are clearly different
> and add labels to signals and I would be happy.
>=20
> The idea is this diagram would be built by a cron job from regression test=
s every night
> and if the timings drifted in the system it should be quite easy to see wh=
ere the time
> has been wasted.
>=20
> Alternatively A GUI interface could be used - this might have advantages (=
cursors?)
> but really a PDF and page(1) would probably do.
>=20
> Somthing like graphviz for timing diagrammes.
>=20
> -Steve
>=20