Re: how to use ICE to debug eboot under platbuilder?

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

From: Steve Maillet \(eMVP\) (nospam1_at_EntelechyConsulting.com)
Date: 04/18/04 

Date: Sun, 18 Apr 2004 15:21:12 -0400

eboot.exe is renamed to nk.exe in the boot.bib files for the boot loader.
you can open the eboot.bin file for the boot loader from platform builder
and it will read the TOC from that ROM image to identify the modules and the
debug symbols. Typically ICE debuggers will stop at the reset vector for the
chip so you can start debugging from that point. You should be able to set a
breakpoint at any part of the boot loader and after hitting go it stops
there. Keep in mind that if the disassembly view is still open that is what
is shown so you might want to close it to get the source view by default. If
your boot loader switches the MMU on you will need to set a breakpoint in
the code after the MMU is on using a hardware breakpoint with the new
virtual address (Even if it's a 1:1 mapping you need a hardware breakpoint
for this.) 

-- 
Steve Maillet (eMVP)
EmbeddedFusion
smaillet_AT_EmbeddedFusion_DOT_com

Relevant Pages

  • Re: MMU questions
    ... It depends on the boot loader. ... The only requirement is that the MMU is OFF ... enable the cache as some CPUs require the MMU for caching. ... Steve Maillet ...
    (microsoft.public.windowsce.platbuilder)
  • Problems with MMU on PXA255
    ... Currently i'm developing a boot loader for a custom PXA255-based board. ... What causes me troubles is the ... Without MMU the HW behaves as ...
    (comp.os.linux.embedded)
  • Problem with MMU on PXA255
    ... Currently i'm developing a boot loader for a custom PXA255-based board. ... What causes me troubles is the ... Without MMU the HW behaves as ...
    (microsoft.public.windowsce.embedded)