public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
* hw-visual-tty
@ 2004-11-14 17:18 Tarun Siripurapu
  2004-11-14 18:00 ` hw-visual-tty Frank Ch. Eigler
  0 siblings, 1 reply; 3+ messages in thread
From: Tarun Siripurapu @ 2004-11-14 17:18 UTC (permalink / raw)
  To: sid

Hi,

To run SID and show the 'hw-uart-ns16550 uart1' tty window, this is
what I'm currently doing:

$ arm-elf-sid --board=pid7t-normalmap --gdb=2000 -EL --tksm &

And then I select the experimental GUI window titled 'System Monitor'
and left-click and hold on 'uart1' in the left hand column, select
'GUIs' and then 'tk tty'.

Is there a way to do it with out having to open the System Monitor and
click these every time?

Thanks,
Tarun

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: hw-visual-tty
  2004-11-14 17:18 hw-visual-tty Tarun Siripurapu
@ 2004-11-14 18:00 ` Frank Ch. Eigler
       [not found]   ` <c36e089004111417255552f041@mail.gmail.com>
  0 siblings, 1 reply; 3+ messages in thread
From: Frank Ch. Eigler @ 2004-11-14 18:00 UTC (permalink / raw)
  To: Tarun Siripurapu; +Cc: sid

Hi -


On Sun, Nov 14, 2004 at 12:18:30PM -0500, Tarun Siripurapu wrote:
> [...]
> To run SID and show the 'hw-uart-ns16550 uart1' tty window, this is
> what I'm currently doing:
> $ arm-elf-sid --board=pid7t-normalmap --gdb=2000 -EL --tksm &
> [...]

Sounds good.

> Is there a way to do it with out having to open the System Monitor and
> click these every time?

Certainly.  In the sid framework, a gui frontend component can be
configured into the simulation just as easily as any hardware
model - even easier perhaps.  The GUI component convention consists
of only a few additional bits of sid configuration:

	# ... other configuration
	new hw-uart-ns16550 uart
	# ...
	new hw-visual-tk widget
	relate widget "hw-uart-ns16550 uart" uart

The key of course is the last "relate" command.   For GUI connections,
the "relationship name" is a two-part string, the first of which
identifies the component type of the target hardware model.  (This
way the GUI can adapt itself to several virtual hardware variants.)
The second component appears to be just some identifying text used
in the title bar of the GUI component, in order to tell the user 
which hardware module is being observed.

So all you need to do is to append those two lines of configuration
to your sid run, perhaps using two "-e '......'" options, or else
generating and editing a configuration file.


- FChE

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: hw-visual-tty
       [not found]   ` <c36e089004111417255552f041@mail.gmail.com>
@ 2004-11-15  1:31     ` Frank Ch. Eigler
  0 siblings, 0 replies; 3+ messages in thread
From: Frank Ch. Eigler @ 2004-11-15  1:31 UTC (permalink / raw)
  To: Tarun Siripurapu; +Cc: sid

Hi -

> Are there instructions available on how to generate and edit a
> configuration file? If so, how do I access them?

Run "sid" with no options.  It will enumerate options such as ...
"--no-run --save-temps=FILE" to save a sid configuration file
generated for the current set of general options.  It's just a
text file which you may edit, then resubmit to sid simply via
"sid FILE.conf".

- FChE

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-11-15  1:31 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-11-14 17:18 hw-visual-tty Tarun Siripurapu
2004-11-14 18:00 ` hw-visual-tty Frank Ch. Eigler
     [not found]   ` <c36e089004111417255552f041@mail.gmail.com>
2004-11-15  1:31     ` hw-visual-tty Frank Ch. Eigler

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 read-only IMAP folder(s) and NNTP newsgroup(s).