Re: Unable to get debug message which is in kernel

Your device has probably crashed. That's a good reason you won't get any
more messages... Check for a stuck interrupt (likely), or possibly a
memory/cache problem.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Chitra" <chitrar25@xxxxxxxxxxx> wrote in message
news:1170925493.092459.186780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx







On Feb 8, 1:16 pm, "Henrik Viklund" <henrik.vikl...@xxxxxxxxx> wrote:
On Feb 8, 6:43 am, "Arun" <sirsiarunhe...@xxxxxxxxx> wrote:





HI all,

I am developing BSP for MC9328MXL litekit in WINCE5.0. I have
downloaded the
kernel image on to the target and I have ensured that ARMInit function
is called. But
I don't get the debug message " ARMInit done" printed on the
hyperterminal which is in mdarm.c

#ifdef DEBUG
OEMWriteDebugString(TEXT("ARMInit done.\r\n"));
#endif

I have not checked the SHIP BUILD option while building, and my UART
is working fine
and I get the debug messages which are in bootloader code but I don't
get the debug messages which are in kernel without this I am not able
to proceed further.

I take it that you have no JTAG debugger? If you don't have a JTAG
debugger available, you're pretty much left with "debugging by
flickering LEDs". This is why I say to my customers that sure, a JTAG
debugger cost a lot of money, but it's not *expensive*.

First of all, are you shure you're using the same implementation of
serial debug (OEMDebugInit, OEMWriteDebugString, OEMWriteDebugByte,
OEMReadDebugByte) in both the bootloader and the OS image? When that
is sorted, I'd start by making sure the serial debug init fuction is
actually called (using LEDs for example), and work my way from there.

Should I define the DEBUG macro in my code if so where should I define
this
macro?

DEBUG is automagically defined when selecting to build a debug image,
so there's no need to define it yourself.

Henrik Viklundhttp://www.addlogic.se



please reply

Regards,
Arun- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -


Hi Henrik, Thanks for your quick response
I am using the same OEMDebugInit, OEMWriteDebugString,
OEMWriteDebugByte,
OEMReadDebugByte) in both the bootloader and the OS image and
OEMDebugInit function is called in ARMInit() function. I think there
is no problem with this because I get messages as follows which is
after OEMDebugInit()

Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at
18:25:00
ProcessorType=0920 Revision=0
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable =
81601270
Sp=ffffc7cc

this prints are in NKDbgPrintfW, these are fine.
and I am not enabled KITL (i.e I don't call KITLInit function ) for
time being and I tried building the image by both disabling and
enabling kernel debugger and KITL in BUILD options but no difference.
To get these messages should I enable KITL. Please help



.

Relevant Pages

  • Re: Firewire blues
    ... I compiled a kernel with exactly the same options that you cited below. ... it entering the debugger and waiting for the remote gdb attach. ... When I try to attach from the debug machine, ...
    (freebsd-hackers)
  • Re: Debug and RELFSD
    ... There have been some notes in the past about problems with the kernel ... but if I build a debug version and load it via debug ... Kernel debugger connected. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Debugging VS2008 App and Driver under PB5
    ... application using .NET CF 3.5 running in DEBUG OS build over the kernel ... But I can't debug the app under VS2008 if my OS is generated to include ... Kernel Debugger. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Unable to get debug message which is in kernel
    ... kernel image on to the target and I have ensured that ARMInit function ... I don't get the debug message " ARMInit done" printed on the ... and I get the debug messages which are in bootloader code but I don't ... I take it that you have no JTAG debugger? ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Unable to get debug message which is in kernel
    ... I don't get the debug message " ARMInit done" printed on the ... and I get the debug messages which are in bootloader code but I don't ... debugger cost a lot of money, ... I am using the same OEMDebugInit, OEMWriteDebugString, ...
    (microsoft.public.windowsce.platbuilder)