Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.electronics.design > #449314
| From | Joerg <news@analogconsultants.com> |
|---|---|
| Newsgroups | sci.electronics.design |
| Subject | Re: analog failures |
| Date | 2017-02-26 09:46 -0800 |
| Message-ID | <ehgik2F3ergU1@mid.individual.net> (permalink) |
| References | (10 earlier) <004c4a1f-ecc9-422d-a982-ce163d9224a2@googlegroups.com> <eh8oq2Fgp7rU1@mid.individual.net> <1a268f48-ccf5-4699-9f4e-44fd973f58c1@googlegroups.com> <ehe8lrFk2ehU1@mid.individual.net> <7a46230f-a92a-4357-89a6-e6e7caa8a8db@googlegroups.com> |
On 2017-02-26 08:29, dagmargoodboat@yahoo.com wrote: > On Saturday, February 25, 2017 at 3:44:47 PM UTC-5, Joerg wrote: >> On 2017-02-24 09:02, dagmargoodboat@yahoo.com wrote: >>> On Thursday, February 23, 2017 at 1:43:23 PM UTC-5, Joerg wrote: >>>> On 2017-02-22 15:45, dagmargoodboat@yahoo.com wrote: >>>> >>>> [...] >>>> >>>>> >>>>> AIUI you can clear nearly all the i2c deadlocks by having the master >>>>> cycle the clock 9 times (or by just cycling the power :). >>>>> >>>> >>>> Thing is, my clients typically do not want to hear the word "nearly" :-) >>> >>> Which is why you'd want to design the thing so the i2c could never >>> deadlock in the first place. But if you're like me, chastened by >>> others' tales, you could include two levels of recovery so that even >>> if the inconceivable happened it could ever be a critical fault, just >>> in case. >>> >>> Reliable + (redundancy + retry) = spandex, belt, and suspenders. >>> >>> SPI can fail too if someone think's he's enabled when he isn't. What's >>> the fallback then? But that doesn't much happen, right? >>> >> >> Not really because the master enables and disables. So having a hung bus >> because or a rogue device isn't likely unless the device is physically >> damaged. > > Well that was my point-- > >> Not so with I2C where I saw cases where a power cycle made it >> all come back and work fine. For a while ... > > Such a system plainly has a flaw somewhere--a race condition or some > protocol problem--and that's obviously NOT okay. > The problem is that the issue is often not controlled by the quality of the design but by that of the circuitry inside an IC, so out of the hands of the board level designer. > I just tied five boards together in a system comprising twenty-one i2c > devices, and did it with a four-inch / two-wire bus. I2c was ideal for > that. > I2C is a great idea. It's just the implementation that often isn't sufficiently rugged. -- Regards, Joerg http://www.analogconsultants.com/
Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
analog failures John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-02-14 14:47 -0800
Re: analog failures Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-02-14 15:05 -0800
Re: analog failures Reinhardt Behm <rbehm@hushmail.com> - 2017-02-15 10:52 +0800
Re: analog failures bill.sloman@ieee.org - 2017-02-14 19:00 -0800
Re: analog failures Reinhardt Behm <rbehm@hushmail.com> - 2017-02-15 11:55 +0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-15 07:53 -0800
Re: analog failures John Larkin <jjlarkin@highlandtechnology.com> - 2017-02-15 08:30 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-15 10:19 -0800
Re: analog failures John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-02-15 10:53 -0800
Re: analog failures Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-02-15 10:58 -0800
Re: analog failures "Tim Williams" <tiwill@seventransistorlabs.com> - 2017-02-15 21:25 -0600
Re: analog failures John Larkin <jjlarkin@highlandtechnology.com> - 2017-02-15 20:18 -0800
Re: analog failures rickman <gnuarm@gmail.com> - 2017-02-17 15:44 -0500
Re: analog failures rickman <gnuarm@gmail.com> - 2017-02-17 15:30 -0500
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-17 14:05 -0800
Re: analog failures rickman <gnuarm@gmail.com> - 2017-02-17 17:16 -0500
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-17 14:38 -0800
Re: analog failures rickman <gnuarm@gmail.com> - 2017-02-17 17:58 -0500
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-17 15:37 -0800
Re: analog failures rickman <gnuarm@gmail.com> - 2017-02-17 18:51 -0500
Re: analog failures krw@notreal.com - 2017-02-17 20:27 -0500
Re: analog failures John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-02-17 17:56 -0800
Re: analog failures "Tim Williams" <tiwill@seventransistorlabs.com> - 2017-02-17 21:03 -0600
Re: analog failures krw@notreal.com - 2017-02-17 22:36 -0500
Re: analog failures rickman <gnuarm@gmail.com> - 2017-02-19 00:45 -0500
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-19 08:32 -0800
Re: analog failures John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-02-21 12:31 -0800
Re: analog failures rickman <gnuarm@gmail.com> - 2017-02-23 14:57 -0500
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-23 12:02 -0800
Re: analog failures John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-02-17 17:27 -0800
Re: analog failures rickman <gnuarm@gmail.com> - 2017-02-17 20:39 -0500
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-18 07:41 -0800
Re: analog failures John Larkin <jjlarkin@highlandtechnology.com> - 2017-02-18 08:04 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-18 08:16 -0800
Re: analog failures Reinhardt Behm <rbehm@hushmail.com> - 2017-02-16 06:49 +0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-16 07:14 -0800
Re: analog failures John Larkin <jjlarkin@highlandtechnology.com> - 2017-02-16 07:24 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-16 07:41 -0800
Re: analog failures Reinhardt Behm <rbehm@hushmail.com> - 2017-02-17 13:22 +0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-17 06:58 -0800
Re: analog failures John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-02-17 12:26 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-17 14:03 -0800
Re: analog failures "Tim Williams" <tiwill@seventransistorlabs.com> - 2017-02-17 21:05 -0600
Re: analog failures John Larkin <jjlarkin@highlandtechnology.com> - 2017-02-18 08:07 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-18 08:20 -0800
Re: analog failures John Larkin <jjlarkin@highlandtechnology.com> - 2017-02-18 09:20 -0800
Re: analog failures rickman <gnuarm@gmail.com> - 2017-02-19 00:48 -0500
Re: analog failures John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-02-21 12:39 -0800
Re: analog failures "Tim Williams" <tiwill@seventransistorlabs.com> - 2017-02-21 22:54 -0600
Re: analog failures krw@notreal.com - 2017-02-17 20:33 -0500
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-18 07:37 -0800
Re: analog failures dagmargoodboat@yahoo.com - 2017-02-22 15:45 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-23 10:43 -0800
Re: analog failures krw@notreal.com - 2017-02-23 20:42 -0500
Re: analog failures "Tim Williams" <tiwill@seventransistorlabs.com> - 2017-02-24 03:31 -0600
Re: analog failures grahamholloway@graham65.plus.com - 2017-02-24 06:39 -0800
Re: analog failures Don Kuenz <g@crcomp.net> - 2017-02-24 14:58 +0000
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-25 12:48 -0800
Re: analog failures pcdhobbs@gmail.com - 2017-02-26 04:39 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-26 07:52 -0800
Re: analog failures dagmargoodboat@yahoo.com - 2017-02-24 09:02 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-25 12:44 -0800
Re: analog failures dagmargoodboat@yahoo.com - 2017-02-26 08:29 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-26 09:46 -0800
Re: analog failures John Larkin <jjlarkin@highlandtechnology.com> - 2017-02-26 10:11 -0800
Re: analog failures krw@notreal.com - 2017-02-26 17:55 -0500
Re: analog failures John Larkin <jjlarkin@highlandtechnology.com> - 2017-02-26 15:09 -0800
Re: analog failures krw@notreal.com - 2017-02-26 19:30 -0500
Re: analog failures John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-02-27 10:37 -0800
Re: analog failures Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-02-24 09:14 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-25 12:46 -0800
Re: analog failures Klaus Kragelund <klauskvik@hotmail.com> - 2017-02-26 17:44 -0800
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-27 07:51 -0800
Re: analog failures Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-02-23 21:36 +0200
Re: analog failures dagmargoodboat@yahoo.com - 2017-02-24 08:38 -0800
Re: analog failures krw@notreal.com - 2017-02-24 20:20 -0500
Re: analog failures kevin93 <kevin@whitedigs.com> - 2017-02-24 17:36 -0800
Re: analog failures Ralph Barone <ralph@invalid.com> - 2017-02-15 03:25 +0000
Re: analog failures John Larkin <jjlarkin@highlandtechnology.com> - 2017-02-14 19:20 -0800
Re: analog failures Tim Wescott <seemywebsite@myfooter.really> - 2017-02-14 17:46 -0600
Re: analog failures Jim Thompson <To-Email-Use-The-Envelope-Icon@On-My-Web-Site.com> - 2017-02-14 17:50 -0700
Re: analog failures Tim Wescott <tim@seemywebsite.com> - 2017-02-14 23:49 -0600
Re: analog failures Jim Thompson <To-Email-Use-The-Envelope-Icon@On-My-Web-Site.com> - 2017-02-15 07:03 -0700
Re: analog failures John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-02-15 10:18 -0800
Re: analog failures Tim Wescott <seemywebsite@myfooter.really> - 2017-02-15 15:06 -0600
Re: analog failures legg <legg@nospam.magma.ca> - 2017-02-16 23:06 -0500
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-17 07:00 -0800
Re: analog failures legg <legg@nospam.magma.ca> - 2017-02-17 13:22 -0500
Re: analog failures Joerg <news@analogconsultants.com> - 2017-02-17 11:06 -0800
csiph-web