Mic Array: USB Audio Device - No Devices connected

New to XMOS and XCore? Get started here.
User avatar
mon2
XCore Legend
Posts: 1913
Joined: Thu Jun 10, 2010 11:43 am
Contact:

Post by mon2 »

@woodsb,

do not own this mic array but can you attempt to reflash the PCB with the recommended firmware?

Aside from this suggestion:

a) test with other USB cables
b) test with other USB ports

Hoping not but perhaps there is a hardware issue related to in rush current. This is where the USB Vbus rail is spiked with a voltage higher than spec and results in damaging the USB interface. The documentation / errata related to this fault is now posted inside the datasheets. As noted, start with the firmware upgrade and move from there.

Should you replicate the XMOS design, be sure to place in rush current protection onto the Vbus rail that has been discussed on this forum a few times.


woodsb
Experienced Member
Posts: 79
Joined: Thu Nov 17, 2016 11:24 pm

Post by woodsb »

Thx. Not sure how to recommended firmware. Lunk?
woodsb
Experienced Member
Posts: 79
Joined: Thu Nov 17, 2016 11:24 pm

Post by woodsb »

How to GET rcommended....
User avatar
mon2
XCore Legend
Posts: 1913
Joined: Thu Jun 10, 2010 11:43 am
Contact:

Post by mon2 »

Courtesy of the op above...
Download "sw_usb_audio-[sw]_6.15.2rc1.zip" from the below link
http://www.xmos.com/support/software/uac2

And replace module_xud with the below one
https://drive.google.com/drive/folders/ ... sp=sharing

Then generate "app_usb_aud_mic_array_2i8o2.xe" firmware file with the above combination using xtimecomposer

Now you must be able to find XMOS USB 2.0 audio device on your windows PC.

Note: Makesure you have installed windows driver from the below link (TUSBAudio control panel)
http://www.xmos.com/support/usb-audio-driver-support

Here is a compiled version:
Hi,
Working version of .xe(1i8o2 and 2i8o2) files for "app_usb_aud_mic_array" module are shared below:
https://drive.google.com/drive/u/0/fold ... TdLbGdxbmM

Thanks,
Bhanu
woodsb
Experienced Member
Posts: 79
Joined: Thu Nov 17, 2016 11:24 pm

Post by woodsb »

Okay, for me it was the USB cable. Thanks for the tip.

-Bill
Post Reply