Problem seeing OutputDebugStrings output from CE 5.0 target



Hello All,
I have created a device driver for my CEPC system, which I have included in
the sysgen, along with registry entries to automatically load my driver on
bootup. Over the course of my XXX_Init() routine, I call OutputDebugString()
a number of times to send debug output to the debugger (PB 5.0); and I
believe the XXX_Init() is indeed being called, becaused my driver appears in
the "gi mod" list. However, I never see the debug statements. What might be
the problem?
More Specific Info on my configuration:
1] I am using Platform Builder 5.0 to attach to the device and download the
image. This process works successfully.
2] As noted, the command "gi mod" shows my device driver among the other
modules. My driver is also listed under the builtin/active registry key. I
take these signs to indicate that my device driver is being loaded, and that
my XXX_Init() routine is being called. Is this a valid assumption?
3] I am looking for the output from OutputDebugString() in the "debug" pane
of the Platform Builder environment. Is this where it should appear? [I also
checked the terminal showing the bootup serial output, and the debug
statements do not appear there, either.]
4] I am using the "release" build of the CEPC system (since the debug build
had errors during the sysgen). Would this affect whether the debug strings
are displayed? I am inclined to think that it would not, especially since I
do see debug statements from other drivers in the system (such as the
keyboard layout driver).

Sincerely,
Avi Shmidman
Jerusalem, Israel

.



Relevant Pages

  • [RFC: 2.6 patch] remove the broken SCSI_SEAGATE driver
    ... But if anyone wants to ever revive this driver, ... * Will activate debug code. ... -static int internal_command (unsigned char target, unsigned char lun, ... -/* If the user specified the controller type from the command line, ...
    (Linux-Kernel)
  • [RFC: 2.6 patch] remove the broken SCSI_SEAGATE driver
    ... But if anyone wants to ever revive this driver, ... * Will activate debug code. ... -static int internal_command (unsigned char target, unsigned char lun, ... -/* If the user specified the controller type from the command line, ...
    (Linux-Kernel)
  • [2.6 patch] remove the broken SCSI_SEAGATE driver
    ... But if anyone wants to ever revive this driver, ... * Will activate debug code. ... -static int internal_command (unsigned char target, unsigned char lun, ... -/* If the user specified the controller type from the command line, ...
    (Linux-Kernel)
  • RE: freebsd-hackers Digest, Vol 200, Issue 7
    ... Updated Driver for 3945ABG Intel 3945ABG Wireless LAN ... sysctlinterface ... Jan 27 10:30:39 vaio kernel: bus_dmamem_alloc failed to align memory properly. ... debug: all: oid: 0 2 440 ...
    (freebsd-hackers)
  • RE: Bluetooth Obex Ftp Bcsp
    ... Can you please capture some debug output from the Bluetooth stack? ... should be able to see what was last happening in bthcsr before the transfer ... debug into this driver. ...
    (microsoft.public.windowsce.platbuilder)