This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
diag_printf problems
- From: agyhoo <agyhoo at yahoo dot com>
- To: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 24 Mar 2004 13:39:16 -0800 (PST)
- Subject: [ECOS] diag_printf problems
Hi,
I am using an A&M Rattler board in which I installed
a pretty up-to-date RedBoot version (from ecos cvs)
I also built an eCos application library based on
the net template. The Inherit Console settings option
was turned so that I could use RedBoot's console channel
for my diagnostic outputs. I also created a "/dev/tty0"
device mapped to "/dev/ser1" the SMC1 port of the MPC8250.
This is what I set as my console channel. I also set
this as the I/O channel for ISO C stdio.
Next, I linked a simple hello world application which
essentially uses printfs and diag_printfs.
At the first diag_printf statement the code hangs.
When I run the code using GDB, the code work fine because
the diag_printf output is routed to the GDB console.
Upon navigating through the code, I discovered that the
RedBoot ecc file has the Route Diagnostic Output to Debug
Channel output turned on. Thinking that this was the
problem, I rebuilt RedBoot again with this option turned
off
and tried the same sequence. I hit the same problem.
Any ideas as to what the problem is? How do I get my
diag_printfs to show up on my console (SMC1 port) along
with my printfs without hanging up the console?
- Anunoy
PS. The reason I need to use both printf and diag_printf
is because the FreeBSD TCP/IP stack uses diag_printf
and I am using the stack. I could change this but I'd
rather try to figure out the problem.
__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss