• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 227 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Debugging CE apps under WinCE 6.0

SimpleSoft
Intellectual 840 points

Good day!

I have an EVM3530 with WinCE 6.0 R2 (BSP 6.11.00) and CE 2.25 apps. But i don't find any mention about debugging under Windows CE 6.0 environment.

How can user debug GPP side apps under Windows CE 6.0 environment, or maybe under Platform Builder 6.0 R2?

Thanks.

Artiom.

  • 0
    Intellectual 840 points

    CE = Codec Engine.

    Did anybody help with this question?

  • 0 in reply to SimpleSoft
    TI__Genius 17205 points

    The standard WinCE Platform Builder debugging process should apply.

    The only thing Codec Engine specific about it might be how to link in the appropriate debug-enabled libraries.  In Codec Engine 2.25, you should be able to cause all the Codec Engine-related debug-built libraries to be linked in by adding the following line to your ARM-side config script:

    xdc.loadPackage('ti.sdo.ce.global.Settings').profile = "debug";

    Chris

  • 0 in reply to Chris Ring
    Intellectual 840 points

    Thanks for answer. I will try to do it.

    Other side:

    problem to run ready example, like describe in "Build/Run Instructions for Codec Engine Examples for Windows CE" :

    i try to run

    s app_remote_wince.exe in.dat out.dat , but I've got message "error: can't open engine image1_copy", but i place into image (NK.bin) all.x64P (from examples\ti\sdo\ce\examples\servers\all_codecs\bin\ti_platforms_evm3530\), and when wince image running i can see all.x64P file in \windows directory.

    How i can fix this problem? How i can debug this problem?

  • 0 in reply to SimpleSoft
    Intellectual 840 points

    Sorry [:D] , i found solution in

    http://e2e.ti.com/forums/t/8021.aspx?PageIndex=1