--- In AVR-Chat@yahoogroups.com, "rtstofer" <rstofer@p...> wrote: > ... Is the ATmega32 a > reasonable platform ... Assuming you've read the data sheet and the resources of this MCU are adequate to the job, yes, this is a reasonable platform. > ... will the WinAVR/AVR Studio 4 > and STK500 work together to get > this thing done? ... Yes. Although you can't kick off builds from inside AVR Studio, it does detect that the load file has changed due to a build kicked off from somewhere else (Programmer's Notepad or the command line) and reloads the project. > ... Any particular gotchas ... Note that there is no in-circuit debugger in the setup you're proposing. The ATmega32 supports OCD via the JTAG interface, but there is no JTAG header on the STK500. You will need two additional things, first a JTAG interface and second some kind of adapter to connect it to the STK500. The Atmel JTAG interface, the JTAG ICE, is about $300, but if this is outside your budget there are "clones" available which will do the job for you. It isn't too hard to puzzle out how to make the adapter. If you get a clone JTAG interface you may be able to get a ready-made adapter along with it. When you move from the STK500 to your own target system, remember to build in the JTAG header. Graham.
Message
Re: Recommendations re: ATmega32 Development
2005-04-03 by Graham Davies
Attachments
- No local attachments were found for this message.