* [ECOS] Configuring serial ports for Redboot and GDB
@ 2004-07-07 2:00 Miguel J. Vega
2004-07-07 16:27 ` Gary Thomas
0 siblings, 1 reply; 3+ messages in thread
From: Miguel J. Vega @ 2004-07-07 2:00 UTC (permalink / raw)
To: ecos-discuss; +Cc: gary
Hi Gary and list,
I have built redboot with CYGPKG_REDBOOT_ANY_CONSOLE disabled, debugging
serial port set to channel 0 (serial port 1 on board), diagnostic serial
port set to channel 1 (serial port 2 on board). I disabled
CYGPKG_REDBOOT_ANY_CONSOLE to simplify things and spare myself some
confusion.
When I start up, redboot's output (redboot start-up banner, commands,
etc.) comes from the debug port, which I assume is correct. I also use
this port to communicate with the GDB-console (load, continue, inserting
breakpoints, etc.). The only thing that I was not expecting was for the
printf() functions (when I am running programs from GDB) to output through
the diagnostic port. This output appears on a hyperterminal window that
I have open on another PC, since I only have one com port available on
each PC.
I would like for the printf() output to go to the GDB-console,
but the GDB-console currently communicates to the board via the debugging
port. Any ideas on how I can make it happen?
By the way I am building eCos programs with a default eCos build and the
option "work with a ROM monitor" is checked.
Thanks,
Miguel J. Vega
FEGI C&DH Team
University of Michigan
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ECOS] Configuring serial ports for Redboot and GDB
2004-07-07 2:00 [ECOS] Configuring serial ports for Redboot and GDB Miguel J. Vega
@ 2004-07-07 16:27 ` Gary Thomas
2004-08-16 16:57 ` [ECOS] redboot help Sam Pham
0 siblings, 1 reply; 3+ messages in thread
From: Gary Thomas @ 2004-07-07 16:27 UTC (permalink / raw)
To: Miguel J. Vega; +Cc: ecos-discuss
On Tue, 2004-07-06 at 20:00, Miguel J. Vega wrote:
> Hi Gary and list,
>
> I have built redboot with CYGPKG_REDBOOT_ANY_CONSOLE disabled, debugging
> serial port set to channel 0 (serial port 1 on board), diagnostic serial
> port set to channel 1 (serial port 2 on board). I disabled
> CYGPKG_REDBOOT_ANY_CONSOLE to simplify things and spare myself some
> confusion.
>
> When I start up, redboot's output (redboot start-up banner, commands,
> etc.) comes from the debug port, which I assume is correct. I also use
> this port to communicate with the GDB-console (load, continue, inserting
> breakpoints, etc.). The only thing that I was not expecting was for the
> printf() functions (when I am running programs from GDB) to output through
> the diagnostic port. This output appears on a hyperterminal window that
> I have open on another PC, since I only have one com port available on
> each PC.
>
> I would like for the printf() output to go to the GDB-console,
> but the GDB-console currently communicates to the board via the debugging
> port. Any ideas on how I can make it happen?
This is how it is supposed to work - all "console" output through GDB
goes via the debug channel.
If you want to have a debug channel (used by GDB and diag_printf()), and
separate other channel for printf() to use (of course, this would
require two serial connections), then you'll need to do some
configuring.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ECOS] redboot help
2004-07-07 16:27 ` Gary Thomas
@ 2004-08-16 16:57 ` Sam Pham
0 siblings, 0 replies; 3+ messages in thread
From: Sam Pham @ 2004-08-16 16:57 UTC (permalink / raw)
To: ecos-discuss
Hi all,
I ran my application from RAM of the rattler board
with gdb as the debugger. Gdb on the host computer
connected to the rattler board through 1 of its 2
ethernet ports. After approximately less than 1 hour,
the host gdb received the message:
"FLASH configuration checksum error or invalid key"
and the program asserted and stopped right after that.
I looked up this string message and found out that it
came from function flash_get_config() in file
redboot/current/src/fconfig.c. My application doesn't
do anything with flash. I don't have a way to trace
back to see what function calls function
flash_get_config() to determine the cause of this
error because gdb doesn't have fconfig.c in its list
of source file. And I couldn't use backtrace feature
in gdb for this particular case neither.
So anyone knows what its possible causes are? Why
would redboot try to get the flash config anyway?
Thanks.
Sam
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-08-16 16:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-07-07 2:00 [ECOS] Configuring serial ports for Redboot and GDB Miguel J. Vega
2004-07-07 16:27 ` Gary Thomas
2004-08-16 16:57 ` [ECOS] redboot help Sam Pham
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).