Re: OutputDebugString on Release build?
- From: Shawn Rosti <ShawnRosti@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 Feb 2009 12:09:01 -0800
Hi Michel,
It turns out that my issue was build related. In this particular instance
when KITL was disabled my driver wasn't being loaded which is why I didn't
see anything on the serial port. I should have checked the obvious first.
After fixing the build issue, I now see plenty of debug on the serial port
on a release build
Thanks,
Shawn Rosti
"Michel Verhagen (eMVP)" wrote:
Also check your code for obvious #ifdef DEBUG, for instance around the.
code that enables serial debug (in debug.c)
Good luck,
Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog
GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.
Shawn Rosti wrote:
I didn't hear you say that serial debug doesn't work on Release builds, so
that's good. I did take a look at the IO library you pointed to and there
isn't much there, the only thing it does is check to see if the serial port
is being used and then disables the serial driver.
It sounds like serial debug on Release builds should work. I'll dig into it
some more. I'm sure it's something that I've missed in the BSP or in the
configuration in Platform Builder.
Thanks Again,
Shawn Rosti
"Luca Calligaris" wrote:
"I'm wondering if there is a WinCE serial driver somewhere overriding my
settings such as baud
rates/divisors so I no longer see serial output." Since you have the BSP
and you're building an image,
only you can tell: if you look at platform.reg you should be able to check
if you're loading a serial
driver on the debug serial port. Since you'rerunning on a x86 platform it's
unlikely that your serial
port is not UART compatible.
Anyway take a look at %_WINCEROOT%\PLATFORM\COMMON\SRC\X86\COMMON\IO\ioctl.c
code: the last serial output you see comes form there: analyze the functions
to se what's going on
--
Luca Calligaris (MVP-Windows Embedded)
http://geekswithblogs.net/WindowsEmbeddedAnnotations
l.calligaris.nospam@xxxxxxxxxxxxxxxxxx
www.eurotech.it
"Shawn Rosti" <ShawnRosti@xxxxxxxxxxxxxxxxxxxxxxxxx> ha scritto nel
messaggio news:2C417921-151F-4A0A-BAA3-5DC0531D8529@xxxxxxxxxxxxxxxx
Hi,
Does anybody know if I should expect to see serial debug output on a
Release
build that has KITL disabled? I know the serial port works, the BSP
outputs
some stuff on the serial port and then it just stops. I don't see any of
the
debug strings coming out from my driver. I've tried using
OutputDebugString,
NKDebugPrintW, and debug zones and nothing comes out the serial port.
I can think of two things that might be going on.
1) I need to enable serial debug somehow for a Release Build with KITL
disabled
2) I am using a somewhat non-standard UART that needs special init code.
This UART init code was added to debug.c in the BSP, but I'm wondering if
there is a WinCE serial driver somewhere overriding my settings such as
baud
rates/divisors so I no longer see serial output.
Thanks for any pointers,
Shawn
This is the last serial output I see at bootup:
Windows CE Kernel for i486 Built on Jun 11 2008 at 15:31:04
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = 0, dwIoBase = 0,
dwDfltType
= 0) ...
RTC - Status Reg B - 0x02
disLegacyUsbSupport deviceId = 0x27b8
X86Init done, OEMAddressTable = 80224d20, RAM mapped = 20000000.
Override Serial Driver: No COM port selected for serial KITL transport, no
overr
ide necessary.
- References:
- OutputDebugString on Release build?
- From: Shawn Rosti
- Re: OutputDebugString on Release build?
- From: Luca Calligaris
- Re: OutputDebugString on Release build?
- From: Shawn Rosti
- Re: OutputDebugString on Release build?
- From: Michel Verhagen (eMVP)
- OutputDebugString on Release build?
- Prev by Date: Re: Get red of "Networks Detected" dialog
- Next by Date: Re: Why are you blocking Firefox?
- Previous by thread: Re: OutputDebugString on Release build?
- Next by thread: USB Host Printer Driver - Unable to Print Win CE 6.0
- Index(es):
Relevant Pages
|
Loading