From the help of Windows CE Platform Builder 4.2 I knew that bootloader can
be debugged by eXDI hardware driver and then I downloaded the ARM eXDI driver
for Windows CE PB from www.arm.com. But the help of Windows CE Platform
Builder 4.2 don't detail how to debug bootloader using eXDI driver. Who can
tell me what I should do to debug bootloader of WinCE? The target board is
S3C2410. Thanks.

Re: How to debug bootloader using ARM eXDI driver for Windows CE PB? by Yannick

Yannick
Thu Feb 09 01:58:30 CST 2006

First you'll need to check that your ICE is correctly setup to recognise the
CPU.

Next, once ICE connection is ok, and ExDI driver installed, you can setup in
PB connection settings the fact that PB should use ExDI to debug. Then, open
nk.bin file with PB to start JTAG debugging

--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADENEO (ADESET)
Windows Embedded Manager
ychammings AT adeneo DOT adetelgroup DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"dudu" <dudu@discussions.microsoft.com> a écrit dans le message de news:
3C4A671D-8E5D-43CE-A9E0-5FB9A97C0D83@microsoft.com...
> From the help of Windows CE Platform Builder 4.2 I knew that bootloader
> can
> be debugged by eXDI hardware driver and then I downloaded the ARM eXDI
> driver
> for Windows CE PB from www.arm.com. But the help of Windows CE Platform
> Builder 4.2 don't detail how to debug bootloader using eXDI driver. Who
> can
> tell me what I should do to debug bootloader of WinCE? The target board is
> S3C2410. Thanks.



Re: How to debug bootloader using ARM eXDI driver for Windows CE P by dudu

dudu
Thu Feb 09 06:11:28 CST 2006

Hello,Yannick Chamming's
Thanks for your answer. And I have two questions related to this topic to
ask you. If I use eXDI to debug eboot.bin, how can I open it with PB? The
other question is it is printed by the help of WinCE PB 4.2 that breakpoint
in flash ROM can be set by eXDI but not detailed much. Can you tell me how to
set breakpoint in flash ROM? Thanks a lot.

"Yannick Chamming's [eMVP]" wrote:

> First you'll need to check that your ICE is correctly setup to recognise the
> CPU.
>
> Next, once ICE connection is ok, and ExDI driver installed, you can setup in
> PB connection settings the fact that PB should use ExDI to debug. Then, open
> nk.bin file with PB to start JTAG debugging
>
> --
> ----------------------------------------------------------------
> Yannick Chamming's (eMVP)
> ADENEO (ADESET)
> Windows Embedded Manager
> ychammings AT adeneo DOT adetelgroup DOT com>
> http://www.adeset.com
> Tél : +33 (0)4.72.18.57.77
> Fax : +33 (0)4.72.18.57.78
> ----------------------------------------------------------------
>
> "dudu" <dudu@discussions.microsoft.com> a écrit dans le message de news:
> 3C4A671D-8E5D-43CE-A9E0-5FB9A97C0D83@microsoft.com...
> > From the help of Windows CE Platform Builder 4.2 I knew that bootloader
> > can
> > be debugged by eXDI hardware driver and then I downloaded the ARM eXDI
> > driver
> > for Windows CE PB from www.arm.com. But the help of Windows CE Platform
> > Builder 4.2 don't detail how to debug bootloader using eXDI driver. Who
> > can
> > tell me what I should do to debug bootloader of WinCE? The target board is
> > S3C2410. Thanks.
>
>
>

Re: How to debug bootloader using ARM eXDI driver for Windows CE P by Yannick

Yannick
Fri Feb 10 01:59:57 CST 2006

Just drag and drop eboot.bin to a pb window. Pb will open the .bin file.
Then, configure target connection to use ExDI and launch debugger (F5 key).

PB will automatically connect to the target through JTAG, and will break at
the current instruction. Then you can debug as usual.

Setting breakpoint in flash ROM can be done the same way as in SDRAM : you
set a breakpoint at a specific line of source code. The important point is
that even if the code at this place is executed in ROM, using ICE debugger
will allow you breaking at this line of code, which is not the case without
ICE/JTAG debugging

--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADENEO (ADESET)
Windows Embedded Manager
ychammings AT adeneo DOT adetelgroup DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"dudu" <dudu@discussions.microsoft.com> a écrit dans le message de news:
2BC67AF1-084C-4172-BC16-BB00E87BEF4F@microsoft.com...
> Hello,Yannick Chamming's
> Thanks for your answer. And I have two questions related to this topic to
> ask you. If I use eXDI to debug eboot.bin, how can I open it with PB? The
> other question is it is printed by the help of WinCE PB 4.2 that
> breakpoint
> in flash ROM can be set by eXDI but not detailed much. Can you tell me how
> to
> set breakpoint in flash ROM? Thanks a lot.
>
> "Yannick Chamming's [eMVP]" wrote:
>
>> First you'll need to check that your ICE is correctly setup to recognise
>> the
>> CPU.
>>
>> Next, once ICE connection is ok, and ExDI driver installed, you can setup
>> in
>> PB connection settings the fact that PB should use ExDI to debug. Then,
>> open
>> nk.bin file with PB to start JTAG debugging
>>
>> --
>> ----------------------------------------------------------------
>> Yannick Chamming's (eMVP)
>> ADENEO (ADESET)
>> Windows Embedded Manager
>> ychammings AT adeneo DOT adetelgroup DOT com>
>> http://www.adeset.com
>> Tél : +33 (0)4.72.18.57.77
>> Fax : +33 (0)4.72.18.57.78
>> ----------------------------------------------------------------
>>
>> "dudu" <dudu@discussions.microsoft.com> a écrit dans le message de news:
>> 3C4A671D-8E5D-43CE-A9E0-5FB9A97C0D83@microsoft.com...
>> > From the help of Windows CE Platform Builder 4.2 I knew that bootloader
>> > can
>> > be debugged by eXDI hardware driver and then I downloaded the ARM eXDI
>> > driver
>> > for Windows CE PB from www.arm.com. But the help of Windows CE Platform
>> > Builder 4.2 don't detail how to debug bootloader using eXDI driver. Who
>> > can
>> > tell me what I should do to debug bootloader of WinCE? The target board
>> > is
>> > S3C2410. Thanks.
>>
>>
>>



Re: How to debug bootloader using ARM eXDI driver for Windows CE P by micchen

micchen
Fri Feb 17 10:19:38 CST 2006


>From: "Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com>
>Subject: Re: How to debug bootloader using ARM eXDI driver for Windows CE P
>Date: Fri, 10 Feb 2006 08:59:57 +0100
>
>Just drag and drop eboot.bin to a pb window. Pb will open the .bin file.
>Then, configure target connection to use ExDI and launch debugger (F5 key).

You will also want to rename the eboot.exe / eboot.pdb to nk.exe / nk.pdb
respectively.


>Setting breakpoint in flash ROM can be done the same way as in SDRAM : you
>set a breakpoint at a specific line of source code. The important point is
>that even if the code at this place is executed in ROM, using ICE debugger
>will allow you breaking at this line of code, which is not the case
without
>ICE/JTAG debugging

When setting breakpoints in flash ROM, you will want to use a hardware
breakpoint. Using the breakpoint dialog, you can specify whether to set a
hardware / software / any breakpoint. Most probes support both hardware
and software breakpoints, and in the general case, the number of hardware
breakpoints are limited when compared to the number of software breakpoints
availabe. Hardware breakpoints typically use a cpu debug register or
internal debug functionality exposed through JTAG. Software breakpoints
involve writing a trap instruction recognizable by the probe in memory,
which will obviously fail when debugging ROM.

---
This posting is provided "AS IS" with no warranties, and confers no rights.