Re: Atmel AVR development tools

On Thu, 31 Jan 2008 14:34:43 -0800 (PST), in sci.electronics.design
dbvanhorn <microbrix@xxxxxxxxx> wrote:


Why do you need that?

The only tools I ever used for AVR are the scope, the byteblaster and
the debug printout to RS-232. I developed the projects of up to about
20k lines of C++ code and the home made RTOS.

I hear ya. I have in the past, done "crash and burn" with only single
pin output of many bytes of data.
It's error-prone and tedious, but it does work. The additional code
to output the debugging data takes time and space too though, and I
don't always have that spare.

Short version, neither they nor I can figure out WTF is going on.

Apparently the problem is with you.

:) Yeah. I'm leaning twoard Studio using some memory somewhere
that's not initialized.
That's sure what it feels like.


You have to stop playing games with the fancy toys and content yourself
with the essential.
The entities should not be multiplied beyond the necessity.

This would be the second time I've heard someone tell me to just ditch
the Atmel toolchain entirely.
Maybe I'm just stuck because it USED TO WORK. It worked flawlessly. I
delivered apps one after the other, and NEVER had to worry wether a
tool would work. The sim was great, and very useful. Their ICE-200
was wonderful. The ICE-50 was great, up till the first official
release, then it went to hell.

Just had the same problem, I downloaded the latest GCC/studio4 stuff,
but the thinkulator would not run :

"AVR Simulator: Invalid opcode 0xffff at address 0x00f000"

on a "helloworld.c", but simpler

While(1)
{
counter++;
}

It worked on a 1 year old "not updated" setup on my laptop.

MSP430 anyone?


martin
.