• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 881 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/MSP-EXP432P401R: Getting Started, Resource Explorer and App Center inaccessible

Clyde Laforge
Prodigy 50 points

Part Number: MSP-EXP432P401R

Tool/software: Code Composer Studio

I am not able to access Getting Started, Resource Explorer and App Center page in CCS 10.1.1.00004 on linux. The only thing I can see is a unform white, grey or blue backgroud.

Going in the logs, I can see this error message: 

!ENTRY com.ti.ccstudio.app.center 4 0 2020-10-02 13:02:49.835
!MESSAGE Unable to read software-dl.ti.com/.../apps_10.1.1.json file.
!STACK 0
java.io.FileNotFoundException: software-dl.ti.com/.../apps_10.1.1.json
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1872)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
	at java.net.URL.openStream(URL.java:1045)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter.readFile(CCSAppCenter.java:190)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter.getAppJson_0(CCSAppCenter.java:206)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter.access$1(CCSAppCenter.java:205)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter$1.run(CCSAppCenter.java:177)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

And sure enough, from a browser this page displays "Sorry! We are currently doing site maintenance."

This has been happenning ever since I installed CCS, and this page has been consitently under maintenance ever since (1 or 2 weeks).

What is the problem?

P.S: I have already tried "export SWT_GTK3=0"

  • 0
    TI__Guru**** 464431 points

    Hello,

    There is a known issue with the App Center that we are looking into. But Resource Explorer and the Getting Started view should be working. It works on my Ubuntu 18.04LTS environment.

    What Linux distro are you using?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 50 points

    Thank you for the quick response

    I am using fedora 32 (which is up to date)

  • 0 in reply to Clyde Laforge
    TI__Guru**** 464431 points

    Thanks. Fedora is not an environment we officially support hence I will have to set up an environment and try this out myself.

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

    Just to confirm, you resolved all missing dependencies reported by the installer during the dependency check?

  • 0 in reply to Ki
    Prodigy 50 points

    Sorry for my late response,

    The installer did not report any missing dependencies during installation

  • 0 in reply to Clyde Laforge
    TI__Guru**** 464431 points

    Thanks. I set up a Fedora 32 environment. I have the same issues with those views being blank. However I did not resolve all the required dependencies. 

    I'm pretty sure this issue is related to some missing dependencies.

    can you try running ldd on the libraries in: 

    ./ccs/eclipse/configuration/.jxbrowser-chromium-lib

    and see if there are any missing dependencies?

    ki

  • 0 in reply to Ki
    Prodigy 50 points

    There are indeed a missing dependency, namely libjawt.so. ldd also complains about "ldd: warning: you do not have execution permission for `./XXX.so'" (replace XXX with any .so file in the folder)

    I tried going a bit further by chmod +x *.so and "export LD_LIBRARY_PATH=/usr/lib/jvm/jre-1.8.0/lib/amd64:/usr/lib/jvm/jre-1.8.0/lib/amd64/server/ "(the server folder is necessary for getting libjvm.so, required by libjawt.so).

    After that, no more ldd errors, but running ccstudio still gives me the same result

  • 0 in reply to Clyde Laforge
    Prodigy 50 points

    I found a workaround. It seems that a java component, probably javaFX, used for thoses windows is not well supported under wayland (the new default display server protocol replacing xorg). It is a bummer, but reverting to Gnome on Xorg fixes the rendering issue.

    I have not tested this under other distributions, but if it is really a problem inherent to wayland, this could become a growing concern as many distributions are currently replacing xorg by wayland as the default.