Cannot connect XK-AUDIO-216-MC-AB on ubuntu for flash

If you have a simple question and just want an answer.
Post Reply
zhenhao
Newbie
Posts: 1
Joined: Tue Jun 11, 2019 11:01 am

Cannot connect XK-AUDIO-216-MC-AB on ubuntu for flash

Post by zhenhao »

Hello,
I use Usb to link XK-AUDIO-216-MC-AB to Ubuntu, but when I use xTIMEcomposer for flash, I see the following message.
I have already run the script of "setup_xmos_devices.sh".
Error: F03136 No devices attached - Cannot run the enquirer until a device is found
run "lsusb", i get:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 03f0:334a Hewlett-Packard
Bus 001 Device 011: ID 20b1:0008 XMOS Ltd
Bus 001 Device 003: ID 03f0:134a Hewlett-Packard Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
run "xrun -l", i get:
Available XMOS Devices
----------------------

No Available Devices Found
run "check_xmos_devices.sh", i get:
*** XMOS USB device installation checker --- Tue Jun 11 19:30:50 JST 2019 ***

Checking for connected XMOS device on USB bus
---------------------------------------------

* SUCCESS ... Connected XMOS USB device found

Checking for XMOS XTAG-1 connected to USB bus
---------------------------------------------

X FAILURE ... XMOS XTAG-1 has not been found

Checking for XMOS XTAG-2 connected to USB bus
---------------------------------------------

X FAILURE ... XMOS XTAG-2 has not been found

Checking for XMOS XTAG-3 connected to USB bus
---------------------------------------------

X FAILURE ... XMOS XTAG-3 has not been found

Checking for XMOS XTAG-PRO connected to USB bus
-----------------------------------------------

X FAILURE ... XMOS XTAG-PRO has not been found

Checking for XMOS startKIT connected to USB bus
-----------------------------------------------

X FAILURE ... XMOS startKIT has not been found

Checking for Segger JLINK connected to USB bus
----------------------------------------------

X FAILURE ... Segger JLINK has not been found
Any insight into what could be happening would be appreciated.

Thanks,
zhenhao


User avatar
mon2
XCore Legend
Posts: 1913
Joined: Thu Jun 10, 2010 11:43 am
Contact:

Post by mon2 »

Hi.

Start with this page:

https://www.xmos.com/developer/publishe ... vers-linux

next,

1) can you check to see if you have BLACK insulator USB ports on your PC? This will be USB 2.0 ports. They are known to be more stable with these tools.

2) If possible, try again with a short but quality USB 2.0 marked cable (fully loaded that features all the wires for power & data transfer).

3) Check if possible on a Windows box and report back on your results.

I think the USB firmware is not completely solid and does have some compatibility issues across different platforms.
Shota.Sato
Member
Posts: 11
Joined: Tue Jul 02, 2019 3:30 am

Post by Shota.Sato »

Hi

Thank you for your reply.
My name is Shota Sato. I took over this job from Zhenhao.
I using a different PC from Zhenhao ,and the same error has occured.
(OS is Ubuntu 16.04)

The confirm contents are listed below.
>Is the USB driver valid?
$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
    |__ Port 8: Dev 23, If 0, Class=Vendor Specific Class, Driver=, 480M
    |__ Port 8: Dev 23, If 1, Class=Vendor Specific Class, Driver=, 480M
    |__ Port 8: Dev 23, If 2, Class=Vendor Specific Class, Driver=, 480M
    |__ Port 8: Dev 23, If 3, Class=Vendor Specific Class, Driver=, 480M
    |__ Port 8: Dev 23, If 4, Class=Vendor Specific Class, Driver=, 480M
    |__ Port 8: Dev 23, If 5, Class=Vendor Specific Class, Driver=usbfs, 480M      <---device
    |__ Port 10: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 11: Dev 14, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 11: Dev 14, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
USB driver seems to enable, because it is displayed as "Driver=usbfs".

>1) can you check to see if you have BLACK insulator USB ports on your PC? This will be USB 2.0 ports. They are known to be more stable with these tools.
I changed to use USB 2.0 ports

>2) If possible, try again with a short but quality USB 2.0 marked cable (fully loaded that features all the wires for power & data transfer).
I changed to use 50cm cable.

>3) Check if possible on a Windows box and report back on your results.
I tried again ,but the device seems to be unrecognized.
$ sudo ./setup_xmos_devices.sh

*** XMOS USB device installation --- Tue Jul  2 14:41:03 JST 2019 ***

Install XMOS rules to /etc/udev/rules.d
---------------------------------------

 *   SUCCESS ... XMOS rules installed correctly into /etc/udev/rules.d/

Restart UDEV service to pick up XMOS rules
---------------------------------------

 *   SUCCESS ... UDEV service has been restarted

***********************************************************
* PLEASE RECONNECT ALL XMOS USB DEVICES TO ENABLE CHANGES *
***********************************************************

$ sudo ./check_xmos_devices.sh 

*** XMOS USB device installation checker --- Tue Jul  2 14:41:19 JST 2019 ***

Checking for connected XMOS device on USB bus
---------------------------------------------

 X	FAILURE ... Connected XMOS USB device has not been found
Shota.Sato
Member
Posts: 11
Joined: Tue Jul 02, 2019 3:30 am

Post by Shota.Sato »

Sorry, my perception was wrong, it will be resent.

Check if is activated USB Driver.
Device is Set
$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
    |__ Port 5: Dev 31, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 5: Dev 31, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 6: Dev 30, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 8: Dev 32, If 0, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 8: Dev 32, If 1, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 8: Dev 32, If 2, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 8: Dev 32, If 3, Class=Application Specific Interface, Driver=, 480M
    |__ Port 8: Dev 32, If 4, Class=Human Interface Device, Driver=usbhid, 480M

Device not set
$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
    |__ Port 5: Dev 31, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 5: Dev 31, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 6: Dev 30, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M

Is there am error because there is no Driver below.
    |__ Port 8: Dev 32, If 3, Class=Application Specific Interface, Driver=, 480M
User avatar
mon2
XCore Legend
Posts: 1913
Joined: Thu Jun 10, 2010 11:43 am
Contact:

Post by mon2 »

I would try:

** disconnect the XMOS kit from your Linux box

Code: Select all


lsusb -v 

or

lsusb -v > output_without_kit.txt

** connect the XMOS kit to your Linux box

Code: Select all


lsusb -v

or

lsusb -v > output_with_kit.txt
Post the results from above and compare the output to see if the XMOS kit is being detected.

reference:
https://www.xmos.com/file/enable-usb-drivers-linux
Shota.Sato
Member
Posts: 11
Joined: Tue Jul 02, 2019 3:30 am

Post by Shota.Sato »

I compare the two result ,XMOS kit was being detected.
Attachments
Conected_XMOSDevice.txt
Result for "lsusb -v" with XMOS connected
(38.87 KiB) Downloaded 115 times
Conected_XMOSDevice.txt
Result for "lsusb -v" with XMOS connected
(38.87 KiB) Downloaded 115 times
Shota.Sato
Member
Posts: 11
Joined: Tue Jul 02, 2019 3:30 am

Post by Shota.Sato »

Just to confirm...
I thought that "FAILURE" is not a good thing to happen when excute "check_xmos_devices.sh".
$ sudo ./check_xmos_devices.sh
*** XMOS USB device installation checker --- Wed Jul 3 17:27:23 JST 2019 ***

Checking for connected XMOS device on USB bus
---------------------------------------------

* SUCCESS ... Connected XMOS USB device found

Checking for XMOS XTAG-1 connected to USB bus
---------------------------------------------

X FAILURE ... XMOS XTAG-1 has not been found

Checking for XMOS XTAG-2 connected to USB bus
---------------------------------------------

X FAILURE ... XMOS XTAG-2 has not been found

Checking for XMOS XTAG-3 connected to USB bus
---------------------------------------------

X FAILURE ... XMOS XTAG-3 has not been found

Checking for XMOS XTAG-PRO connected to USB bus
-----------------------------------------------

X FAILURE ... XMOS XTAG-PRO has not been found

Checking for XMOS startKIT connected to USB bus
-----------------------------------------------

X FAILURE ... XMOS startKIT has not been found

Checking for Segger JLINK connected to USB bus
----------------------------------------------

X FAILURE ... Segger JLINK has not been found
I confirmed "check_xmos_devices.sh" , it looks like BUS number and DEVICE number are fixed.
When executed "check_xmos_devices.sh", isn't it all "SUCCESS" ?
$ lsusb
Bus 001 Device 011: ID 20b1:0008 XMOS Ltd
Shota.Sato
Member
Posts: 11
Joined: Tue Jul 02, 2019 3:30 am

Post by Shota.Sato »

May I ask one more question?
Currently, i am connect as below, would this be okay?
PC port : USB 2.0 typeA
Xcore-200 Port : Micro USB2.0 Type-B
Shota.Sato
Member
Posts: 11
Joined: Tue Jul 02, 2019 3:30 am

Post by Shota.Sato »

I solved it myself.
The cause was the connection problem of Xcore-200 and PC.
I had to connect JTAG emulator to Xcore-200.
Post Reply