Yahoo Groups archive

AVR-Chat

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

Message

RE: [AVR-Chat] Re: Debugwire, stk-500 and M168

2008-01-24 by Philippe Habib

The problem is that these things are like dog food.  The consumer and the
purchaser have different priorities.  I'm sure that if you got a few beers
into an Atmel exec, they'd tell you the purpose of the studio is to sell
parts by making people like us think it will make our lives easier and allow
us to deliver more working code faster.  By the time we discover the bugs
we're committed to their parts and when the next project rolls around, we'd
rather deal with a bug set we've learned than to fight the same battles
again with another IDE for another vendor's part.

-----Original Message-----
From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf
Of David VanHorn
Sent: Thursday, January 24, 2008 1:08 PM
To: AVR-Chat@yahoogroups.com
Subject: Re: [AVR-Chat] Re: Debugwire, stk-500 and M168

On Jan 24, 2008 3:48 PM, Dennis Clark <dlc@frii.com> wrote:
> Has anyone used the ICE MK II with GDB or Avarice?  It'd be interesting to
> see if those debuggers work better than the Atmel IDE.  The only reason
> that I mentioned this ICE is that I own that one, so of course its more
> interesting to me...  Does anyone have any experience at all with avarice
> or GDB?

They tell me there's a new studio coming, a ground-up rewrite.
But my project is probably going to be complete before we see that release.


Somewhere, there has to be someone in atmel who understands that the
purpose of these tools is to make our lives EASIER, and help us
deliver more working code FASTER.   IMHO those points are being
missed, entirely.


 
Yahoo! Groups Links






-- 
No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.19.10/1241 - Release Date: 1/24/2008
9:58 AM

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.