How do I redirect debug messages to the serial port? (debugging 91c96 lan ISR routines on pxa255, PB 4.2)
WinCE_Newbie_at_no_email.com
Date: 12/17/04
- Next message: David Liao \(MS\): "Re: PCI driver gets loaded too many times"
- Previous message: Tom Gensel \(eMVP\): "Re: [Q]Questions about usb driver in bootloader?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 17 Dec 2004 16:34:21 -0500
I'm modifying the SMSC 91c96 driver for our custom pxa255 board. I'd
like to get some debug information out of the ISR routines. There's
only one ethernet chip on the board, so I have to use the serial port
for printing debug information. The hardware design is based on the
Intel Lubbock board. Debugging over the ethernet/vmini link has been
working for other hardware/driver features.
I'm trying to find a way to either redirect the RETAILMSG/DEBUGMSG
text output, or just send text debug messages to the Xscale serial
port. I've been googling and reading for the past few days and haven't
found a working solution yet.
I have a serial cable that I've tested that works with ActiveSync. The
bootloader menu I/O also works with the cable and HyperTerminal. The
driver is the 91c96 driver from SMSC dated March 2003.
Here is what I've tried, based on previous posts in this newsgroup (a
Google search of Groups of microsoft.public.windowsce.platbuilder):
1) Retail Build with KITL turned off. Someone reported that the debug
messages would be redirected to the serial port if KITL was disabled.
I tried this with HyperTerminal set to a variety of baud rates, but no
serial text appeared. HyperTerminal was initially set to 38,400 N-8-1,
no hardware flow control. Were those the right settings for what the
Kernel debugger sets the serial port to? Do I need to make another
call to set up the serial port for debug message output?
2) Debug Build with KITL turned off, Kernel Debugging turned off (and
in a later build, turned on). No serial text appeared. I also tried
OutputDebugString("Serial Output Test") with this build and nothing
appeared on the serial port.
3) Debug Build with KITL turned off, Kernel Debugging turned off (and
in a later buld, turned on) with the following registry settings in
Platform.reg:
[HKEY_LOCAL_MACHINE\Drivers\Console]
"OutputTo"=dword:1 ;; Redirects CMD to COM1
"COMSpeed"=dword:9600 ;; Speed of serial connection
(38,400bps, dword is in hex)
No serial output in that case either. That looked like something meant
for x86, but I thought I'd try it.
4) There was a suggestion to include the ethernet debugging libraries
into the build, to expose the serial debug routines. What .lib files
should be included if I were to try this? I assume they'd be included
in platform.bib. Would that be correct?
I tried to use EdbgOutputDebugString and OEMWriteDebugString but not
surprisingly the IDE reported unresolved external link errors.
Does anyone have a working method of printing out debug information
from an ISR over the Xscale serial port?
Thanks in advance.
- Next message: David Liao \(MS\): "Re: PCI driver gets loaded too many times"
- Previous message: Tom Gensel \(eMVP\): "Re: [Q]Questions about usb driver in bootloader?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
