Yahoo Groups archive

AVR-Chat

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

Message

Re: ATxmega64A3 Capture TCD0.CCA problem

2011-07-28 by warm38spl

Yes, the compiler knows that I'm working with the 64A3 not the 16A4.
I have not worked with the 16A4 only the 64A3.  But then, everything else works just fine.  The only problem the extra 0x8000 in the CCA.  Why is it there?  It's driving me nuts! (or, at least, more so than is normal for me)

--- In AVR-Chat@yahoogroups.com, Cat C <catalin_cluj@...> wrote:
>
> 
> Pulling at straws...
> -Do you have a 16A4 to try this on?
> -Did you tell the environment that you're using a 64A4?
> -Could it be a memory address? There's more in the 64A4; 0x8000 is 32K that was not available in the 16A4 but is in the 64A4...
>  
> Good luck,
>  
> Cat
>  
> 
> > 
> > Before (on the 16A4) the testing that the other guy did showed about 1056 (0x0420) plus/minus a little in CCA. Why is mine 0x8000 over?
> > Did the processor hear my negative spoken comments about its ancestry and decide to go negative to get back at me?
> > 
>  		 	   		  
> 
> [Non-text portions of this message have been removed]
>

Attachments

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.