GUIComposer: 'Maqetta Bundler Loader' has encountered a problem

Hi Matt,

It could be that one of the required plugin is missing or you have a proxy setting that prevents the browser from communicating with the server. Can you attach the workspace log file here?

Thanks,
Patrick 

Here you find the workspace log:

5277.log.zip

I hope this is the right one.

P.S.: First I started without setting the environment variable NO_PROXY. The command "SET" in the shell gives now "NO_PROXY=localhost".

Matt,

Can you check if port 8081 to 9091 is blocked on your computer or not? Also, are you starting CCS by running ccstudio.exe or not? If you are using ccstudio.exe, check to see if you have this line in the ccstudio.ini file, -Dorg.eclipse.equinox.http.jetty.customizer.class=com.ti.ccstudio.gui.composer.http.jetty.MaqettaJettyCustomizer.

To workaround this issue, try adding these two lines to the ccstudio.ini file. Repleace <free port> with a usable port on your machine, perhaps 80.

-Dorg.eclipse.equinox.http.jetty.http.host=localhost
-Dorg.eclipse.equinox.http.jetty.http.port=<free port>

Now restart CCS by running ccstudio.exe

Regards,
Patrick 

Patrick,

The Weekend didn't help :-)

I checked the ports with NetCat and cmd netstat. Ports 8081 to 9091 should be ok.

I do start CCS always with ccstudio.exe.

I checked also the ccstudio. ini file for the line "-Dorg.eclipse.equinox.http.jetty.customizer.class=com.ti.ccstudio.gui.composer.http.jetty.MaqettaJettyCustomizer". It's okay.

After all that I tried the workaround and set port to 8081. To check I used the cmd netstat, see below.

D:\>netstat -abn

Active Connections

  Proto  Local Address          Foreign Address        State

TCP    127.0.0.1:4242         0.0.0.0:0              LISTENING
 [ccstudio.exe]
  TCP    127.0.0.1:8081         0.0.0.0:0              LISTENING
 [ccstudio.exe]
  TCP    127.0.0.1:8081         127.0.0.1:55443        ESTABLISHED
 [ccstudio.exe]

...

  TCP    127.0.0.1:55344        127.0.0.1:55345        TIME_WAIT
  TCP    127.0.0.1:55353        127.0.0.1:8081         TIME_WAIT
  TCP    127.0.0.1:55434        127.0.0.1:55435        ESTABLISHED
 [ccstudio.exe]
  TCP    127.0.0.1:55435        127.0.0.1:55434        ESTABLISHED
 [ccstudio.exe]
  TCP    127.0.0.1:55442        127.0.0.1:8081         TIME_WAIT
  TCP    127.0.0.1:55443        127.0.0.1:8081         ESTABLISHED
 [ccstudio.exe]

If I start GUIComposer a new tab will open, but the tab will stay blank. Now no more error message will appear.

During my research I saw this http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/257871/906172.aspx#906172 post, it looks to me the same.

My system is:

Intel Core i7-2620M CPU 2.70GHz, Windows 7 Enterprise SP1 64bit

What could I do more?

Kind regards

Matt

Having the GUI Composer tab open inside CCS, can you open up an external browser and enter this url, http://localhost:8081/maqetta/. See whether GC Designer comes up or not? This will at least tell us know whether it is a server issue or a browser issue.

Thanks,
Patrick 

Looks much better:

What do you propose to do? As I unterstand I could also work with GUIComposer direct in Browser.

Not all functions are usable in the external browser, you can certainly use it to do most of your design work. I just want to see whether it is a browser issue or not.

Can you also try these couple more things?

1. Open the GC Designer once in CCS to startup the server, then close it and open it again to see if it is a timing issue or not?

2. Switch to use a different browser, edit ccstudio.ini and add -DTIBrowserType=mozilla. Restart CCS and see if GC Designer works or not?

Thanks,
Patrick 

Patrick,

1. Open the GC Designer once in CCS to startup the server, then close it and open it again to see if it is a timing issue or not?

I've done the following steps:

1. Open ccstudio.exe

2. In Perspective CCS Edit, start View-> GUIComposer

3. Wait, only blank Tab is visible in CCS. To check server, open in Firefox http://localhost:8081/maqetta/. In Firefox GUIComposer is visible.

4. Close blank GUIComposer tab in CCS.

5. In Perspective CCS Edit, start View-> GUIComposer

6. Wait, only blank Tab is visible in CCS.

2. Switch to use a different browser, edit ccstudio.ini and add -DTIBrowserType=mozilla. Restart CCS and see if GC Designer works or not?

After edit the ini-file I restarted the CCStudio. Now the GUIComposer can be started inside the CCStudio. Is this now the workaround? Can I use GUIComposer in this way without any restrictions?

Regards Matt

Hi Matt,

My problem was that GUIcomposer did not work correctly (e.g. did not start) on a system with a 6 core Intel Xeon CPU. At the same time it work correctly on my laptop with Intel i7 CPU. Both systems had W7 Professional 64-bit. TI had found the problem and will implement a fix in a new release of the GUIcomposer as well as updating Hercules motor control webapp. They will let me know when it will happen via post.

Kind Regards,

-Slav. 

Patrick,

Thank you for your support. Now I could make my first experience with the tool.

You can contat me for further information. Maybe I can give you them if it not need to much time.

Regards

Matt

Hi Matt,

To follow up with the default (chrome) browser issue, can you do a small experiment and see if this solve your issue regarding the browser not displaying anything? It should take a couple minutes of your time.

Can you open this file, <install dir>\ccsv5\eclipse\plugins\maqetta.core.client_1.0.0.<buildid>\WebContent\pagedesigner.html. Uncomment the line require.on('error', moduleLoaderErrorHandler), line 143. And remove the mozilla browser property in ccstudio.ini.

See if you can open up GUI Composer with the default browser.

Thank you very much!
Patrick 

Hi Patrick,

I tried the way you told me.

Result: When I start GuiComposer it take some time and after that the text below appears in the GuiComposer tab. The text changes continously it seems that the program is doing a loop.

Same result I have after closing and restart GuiComposer and after closing and restarting CCS.

Another try was to create a new workspace this gives the same result. This idea I had because I used normally my old workspace from the former CCSv5.2 installation. Before I installed CCSv5.4 I removed the CCSv5.2 this was necessary because updating didn't work.

Regards,

Matt