Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #31106
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: Cortex-Mx MCUs with SWD access locked |
| Date | 2022-06-24 20:34 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <t95030$f52$1@dont-email.me> (permalink) |
| References | <t92mgi$d1l$1@dont-email.me> <t93vu7$ukp$1@dont-email.me> <t949sk$4jp$1@dont-email.me> <t94hhi$u4k$1@dont-email.me> <nnd$6eee50df$7dbf7e68@8d4ce289928ac989> |
On 24/06/2022 20:29, Stef wrote: > On 2022-06-24 pozz wrote in comp.arch.embedded: >> Il 24/06/2022 14:15, David Brown ha scritto: >> >>> Of course you could always have had damage from ground loops, spikes >>> when plugging the debugger in and out (if power is on), short-circuits >>> when trying to use an oscilloscope probe with clumsy fingers, etc. If >>> you have access to an X-Ray machine, you might be able to get some idea >>> about what happened. >> >> I admit I don't have professional workbench with anti-static writ strap >> band and so on, but I worked for many years without these kind of >> problems. It's strange I encountered so many problems concentrated in a >> few weeks. >> >> I will understand the problem of ground loops. > > Anti-static measures will not help for any of the problems David > describes. But they will prevent damage from ESD. Which could also be a > source for your problem. > > Has the weather been very dry in those problem weeks? Or did you change > your floor or did you get new shoes? > > My experience with ESD damage is that it is often subtle - it leads to long-term reliability issues, rather than outright failures. So the production department at my company is extremely careful about ESD. Up in the development department, we can be a bit laxer as long as the devices are not going to customers (or at least, not going further than the customers' development departments). I can't remember ever having a failure that I could definitely attribute to ESD damage in my lab, while I have definitely solved reliability problems by extra ground connections. Mind you, I would still avoid woollen slippers on a nylon carpet!
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-23 23:38 +0200
Re: Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-24 11:25 +0200
Re: Cortex-Mx MCUs with SWD access locked dalai lamah <antonio12358@hotmail.com> - 2022-06-24 12:22 +0200
Re: Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-24 16:27 +0200
Re: Cortex-Mx MCUs with SWD access locked dalai lamah <antonio12358@hotmail.com> - 2022-06-24 16:42 +0200
Re: Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-24 16:56 +0200
Re: Cortex-Mx MCUs with SWD access locked dalai lamah <antonio12358@hotmail.com> - 2022-06-24 17:16 +0200
Re: Cortex-Mx MCUs with SWD access locked David Brown <david.brown@hesbynett.no> - 2022-06-24 18:26 +0200
Re: Cortex-Mx MCUs with SWD access locked Dimiter_Popoff <dp@tgi-sci.com> - 2022-06-24 20:00 +0300
Re: Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-27 08:54 +0200
Re: Cortex-Mx MCUs with SWD access locked David Brown <david.brown@hesbynett.no> - 2022-06-27 09:23 +0200
Re: Cortex-Mx MCUs with SWD access locked David Brown <david.brown@hesbynett.no> - 2022-06-24 14:15 +0200
Re: Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-24 16:25 +0200
Re: Cortex-Mx MCUs with SWD access locked Stef <me@this.is.invalid> - 2022-06-24 20:29 +0200
Re: Cortex-Mx MCUs with SWD access locked David Brown <david.brown@hesbynett.no> - 2022-06-24 20:34 +0200
Re: Cortex-Mx MCUs with SWD access locked Stef <me@this.is.invalid> - 2022-06-24 22:12 +0200
Re: Cortex-Mx MCUs with SWD access locked David Brown <david.brown@hesbynett.no> - 2022-06-25 10:19 +0200
Re: Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-27 09:06 +0200
Re: Cortex-Mx MCUs with SWD access locked David Brown <david.brown@hesbynett.no> - 2022-06-27 09:25 +0200
Re: Cortex-Mx MCUs with SWD access locked Reinhardt Behm <rbehm@hushmail.com> - 2022-06-26 14:25 +0000
Re: Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-27 10:07 +0200
Re: Cortex-Mx MCUs with SWD access locked Reinhardt Behm <rbehm@hushmail.com> - 2022-06-27 15:11 +0000
Re: Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-27 23:50 +0200
Re: Cortex-Mx MCUs with SWD access locked Stef <me@this.is.invalid> - 2022-06-28 11:23 +0200
Re: Cortex-Mx MCUs with SWD access locked pozz <pozzugno@gmail.com> - 2022-06-28 12:42 +0200
Re: Cortex-Mx MCUs with SWD access locked Stef <me@this.is.invalid> - 2022-06-28 17:06 +0200
csiph-web