TimingAnalyzer is now freeware

[timinganalyzer]

Hi All,

I just wanted to let you know that the TimingAnalyzer is now licensed
as freeware. I just don't have the time needed to make a high
quality commercial product but I do want to keep the development
moving forward and continue to fix problems and add new features as
time permits.

Recently, I have become very interested in Python and using it to
develop similar type cad programs. My plan is to convert the
TimingAnalyzer Java to Python with mostly a scripting interface for
building complex timing diagrams, doing timing analysis, creating
testbenches and testvectors from waveform diagrams,
and creating timing diagrams from simulation VCD files. Most all of
this is text based work anyway.

Developing professional GUIs is very time consuming for me. This has
been my bottleneck with the program all along. With a command line
interface, you will execute a script and in one window, and view and
edit and print the timing diagram shown in another window. Like
Matlab interface.

If anyone is interested in helping with the development, I will make
this an open source project. Just let me know if your interested.

Thanks,
Dan Fabrizio

[Antti....@googlemail.com]

a link to your webpage would help
(for those who are lazy)

Antti

[chewie]

On Jun 20, 12:24 pm, "Antti.Luk...@googlemail.com"

Sorry about that. The website is:

www.timing-diagrams.com

[Benjamin Krill]

Hi Dan,

> > > Developing professional GUIs is very time consuming for me. This has
> > > been my bottleneck with the program all along. With a command line
> > > interface, you will execute a script and in one window, and view and
> > > edit and print the timing diagram shown in another window. Like
> > > Matlab interface.

This descriptions sounds somehow like a program I used some time ago. Of
course not with the analyzing options you have implemented in your
TimingAnalyzer tool.

http://drawtiming.sourceforge.net/

cheers
ben

[chewie]

Hi ben,

I did see that before and that is similar but my approach will be much
more
higher level thus easier.

For example:

micro = m68000()
micro.write(add, data, wait_states)
micro.read(add, wait_states).

or

add_clock(......)
add_signal(.....)
add_delay(......)
add_constraint(.....)
add_or_gate(....)
add_and_gate(....)
add_counter(....)
add_clock_jitter(.....)

analyze_clock_domains(.....)
analyze_worst_case_timings(....)
analyze_best_case_timings.

read_vcd(....)
vcd_2_timing_diagram(.....)
create_testvectors(.....)
create_testbench(....)

A lot of these functions are built into the program now so its a
matter of converting them java to python. I won't have to spend most
of the time getting the user interface to look good and be friendly.
If this is made an open source project, I would hope that others
would help with the development and new features and bug fixes will
happen very quickly.

-Dan

[OutputLogic]

I agree. This could grow into a quite useful tool.

- outputlogic

http://outputlogic.com

[James Harris]

I prefer command-line interfaces in general. They are more flexible
and can be automated.

Good choice to move to Python as long as the speed holds up. You may
want to inclulde comp.lang.python.

James

[chewie]

Thanks James. I did post a similar message on comp.lang.python.
If there are some speed bottlenecks in Python, there is always the
option
of writing only those parts in a C extension.

[Petrov]

On Jul 3, 11:52 am, chewie <timinganaly...@gmail.com> wrote:
> Thanks James.  I did post a similar message on comp.lang.python.
> If there are some speed bottlenecks in Python,  there is always the
> option

> of writing only those parts in a C extension.- Hide quoted text -
>
> - Show quoted text -

Personally... I wouldn't bother optimizing it with a C extension.
Programmer time is more expensive than computing time. Computers are
getting faster every year. Soon, the slow parts might not even be
noticeable.

Pete