I'm using it with TI's pcm4222 EVM.
I have not found a way to make it a slave. I suspect that it would require changes in its firmware..
I have not found a way to make it a slave. I suspect that it would require changes in its firmware..
Thanks! Really pity it don't do slave as this means that I can not use the clock on the Acko ADC board. It's the same clocks but I prefer to feed the ADC with one that sits on the same board 20mm away.
//
//
Can it do both I2S input and output at the same time? IE, have it working as USB->I2S->DAC and ADC->I2S->USB, with both an input and an output showing up on the host PC?
Can it do both I2S input and output at the same time? IE, have it working as USB->I2S->DAC and ADC->I2S->USB, with both an input and an output showing up on the host PC?
Yes you can.
I have try this tiny board with USB to I2S to DAC and the same time I was routing ADC to USB with my EMU 0404 (Win XP, atom processor) without problems.
does it require usb 5v signal detect?
is it an external 3.3v it requires?
is there an onboard power regulator ?
The PCB uses external regulated 3.3V.
It do not require usb 5v signal detect.
The current firmware of the 768k PCB is only enabled and tested for usb to i2s 768k and DSD512/1024*
Enable 768k from the official firmware requires 45/49 clock and unique optimization and it can not be done by user following the official xmos programming guide normally.
For ADC->I2S->USB usage, the multichannel xmos pcb using 22/24 clock should be the choice for most people, but it is only upto 384k. User can follow the port map and uses the onboard full size XSYS connector to program the xmos with their customized firmware to add any feature and function by following the xmos programming guide.
Enable 768k from the official firmware requires 45/49 clock and unique optimization and it can not be done by user following the official xmos programming guide normally.
For ADC->I2S->USB usage, the multichannel xmos pcb using 22/24 clock should be the choice for most people, but it is only upto 384k. User can follow the port map and uses the onboard full size XSYS connector to program the xmos with their customized firmware to add any feature and function by following the xmos programming guide.
anybody tested the multichannel (up to 8ch) playback on linux ?
which channels does the vumeter measure (can we choose the measured channels) ?
thanks
which channels does the vumeter measure (can we choose the measured channels) ?
thanks
This seems like it might be the perfect USB reciever I have been looking for. Plan to interface with a TI PCM1863 ADC and a PCM5242 DAC. DimDim, can you confirm that you get both an input and an output under recording devices and playback devices respectively in Windows? I only need stereo in and out for now.
Yes, I can confirm that.
I have in fact done simultaneous playback and recording in Windows 10 64bit. But you will have to slave the ADC to the XMOS.

I have in fact done simultaneous playback and recording in Windows 10 64bit. But you will have to slave the ADC to the XMOS.
You are very welcome, it's been my pleasure. 🙂
You should also keep in mind that the BCLK & LRCK signals will need to be shared by both your DAC and ADC.
You should also keep in mind that the BCLK & LRCK signals will need to be shared by both your DAC and ADC.
Hi Dimdim,
How does this board handle the I2S interface clocking?
Can it receive an external master clock?
Further can the I2S interface be easily isolated and reclocked?
I am trying to see if i can use this with an ESS9018 multichannel DAC board which can operate in synchronous mode
How does this board handle the I2S interface clocking?
Can it receive an external master clock?
Further can the I2S interface be easily isolated and reclocked?
I am trying to see if i can use this with an ESS9018 multichannel DAC board which can operate in synchronous mode
AFAIK with the firmware that comes with the board there is no way for it to receive an external MCLK. You have to use it pretty much as-is.
I suspect that XMOS provides the tools necessary for creating a custom firmware that could support external MCLK, but I also suspect that actually making such a firmware would not be easy.
Isolation & reclocking should not be a problem. We are talking about standard I2S lines.
I suspect that XMOS provides the tools necessary for creating a custom firmware that could support external MCLK, but I also suspect that actually making such a firmware would not be easy.
Isolation & reclocking should not be a problem. We are talking about standard I2S lines.
I’m still a novice regarding the digital side of audio, however I came across this application note for interfacing high speed ADCs with xCORE devices, http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwje49LtoJ_MAhWqC8AKHWBhD2wQFggdMAA&url=https%3A%2F%2Fwww.xmos.com%2Fdownload%2Fprivate%2FAN01021%253A-Interfacing-High-Speed-ADCs-with-xCORE(1.0.1rc3).pdf&usg=AFQjCNEYkzA1-hBAAToQXYnupmN_SyxrCA&sig2=slnd5rhqYgGtyD8Rb3f1ig&cad=rja
Which would suggest that it can receive an external clock frequent of 100Mhz and output this to slave the ESS9018. Just dont aks me how 🙂
Which would suggest that it can receive an external clock frequent of 100Mhz and output this to slave the ESS9018. Just dont aks me how 🙂
Just learnt that Ian from the jitter reduction FIFO thread is developing a multichannel USB to I2S with isolation and reclocking.
Thanks Guys.
Thanks Guys.
Hi diyhkare you saying in #17 that with the use xTIME composer we can alter your firmware or do you mean writing from skratch which is beyond me?
Yes, it can. That's why I bought it.
I'm afraid that I must quote myself to apologise to you guys.
I was under the impression that this board is just a new version of the green multichannel board. I just realized that this board is only stereo.
So my comments are related to the multichannel board.
Again, sorry for the confusion.
- Home
- Vendor's Bazaar
- diyinhk Store