Re: Breakpoint instantiation

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Read this
http://blogs.msdn.com/ce_base/archive/2006/12/22/kitl-and-oal-debug-messages-in-windows-ce6-0.aspx
it's a good explanation about debug zones - and in oal/kitl
specifically

Shai

On Jun 5, 1:50 pm, Selin Metin <nosp...@xxxxxxxxx> wrote:
Thanks.

I already asked phytec support, but received no answer yet :-(

How can I enable more debugzones in the OAL and put more debug messages?

Selin

Erwin Zwart schrieb:



So KitlInit failed, and it looks like the Ethernet chip is not initialized
correctly (Auto Negotiation failed).

If you have the source code of the bootloader you can compare this, because
here also the Ethernet must be initialized and is successful (see logging
"auto negotiation done").

Enable more debugzones in the OAL, or put more debugmessages and share it
with us.

You need to dig into initialization code and see what's going wrong or
contact phytec for support if you got the BSP from them...

Erwin Zwart

"Selin Metin" <nosp...@xxxxxxxxx> wrote in message
news:up$ipikxIHA.524@xxxxxxxxxxxxxxxxxxxxxxx
You are right about KITL, there is a kitlinit failed message in my
bootlog. What could cause this? I attach the log file.

Erwin Zwart schrieb:
Hi,

So this means, for what reason, that the kernel debugger is not running
and
KITL is not initialized. When the kernel boots it tries to initializes
KITL.
When this fails, it automatically starts without KITL and kernel
debugging,
and thats why you see the output on the serial port in stead of the
Platform
Builder output window.

Perhaps you can see some error message regarding failing to initialize
KITL
in your serial output?
What are your connectivity settings (Target | connectivity options)

I missed which WinCE version you are running but i assume that for CE 6.0
Kitl.dll is in your ce.bib? And for 5.0 that:
   nk.exe
<WINCEROOT>\PBWorkspaces\<YourProject>\RelDir\<CONFIGURATION>\kernkitl..exe
NK  SH is used and not
   nk.exe
<WINCEROOT>\PBWorkspaces\<YourProject>\RelDir\<CONFIGURATION>\kern.exe
NK  SH

Erwin Zwart

"Selin Metin" <nosp...@xxxxxxxxx> wrote in message
news:O0pggajxIHA.1980@xxxxxxxxxxxxxxxxxxxxxxx
I tried that already, but the breakpoints looked the same way. The
application may have problem, but also the breakpoints I put in the OS
source files are not instantiated. They are never hit.
I expect the output to be directed to the PB output window, but all
messages are on serial port, and PB output window is empty.
I even suspected that I was not loading any image and the board boots
with
pre-installed image, but the modifications I make appear on the system,
so
I can download the image.
Selin

shai schrieb:
Hi,
I misunderstood something along the way.
You don't have breakpoints wroking in the BSP at all, or are they not
working just in an application independent of the OS/IMAGE.
Some of the suggestions made above are for the BSP and you seemed to
be complaining on an independent program, yet in your last post you
refer to the platform (BSP?).
Anyway if you download a debug image to the device (this has nothing
to do with hello world app), try to put a breakpoint (say in the init
of the display driver),
all output is supposed to be directed to the PB console. If KITL
connects properly (look at the messages) you should hit the break
point if you are in debug mode.

Shai

On Jun 4, 10:34 am, Selin Metin <nosp...@xxxxxxxxx> wrote:
Once again I'm telling: I have a platform compiled for debug build,
with
  KITL and Kernel debugger enabled (since the beginning). With all
these
settings enabled, I don't have breakpoints!!!

Erwin Zwart schrieb:

The problem is that you are not running a debug kernel.
Select the debug configuration and make sure that the following
options
are
enabled:
Right click on your OSDesign in the "Solution explorer" tab and
select
options from the context menu:
Under the "Configuration proporties" item select "build options".
Make sure that, in the right pane, "Enable KITL"  and "Enable Kernel
Debugger" are enabled.
Erwin Zwart
"Selin Metin" <nosp...@xxxxxxxxx> wrote in message
news:%23k6AWjVxIHA.2208@xxxxxxxxxxxxxxxxxxxxxxx
But my module is loaded, I can run it on the device. I see the
module
loading message on the output window....
Also I cannot connect to the device with the remote tools. I played
with
the settings, and so on, but it didn't work. The connection is OK
for
downloading the image, but no remote connection nor remote shell
execution
is possible. Could the breakpoint problem be related with this? I
only
see
Default Device in the remote tools device list.
Selin
SelinAtHeitec
Erwin Zwart schrieb:
The image tells me that your module is not loaded. Thus the
application
did not start.
When you start the module the breakpoint will become a dark red
dot/circle. When the breakpoint hits, there is a yellow arrow in
the
red
dot. Thats with the colors ;-)
Have you tried a DebugBreak();?
Erwin Zwart
"Selin Metin" <nosp...@xxxxxxxxx> wrote in message
news:OkMiyeLxIHA.1236@xxxxxxxxxxxxxxxxxxxxxxx
When I set breakpoints, they look like the image file. Normally
they
should have dark red colour, and when the debugger becomes active
and
the application is loaded, they should turn to bright red. The
caution
triangle makes me suspicious that something is wrong.
Almost all the settings of my OS design and the subproject are
default.
Where could be the problem?
Jack schrieb:
The behaviour you describe is correct.
The breakpoints are only "active" when you have a debug
connection,
and the pdb file is loaded.- Hide quoted text -
- Show quoted text -- Hide quoted text -

- Show quoted text -

.

Relevant Pages

  • Re: doesnt boot after enable Kernel debugger
    ... after boot configure the debug port in Connectivity Options. ... Turn on KITL. ... > process will stop until it gets a KITL connection). ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Breakpoint instantiation
    ... How can I enable more debugzones in the OAL and put more debug messages? ... Erwin Zwart schrieb: ... When the kernel boots it tries to initializes KITL. ... Could the breakpoint problem be related with this? ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Running active sync on versalogic python board
    ... that uses KITL, *then* you can just connect over that same KITL connection ... If you have an ActiveSync connection, then, yes, you have to have an SDK ... If you have KITL connected to a debug build of the OS running on the ...
    (microsoft.public.windowsce.platbuilder)
  • Re: just cut the kitl cord and my ethernet stopped working
    ... an ip address that was passed along to the debug ethernet connection. ... (I do know it isn't the same one as the bootloader ... Ship version of the image removes KITL support and other debug stuff. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: [RFC] hwbkpt: Hardware breakpoints (was Kwatch)
    ... Debug exceptions don't occur very often, and when they do it won't ... The global kernel allocations will already be set in the processor from the ... CPU 1 goes in and alters the user breakpoint data, ... * Hardware breakpoints are implemented using the CPU's debug registers, ...
    (Linux-Kernel)