• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 55 subscribers
  • Views 1000 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.

Original question:

Request to display names on chip diagram in SysConfig

CODECOMPOSER: Sysconfig custom board

Martin Helie
Expert 2555 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: SYSCONFIG, CCSTUDIO

Hi, using CCS10 on MacOS.

When switching to a custom board, all I can see in Sysconfig is pin numbers. The referenced thread mentions hovering over pins to get more details, but that doesn't work in my case.

Also, when choosing the pin in pinmux, all I see there is the pin number, not the pin's function. It would be very helpful to see more details there; here, one has to reference the datasheet for a device as well as the custom board schematic.

Of course, it would also be helpful to be able to define custom boards as well to avoid schematic lookups too.

Oh, also, in Sysconfig CCS, CMD-S doesn't work, and one has to use the dropdowns everytime.

Is any of that in the roadmap?

  • 0
    TI__Guru**** 251710 points

    Unfortunately, the SysConfig experts are out today.  A reply should be posted by tomorrow.

    Thanks and regards,

    -George 

  • 0
    TI__Guru**** 474151 points

    Hello,

    Can you specify the exact CCS10 version being used and the exact macOS version being used?

    Thanks

    ki 

  • 0 in reply to Ki
    Expert 2555 points

    Hi! CCS 10.3.1, MacOS 11.6 (Big Sur).

    FYI, I found the thread with CCS11 beta download, which I am also using, and the editor works much better on Big Sur, but Sysconfig doesn't seem to launch).

  • 0 in reply to Martin Helie
    TI__Guru**** 162965 points

    mh,

    Which device are you using?  I want to try importing a project that uses SysConfig to see if I am able to open it on my BigSur machine.  I tried a project for CC1312 and I am able to open the SysConfig tool fine from within CCS by double-clicking on the .syscfg file in the project explorer in CCS.

    John

  • 0 in reply to JohnS
    Expert 2555 points

    Hi John,

    I don't think it's related to the device (neither CC1352 or CC1312 projects appear to launch Sysconfig within CCS11). Even Resource explorer comes up empty (looks identical to when I open Sysconfig):

  • 0 in reply to Martin Helie
    TI__Guru**** 162965 points

    Ok that looks like the same issue that someone was running into here:

    https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1041152/installed-ccs-10-4-with-issues-on-mac-m1/3852555#3852555

    Basically browser-based views in CCS (Resource Explorer, SysConfig...) were coming up blank.  For this user it just went away.  If you open the error view does it display anything?  Go to the View menu.  Select Other.  And then type error at the top of the dialog that opened and then select the error log view.

    Regards,

    John

  • 0 in reply to JohnS
    Expert 2555 points

    John, here's a stack trace:

    !ENTRY org.eclipse.e4.ui.workbench 4 0 2021-10-12 11:17:08.392
!MESSAGE
!STACK 0
java.lang.NullPointerException
        at com.ti.ccstudio.project.ui.webcontent.internal.sysconfig.SysConfigEditor.api_navigateToScript(SysConfigEditor.java:838)
        at com.ti.ccstudio.project.ui.webcontent.internal.sysconfig.SysConfigEditor.access$2(SysConfigEditor.java:833)
        at com.ti.ccstudio.project.ui.webcontent.internal.sysconfig.SysConfigEditor$SelectionListener.selectionChanged(SysConfigEditor.java:394)
        at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:266)
        at org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(SelectionService.java:98)
        at org.eclipse.ui.internal.e4.compatibility.SelectionService.lambda$0(SelectionService.java:72)
        at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$1.run(SelectionAggregator.java:123)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
        at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(SelectionAggregator.java:120)
        at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$5.lambda$0(SelectionAggregator.java:220)
        at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:59)
        at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$5.changed(SelectionAggregator.java:220)
        at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:108)
        at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:364)
        at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:379)
        at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(SelectionServiceImpl.java:34)
        at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(CompatibilityPart.java:471)
        at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:151)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
        at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:174)
        at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:148)
        at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2132)
        at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1178)
        at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:466)
        at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1207)
        at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
        at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:237)
        at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:402)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
        at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4441)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1512)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1535)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1520)
        at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1324)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4227)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3837)
        at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1157)
        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:134)
        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:653)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1461)

  • 0 in reply to Martin Helie
    Expert 2555 points

    Applied a rather brute force fix by removing:

    .metadata/.plugins/com.ti.ccstudio.project.ui.webcontent, which allows me to confirm that some of the issues reported in CCS10.3 are fixed:

    CMD-S works

    Hover over a pin works as advertised

    BUT

    PinMux still only shows pin number, and it would really be helpful to get pin function, even when using custom boards.

  • +1 in reply to Martin Helie
    Expert 2555 points

    Well, I guess I can close this topic by saying I just discovered this:

    which solves my last reported issue.

    Next thing you'll tell me is we can in fact define our own custom boards :-)

    If it's any help for beta, the ccs workspace that produced the null pointer error was imported from a ccs 10 workspace.

  • +1 in reply to Martin Helie
    TI__Guru**** 474151 points

    Glad to hear that your issues appear to be resolved!

    Martin Helie said:
    If it's any help for beta, the ccs workspace that produced the null pointer error was imported from a ccs 10 workspace.

    We do not recommend re-using a workspace from an older CCS version, especially if it is a major revision difference (like CCSv10 and CCSv11). It can cause various issues like what you experienced. It is always best to work with a clean new workspace and import the projects to it.

    Thanks

    ki

  • 0 in reply to Martin Helie
    TI__Guru**** 162965 points

    There is some information on working with custom boards here:

    https://software-dl.ti.com/ccs/esd/sysconfig/docs/guide/custom-board.html

    I suspect that you are already following the instructions in section 1.2.

    Regards,

    John