This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos 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: console Vs GUI gdb on i386 target


Pete Barrie wrote:
> 
> At 14:36 13/02/2002 +0000, Jonathan Larmour wrote:
> >Pete Barrie wrote:
> > >
> > > Running PC-host, Win2000, Cygwin and i386-elf-gdb
> > > to PC target.
> > >
> > > I've spent some time with docs and site search but I'm
> > > not clear about the following:
> > >
> > > Q1. On gdb console version standard output from tutorial programs
> > > hello.c , twothreads.c, etc comes back to the gdb console. Good.
> > > But...if I'm running Insight GUI where can I see the
> > > output?  I've checked manuals but I'm not
> > > clear on this.
> >
> >View->Console
> >
> > > Q2. Can I redirect output to other display's on host or PC video?
> > >
> > > CYGSEM_HAL_I386_PC_DIAG_SCREEN (Output to PC screen) _is_ enabled
> > > within the i386 PC Target configuration in the 1.3.net configuration
> > tool but
> > > this does not seem to make any difference. Should output be going to
> > > another device
> > > (config tool help says that PC screen is a third virtual serial device.
> > > What is this device
> > > name ?)
> >
> >There should be _something_ on the attached screen, or at least, the
> >RedBoot stuff.
> 
> Yes, not a problem. PC screen shows usual
> boot messages and "RedBoot>"  prompt
> 
> Programs are running. I've got latest
> ecos updates and have rebuilt redboot.
> 
> >I think the issue is that RedBoot selects the default console once it has
> >got input from it, so if you connect over serial, all console I/O goes to
> >serial.
> >
> >You could change this in your application by disabling
> >CYGSEM_HAL_VIRTUAL_VECTOR_INHERIT_CONSOLE in the Common HAL options, and
> >setting the default console channel to that of the screen. Do that with
> >CYGNUM_HAL_VIRTUAL_VECTOR_CONSOLE_CHANNEL in the PC HAL config.
> 
> I've changed both of these with 1.3net  Config Tool
> 1. Within my i386 ecos build - no joy, everything comes back
> via the serial line - still no printf output to PC screen

What channel number did you choose for
CYGNUM_HAL_VIRTUAL_VECTOR_CONSOLE_CHANNEL ?
 
> I did:  build|clean
>           build|library
> Did I miss anything else required for a new build?

Probably not :-|. You did relink of course ;).
 
> 2. I've also changed these in Redboot build - no
> success - printf still goes to debug serial line

Hmm...
 
> Are the PC screen/keyboard available through a separate device name
> or should things really be working after these changes?

It's not a device name as such - it's redirecting where the "diagnostic"
output goes.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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