=20
quoted
Second question would be - is there an easier way to accomplish what=20
I'm trying to do, which is basically emulate a serial port with GDB.
=20
Use NetConsole or remotey log it with syslog...
=20
I guess I wasn't clear in the problem statement - this target doesn't
have a serial port, an ethernet port, or a file system. So I can't log
over Ethernet or log by writing to a file. I'm fairly restricted to
getting data out of the system using GDB controlling a hardware JTAG
debugger (think BDI2000).
Tim
On Thursday 10 August 2006 15:00, Martin, Tim wrote:
quoted
quoted
Second question would be - is there an easier way to accomplish what
I'm trying to do, which is basically emulate a serial port with GDB.
Use NetConsole or remotey log it with syslog...
I guess I wasn't clear in the problem statement - this target doesn't
have a serial port, an ethernet port, or a file system. So I can't log
over Ethernet or log by writing to a file. I'm fairly restricted to
getting data out of the system using GDB controlling a hardware JTAG
debugger (think BDI2000).
I don't know GDB internals so I cannot answer the specific question relating
to synchronous writes via GDB.
But...
How much data are we talking and is there some area of private memory to stash
the logged data in and use the JTAG adapter to fetch the memory blocks and
write to a local file for post processing? I've done this in places where I
am doing kernbel bringup without a serial port. Your other option is use a
few IO pins (if available) and make a bit banging serial interface with some
extrnal components.
Thanks
Brian