Single Step not possible in debugging

  • Hello,


    are there problems in debug mode?

    I try to debug - program stops at break point correctly.

    But when press the F10 or F11 (single step) program runs to next break point (like F5).

    No single step is available.

    Is there a problem or do I something wrong?


    Best regards, Andy

  • Hello,


    which SDK, Visual Studio and OS you are using?

    Any additional messages from Vsiual Studio?

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • Hello,


    installed the current SDK from your webpage (FSIMX6_WEC7_SDK_151015.msi and FSVYBRID_WEC7_SDK.msi). Using MS Visual Studio 2008 on Windows7pro.

    There are no additional messages from Visual Studio.

    Sometimes it works but sometimes not - don't know what's different.


    Best regards, Andy

  • Hello,


    sorry i just debug on a NetDCUA9 using FSVYBRID_WEC7_SDK and MS Visual Studio 2008 but i cannot reproduce the problem.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • Hello,


    sorry i just debug on a NetDCUA9 using FSVYBRID_WEC7_SDK and MS Visual Studio 2008 but i cannot reproduce the problem.

    This works? Why then different SDKs? I thought pinmapping or smth else is different? Means this, i can build 100% working binary compatible exe-Files for NetDCUA9 by using the SDK for the NetDCUA5?

  • Hello,


    yes this works! In the worst case some headers/libs missed*). SDK contains only contains only stuff about APIs. API is the same for all our boards (else you can't built). Processor dependend stuff is in the "OS". Take a look to the SDK folder.


    >>Means this, i can build 100% working binary compatible exe-Files for NetDCUA9 by using the SDK for the NetDCUA5?

    << Concerning the SDK yes. But it depends also on your code, e.g. if you use hard code registry paths or DLL names it won't work.


    >> Why then different SDKs?

    << *)To be sure all headers and libs for the modules include into the image are available. But this is a minor issus and i rarely saw it.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • i compared with meld and winmerge the sdk folders and saw some differences in several header files. but if this makes no difference and i can use same sdk for the different platforms, i will not have to build binaries for every target any longer


    :-)

  • sorry i just debug on a NetDCUA9 using FSVYBRID_WEC7_SDK and MS Visual Studio 2008 but i cannot reproduce the problem.


    Hello,


    still have the problem. Either with FSVYBRID_WEC7_SDK or with FSIMX6_WEC7_SDK. Still the same wrong behaviour.

    The only thing I do after creating a new project, is to add the 2 directories

    Code
    1. C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce7\atlmfc\include
    2. C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce7\include

    into include path. Did I forgot something?

    Could you maybe send me a small "Hello World" project, where I could test to debug? If it's not working with that, then there should be a problem with my configuration? But on the other side - debugging with a NetDCU11.2 board works without problems...


    Thanks a lot in advance...


    Andy

  • Hello,


    this seems to be exactly your problem Debugger issues with Embedded Compact 7.

    Does it help?


    I wonder about "Sometimes it works but sometimes not - don't know what's different."


    PS: link to the Service Pack (the link inside the link above is obsolet) Visual Studio 2008 SP1 update for Windows Embedded Compact 7

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Edited once, last by fs-support_ZU ().

  • Hello,


    yes thank you. This helped.

    After searching the appropriate file for approx. 1h, I finally found the needed file.

    The link of your referenced page unfortunately didn't work. So I had to search manually.

    Just for interest, the needed file is called: "VS90SP1-KB2483802-x86.exe"

    Now debugging works as expected. :-)

    Thanks a lot.


    Best regards, Andy