problem with xtimecomposer on ubuntu 16.04

If you have a simple question and just want an answer.
Posts: 9
Joined: Tue Feb 04, 2020 1:33 pm

Re: problem with xtimecomposer on ubuntu 16.04

Postby troldenstein » Wed Apr 22, 2020 5:45 am

tom18 wrote:
Fri Jan 04, 2019 2:27 am
My setup for using xTIMEcomposer Community 14.3.3 under 64-bit Ubuntu 16.04 and 18.04:

1. install Java runtime from I have uninstalled the OpenJDK comes with the system before that.

2.Create /etc/udev/rules.d/99-xmos-xtag.rules with following content to allow Ubuntu to detect xTAG2 or xTAG3 hardware. Remember to change "tom18" to your ID.

Code: Select all

Plug your xTAG debugger to you PC and run "ls -lR /dev/bus/usb". You should see a device owned by you :

Code: Select all

crw-rw-r-- 1 root   root 189, 5 Jan  4 08:03 006
crw-rw-r-- 1 root   root 189, 6 Jan  4 08:03 007
crw-rw-r-- 1 root   root 189, 7 Jan  4 08:03 008
crw-rw-r-- 1 tom18  root 189, 9 Jan  4 09:22 010
3. As described earlier in the thread, comment out line 144 inside xTIMEcomposer/Community_14.3.3/bin/xtimecomposer to fix the square character issue:

Code: Select all

#            $ENV{LD_LIBRARY_PATH} = "$installpath/xtimecomposer_bin/swtbrowserlibs:$ENV{LD_LIBRARY_PATH}";
I tried this solution on my ubuntu distro (ubuntu studio)

Added udev rule as above suggested by copy-paste and editing my username to it and listed connected usb devices.

Code: Select all

ls -lR /dev/bus/usb/

Code: Select all

crw-rw-r-- 1 root root 189, 128 huhti  22 07:32 001
crw-rw-r-- 1 root root 189, 129 huhti  22 07:32 002
crw-rw-rw- 1 user root 189, 131 huhti  22 07:32 004
crw-rw-r-- 1 root root 189, 132 huhti  22 07:32 005
Now i started xtimecomposer with:

Code: Select all

cd /pathtocomposerrootdirectory/
source SetEnv
and still.. xtag is not detected by the composer studio. Any suggestions?
Posts: 9
Joined: Tue Feb 04, 2020 1:33 pm

Postby troldenstein » Fri Apr 24, 2020 5:24 am

okay.. libncurses5 was missing somehow:

sudo apt install libncurses5

Now everything is smooth. ':D
Posts: 1
Joined: Tue Apr 28, 2020 1:50 am

Postby Gsmith » Tue Apr 28, 2020 2:45 am

What is the purpose of the OWNER="tom18"?
User avatar
XCore Expert
Posts: 522
Joined: Thu Nov 26, 2015 11:47 pm

Postby akp » Tue Apr 28, 2020 3:00 pm

I'm pretty sure he/she just set the owner to their Ubuntu username, if you refer to the statement 'Remember to change "tom18" to your ID.'
Posts: 1
Joined: Wed Aug 26, 2020 5:56 am

Postby Sodor » Wed Aug 26, 2020 7:47 am

This is my little history (happy end)...

I'm using linux Lubuntu 19.04 64-bits and xtime composer community 14.4.1 with a startkit board, at first the xtime composer run but it doesn't connect to startkit (using the udev rule file suggested by xmos documentation modified to find startkit board), I do everything suggested by user tom18 in this post (please take the time to follow the link and see) so I changed the rule file 99-xmos.rules to only have one line, remember that "OWNER" field will be your user name:

Code: Select all

Uninstalled all trail of java and installed OpenJava 8 using the Discover software included with Lubuntu:

Code: Select all

MyUserName@MyHostName:~$ java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (build 1.8.0_265-8u265-b01-0ubuntu2~20.04-b01)
OpenJDK 64-Bit Server VM (build 25.265-b01, mixed mode)
Still xtime composer can't connect to startkit, I'm still fighting so:

Installed libncurses5 as suggested by user troldenstein (on this same post), but same results, finally at the execution of xtimecomposer I'm seeing some fail messages from xtime composer:

Code: Select all

MyUserName@MyHostName:~/Programas/XMOS/xTIMEcomposer/Community_14.4.1$ source SetEnv
MyUserName@MyHostName:~/Programas/XMOS/xTIMEcomposer/Community_14.4.1$ xtimecomposer
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0

(xTIMEcomposer:2976): GLib-GIO-CRITICAL **: 23:06:51.815: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(xTIMEcomposer:2976): GLib-GIO-CRITICAL **: 23:06:51.816: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(xTIMEcomposer:2976): GLib-GIO-CRITICAL **: 23:06:51.816: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(xTIMEcomposer:2976): GLib-GIO-CRITICAL **: 23:06:51.816: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
I admit that I have seen those messages from the begining but I dont pay attention, on my limited linux knowledge DBUS is used by udev to warn others applications about connection and disconecction of devices (like a startkit board) so if xtime composer is failing to connect to DBUS, that mean something is wrong, serching in google I found THIS where the user ederag points to a problem with fcitx and purging fcitx-module-dbus remove the problem, so in terminal:

Code: Select all

sudo apt-get purge fcitx-module-dbus
there is no more DBUS connection fail messages and xtime composer can connect to startkit board.

Who is online

Users browsing this forum: akp and 7 guests