After CCS 12.2.0.00009 Installation Error Message

Some additional information:

If I click OK on the error dialog and load another workspace the error appears again.

Seems to appear every time a workspace is loaded, example workspace or old workspace from old laptop.

Also I am using a 28379D processor.

Any ideas appreciated, old laptop crashed last week and I'm trying to get going on a new laptop.

Thanks John

Hi John,

Based on your log, looks like the installation went fine. The issue looks to be when trying to run CCS.

Which processor is in your Mac? M1?

Please attach the Eclipse error log in <WORKSPACE>\.metadata\.log

Thanks

ki

Hi Ki,
Thanks for the response.
I have a:
MacBook Pro (16-inch, 2019)
2.4 GHz 8-Core Intel Core i9
64 GB 2667 MHz DDR4

Attached is the Eclipse error log from the workspace that loaded when I started up.
Thanks John

5315..log.zip

J. Gomez said:

Seems to appear every time a workspace is loaded, example workspace or old workspace from old laptop.

Does it crash when using a new (empty) workspace?

I switched to a new workspace name so it would be created and I got the same error dialog with the addition that the Welcome screens says:

Failed to create the part's controls

If I click details I get:

java.lang.ExceptionInInitializerError
at com.ti.chromium.browser.ChromiumBrowserContributor.createBrowser(ChromiumBrowserContributor.java:39)
at com.ti.browser.internal.TIBrowser.<init>(TIBrowser.java:98)
at com.ti.browser.internal.TIBrowser.<init>(TIBrowser.java:88)
at com.ti.browser.internal.TIBrowser.<init>(TIBrowser.java:84)
at com.ti.browser.TIBrowserFactory.createBrowser(TIBrowserFactory.java:45)
at com.ti.ccstudio.branding.internal.CCSIntroPart.createPartControl(CCSIntroPart.java:177)
at org.eclipse.ui.internal.ViewIntroAdapterPart.createPartControl(ViewIntroAdapterPart.java:135)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:158)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:155)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:365)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:995)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:960)
at org.eclipse.e4.core.internal.di.InjectorImpl.internalInject(InjectorImpl.java:140)
at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:403)
at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:330)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:202)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:91)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:60)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:42)
at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:132)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:995)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:659)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:544)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:528)
at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:73)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:995)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:659)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:763)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:712)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.subscribeTopicToBeRendered(PartRenderingEngine.java:161)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
at org.eclipse.e4.core.di.internal.extensions.EventObjectSupplier$DIEventHandler.handleEvent(EventObjectSupplier.java:92)
at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:205)
at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:203)
at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:151)
at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:133)
at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:75)
at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:44)
at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:55)
at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:63)
at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:424)
at org.eclipse.e4.ui.model.application.ui.impl.UIElementImpl.setToBeRendered(UIElementImpl.java:314)
at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:655)
at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:624)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:787)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:758)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:680)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:675)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1252)
at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1247)
at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1235)
at org.eclipse.ui.internal.WorkbenchPage.lambda$11(WorkbenchPage.java:4228)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:74)
at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4226)
at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4208)
at org.eclipse.ui.internal.WorkbenchIntroManager.createIntro(WorkbenchIntroManager.java:176)
at org.eclipse.ui.internal.WorkbenchIntroManager.showIntro(WorkbenchIntroManager.java:124)
at org.eclipse.ui.application.WorkbenchWindowAdvisor.openIntro(WorkbenchWindowAdvisor.java:188)
at org.eclipse.ui.internal.ide.application.IDEWorkbenchWindowAdvisor.openIntro(IDEWorkbenchWindowAdvisor.java:573)
at org.eclipse.ui.internal.WorkbenchWindow.setup(WorkbenchWindow.java:933)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:995)
at org.eclipse.e4.core.internal.di.InjectorImpl.internalInject(InjectorImpl.java:140)
at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:96)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.inject(ContextInjectionFactory.java:83)
at org.eclipse.ui.internal.Workbench.createWorkbenchWindow(Workbench.java:1469)
at org.eclipse.ui.internal.StandardTrim.createStatusLine(StandardTrim.java:118)
at org.eclipse.ui.internal.StandardTrim.createWidget(StandardTrim.java:48)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:995)
at org.eclipse.e4.core.internal.di.InjectorImpl.internalInject(InjectorImpl.java:140)
at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:403)
at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:344)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:227)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:94)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:60)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:37)
at org.eclipse.e4.ui.workbench.renderers.swt.ToolControlRenderer.createWidget(ToolControlRenderer.java:129)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:995)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:659)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:763)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:712)
at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72)
at org.eclipse.e4.ui.workbench.renderers.swt.TrimBarRenderer.processContents(TrimBarRenderer.java:109)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:673)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:544)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:528)
at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.processContents(WBWRenderer.java:680)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:673)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:763)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:712)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1083)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
Caused by: com.teamdev.jxbrowser.engine.ChromiumProcessStartupFailureException: Process exit code: 139
at com.teamdev.jxbrowser.engine.internal.EngineImpl.throwExceptionAndCleanup(EngineImpl.java:478)
at com.teamdev.jxbrowser.engine.internal.EngineImpl.newInstance(EngineImpl.java:281)
at com.teamdev.jxbrowser.engine.Engine.newInstance(Engine.java:106)
at com.ti.chromium.browser.JxBrowser.<clinit>(JxBrowser.java:236)
... 139 more

Please attach this newly generated .log file

Thanks

ki

Ki said:

Please attach this newly generated .log file

From the new workspace folder

Attached is the log from the new workspace.

7242..log.zip

Thanks.

Can you add the following lines to <CCS INSTALL DIR ROOT>/ccs/eclipse/ccstudio.ini :

-Djxbrowser.logging.level=ALL
-Djxbrowser.logging.file=<path to jxbrowser.log>

Then run CCS again and reproduce the error. Then attach the generated log located in the specified path above.

Thanks

ki

Hi ki,

I wanted to verify that I will be changing the correct file, since the location is a little different.
You said:
    <CCS INSTALL DIR ROOT>/ccs/eclipse/ccstudio.ini

When I look at the defined links I see:
    <CCS INSTALL DIR ROOT> = Applications/ti/ccs1220/ccs

This already has ccs in the link so I assumed a typo, but I didn't see the file in that location.
When I dug down a little I see this by opening the Eclipse.app package:
    /Applications/ti/ccs1220/ccs/eclipse/Eclipse.app/Contents/Eclipse/ccstudio.ini

Is this the correct file to modify ?

Thanks John

Also found a second copy along that same path:

    /Applications/ti/ccs1220/ccs/eclipse/Eclipse.app/Contents/Eclipse/configuration/ccstudio.ini

ki,

Is this something I was supposed to change to a path ?

    <path to jxbrowser.log>

J. Gomez said:

This already has ccs in the link so I assumed a typo, but I didn't see the file in that location.
When I dug down a little I see this by opening the Eclipse.app package:
    /Applications/ti/ccs1220/ccs/eclipse/Eclipse.app/Contents/Eclipse/ccstudio.ini

Sorry, I forgot to account for the difference in the macos directory structure. Yes, the above path looks correct

J. Gomez said:

Is this something I was supposed to change to a path ?

    <path to jxbrowser.log>

Yes, specify the path you want the jxbrowser.log file to be generated in

Attached is the log that was generated.

jxbrowser.log

Thanks. Engineering does not see any issue in the log. When this log was generated, you got the "CrashReportJob". java.lang.NullPointerException error?

Yes, I got the same error dialog.

Can you provide any jxbrowser crash dump files in:

$HOME/Library/Application Support/JxBrowser/7.12.1/CrashReports

Maybe just zip up the whole folder and attach to this thread

Attached is the CrashReports folder.

CrashReports.zip

Thanks. I have sent them to engineering for further analysis. I'll pass on any updates as I receive them.

ki,

I wanted to try and build one of my projects to see if the binary output files match what I got from the old laptop that crashed.

I used the same cgt, but I got an error message when I tried to build one of the processors.

    gmake[1]: /Applications/ti/ccs1220/ccs/utils/tiobj2bin/tiobj2binfill: Command not found

Should I open another post or wait until this current issue is resolved ?

Thanks John

Just for future reference:

J. Gomez said:

Seems to appear every time a workspace is loaded, example workspace or old workspace from old laptop.

It is typically not recommended to reuse an existing workspace folder from another machine. Workspace folders have a bunch of cached data that is specific to the machine that created the workspace and is not designed to be portable. Please use a new workspace folder in these scenarios and import existing projects to the new workspace.

J. Gomez said:

    gmake[1]: /Applications/ti/ccs1220/ccs/utils/tiobj2bin/tiobj2binfill: Command not found

tiobj2binfill doesn't exist on my machine either. What called this command? A post build step? 

The old laptop is not available, so I can't export settings and I have noticed that exporting settings does not seem to export everything. I have a backup of the entire workspace. If I start a new workspace, I have no way to remember all the settings that have been done over the years.

Yes, a post build step called this to generate the binary files we have been using.

I looked in the old machines backups in the ccs1020 folder I found:
    /Applications/ti/ccs1020/ccs/utils/tiobj2bin/tiobj2binfill

J. Gomez said:

I looked in the old machines backups in the ccs1020 folder I found:
    /Applications/ti/ccs1020/ccs/utils/tiobj2bin/tiobj2binfill

I looked inside the same ccs1020 folder on my macbook and do not see tiobj2binfill file. Is that file a script based off tiobj2bin? if so, it may have been a custom script that didn't originally come from CCS.

Yes, it is a script. So I can just copy it to the new directory.

I'm guessing it is an old script that we got from TI a long time ago and when cgt tools were updated it just kept getting copied over.

I'll try that, how long do you think it will take for engineering to get back to you? I'm getting a lot of pressure from my boss to get back up and running. 

Here's the top of the script:

#!/bin/bash
#---------------------------------------------------------------------------
# tiobj2bin - Converts TI object file from COFF or ELF to binary
# dump format. Intended for use as a post-build step in CCS.
#
# This code released under a license detailed at the end of this file.
#
# Invoke: tiobj2bin file.out file.bin [ofd] [hex] [mkhex]

J. Gomez said:

I'm guessing it is an old script that we got from TI a long time ago and when cgt tools were updated it just kept getting copied over.

yes it looks like someone took the original tiobj2bin script and modified it. Not wure where it is from but it does not come with CCS by default.

J. Gomez said:

I'll try that, how long do you think it will take for engineering to get back to you?

The issue is that not all the components in CCS are developed by TI. The error you are reporting appears to be related to the JxBrowser so we need to work with the external group that develops JxBrowser. We escalated the issue to them and are waiting for a response. 

Can you try the below:

Browse to:

/Applications/ti/ccs1220/ccs/eclipse/Eclipse.app/Contents/Eclipse/plugins/com.ti.ccstudio.branding_[version]

Open "plugin_customization.ini" in a text editor

In line 2, change the value of "org.eclipse.ui/showIntro" to "false" 

Then launch CCS using a NEW workspace folder.

The above steps will disable the Getting Started view from opening by default in a new workspace. I'm curious if that will prevent the error on startup.

Sorry, still got:

An internal error occurred during: "CrashReportJob".

java.lang.NullPointerException

I copied the script file over and built an old project from the backed off workspace and the binary output files are bit for bit equal with the old binary output files, so at least it looks like I can build an old release. Hopefully we can resolve this issue and see that this all should be working.

Engineering provided an update that there was nothing of concern in the dump file.

Can you try one more thing:

-Delete all dump files in: $HOME/Library/Application Support/JxBrowser/7.12.1/CrashReports (maybe just detele all the contents in the folder)

-start CCS using a brand new (empty) workspace

-I assume the error will occur and shut down CCS. When that happens, again send the new <WORKSPACE>/.metadata/.log file and all the CrashReports generated.

Thanks

ki

Ki said:

-Delete all dump files in: $HOME/Library/Application Support/JxBrowser/7.12.1/CrashReports (maybe just detele all the contents in the folder)

-start CCS using a brand new (empty) workspace

-I assume the error will occur and shut down CCS. When that happens, again send the new <WORKSPACE>/.metadata/.log file and all the CrashReports generated.

Please disregard the above request. We believe the root issue of the error you get is proxy related:

!ENTRY org.eclipse.core.jobs 4 2 2023-01-23 14:10:38.037
!MESSAGE An internal error occurred during: "CrashReportJob".
!STACK 0
java.lang.NullPointerException
at com.btr.proxy.search.desktop.osx.OsxProxySearchStrategy.getProxySelector(OsxProxySearchStrategy.java:103)
at com.btr.proxy.search.desktop.DesktopProxySearchStrategy.getProxySelector(DesktopProxySearchStrategy.java:34)
at com.btr.proxy.search.ProxySearch.getProxySelector(ProxySearch.java:193)
at com.ti.ccstudio.errorreporting.HtmlPostUtility.getProxy(HtmlPostUtility.java:84)
at com.ti.ccstudio.errorreporting.HtmlPostUtility.<init>(HtmlPostUtility.java:62)
at com.ti.ccstudio.errorreporting.ErrorReportJob.run(ErrorReportJob.java:64)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

When the error happens, does CCS crash (shut down) or is it still running afterwards.

CCS is still running, if I click OK. I can do a build like I mentioned earlier and the results seem correct.

Just every time I open/switch workspaces I get the null pointer exception error, this sounds like a bad error, but CCS seems to work afterwards.

Do views like Resource Explorer work for you? Can you browse content successfully there?

I selected the Resource Explorer view and opened the datasheet for this processor successfully.

I don't really use this normally,

Based on your logs, you get that error popup because of some Eclipse proxy issue. But CCS itself does not seem to have an issue accessing the internet. The error shouldn't impact your builds and usage of CCS but I imagine that it is very annoying.

I built some code and went to debug it, I went to disconnect the CLA on processor 2 like usual and it also disconnected processor 2.

This has not happened in the past, usually I can disconnect from the CLA without the debugger disconnecting from the associated processor.

Is this something new or a problem? I usually disconnect from the CLA since it always grabs context in the debugger and I really don't need to debug CLA code usually, but I do need to debug processor 2.

J. Gomez said:

Is this something new or a problem? I usually disconnect from the CLA since it always grabs context in the debugger and I really don't need to debug CLA code usually, but I do need to debug processor 2.

I can reproduce this in 12.2.0. And yes, this did not happen on older CCS versions (I tried on 10.4.0 and there is no issue there). I'm not sure if this change is intentional or not. I'll need to follow up with engineering

Thanks, this is making debugging difficult.