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.

...

After several minutes you will see that the build finished with an image up to 67MB in size. Because on default the Trizeps5 is equipt with 128MB of RAM, this is no problem. But if you have a bigger project or want less debugging modules (DLL's, EXE)in the CE6 image, you could:

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

  2. Change the name of this directory from TR5CONXS_ARMV4I_Debug to TR5CONXS_ARMV4I_FullDebug.

  3. Make a copy of the TR5CONXS_ARMV4I_Release directory and name it TR5CONXS_ARMV4I_Debug.

  4. Build –> Advanced Build Commands –> ReBuild Current BSP and Subprojects.

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

  6. Build –> Make Run-Time Image

Prepare SD-Card

The easiest way to load a debug-image, is to use a SD-card. Put nk_ram.nb0 and a autoboot.bat with following contents onto the card:

...

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 debug tools of the Windows CE Platform Builder.

Download

Related Article