--- In AVR-Chat@yahoogroups.com, Cat C <catalin_cluj@...> wrote: > > > The watchdog does it's job, it just happens to be the convenient way to have a reset a little while after a power up, if the SPI doesn't work. > I don't see any other way of "cleaning" the SPI. > It's not a simple communication timeout, it's a complicated one, and if I have 1000 SPI calls, they will all fail until I do a reset. > If you're gonna propose a reset chip, or other circuitry to get a reset other ways, why? This works fine. This may "fix" your SPI problem, but what other problems will it cause in the future. I see from the Atmel web site that the ATMega664P has been obsoleted and to use the ATMega664P'A' device. I would think there is some other problem and this is how it shows itself. Lets face it, the SPI port should always work and this is just wrong. If this is for a product and you can not get non'A' versions, what problems will you see then ? I will be moving from a ATmega16 to a 64K part this summer. If the 664P is having problems, I don't want to include it in my parts list. ( maybe that why Atmel dis-continued it) I did not see any errata about SPI or RESET problems. If a RESET chip will fix this problem, it will be better then waiting for a strange problem to appear in production. good luck don
Message
Re: Code stuck waiting for SPI transmission but only after power-up. (ATMega644P)
2010-03-15 by Donald H
Attachments
- No local attachments were found for this message.