Breaking into a stopped code RRS feed

  • Question

  • Hi all,

    my image has some problems that stop the boot of the image compiled in SD/MMC mode.

    If i compile in RAM mode and download via PB, the image never stop.

    Is there a way to break in the code with the PB when i see the problem?


    Thursday, August 2, 2012 3:12 PM

All replies

  • With passive KITL you can connect Platform Builder even when booting off SD/MMC (of course the image on SD/MMC has to be a debug one for full debugging support).

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog:

    Microsoft Embedded Partner
    Consultancy, training and development services.

    Thursday, August 2, 2012 11:33 PM
  • Eboot configured as:

    KITL: Polling

    Kitl enable: enable

    KITL passive: Enable

    Image compiled in debug mode with enabled kernel debugger and KITL enabled.

    The image runs and stops inside a driver: how can i connect the PB????


    Friday, August 3, 2012 8:27 AM
  • As an alternative, how about putting a DebugBreak() in the Init call for the driver (or the equivalent point, depending on the driver type), and using an active KITL connection to step through the driver. Alternatively, sprinkle debug statments through the code and put your DebugBreak() just before the last one before the code stops running.

    Paul T.

    Saturday, August 11, 2012 1:00 AM