Versions Compared

Old Version 2

changes.mady.by.user Albinleo Velappan

Saved on

compared with

New Version Current

changes.mady.by.user Anu Selvaraj

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Every Platform-Builder-Workspace has two different configurations. The Release-configuration which you have used in the Building a Windows CE 5.0 Image for Trizeps4 from Scratch-application note and the Debug-configuration. In the Debug-configuration all moudles modules are build with debugging-information. This and the fact that some optimizations are disabled increases the size of the output files.

...

Unlike the CoreMax-project, which can be easily built for Release and Debug, the Demo-project is far too big.
To be able to build a debug-image, we can use a trick:

  1. Build OS –> Open Build Release Directory will show you where the _FLATRELEASEDIRECTORY resides.

  2. Change the name of this directory from TR4CONXS_ARMV4I_Debug to TR4CONXS_ARMV4I_FullDebug.

  3. Make a copy of the TR4CONXS_ARMV4I_Release directory and name it TR4CONXS_ARMV4I_Debug.

  4. Build OS –> Build Sysgen Current BSP.

  5. Copy desired debug-DLL's and EXE to the debug directory.

  6. Build OS –> Make Run-Time Image

This time Make Run-Time Image will finish with success.

...

Now that you have a Windows CE5.0-Debug-Image, you can start to debug.
Select Target –> Connectivity Options.

...

Now set:

  1. Download to None.

  2. Transport to Ethernet.

  3. Debugger to KdStub.

Press Settings-button next to the Transport-box and power-up your device.

...

Now the kitl-debug-connection will be established and you may set breakpoints, use the Windows CE Shell-extension or other powerfull powerful debug tools of the Windows CE Platform Builder.

Download