Attached is the sample code for Audio Talk through on EVAL-SC589-EZLITE for I2S mode of operation.
Attached is the sample code for Audio Talk through on EVAL-SC589-EZLITE for I2S mode of operation.
Hi Ksam,
I think you are referring to example code that is offered along with the EE-377, please correct me if I am wrong.
1. First important difference, It is a single core framework, ie.. only SHARC1 core configures the ADC/DAC receives data from ADC over sport and copies them to DAC buffers to be played by DAC. Here all the buffers are placed in SHARC 1 core.Code that comes along with EE-377 actually demonstrates inter-core communications. Here SHARC 1 core controls ADC and SHARC 2 core controls DAC. It demonstrates how inter-core communication need to be taken care in such scenarios.
2. The code attached here doesn't use any drivers and services. It performs simple register read and write. The codes provided in EE-377 uses devices drivers and services. So this code is for people who prefer register level programming over device drivers and services.
3. The EE-377 code performs input filtering but the code attached here is just a passthrough.
4.The EE-377 code is for 4 Audio channels and configures serial ports in TDM 4 mode. the code attached here is only for 2 audio channels and configures serial port to I2S mode
There may many other subtle differences but most importantly I had this code lying around my machine just thought that I will share with the community.
Thanks,
Sachin
Hi Ksam,
I think you are referring to example code that is offered along with the EE-377, please correct me if I am wrong.
1. First important difference, It is a single core framework, ie.. only SHARC1 core configures the ADC/DAC receives data from ADC over sport and copies them to DAC buffers to be played by DAC. Here all the buffers are placed in SHARC 1 core.Code that comes along with EE-377 actually demonstrates inter-core communications. Here SHARC 1 core controls ADC and SHARC 2 core controls DAC. It demonstrates how inter-core communication need to be taken care in such scenarios.
2. The code attached here doesn't use any drivers and services. It performs simple register read and write. The codes provided in EE-377 uses devices drivers and services. So this code is for people who prefer register level programming over device drivers and services.
3. The EE-377 code performs input filtering but the code attached here is just a passthrough.
4.The EE-377 code is for 4 Audio channels and configures serial ports in TDM 4 mode. the code attached here is only for 2 audio channels and configures serial port to I2S mode
There may many other subtle differences but most importantly I had this code lying around my machine just thought that I will share with the community.
Thanks,
Sachin