Ticking problem between nRF52832 and TLV320AIC3104

[Om Agrawal]

Hi,

I am currently integrating nRF52832 with TLV320AIC3104 codec. I have successfully initialized I2C and I2S communication between the two boards and configured nRF52832 as master and TLV320AIC4104 as slave.

These are my current I2S settings:
    i2s_cfg.word_size = 16U;
    i2s_cfg.channels = 2U;
    i2s_cfg.format = I2S_FMT_DATA_FORMAT_I2S;
    i2s_cfg.frame_clk_freq = sample_rate;
    i2s_cfg.block_size = BLOCK_SIZE;
    i2s_cfg.timeout = 5000;
    i2s_cfg.options = I2S_OPT_FRAME_CLK_MASTER | I2S_OPT_BIT_CLK_MASTER;
    i2s_cfg.mem_slab = &tx_0_mem_slab;

The problem which I am currently facing is that I am hearing periodic ticks on the headphone output whenever I send data from nRF to TLV. The ticks are of the frequency which I am sending, but it's not a tone. There are some concerns regarding data misalignment between nRF and TLV, but I am not finding any solution for this problem. 

Regards,
Om

[Kenneth]

Hello,

What is the block size used here? Have you tried to increase the size of it?

Have you any measurements of the audio? e.g. if you play a 1kHz test tone, what does the audio sound like (it can tell us something about the duration of the noise).

Kenneth

[Om Agrawal]

Hi,
I am currently implementing Direct Digital Synthesis(DDS) algorithm for producing different pure tones and my I2S_Word Size is set to 16bits.
I have also checked the output via an osiclloscope and I am attaching the image for your reference.

[Om Agrawal]

[Kenneth]

The buffer size I am thinking of is the audio buffer size for each i2s transfer, which I suspect is what I can see between the red lines here:

Increasing that should allow less constraints on how frequently you need to update the i2s transfers, in this case almost looks like you miss or skip some buffers.

Kenneth