FPGA Central

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

On Jun 20, 1:33*pm, Benjamin Krill <b...@codiert.org> wrote:
> Hi Dan,
>
> > > > Developing professional GUIs is very time consuming for me. *Thishas
> > > > 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


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

On Jun 20, 10:51*am, chewie <timinganaly...@gmail.com> wrote:
> On Jun 20, 1:33*pm, Benjamin Krill <b...@codiert.org> wrote:
>
>
>
>
>
> > 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, *andview 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
>
> 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


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

- outputlogic

http://outputlogic.com