• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 3612 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

OMAP3530 / WINCE / BSP6.14.01 Debug Build Error

Luan Le
Expert 2280 points

Hi,

I have the following error when building a Debug build.  It is built OK for the Release.

BUILD: [00:0000006936:PROGC ] Building LINK Pass in C:\WINCE600\PLATFORM\COMMON\SRC\SOC\OMAP35XX_TPS659XX_TI_V1\omap\PM\CONSTRAINTADAPTERS\DLL\ directory.
BUILD: [01:0000006947:PROGC ] Linking C:\WINCE600\platform\common\target\ARMV4I\debug\ti_constraintadapters_omap35xx_tps659xx_ti_v1.dll
BUILD: [01:0000006965:ERRORE] pwrdom_constraint_lib_omap35xx_tps659xx_ti_v1.lib(powerdomaincontext.obj) : error LNK2001: unresolved external symbol __CxxFrameHandler3
BUILD: [01:0000006966:ERRORE] corelib0.lib(gshandlereh.obj) : error LNK2001: unresolved external symbol __CxxFrameHandler3
BUILD: [01:0000006967:ERRORE] C:\WINCE600\platform\common\target\ARMV4I\debug\ti_constraintadapters_omap35xx_tps659xx_ti_v1.dll : fatal error LNK1120: 1 unresolved externals

Would anyone please give some tips to solve this problem?

Thanks,

Luan

  • 0
    TI__Genius 9185 points

    Luan,

    The BSP 6.14.01 "debug build" builds fine. Are you using the unmodified BSP/OSDesign to build (as a baseline) or do you have changes in the BSP/Catalog?

    Did you do a clean solution and build solution (even better just delete the C:\WINCE600\OSDesigns\EVM_3530\EVM_3530\RelDir and C:\WINCE600\OSDesigns\EVM_3530\EVM_3530\Wince600 directories before you do the build solution).

    Jatin

     

  • 0 in reply to Jatin Jain
    TI__Genius 9185 points

    Are you still having issue with the debug build?

     

  • 0 in reply to Jatin Jain
    Expert 2280 points

    Hi Jatin,

    I no longer have the problem with my debug build after I added several catalog items to my default OS designs.  I do not know which item fixes my problem and have not had time to find out.  The items that I added are

    Internet Explorer 6.0 Sample Browser, Network Utilities, Cab File Installer/Uninstaller, and OS Dependencies for .NET Compact Framwork 2.0

    I do not need any of these items but I have them included to keep me going.  I would appreciate your insights very much.

    Thanks,

    Luan

     

  • 0 in reply to Luan Le
    TI__Genius 9185 points

    Good to know at least you have been able to proceed. Couple of things that I can think of

    1. What is the latest QFE you have installed. We recommend at least the Jun 2010 if not later.

    2. Size of the debug build (this is not the issue based on your first post but something to keep in mind with debug builds).

     

  • 0 in reply to Jatin Jain
    Prodigy 10 points

    Thanks for sharing valuable information.

    I too faced the same problem and used information in thread. I nailed down to only one SYSGEN finally "OS Dependencies for .NET Compact Framwork 2.0"


    And yes you must also have certain other built tools in chain if expected

     

    Thanks

    Himanshu