This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
i just have found out about the issues concerning the AVcc connection and i cannot find a real answer for myself by reading all the older forum posts.
So the problem in my Layout is, I supply the AVcc-Voltage directly from one GPIO Pin, which gets put as an Output with logic "high".
So generally there should be around 3,3 V output from the GPIO-Pin to the AVcc Pin, but whenever i meassure it it says about 2,5 V.
Now strange things first:
1. I read a lot of things about possible oscillation, when AVcc and DVcc are not about euqal on startup, which it is in my case.
My code is working properly, i do not have any high currents in my device, my LPM3 is working just fine, so am I just a lucky guy, or why is it working for me.
2. Now i am also wondering if it is intelligent to supply the AVcc voltage form within the MSP GPIO, or should I as everywhere recommended, put the AVCC directly to my battery Vcc, just seperated with a LC-filter from my DVcc?
3. Another question came up. I do use an external reference vor ADC12, i do not have a buffer network attached to the Veref Pins, do I have to put one in there, or is it dependend on how much current i use of my reference?
Thanks for your time.
You should not be sourcing AVcc from a GPIO. AVcc will sink more current than the GPIO can source, and that is why the voltage drops. There are graphs in the datasheet showing this phenomenon. This is also why it works in LPM3, because almost no current is being consumed, so the GPIO is capable of sourcing it. That doesn't mean that it is a good idea however. Sourcing AVcc through the GPIO is a bad practice.
It is typical to simply connect AVcc and DVcc. On the devices without a specific AVcc pin, the AVcc and DVcc pins are simply shorted on the inside. In most use cases connecting AVcc to DVcc directly will work fine. My guess is that it will be fine for you if you were originally trying to source AVcc from a GPIO. If for some reason you want AVcc and DVcc to be separate, you can do that, but don't use MSP GPIO.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
Sorry, Mike, that's not exaclty right.
the GPIO pins will definitely be able to source enough current. AVcc only draws one or two milliamperes even with all analog circuitry is active. Any GPIO pin will be able to source that.
The reason why thi sis not allows is a different one:
AVCC must not differ from DVCC by more than 0.2V. So it may not be switched off at all, and sicne the IO pins have a voltage drop, they won't provide enough voltage.If external AVcc is not sourced by a sufficiently high volage, a cross-current will flow internally from DVCC to AVCC, stressing the internal ciscuitry.
The reason for separating AVCC and DVCC is not to provide two different voltages. Is is meant to decouple the two so that small changes in DVCC due to digital current ripple can be filtered-out and do not affect the analog circuitry.
sebwhenever i meassure it it says about 2,5 V.
2) you should do the RC filter. LC is usually not necessary.
3) indeed, it depends on the impedance of your reference. The MSP doesn't draw much (see the datasheet). However, a capacitor couple (10µF tantalum and 100nF ceramic) ensure that the reference will be stable and withstand crosstalk as well as the small current changes during conversion (the MSP only draws from the reference during the 13 conversion cycles, not during the sampling time or when not converting).
It depends on how high precision you need.
Time to say goodbye - I don't have the time anymore to read and answer forum posts. See my bio for details.Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.I'm sorry that I can no longer provide help in the forum or by private conversation.
In reply to Jens-Michael Gross:
You are right, thanks for clarifying.
In reply to MikeS:
I have a MSP430F5659 powered by a TPS63031 3.3V Buck-Boost Regulator and I have concerns about the reference voltage on the ADCa12.
Is it better to source AVcc pin from a 3.3 Reference voltage generator (such as REF3333) rather than DVcc (Switching 3.3V) ? Is there any advantage on using external reference or the capacitors between DVcc and AVcc are good enough ? Should be the REF3333 connected to the external Vref pin or to AVcc ?
In reply to Santiago Barros:
Wow long lost post, did also forget to answer back then...
If you want some precise ADC results you have to use some precise Voltage references, your ADC result will be dependent on those references.
So you will have to decide for yourself if its important or not to measure precisly.
Yout TPS volatge regulator will have a ripple for sure and that ripple will be in your ADC results as well, although the ripple will be different for different load scenarios, for example how much current will be drawn from your TPS, wheather the MSP430 is running at full speed or slowly, all this matters then.
In reply to seb:
That ripple would only affect the ADC results if AVcc is selected as Vr+, but not if the Internal reference generator is active (@1.5 or 2.5V). Am I right?
Thats of course right, if you use the internal 2,5V or 1,5 V you have to look into the Datasheet for further specifications and compare with your demands, perhaps its accuracy and long time stability, temperature etc will fit if not consider using an external reference which does.
If you do not know yet, you can of course plan for both, install an external Vref. By c-code you can change the settings in the MSP430 for either external or internal Vref, as described in the FamilyUserGuide, so you could easily compare both or even more settings.
Santiago BarrosThat ripple would only affect the ADC results if AVcc is selected as Vr+, but not if the Internal reference generator is active (@1.5 or 2.5V). Am I right?
Thanks Jens-Michael, you're right about considering the ripple on Vr- as well.
Jens-Michael Gross The internal reference is also affected by changes on AVcc. Yet the effect is by magnitudes smaller.
Regarding the resulting ripple on the internal reference output, would be better then, to source the AVcc pin from the 3.3V external reference ? therefore, que 1.5, 2 and 2.5V internally generated voltages would be "cleaner" ? Is this worth it in terms of measurement improvement ?or the ripple in the internal reference is just insignificant even with a switching 3.3V AVcc? .
The other problem i have doubts about is that there would be a small varying voltage differences between AVcc and DVcc (while the microcontroller is in operation ) since one DVcc would be sourced from the TPS 3.3V switching regulator and AVcc from a reference voltage. In the datasheet says that the difference between these two voltages should not be greater than 0.2V. Is this difference relevant ?
AVcc and Reference inputs are 2 completly different voltages supplied by you on completly different pins of the MSP430
I you should supply Vcc with 3V3 and AVcc with 2V5 you can expect some excess current flowing and perhaps the dead of your MSP430.
I did this once in my design nothing did break or overheat, but i drew way too much current, since I didnt expect it, so I already did this failure some years ago, learning by doing :)
Another question comes into my mind with hte GND ripple, I have some batterie run device, I did couple AVss and DVss ( analog and digital GND) right beside the Batterie not right beside the swichting supply, but I always wondered what solution is best, any ideas to that? I did argue with current will be drawn from the batterie directly, so alongside the batteriepath there will be some voltage ripple or at least some voltage offset on the GND line, so I decided to couple them both at the very source.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.