Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Thread

Vref on ATTiny861a

Vref on ATTiny861a

2010-01-21 by Jeff Blaine AC0C

I am having a tough time getting this chip to respond to any other ADC voltage reference than the default AVcc.

The code snip is really simple...  Below, using the MakroC Pro compiler, however the results seem to be the same if I do the same using ASM instructions instead of their bit-level defines.

I must be overlooking something.  It seems so simple, driving me nuts that it's not working right.  I have used the same compiler and basic code to get a mega328 to work.  

Appreciate any suggestions the group may have.

Thanks/jeff


 REFS0_bit = 1;                    // 001 invokes external Vref as ADC reference
    ADEN_bit = 1;                     // enable adc
    ADSC_bit = 1;                     // start conversion
    while(adsc_bit);
    lb=ADCL;                          // get lower byte
    ub=ADCH;                          // get upper byte
    adc_rd0 = (256*ub) + lb;          // build number

[Non-text portions of this message have been removed]

RE: [AVR-Chat] Vref on ATTiny861a

2010-01-21 by Dave McLaughlin

Hi Jeff,

 

What results are you seeing from the ADC with this code?

 

What voltage have you got on Vref?

 

What else have you tried?

 

Dave.
Show quoted textHide quoted text
From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf
Of Jeff Blaine AC0C
Sent: 21 January 2010 17:47
To: AVR-Chat@yahoogroups.com
Subject: [AVR-Chat] Vref on ATTiny861a

 

  

I am having a tough time getting this chip to respond to any other ADC
voltage reference than the default AVcc.

The code snip is really simple... Below, using the MakroC Pro compiler,
however the results seem to be the same if I do the same using ASM
instructions instead of their bit-level defines.

I must be overlooking something. It seems so simple, driving me nuts that
it's not working right. I have used the same compiler and basic code to get
a mega328 to work. 

Appreciate any suggestions the group may have.

Thanks/jeff

REFS0_bit = 1; // 001 invokes external Vref as ADC reference
ADEN_bit = 1; // enable adc
ADSC_bit = 1; // start conversion
while(adsc_bit);
lb=ADCL; // get lower byte
ub=ADCH; // get upper byte
adc_rd0 = (256*ub) + lb; // build number





[Non-text portions of this message have been removed]

Re: [AVR-Chat] Vref on ATTiny861a

2010-01-21 by Jeff Blaine AC0C

Dave,

I ramp the physical voltage into the port 0 up, and at about 5V, it hits the 1023 level.  So that's why I conclude it's referencing only the Avcc which I have tied to +5.

I have tried every combination of the Vref settings, one by one.   Including the 2.5V, the 1.1v internal, etc.  I get the same response (meaning full scale at 5v) in each case.

I have to believe that the chip does not that kind of significant bug - and I have also got to believe that the compiler works on this chip just as it's done on a couple of others.  

The most logical conclusion is that I am overlooking some footnote in a register explanation or something that is specific to this chip...

Regards,
JB
Show quoted textHide quoted text
From: Dave McLaughlin 
Sent: Thursday, January 21, 2010 9:36 PM
To: AVR-Chat@yahoogroups.com 
Subject: RE: [AVR-Chat] Vref on ATTiny861a


  
Hi Jeff,

What results are you seeing from the ADC with this code?

What voltage have you got on Vref?

What else have you tried?

Dave.

From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf
Of Jeff Blaine AC0C
Sent: 21 January 2010 17:47
To: AVR-Chat@yahoogroups.com
Subject: [AVR-Chat] Vref on ATTiny861a

I am having a tough time getting this chip to respond to any other ADC
voltage reference than the default AVcc.

The code snip is really simple... Below, using the MakroC Pro compiler,
however the results seem to be the same if I do the same using ASM
instructions instead of their bit-level defines.

I must be overlooking something. It seems so simple, driving me nuts that
it's not working right. I have used the same compiler and basic code to get
a mega328 to work. 

Appreciate any suggestions the group may have.

Thanks/jeff

REFS0_bit = 1; // 001 invokes external Vref as ADC reference
ADEN_bit = 1; // enable adc
ADSC_bit = 1; // start conversion
while(adsc_bit);
lb=ADCL; // get lower byte
ub=ADCH; // get upper byte
adc_rd0 = (256*ub) + lb; // build number

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]

Re: [AVR-Chat] Vref on ATTiny861a

2010-01-21 by Dennis Clark

Try disconnecting the external Aref when using an internal reference and
see if that clears it up.  The data sheet shows these all being
switchable, but there may be conflicts.  I'd disconnect the Aref and hang
a bypass cap off of it for the internal ref like that data sheet says and
see what happens.

DLC

> Dave,
>
> I ramp the physical voltage into the port 0 up, and at about 5V, it hits
> the 1023 level.  So that's why I conclude it's referencing only the Avcc
> which I have tied to +5.
>
> I have tried every combination of the Vref settings, one by one.
> Including the 2.5V, the 1.1v internal, etc.  I get the same response
> (meaning full scale at 5v) in each case.
>
> I have to believe that the chip does not that kind of significant bug -
> and I have also got to believe that the compiler works on this chip just
> as it's done on a couple of others.
>
> The most logical conclusion is that I am overlooking some footnote in a
> register explanation or something that is specific to this chip...
>
> Regards,
> JB
>
>
> From: Dave McLaughlin
> Sent: Thursday, January 21, 2010 9:36 PM
> To: AVR-Chat@yahoogroups.com
> Subject: RE: [AVR-Chat] Vref on ATTiny861a
>
>
>
> Hi Jeff,
>
> What results are you seeing from the ADC with this code?
>
> What voltage have you got on Vref?
>
> What else have you tried?
>
> Dave.
>
> From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf
> Of Jeff Blaine AC0C
> Sent: 21 January 2010 17:47
> To: AVR-Chat@yahoogroups.com
> Subject: [AVR-Chat] Vref on ATTiny861a
>
> I am having a tough time getting this chip to respond to any other ADC
> voltage reference than the default AVcc.
>
> The code snip is really simple... Below, using the MakroC Pro compiler,
> however the results seem to be the same if I do the same using ASM
> instructions instead of their bit-level defines.
>
> I must be overlooking something. It seems so simple, driving me nuts that
> it's not working right. I have used the same compiler and basic code to
> get
> a mega328 to work.
>
> Appreciate any suggestions the group may have.
>
> Thanks/jeff
>
> REFS0_bit = 1; // 001 invokes external Vref as ADC reference
> ADEN_bit = 1; // enable adc
> ADSC_bit = 1; // start conversion
> while(adsc_bit);
> lb=ADCL; // get lower byte
> ub=ADCH; // get upper byte
> adc_rd0 = (256*ub) + lb; // build number
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


-- 
Dennis Clark
TTT Enterprises

Re: Vref on ATTiny861a

2010-01-21 by ecros_technology

--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:

> The most logical conclusion is that
> I am overlooking some footnote ...

You haven't answered Dave's question "What voltage have you got on Vref?".  My guess is that you've wired the VREF pin to some source of 5 volts and overlooked the footnote that says that if you do this you should not select the internal references because a) it won't work and b) you could let the magic smoke out.  The VREF pin is connected directly to the selected reference voltage, the reason for this being that you can hang a capacitor on it to reduce reference noise.  As a result, if you select an internal reference, you must ONLY have the capacitor out there; you can't stick some other voltage on it or it will conflict with the internal reference.  (This is all from ATmega parts, which is one of the reasons I say this is a guess.)

Graham.

Re: Vref on ATTiny861a

2010-01-21 by ivernot

Hi Jeff,
I am not familiar with the MakroC complier (by your code smippet it seems that one can set things at a bit level rather than having to write the entire register - interesting...)

A few things to note -
1. What happens to the bits that you are not explicitly setting? We assume they are zero - but are they  _really_??
2. Are you select the correct ADC channel you are reading from? (ADMUX bits)
3. Did you setup the ADC clock? (ADPS bits)

Can you look at the generated asm to check that the registers are written as you'd expect?

Below is code I use to init the adc on an ATMega128. HTH

Please let us know how you get on.
Regards,
Ivan Vernot

void ADC_Init(BOOL use_internal_ref )
{
	ADMUX = 0;		        // Sel Ch0
	if(use_internal_ref)
	{  // use VCC as reference
	   ADMUX  = BIT(REFS0);		// 01xx xxxx; AVCC as ref
   	   // NB: ;'use internal' does not mean use 
           // ACTUAL internal 2.56 V ref 
	   // it means use AVCC are the reference (5V)
	}
	else
	{  // use external reference
	   ADMUX  &= ~(BIT(REFS1)|BIT(REFS0));			
           // 00xx xxxx ; AREF as ref
	}
//	ADMUX  |= BIT(ADLAR);	// xx1x xxxx; Left Adjust results

	ADCSRA = BIT(ADEN) | BIT(ADPS2)|BIT(ADPS1)|BIT(ADPS0); 	
	// Enable ADC in single shot mode
	// ADSP2:0 110 => clk/64   => 14MHz/64  = 230Khz ADC clk)
	// ADSP2:0 111 => clk/128 => 14MHz/128 = 115.2Khz ADC clk)

//	SFIOR = BIT(ADHSM);		// ADC High Speed Mode
	ADCSRA |= BIT(ADSC);		// Start the first conversion

	// initiate dummy conversion
 	while (ADCSRA & BIT(ADSC))
 	{
 	   WATCHDOG();	 // Wait until coversion completed
 	}
}


--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:
Show quoted textHide quoted text
>
> I am having a tough time getting this chip to respond to any other ADC voltage reference than the default AVcc.
> 
> The code snip is really simple...  Below, using the MakroC Pro compiler, however the results seem to be the same if I do the same using ASM instructions instead of their bit-level defines.
> 
> I must be overlooking something.  It seems so simple, driving me nuts that it's not working right.  I have used the same compiler and basic code to get a mega328 to work.  
> 
> Appreciate any suggestions the group may have.
> 
> Thanks/jeff
> 
> 
>  REFS0_bit = 1;                    // 001 invokes external Vref as ADC reference
>     ADEN_bit = 1;                     // enable adc
>     ADSC_bit = 1;                     // start conversion
>     while(adsc_bit);
>     lb=ADCL;                          // get lower byte
>     ub=ADCH;                          // get upper byte
>     adc_rd0 = (256*ub) + lb;          // build number
> 
> [Non-text portions of this message have been removed]
>

Re: [AVR-Chat] Vref on ATTiny861a

2010-01-21 by John Samperi

At 12:55 AM 22/01/2010, you wrote:
>I have tried every combination of the Vref settings, one by one
>Including the 2.5V, the 1.1v internal, etc.

But as others have asked what do you have on the VREF pin?

If it is connected to Vcc or Avcc, accidentally or on purpose
then, by trying other internal references, you are likely to kill
them as they get shorted out to Vref.

Regards

John Samperi

********************************************************
Ampertronics Pty. Ltd.
11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
Tel. (02) 9674-6495       Fax (02) 9674-8745
Website  http://www.ampertronics.com.au
*Electronic Design * Custom Products * Contract Assembly
********************************************************

Re: Vref on ATTiny861a

2010-01-22 by ecros_technology

--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:

> Vref is tied to a variable ps ...

Well, that's your problem, then.

Graham.

Re: Vref on ATTiny861a

2010-01-22 by ecros_technology

--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:

> Can you expand a bit more?
> ... Because the device did not
> seem to recognize the 4.0v bandgap
> ref, I put this in to see if varying
> the Vref would be reflected in
> different ADC readings.  It does not.  

Well, the device "not recognizing" an external reference is not the problem you've asked for help with.  You've reported that the device behaves as if it has a 5.0 volt reference whatever you configure the reference to be (correct me if I'm wrong).  If you read my post of yesterday (Message #16793), you'll see that connecting the VREF pin to a voltage source and selecting an internal reference is probably a bad thing to do.  Consult the data sheet for the device you're using.  Now that you've done that, you won't be able to rely on the device working properly as some of the magic smoke has probably come out.  In other words, you may have blown up the internal references and this could explain what you're now seeing.

Graham.

Re: Vref on ATTiny861a

2010-01-22 by n1ist

If you set the ADC to use an external reference, then Vref is an INPUT and you need to feed in the reference there.  If you set the ADC to use anything else (Avcc, internal references), then Vref is an OUTPUT and the only thing you should have connected to it is a 100n filter cap. Feeding a voltage into Vref when it is trying to source will cause all sorts of problems, including the processor failing at elevated temperatures...

--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:
Show quoted textHide quoted text
>
> Graham,
> 
> Can you expand a bit more?
> 
> Vref is tied to this ps so that I can set the Vref to various levels for testing.  Because the device did not seem to recognize the 4.0v bandgap ref, I put this in to see if varying the Vref would be reflected in different ADC readings.  It does not.  
> 
> Thanks.
> 
> 
> From: ecros_technology 
> Sent: Friday, January 22, 2010 8:10 PM
> To: AVR-Chat@yahoogroups.com 
> Subject: [AVR-Chat] Re: Vref on ATTiny861a
> 
> 
>   
> --- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@> wrote:
> 
> > Vref is tied to a variable ps ...
> 
> Well, that's your problem, then.
> 
> Graham.
> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]
>

Re: [AVR-Chat] Re: Vref on ATTiny861a

2010-01-22 by Jeff Blaine AC0C

Gentlemen,

Thanks for all the comments.  Kindly find my answer to all of the various questions here on top of Ivan's message.  

* It's the AVCC line that is tied to +5.  Not Vref.  So far, no magic smoke coming out.  

* Vref is tied to a variable ps for troubleshooting, but for the formal circuit, it would be tied to a 4.096v bandgap precision reference.

* 8 mhz clock via div/64 prescaler is 125 khz clock rate to the ADC - below the 200khz recommended.

* Setting the input selection via ADMUX = 64 or REFS0=1 provides no different result than ADXMUX=0/REFS0=0;  I can see the 

LST follows:

;attiny861 adc vref test.c,429 ::   for(;;){

L_main39:
;attiny861 adc vref test.c,432 ::   REFS0_bit=1;
0x0D1A 0xB1B7     IN         R27, REFS0_bit+0
0x0D1C 0x64B0     SBR        R27, 64
0x0D1E 0xB9B7     OUT        REFS0_bit+0, R27

;attiny861 adc vref test.c,433 ::   ADEN_bit = 1;                     // enable adc
0x0D20 0xB1B6     IN         R27, ADEN_bit+0
0x0D22 0x68B0     SBR        R27, 128
0x0D24 0xB9B6     OUT        ADEN_bit+0, R27

;attiny861 adc vref test.c,434 ::   ADSC_bit = 1;                     // start conversion
0x0D26 0xB1B6     IN         R27, ADSC_bit+0
0x0D28 0x64B0     SBR        R27, 64
0x0D2A 0xB9B6     OUT        ADSC_bit+0, R27

;attiny861 adc vref test.c,436 ::   while(adsc_bit);
L_main42:
0x0D2C 0xB1B6     IN         R27, ADSC_bit+0
0x0D2E 0xFFB6     SBRS       R27, 6
0x0D30 0xC001     RJMP       L_main43
0x0D32 0xCFFC     RJMP       L_main42

L_main43:
;attiny861 adc vref test.c,439 ::   lb=ADCL;                          // get lower byte
0x0D34 0xB104     IN         R16, ADCL+0
0x0D36 0x830B     STD        Y+3, R16

;attiny861 adc vref test.c,440 ::   ub=ADCH;                          // get upper byte
0x0D38 0xB105     IN         R16, ADCH+0
0x0D3A 0x830A     STD        Y+2, R16

;attiny861 adc vref test.c,441 ::   adc_rd0 = (256*ub) + lb;          // build number
0x0D3C 0x810A     LDD        R16, Y+2
0x0D3E 0x2F30     MOV        R19, R16
0x0D40 0x2722     CLR        R18
0x0D42 0x810B     LDD        R16, Y+3
0x0D44 0xE010     LDI        R17, 0
0x0D46 0x0F02     ADD        R16, R18
0x0D48 0x1F13     ADC        R17, R19
0x0D4A 0x8308     STD        Y+0, R16
0x0D4C 0x8319     STD        Y+1, R17
Show quoted textHide quoted text
From: ivernot 
Sent: Friday, January 22, 2010 5:57 AM
To: AVR-Chat@yahoogroups.com 
Subject: [AVR-Chat] Re: Vref on ATTiny861a


  


Hi Jeff,
I am not familiar with the MakroC complier (by your code smippet it seems that one can set things at a bit level rather than having to write the entire register - interesting...)

A few things to note -
1. What happens to the bits that you are not explicitly setting? We assume they are zero - but are they _really_??
2. Are you select the correct ADC channel you are reading from? (ADMUX bits)
3. Did you setup the ADC clock? (ADPS bits)

Can you look at the generated asm to check that the registers are written as you'd expect?

Below is code I use to init the adc on an ATMega128. HTH

Please let us know how you get on.
Regards,
Ivan Vernot

void ADC_Init(BOOL use_internal_ref )
{
ADMUX = 0; // Sel Ch0
if(use_internal_ref)
{ // use VCC as reference
ADMUX = BIT(REFS0); // 01xx xxxx; AVCC as ref
// NB: ;'use internal' does not mean use 
// ACTUAL internal 2.56 V ref 
// it means use AVCC are the reference (5V)
}
else
{ // use external reference
ADMUX &= ~(BIT(REFS1)|BIT(REFS0)); 
// 00xx xxxx ; AREF as ref
}
// ADMUX |= BIT(ADLAR); // xx1x xxxx; Left Adjust results

ADCSRA = BIT(ADEN) | BIT(ADPS2)|BIT(ADPS1)|BIT(ADPS0); 
// Enable ADC in single shot mode
// ADSP2:0 110 => clk/64 => 14MHz/64 = 230Khz ADC clk)
// ADSP2:0 111 => clk/128 => 14MHz/128 = 115.2Khz ADC clk)

// SFIOR = BIT(ADHSM); // ADC High Speed Mode
ADCSRA |= BIT(ADSC); // Start the first conversion

// initiate dummy conversion
while (ADCSRA & BIT(ADSC))
{
WATCHDOG(); // Wait until coversion completed
}
}

--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:
>
> I am having a tough time getting this chip to respond to any other ADC voltage reference than the default AVcc.
> 
> The code snip is really simple... Below, using the MakroC Pro compiler, however the results seem to be the same if I do the same using ASM instructions instead of their bit-level defines.
> 
> I must be overlooking something. It seems so simple, driving me nuts that it's not working right. I have used the same compiler and basic code to get a mega328 to work. 
> 
> Appreciate any suggestions the group may have.
> 
> Thanks/jeff
> 
> 
> REFS0_bit = 1; // 001 invokes external Vref as ADC reference
> ADEN_bit = 1; // enable adc
> ADSC_bit = 1; // start conversion
> while(adsc_bit);
> lb=ADCL; // get lower byte
> ub=ADCH; // get upper byte
> adc_rd0 = (256*ub) + lb; // build number
> 
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]

Re: [AVR-Chat] Re: Vref on ATTiny861a

2010-01-22 by Jeff Blaine AC0C

Graham,

Can you expand a bit more?

Vref is tied to this ps so that I can set the Vref to various levels for testing.  Because the device did not seem to recognize the 4.0v bandgap ref, I put this in to see if varying the Vref would be reflected in different ADC readings.  It does not.  

Thanks.
Show quoted textHide quoted text
From: ecros_technology 
Sent: Friday, January 22, 2010 8:10 PM
To: AVR-Chat@yahoogroups.com 
Subject: [AVR-Chat] Re: Vref on ATTiny861a


  
--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:

> Vref is tied to a variable ps ...

Well, that's your problem, then.

Graham.





[Non-text portions of this message have been removed]

Re: [AVR-Chat] Re: Vref on ATTiny861a

2010-01-22 by Jeff Blaine AC0C

Graham,

Thanks.  But my explanation symantecs are probably a source for confusion...  

In this case, the adc renders readings that coorespond with an effective VREF of 5V.  And no combination of REFSx commands will get the device to behave against a scale of anything other than 5V.  That's the problem.  

Call it failing to recognize the external Vref, or whatever wording would be better, the problem is the same.  The top end of the ADC divider chain works as if there is 5V there - no matter what the code says.

It's not a hardware failure.  The device/code behaves the same in Proteus - and while I will buy the case that the actual hardware can fail with incorrectly applied voltages, the virtual version probably does not suffer from the same potential smoke issues.

I really cannot understand how something so basic and simple like this can fail to work.  Making me lose my mind...  
Show quoted textHide quoted text
From: ecros_technology 
Sent: Friday, January 22, 2010 8:42 PM
To: AVR-Chat@yahoogroups.com 
Subject: [AVR-Chat] Re: Vref on ATTiny861a


  
--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:

> Can you expand a bit more?
> ... Because the device did not
> seem to recognize the 4.0v bandgap
> ref, I put this in to see if varying
> the Vref would be reflected in
> different ADC readings. It does not. 

Well, the device "not recognizing" an external reference is not the problem you've asked for help with. You've reported that the device behaves as if it has a 5.0 volt reference whatever you configure the reference to be (correct me if I'm wrong). If you read my post of yesterday (Message #16793), you'll see that connecting the VREF pin to a voltage source and selecting an internal reference is probably a bad thing to do. Consult the data sheet for the device you're using. Now that you've done that, you won't be able to rely on the device working properly as some of the magic smoke has probably come out. In other words, you may have blown up the internal references and this could explain what you're now seeing.

Graham.





[Non-text portions of this message have been removed]

Re: [AVR-Chat] Re: Vref on ATTiny861a

2010-01-22 by Jeff Blaine AC0C

The variable PS or the 4V bandgap provide the reference.  

With REFS0 set, the external Vref is selected which means it's serving as an input.  

Problem is, the adc provides readings that are scaled against a 5V reference regardless of the actual Vref value.

Behaves the same in simulation so it's not a case of crispy fried chips.  

73/jeff/ac0c
Show quoted textHide quoted text
From: n1ist 
Sent: Friday, January 22, 2010 8:50 PM
To: AVR-Chat@yahoogroups.com 
Subject: [AVR-Chat] Re: Vref on ATTiny861a


  
If you set the ADC to use an external reference, then Vref is an INPUT and you need to feed in the reference there. If you set the ADC to use anything else (Avcc, internal references), then Vref is an OUTPUT and the only thing you should have connected to it is a 100n filter cap. Feeding a voltage into Vref when it is trying to source will cause all sorts of problems, including the processor failing at elevated temperatures...

--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:
>
> Graham,
> 
> Can you expand a bit more?
> 
> Vref is tied to this ps so that I can set the Vref to various levels for testing. Because the device did not seem to recognize the 4.0v bandgap ref, I put this in to see if varying the Vref would be reflected in different ADC readings. It does not. 
> 
> Thanks.
> 
> 
> From: ecros_technology 
> Sent: Friday, January 22, 2010 8:10 PM
> To: AVR-Chat@yahoogroups.com 
> Subject: [AVR-Chat] Re: Vref on ATTiny861a
> 
> 
> 
> --- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@> wrote:
> 
> > Vref is tied to a variable ps ...
> 
> Well, that's your problem, then.
> 
> Graham.
> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]

Re: Vref on ATTiny861a

2010-01-22 by ecros_technology

--- In AVR-Chat@yahoogroups.com, "Jeff Blaine AC0C" <keepwalking188@...> wrote:

> It's not a hardware failure.
> The device/code behaves the
> same in Proteus ...

Have you verified that the bits that control the reference selection are getting set by your code?  This device has debugWIRE.  Go look at the appropriate register after running your code and see how it is set.

Graham.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.