Re: Breakpoints in bootloader assembly

On Oct 8, 2:33 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT no
instrument no spam DOT com> wrote:
Think we might need to know what bootloader you're talking about?  What
version of Windows CE?  What hardware debugging support you have?  What
processor type?  It looks like ARM, but why make us guess?

Paul T.

<> wrote in message


I am trying to setup breakpoints in my bootloader before my the main()
function gets called. For instance, I would like be able to set a
breakpoint at the beginning of the StartUp function which is written
in assembly. I have no problem setting breakpoints for C functions,
for example I can create a new breakpoint and just type "main" into
the New Breakpoint dialog. I can also set a HW breakpoint using the
address of main (in my case 0x9000c1c0) and that works too. Trying to
enter "StartUp" rather than "main" doesn't work, nor does using its
address. I have noticed that the symbol "StartUp" isn't seen in my
bootloader executable like "main" is (as inspected with dumpbin). Any
suggestions of what I might be doing wrong would be appreciated.

Sure, sorry for the lack of details. I am running Windows CE 6 on a
BSquare development board with a PXA320 (XScale) processor. The
bootloader is from BSquare (not eboot), and it is booting from NAND
flash. If I understand things correctly, the processor has a BootROM
that will copy the the bootloader out of the NAND flash into internal
RAM, and then the BootROM will jump to my bootloader. I am using a
Macraigor usb2sprite JTAG probe and the Marvell Debugger Extensions
for Windows 3.0 provides my eXDI2 driver. Thanks.