[time-nuts] Clocking a PIC16F628A from a Rubidium Standard

Ulrich Bangert df6jb at ulrich-bangert.de
Fri Nov 25 13:06:59 UTC 2011


Attila,

> In the past 2 years, i've discovered 3 silicon bugs in Atmel 
> chips and two "bugs" in their documentation. Reporting the 
> silicon bugs resulted in being completely ignored and the 
> documentation bugs were answered with (literally) "it's a 
> silicon thing", completely disregarding the fact that 
> following the documentation will cause hard to trace bugs in 
> the software (that's how i discovered them in the first place).

Can you please contact me offline at df6jb at ulrich-bangert.de for a
discussion on this topic? I use lots of ATTINY85, ATMEGA32 and ATMEGA2560
and have also discovered some issues with ATMEL processors (specially with
the 32). Want to learn more about what you found.

Best regards
Ulrich

> -----Ursprungliche Nachricht-----
> Von: time-nuts-bounces at febo.com 
> [mailto:time-nuts-bounces at febo.com] Im Auftrag von Attila Kinali
> Gesendet: Freitag, 25. November 2011 13:14
> An: Discussion of precise time and frequency measurement
> Betreff: Re: [time-nuts] Clocking a PIC16F628A from a 
> Rubidium Standard
> 
> 
> On Fri, 25 Nov 2011 02:02:04 -0700
> Kevin Rosenberg <kevin at rosenberg.net> wrote:
> 
> > In this case, the use of the protection diode and the 1 ma 
> limit comes 
> > directly from the manufacturer Atmel's App Note AVR182 [1]. 
> That said, 
> > I'm cautious even when the manufacturer in an App Note says 
> it's okay, 
> > but the use falls outside of the datasheet specifications.
> 
> Don't trust a datasheet blindly. Always apply common sense 
> and a bit of caution. Especially when it comes to Atmel.
> 
> In the past 2 years, i've discovered 3 silicon bugs in Atmel 
> chips and two "bugs" in their documentation. Reporting the 
> silicon bugs resulted in being completely ignored and the 
> documentation bugs were answered with (literally) "it's a 
> silicon thing", completely disregarding the fact that 
> following the documentation will cause hard to trace bugs in 
> the software (that's how i discovered them in the first place).
> 
> 			Attila Kinali
> 
> -- 
> Why does it take years to find the answers to
> the questions one should have asked long ago?
> 
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to 
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.





More information about the Time-nuts_lists.febo.com mailing list