Yahoo Groups archive

AVR-Chat

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

Thread

*AHA* *AHA*

*AHA* *AHA*

2007-01-04 by Thomas Keller

Well, Well.    That solved the problem nicely.  

It turns out my debugger thought it was running an ATtiny13, not the 
ATtiny25.  *!!*

Inexperience in using the AVR Studio tool was the culprit all along 
(thanks Don).

tom

Re: [AVR-Chat] *AHA* *AHA*

2007-01-04 by David VanHorn

On 1/3/07, Thomas Keller <tjkeller1@alltel.net> wrote:
>
> Well, Well.    That solved the problem nicely.
>
> It turns out my debugger thought it was running an ATtiny13, not the
> ATtiny25.  *!!*


I've often wondered why you have to tell studio what chip you're using given
that there's all the information in the world in the file to do that
automatically.

Ah well, these things happen.    Onward and upward.


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

Re: [AVR-Chat] *AHA* *AHA*

2007-01-04 by Don AE5K

Thomas Keller wrote:
> Well, Well.    That solved the problem nicely.  
> 
> It turns out my debugger thought it was running an ATtiny13, not the 
> ATtiny25.  *!!*
> 
> Inexperience in using the AVR Studio tool was the culprit all along 
> (thanks Don).
> 
> tom

I'm glad that my last minute thought turned out to be the problem. It is
too bad that the simulator cannot pick this info up from the assembler,
but it does not.  The assembler summary of bytes used, bytes remaining
and percentage used should also reflect whatever device you specified in
the project file (in terms of correct sizes).

When first starting a project (using I guess what is called the wizard),
it steps you through the project name, whether it is ASM or C, etc. but
most importantly it allows you to specify the debug method (simulator)
AND the AVR device (tiny25 in your case).  If you specify device when
starting a project, you don't need to be concerned about it later when
you start simulation -- unless you change chips in the middle of the stream!

You are apparently also becoming familiar with the Intel hex files that
the assembler/compiler puts out (and the .eep file).  You can Google and
read up on the format, but essentially there are not line numbers, but
number of data bytes, starting address, record type, data bytes, and a
checksum at the very end of line.

You're on you way...

Don

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.