ΣSigmaStudio Ask AI Русский Log in

Strange behaviour of ADC1 on Adau1701 (causing 48K <> 96K switch)

SigmaDSP & SigmaStudio dzingoni Nov 13, 2015 00:00 2 replies Original on forum ↗
Subscribe
dzingoni Question
Nov 13, 2015 00:00

I'm having a very strange behaviour of ADC1 on an Adau1701 standalone board that I designed. The 1701 runs in MASTER mode, so it generates the clocks (BCLK and LRCLK). The MP3 pin of the chip is used as an Aux ADC, and is connected (according to the application notes) to the center pin of a 10K pot (between 3.3 and GND) with a 475 Ohm resistor.

What happens is that when the Mp3 pin is configured as ADC1 the system becomes unstable, and depending on the position of the POT the LRCLK actually switches between 96K to 48K (and noises are generated at the outputs).

Initially I thought about a hardware mistake, or some soldering fault. After many checks I realized that everything is OK. I replicated the same behaviour on a different board. I also use ADC2 (on pin MP2) wired in exactly the same way to another pot, and everything is OK.

I tought about a possible short between the MP3 pin and its adjacent pins ... but no, it's all OK.

In the actual situation I can't use the ADC1. The rest of the board works OK.

But how can it be? Does anybody happened to see something similar on their projects?

How is it possible that a pot connected to ADC1 actually controls the sampling rate in a standalone application?

Can the chip be faulty?

Audio Signal Processors

SigmaDSP Audio Processors

adau1701

DaveThib Reply
Nov 18, 2015 00:00

Hello Daniele,

What is the ADC data being fed to in SigmaStudio schematic? What is probably happening is that you are feeding it into something like a MUX external control input that is expecting to see a number between 0 and 32. If you feed the mux with higher numbers then it will just start writing into memory locations that are way out of range of the memory being used by the MUX. So you would be changing registers or filter coefficients, gains etc. Undefined.

Almost all of these blocks do not do range checking on the control inputs. Since the DSP is not a general purpose controller, it uses up a lot of MIPS to do simple range checking so we keep the instruction usage to a minimum and leave it to the user to properly range the input.

Show us that part of your project so I can get an idea of what you are doing and give you more directed instructions.

Thanks,

Dave T

EZAdministrator Reply
Aug 2, 2018 00:00

This question has been assumed as answered either offline via email or with a multi-part answer. This question has now been closed out. If you have an inquiry related to this topic please post a new question in the applicable product forum.

Thank you,
EZ Admin