Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.arch.embedded > #31108

Re: Cortex-Mx MCUs with SWD access locked

Show all headers | View raw

On 24/06/2022 22:12, Stef wrote:
> On 2022-06-24 David Brown wrote in comp.arch.embedded:
>>>
>>
>> My experience with ESD damage is that it is often subtle - it leads to
>> long-term reliability issues, rather than outright failures.  So the
> 
> True, only large discharges will have an immediate effect. And you will
> probably have felt the spark.
> 
>> production department at my company is extremely careful about ESD.  Up
> 
> Same here. Conductive floors and no access in certain areas without
> conductive shoes or conductive straps in normal shoes.
> 
>> 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).
> 
> Also very recognizable. ;-)
> We do have ESD matts on most work tables, but wrist straps are seldomly
> worn. Floors on development are not conductive, but not static as well.
> Have never felt a discharge on touching stuff there.
> 
>> 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.
> 
> I think I had such an incident in my home office before I changed the
> floor. With certain footware on the old floor I'd spark all over the
> place in dry conditions. Irritating and not good for the equipment.
> 
>> Mind you, I would still avoid woollen slippers on a nylon carpet!
> 
> Laminate flooring and some plastic shoe soles are also a no-no.
> 

I solve that by never wearing shoes inside.

Technically, I fail the conductivity tests everyone has to take before 
entering the ESD areas, but it's a "too good" failure.  That means I am 
fine to handle boards, but I'm not allowed to play with any high voltage 
testbenches - the conductive path through me to ground is too good!

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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