• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1030 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.

CCS/MSP432P4111: Assert while importing projects to CCS workspace

Javier Gaston
Prodigy 50 points
Part Number: MSP432P4111


Tool/software: Code Composer Studio

My workspace consist on 3 projects:

-tirtos_builds_MSP_EXP... (library, TI SDK)

-library (library, dependency to tirtos_builds)

-Application (executable, dependency on abstraction_library and tirtos_builds)

If I try to import by selecting the 3 of them, then ccs pop ups "assertion failed: operation was not prepared"

I've been following   and may other ways, but always have this issue

The log file just gives internal eclipse function assertions but no sense to me.

It actually depends on the order the projects are imported, I mean, if i import the library, the library and the tirtos_builds_MSP_EXP are imported correctly. But if i import the application, then the error occurs and the error window shows there is no tirtos_builds_MSP_EXP project.

Thanks

  • 0
    TI__Guru**** 473441 points

    Hello,

    Is there an explicit project dependency set in the main project for the tirtos_builds_MSP_EXP project?

    Javier Gaston said:
    The log file just gives internal eclipse function assertions but no sense to me.

    Can you attach the log file to this thread?

    Also provide the exact CCS version number for your CCS version.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 50 points

    Hi Ki, thanks for your reply

    CCS version 10.1.0.00010

    Regarding the dependencies: yes, both application and library have explicit project dependencies to tirtos_builds_MSP_EXP library. I've set these dependencies the same way the "outofbox" project. Find attached an image of the project window.

    Also find attached the log file

    Thx

    Fullscreen 6403.log.txt Download 
    !SESSION 2021-01-07 08:44:47.651 -----------------------------------------------
eclipse.buildId=4.14.0.I20191210-0610
java.version=1.8.0_144
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 1 0 2021-01-07 08:44:57.363
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 1 0 2021-01-07 08:44:57.366
!MESSAGE debugServerDir=C:/ti/ccs1010/ccs/ccs_base/DebugServer

!ENTRY com.ti.ccstudio.ui 1 0 2021-01-07 08:45:14.107
!MESSAGE CCS IDE session started!
	CCS build: 10.1.0.00010
	CCS location: C:/ti/ccs1010/ccs
	Workspace location: C:/Users/user/projects/CodeComposer/test2

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.356
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.357
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.359
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.361
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.361
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.364
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.367
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.369
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.371
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-01-07 08:45:14.378
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.project.ui.webcontent 1 0 2021-01-07 08:45:14.461
!MESSAGE CCS HTTP adapter started! [ccs.port:50811] - Open 'http://localhost:50811/ide' in web browser to see listing of available APIs...

!ENTRY org.eclipse.cdt.core 4 0 2021-01-07 08:46:29.714
!MESSAGE Error: assertion failed: Operation was not prepared.
!STACK 0
org.eclipse.core.runtime.AssertionFailedException: assertion failed: Operation was not prepared.
	at org.eclipse.core.runtime.Assert.isTrue(Assert.java:113)
	at org.eclipse.core.internal.resources.Workspace.beginOperation(Workspace.java:352)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2288)
	at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.runAtomic(CProjectDescriptionManager.java:503)
	at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.runWspModification(CProjectDescriptionManager.java:471)
	at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.runWspModification(CProjectDescriptionManager.java:443)
	at org.eclipse.cdt.internal.core.settings.model.CExternalSettingsManager.handleEvent(CExternalSettingsManager.java:631)
	at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.notifyListeners(CProjectDescriptionManager.java:2218)
	at org.eclipse.cdt.internal.core.settings.model.AbstractCProjectDescriptionStorage.fireLoadedEvent(AbstractCProjectDescriptionStorage.java:271)
	at org.eclipse.cdt.internal.core.settings.model.xml.XmlProjectDescriptionStorage.getProjectDescription(XmlProjectDescriptionStorage.java:267)
	at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescriptionInternal(CProjectDescriptionManager.java:426)
	at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(CProjectDescriptionManager.java:408)
	at org.eclipse.cdt.managedbuilder.core.ManagedBuildManager.findBuildInfo(ManagedBuildManager.java:2673)
	at org.eclipse.cdt.managedbuilder.core.ManagedBuildManager.getBuildInfo(ManagedBuildManager.java:2945)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getBuildInfo(CTIProjectCoreUtils.java:247)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getBuildInfo(CTIProjectCoreUtils.java:234)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getManagedProject(CTIProjectCoreUtils.java:343)
	at com.ti.common.project.core.internal.settings.AConfigurationSettings.getDependencies(AConfigurationSettings.java:487)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getDependencies(CTIProjectCoreUtils.java:1613)
	at org.eclipse.rtsc.xdctools.buildDefinitions.XDC.util.XDCManagedBuildCoreUtils.findReferencedRTSCConfiguration(XDCManagedBuildCoreUtils.java:156)
	at org.eclipse.rtsc.xdctools.buildDefinitions.XDC.util.XDCManagedBuildCoreUtils.findRTSCConfiguration(XDCManagedBuildCoreUtils.java:149)
	at org.eclipse.rtsc.builddefinitions.xdc.settings.XDCConfigurationSettingsContributor.getProductsSettingSource(XDCConfigurationSettingsContributor.java:79)
	at com.ti.common.project.core.internal.settings.AConfigurationSettings.getInheritedProductsSource(AConfigurationSettings.java:1042)
	at com.ti.common.project.core.internal.settings.AConfigurationSettings.getInheritedProducts(AConfigurationSettings.java:644)
	at com.ti.common.project.core.internal.settings.AConfigurationSettings.getProducts(AConfigurationSettings.java:670)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getProducts(CTIProjectCoreUtils.java:1699)
	at com.ti.common.project.core.variables.ProductPathVariableResolver.doGetValue(ProductPathVariableResolver.java:84)
	at com.ti.common.project.core.variables.APathVariableResolver.getValue(APathVariableResolver.java:76)
	at org.eclipse.core.internal.resources.ProjectVariableProviderManager$Descriptor.getValue(ProjectVariableProviderManager.java:65)
	at org.eclipse.core.internal.resources.ProjectPathVariableManager.internalGetValue(ProjectPathVariableManager.java:160)
	at org.eclipse.core.internal.resources.ProjectPathVariableManager.resolveVariable(ProjectPathVariableManager.java:233)
	at org.eclipse.core.internal.resources.ProjectPathVariableManager.resolveVariable(ProjectPathVariableManager.java:218)
	at org.eclipse.core.internal.resources.ProjectPathVariableManager.resolveURI(ProjectPathVariableManager.java:291)
	at org.eclipse.core.internal.localstore.FileStoreRoot.computeURI(FileStoreRoot.java:108)
	at org.eclipse.core.internal.localstore.FileSystemResourceManager.locationURIFor(FileSystemResourceManager.java:812)
	at org.eclipse.core.internal.resources.Resource.getLocationURI(Resource.java:1085)
	at org.eclipse.core.internal.resources.LocationValidator.validateLinkLocationURI(LocationValidator.java:172)
	at org.eclipse.core.internal.resources.Workspace.validateLinkLocationURI(Workspace.java:2544)
	at org.eclipse.core.internal.resources.Resource.assertLinkRequirements(Resource.java:166)
	at org.eclipse.core.internal.resources.Resource.createLink(Resource.java:636)
	at org.eclipse.core.internal.resources.Project.reconcileLinksAndGroups(Project.java:1184)
	at org.eclipse.core.internal.resources.Project.open(Project.java:1064)
	at org.eclipse.core.internal.resources.Project.open(Project.java:1112)
	at com.ti.ccstudio.project.core.services.ProjectImporter.internalImportProject(ProjectImporter.java:473)
	at com.ti.ccstudio.project.core.services.ProjectImporter.access$1(ProjectImporter.java:415)
	at com.ti.ccstudio.project.core.services.ProjectImporter$1.run(ProjectImporter.java:377)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2292)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2317)
	at com.ti.ccstudio.project.core.services.ProjectImporter.importProject(ProjectImporter.java:375)
	at com.ti.ccstudio.project.core.services.ProjectImporter.importProject(ProjectImporter.java:397)
	at com.ti.ccstudio.project.ui.internal.wizards.importexport.ProjectImportPage.createExistingProject(ProjectImportPage.java:1373)
	at com.ti.ccstudio.project.ui.internal.wizards.importexport.ProjectImportPage.access$27(ProjectImportPage.java:1211)
	at com.ti.ccstudio.project.ui.internal.wizards.importexport.ProjectImportPage$16.execute(ProjectImportPage.java:1161)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.lambda$0(WorkspaceModifyOperation.java:110)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2292)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2317)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:131)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

!ENTRY com.ti.common.project.core 4 0 2021-01-07 08:46:30.027
!MESSAGE assertion failed: Operation was not prepared.
!STACK 0
org.eclipse.core.runtime.AssertionFailedException: assertion failed: Operation was not prepared.
	at org.eclipse.core.runtime.Assert.isTrue(Assert.java:113)
	at org.eclipse.core.internal.resources.Workspace.beginOperation(Workspace.java:352)
	at org.eclipse.core.internal.resources.Resource.createLink(Resource.java:638)
	at org.eclipse.core.internal.resources.Project.reconcileLinksAndGroups(Project.java:1184)
	at org.eclipse.core.internal.resources.Project.open(Project.java:1064)
	at org.eclipse.core.internal.resources.Project.open(Project.java:1112)
	at com.ti.ccstudio.project.core.services.ProjectImporter.internalImportProject(ProjectImporter.java:473)
	at com.ti.ccstudio.project.core.services.ProjectImporter.access$1(ProjectImporter.java:415)
	at com.ti.ccstudio.project.core.services.ProjectImporter$1.run(ProjectImporter.java:377)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2292)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2317)
	at com.ti.ccstudio.project.core.services.ProjectImporter.importProject(ProjectImporter.java:375)
	at com.ti.ccstudio.project.core.services.ProjectImporter.importProject(ProjectImporter.java:397)
	at com.ti.ccstudio.project.ui.internal.wizards.importexport.ProjectImportPage.createExistingProject(ProjectImportPage.java:1373)
	at com.ti.ccstudio.project.ui.internal.wizards.importexport.ProjectImportPage.access$27(ProjectImportPage.java:1211)
	at com.ti.ccstudio.project.ui.internal.wizards.importexport.ProjectImportPage$16.execute(ProjectImportPage.java:1161)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.lambda$0(WorkspaceModifyOperation.java:110)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2292)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2317)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:131)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

!ENTRY org.eclipse.cdt.core 1 0 2021-01-07 08:46:34.271
!MESSAGE Indexed 'Application' (25 sources, 58 headers) in 2.95 sec: 4,393 declarations; 7,393 references; 47 unresolved inclusions; 0 syntax errors; 451 unresolved names (3.7 %)

!ENTRY org.eclipse.cdt.core 1 0 2021-01-07 08:46:34.275
!MESSAGE Indexed 'Library' (0 sources, 0 headers) in 0.001 sec: 0 declarations; 0 references; 0 unresolved inclusions; 0 syntax errors; 0 unresolved names (0 %)

!ENTRY com.ti.ccstudio.project.core 1 0 2021-01-07 08:46:35.006
!MESSAGE SysConfigOutputNameProvider: error invoking sysconfig-tool for project 'Application': Invalid argument '--product': No product with name "simplelink_msp432p4_sdk" and version "3.40.01.02" found

  • 0
    TI__Guru**** 473441 points

    Thanks. I assume you are importing the project with the "Automatically import referenced projects found in same-directory" enabled. I tried a similar setup and I don't get an assertion. But I get a warning that the tirtos_builds_MSP_EXP432P4111_release_ccs project could not be found when importing the lib project, even though the main application project already imported it. The issue looks like a case where if both the main and dependent project both have another dependency on the same project, then it causes issues with the project import when that auto-import option is enabled. I'm pretty sure that is what is going on in your case also. However, I don't get the assertion, just a warning. I can file a bug regarding the warning, but I can't reproduce the assertion. I will send the logs to engineering for further analysis

  • 0 in reply to Ki
    Prodigy 50 points

    Thanks Ki,

    Regarding the option "Automatically import referenced projects found in same-directory", I've tried with and without this option with no changes. But obviously when this is not enabled I have to check manually all dependent projects.

    Extrange about you dont get the assertion, all the developers of this project are having this issue.

    I'm thinking about the linked folder we are using, Did you also try to do a link to a source folder outside the project folder? if you check the project explorer on my previous post, both the library and application projects have their sources on a linked folder.

    Regards

  • 0 in reply to Javier Gaston
    TI__Guru**** 473441 points

    Javier Gaston said:
    I'm thinking about the linked folder we are using, Did you also try to do a link to a source folder outside the project folder? if you check the project explorer on my previous post, both the library and application projects have their sources on a linked folder.

    I just tried setting that up also. But I still do not get the assertion.

  • 0 in reply to Ki
    TI__Guru**** 473441 points

    Engineering has analyzed the log and it appears there may be some timing problem that is causing the issue. I filed a bug for it. Tracking link:

    https://sir.ext.ti.com/jira/browse/EXT_EP-10207

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 473441 points

    Ki said:
    Thanks. I assume you are importing the project with the "Automatically import referenced projects found in same-directory" enabled. I tried a similar setup and I don't get an assertion. But I get a warning that the tirtos_builds_MSP_EXP432P4111_release_ccs project could not be found when importing the lib project, even though the main application project already imported it. The issue looks like a case where if both the main and dependent project both have another dependency on the same project, then it causes issues with the project import when that auto-import option is enabled. I'm pretty sure that is what is going on in your case also. However, I don't get the assertion, just a warning. I can file a bug regarding the warning, but I can't reproduce the assertion. I will send the logs to engineering for further analysis

    I filed a bug for this also. Tracking ID: https://sir.ext.ti.com/jira/browse/EXT_EP-10208