This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Why gdb don't response diag_printf?
- From: "Water He" <hyhe at PhotonicBridges dot com>
- To: "ECOS-DISCUSS" <ecos-discuss at sources dot redhat dot com>
- Date: Wed, 26 Mar 2003 11:53:01 +0800
- Subject: [ECOS] Why gdb don't response diag_printf?
HI, I am using ecos current in our MPC8260 board. my board use a vxWorks boot image and a SMC as serial port. so I compile my HelloWorld program to an elf file. And it can be loaded via FTP by vxWorks boot image correctly. I can use printf output message to the console port.
But now problem is:
When I use diag_printf, it will stop there and can't connect with GDB. Firstly, I open HyperTerminal. I notice that it is waiting a input character '+'. If I press key '+', it output a string like "$O546872656164205B5461736B5F425D3A283030303030303139293A2064656C617920333832207469636B730A#A6" and stop at this diag_printf and wait next '+'. I decode previous string and find out they are what I want to output.
If I close HyperTerminal, and start up powerpc-eabi-gdb
#powerpc-eabi-gdb --nw hello.exe
(gdb)set remotebaud 9600
(gdb)target remote com2
Remote debugging using com2
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Couldn't establish connection to remote target
Malformed response to offset query, timeout
I don't know why GDB don't send '+'. Or I miss some operation?
How can I?