Scope multichannel inputs

[gana]

*i can record but only one input i can use ?

answer:
I assume you are using Windows? If so you need to use ASIO for mult-channel recording. I suggest you use FooBar2000 with the ASIO plugin, you can route your outputs in preferences in this application.

There is no such thing like "ASIO for mult-channel recording". FooBar2000 can only support output with ASIO.

sorry for new thread that i posted coz you guys do not care about old threads

[Ross]

There are plenty of ASIO recording programs. E.g. Adobe Audition.

FooBar2000 can only support output with ASIO.

Correct. Foobar is for playback only. That was two separate statements, it wasn't suggesting using foobar for recording. You could also use VLC for playback.

sorry for new thread that i posted coz you guys do not care about old threads

It is bad forum etiquette to keep creating new threads because you have not received a reply in your desired timescales. Please refrain from doing so.

[gana]

MC has 4 inputs but first one named MIC is missing in every driver and programs...
is that because of firmware? or depends on program?
how can i recognize?

[Ross]

The CODEC on that board (CS42448) has 6 channels in, 8 channels out.

The firmware takes audio line input from the jacks marked IN 1/2, IN 3/4, IN 5/6.

That extra input is muxed with IN 5/6 in the CODEC. From the data sheet:

Six fully differential, or single-ended, inputs are avail- able on stereo ADC1, ADC2, and ADC3. When operating in Single-Ended Mode, an internal MUX be- fore ADC3 allows selection from up to four single-ended inputs. Digital volume control is provided for each ADC channel, with selectable overflow detection.

4.2.2 ADC3 Analog Input

ADC3 accommodates differential as well as single-ended inputs. In Single-Ended Mode, an internal MUX selects from up to four single-ended inputs.

Single-Ended Mode is selected using the ADC3_SINGLE bit. Analog input selection is then made via the AINx_MUX bits. See register “ADC Control & DAC De-Emphasis (Address 05h)” on page 45 for all bit se- lections. Refer to Figure 13 on page 29 for the internal ADC3 analog input topology.

You would need to modify the firmware to use this muxed input.

[gana]

Thank you
i am trying to do what you suggested to me, so i want to work on source code of firmware but
i do not know it is full or definitely same with original firmware that i downloaded from xmos.
i mean there may be little change in the source code, so i need to prove it that source is same as firmware works or not.

first i want to use small example like burning simple LED illuminating xe.

i can prove that i did burning process in right way as i do it.

then i can prove firmware source code is working well like a firmware demonstrated by xmos.

after that i can work on source code .

where can i find simple LED code with whole source like xn xi make file ...etc. just for testing?

[gana]

where can i find simple project that included whole files to work normaly
not only xc code..?

[gana]

where can i find simple led or other code that really works?

and what is .xi file how can i understand what language is it it is like alien language.

[ozel]

you will find most of your answers in the XC Programming guide
and in the tools user guide:
http://www.xmos.com/download/public/XC- ... 1009A).pdf
http://www.xmos.com/published/tools-user-guide

the .xi files are a good question. The tools guide lists them as XC source files, but without (or after?) preprocessing, which is not very clear. I think they are automatically generated by the compiler.
Anyway, you can ignore them. Just focus on the .xc files.
Depending on your board, you might find further demo code on www.github.com/xcore
and in the ressources section of the XMOS website.

[gana]

thank you another question

i am not proper in this field but trying so...
if you see in codec:
SPI mode is selected if there is a high to low transition on the AD0/CS pin.
And CDIN is the input data line from the microcontroller. But in our schematic/circuit A0/CS and CDIN are connected to GND then we never write/read to/from codec using SPI.

why did you declare SPI below in the source?

fl_PortHolderStruct p_flash = {
XS1_PORT_1A,
XS1_PORT_1B,
XS1_PORT_1C,//sda
XS1_PORT_1D,//scl
XS1_CLKBLK_2
};

int flash_cmd_enable_ports() {
int result = 0;
setc(p_flash.spiMISO, XS1_SETC_INUSE_OFF);
setc(p_flash.spiCLK, XS1_SETC_INUSE_OFF);
setc(p_flash.spiMOSI, XS1_SETC_INUSE_OFF);
setc(p_flash.spiSS, XS1_SETC_INUSE_OFF);
setc(p_flash.spiClkblk, XS1_SETC_INUSE_OFF);

[gana]

i am little confusing..
in the schematic xcore1 has sda and scl pin, and codec , cs2300 has too..
so how do they connected each other i attached a picture in paint kk can you connect it to me