Re: Breakpoint instantiation

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 -

.

Loading