RE: [ECOS] Debug output

RE: [ECOS] Debug output

[Trenton D. Adams]

> > > "Trenton D. Adams" wrote:
> > > > 
> > > > So from what I gather, this is not output to the serial
> > > port when my
> > > > program outputs to the serial port, but when the system 
> starts up 
> > > > right? So, diag_printf () prints to the first serial port
> > > by default
> > > > then right?
> > > 
> > > The default serial port for diag output is defined in your 
> > > configuration.
> > 
> > Does that mean it's hardcoded in or available as an option in
> > my config tool?  If it's an option, where do I find it?
> > 
> Never mind, I found it.  It's called "Debug serial port".
> 

I mean "Diagnostic serial port".

Re: [ECOS] Debug output

[Jonathan Larmour]

"Trenton D. Adams" wrote:
> 
> > > > "Trenton D. Adams" wrote:
> > > > >
> > > > > So from what I gather, this is not output to the serial
> > > > port when my
> > > > > program outputs to the serial port, but when the system
> > starts up
> > > > > right? So, diag_printf () prints to the first serial port
> > > > by default
> > > > > then right?
> > > >
> > > > The default serial port for diag output is defined in your
> > > > configuration.
> > >
> > > Does that mean it's hardcoded in or available as an option in
> > > my config tool?  If it's an option, where do I find it?
> > >
> > Never mind, I found it.  It's called "Debug serial port".
> >
> 
> I mean "Diagnostic serial port".

Remember this is only the default. It _can_ be changed at runtime. But
please don't ask me how unless you really need to know :-).

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
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

Re: [ECOS] Debug output

[Jonathan Larmour]

"Trenton D. Adams" wrote:
> 
> So, when can we expect that in CVS?  No RUSH now! :)

CVS releases normally happen weekly on a Friday. That's the goal anyway.

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
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

RE: [ECOS] Debug output

[Trenton D. Adams]

So, when can we expect that in CVS?  No RUSH now! :)

> -----Original Message-----
> From: gary@chez-thomas.org [ mailto:gary@chez-thomas.org ] On 
> Behalf Of Gary Thomas
> Sent: Wednesday, June 13, 2001 1:50 PM
> To: Jonathan Larmour
> Cc: eCos; eCos; Trenton D. Adams
> Subject: Re: [ECOS] Debug output
> 
> 
> 
> On 13-Jun-2001 Jonathan Larmour wrote:
> > "Trenton D. Adams" wrote:
> >> 
> >> I noticed that my serial I/O is sending some debug info 
> too if I run 
> >> my ROM based program.  Running the RAM based programming using 
> >> RedBoot doesn't send this information to the serial port, but does 
> >> send it back to GDB.
> >> 
> >> Network stack using 65536 bytes for misc space
> >>                     65536 bytes for mbufs
> >>                     131072 bytes for mbuf clusters
> >> serial example is working correctly!
> >> 
> >> I'm using TCP/IP to connect so I can use the serial port 
> separately 
> >> from the GDB connection.
> >> 
> >> How do I get rid of this?  I assume it's an option in the eCos 
> >> config, but I can't seem to find it.
> > 
> > I'm not entirely convinced about it's use now myself. When 
> the TCP/IP 
> > stack was new it was informative, but now we could make it optional.
> > 
> > For you, work around it by editting 
> > net/tcpip/current/src/ecos/support.c,
> > in the function cyg_kmem_init().
> > 
> > Gary, any reason not to make a config option that controls debug 
> > output. It could be a component that included other things like 
> > DHCP_CHATTER.
> 
> That would be fine.  These messages are indeed vestiges of 
> early testing of the stack.
> 

Re: [ECOS] Debug output

[Gary Thomas]

On 13-Jun-2001 Jonathan Larmour wrote:
> "Trenton D. Adams" wrote:
>> 
>> I noticed that my serial I/O is sending some debug info too if I run my
>> ROM based program.  Running the RAM based programming using RedBoot
>> doesn't send this information to the serial port, but does send it back
>> to GDB.
>> 
>> Network stack using 65536 bytes for misc space
>>                     65536 bytes for mbufs
>>                     131072 bytes for mbuf clusters
>> serial example is working correctly!
>> 
>> I'm using TCP/IP to connect so I can use the serial port separately from
>> the GDB connection.
>> 
>> How do I get rid of this?  I assume it's an option in the eCos config,
>> but I can't seem to find it.
> 
> I'm not entirely convinced about it's use now myself. When the TCP/IP stack
> was new it was informative, but now we could make it optional.
> 
> For you, work around it by editting net/tcpip/current/src/ecos/support.c,
> in the function cyg_kmem_init().
> 
> Gary, any reason not to make a config option that controls debug output. It
> could be a component that included other things like DHCP_CHATTER.

That would be fine.  These messages are indeed vestiges of early testing of
the stack.

RE: [ECOS] Debug output

[Trenton D. Adams]

I decided to work around it by switch the diag output to UART2.

> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com 
> [ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of 
> Jonathan Larmour
> Sent: Wednesday, June 13, 2001 12:21 PM
> To: Trenton D. Adams
> Cc: 'eCos'
> Subject: Re: [ECOS] Debug output
> 
> 
> "Trenton D. Adams" wrote:
> > 
> > I noticed that my serial I/O is sending some debug info too 
> if I run 
> > my ROM based program.  Running the RAM based programming 
> using RedBoot 
> > doesn't send this information to the serial port, but does send it 
> > back to GDB.
> > 
> > Network stack using 65536 bytes for misc space
> >                     65536 bytes for mbufs
> >                     131072 bytes for mbuf clusters
> > serial example is working correctly!
> > 
> > I'm using TCP/IP to connect so I can use the serial port separately 
> > from the GDB connection.
> > 
> > How do I get rid of this?  I assume it's an option in the 
> eCos config, 
> > but I can't seem to find it.
> 
> I'm not entirely convinced about it's use now myself. When 
> the TCP/IP stack was new it was informative, but now we could 
> make it optional.
> 
> For you, work around it by editting 
> net/tcpip/current/src/ecos/support.c,
> in the function cyg_kmem_init().
> 
> Gary, any reason not to make a config option that controls 
> debug output. It could be a component that included other 
> things like DHCP_CHATTER.
> 
> 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 Come to the Red Hat 
> TechWorld open source conference in Brussels!
> Keynotes, techie talks and exhibitions    
> http://www.redhat-techworld.com/
> 

RE: [ECOS] Debug output

[Trenton D. Adams]

> > "Trenton D. Adams" wrote:
> > > 
> > > So from what I gather, this is not output to the serial
> > port when my
> > > program outputs to the serial port, but when the system starts up
> > > right? So, diag_printf () prints to the first serial port 
> > by default
> > > then right?
> > 
> > The default serial port for diag output is defined in your
> > configuration.
> 
> Does that mean it's hardcoded in or available as an option in 
> my config tool?  If it's an option, where do I find it?
> 
Never mind, I found it.  It's called "Debug serial port".

RE: [ECOS] Debug output

[Trenton D. Adams]

> -----Original Message-----
> From: jlarmour@cambridge.redhat.com 
> [ mailto:jlarmour@cambridge.redhat.com ] On Behalf Of Jonathan Larmour
> Sent: Wednesday, June 13, 2001 12:34 PM
> To: Trenton D. Adams
> Cc: 'eCos'
> Subject: Re: [ECOS] Debug output
> 
> 
> "Trenton D. Adams" wrote:
> > 
> > So from what I gather, this is not output to the serial 
> port when my 
> > program outputs to the serial port, but when the system starts up 
> > right? So, diag_printf () prints to the first serial port 
> by default 
> > then right?
> 
> The default serial port for diag output is defined in your 
> configuration.

Does that mean it's hardcoded in or available as an option in my config
tool?  If it's an option, where do I find it?

Re: [ECOS] Debug output

[Jonathan Larmour]

"Trenton D. Adams" wrote:
> 
> So from what I gather, this is not output to the serial port when my
> program outputs to the serial port, but when the system starts up right?
> So, diag_printf () prints to the first serial port by default then
> right?

The default serial port for diag output is defined in your configuration.

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
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

RE: [ECOS] Debug output

[Trenton D. Adams]

So from what I gather, this is not output to the serial port when my
program outputs to the serial port, but when the system starts up right?
So, diag_printf () prints to the first serial port by default then
right?

-----Original Message-----
From: jlarmour@cambridge.redhat.com
[ mailto:jlarmour@cambridge.redhat.com ] On Behalf Of Jonathan Larmour
Sent: Wednesday, June 13, 2001 12:21 PM
To: Trenton D. Adams
Cc: 'eCos'
Subject: Re: [ECOS] Debug output


"Trenton D. Adams" wrote:
> 
> I noticed that my serial I/O is sending some debug info too if I run 
> my ROM based program.  Running the RAM based programming using RedBoot

> doesn't send this information to the serial port, but does send it 
> back to GDB.
> 
> Network stack using 65536 bytes for misc space
>                     65536 bytes for mbufs
>                     131072 bytes for mbuf clusters
> serial example is working correctly!
> 
> I'm using TCP/IP to connect so I can use the serial port separately 
> from the GDB connection.
> 
> How do I get rid of this?  I assume it's an option in the eCos config,

> but I can't seem to find it.

I'm not entirely convinced about it's use now myself. When the TCP/IP
stack was new it was informative, but now we could make it optional.

For you, work around it by editting
net/tcpip/current/src/ecos/support.c,
in the function cyg_kmem_init().

Gary, any reason not to make a config option that controls debug output.
It could be a component that included other things like DHCP_CHATTER.

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 Come to the Red Hat TechWorld open source conference in
Brussels!
Keynotes, techie talks and exhibitions
http://www.redhat-techworld.com/

Re: [ECOS] Debug output

[Jonathan Larmour]

"Trenton D. Adams" wrote:
> 
> I noticed that my serial I/O is sending some debug info too if I run my
> ROM based program.  Running the RAM based programming using RedBoot
> doesn't send this information to the serial port, but does send it back
> to GDB.
> 
> Network stack using 65536 bytes for misc space
>                     65536 bytes for mbufs
>                     131072 bytes for mbuf clusters
> serial example is working correctly!
> 
> I'm using TCP/IP to connect so I can use the serial port separately from
> the GDB connection.
> 
> How do I get rid of this?  I assume it's an option in the eCos config,
> but I can't seem to find it.

I'm not entirely convinced about it's use now myself. When the TCP/IP stack
was new it was informative, but now we could make it optional.

For you, work around it by editting net/tcpip/current/src/ecos/support.c,
in the function cyg_kmem_init().

Gary, any reason not to make a config option that controls debug output. It
could be a component that included other things like DHCP_CHATTER.

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
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

[ECOS] Debug output

[Trenton D. Adams]

I noticed that my serial I/O is sending some debug info too if I run my
ROM based program.  Running the RAM based programming using RedBoot
doesn't send this information to the serial port, but does send it back
to GDB.

Network stack using 65536 bytes for misc space
                    65536 bytes for mbufs
                    131072 bytes for mbuf clusters
serial example is working correctly!

I'm using TCP/IP to connect so I can use the serial port separately from
the GDB connection.

How do I get rid of this?  I assume it's an option in the eCos config,
but I can't seem to find it.