This is the mail archive of the sid@sources.redhat.com mailing list for the SID project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: hw-visual-tty


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]