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

Groups > comp.arch.embedded > #28664

Re: H8S2676 faulty chips

Path csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From Paul Rubin <no.email@nospam.invalid>
Newsgroups comp.arch.embedded
Subject Re: H8S2676 faulty chips
Date Sat, 08 Jun 2019 17:44:31 -0700
Organization A noiseless patient Spider
Lines 8
Message-ID <87pnnnvb80.fsf@nightsong.com> (permalink)
References <bc370e5b-b85c-4a56-adf7-3b4904e03622@googlegroups.com> <qcmbkg$7ar$1@dont-email.me> <3a265bb9-4280-4343-86b5-028f208e1366@googlegroups.com> <qcp81d$bl4$1@news2.open-news-network.org> <qcr54q$2kj$1@gioia.aioe.org> <dsj*Wtfpx@news.chiark.greenend.org.uk> <9767a9be-64b7-48bd-b7bd-86f8ba25e044@googlegroups.com> <csj*5qPpx@news.chiark.greenend.org.uk> <db065587-4c84-4c1e-b3ae-f87b25cd6fb9@googlegroups.com>
Mime-Version 1.0
Content-Type text/plain
Injection-Info reader02.eternal-september.org; posting-host="c94d176a6ea1d57d23efb185ccb2a0e8"; logging-data="13503"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX183KKuED+6CxPur/EKIUDJn"
User-Agent Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Cancel-Lock sha1:ES5pHXPpTJ4+dRsK56tC/GPY7RA= sha1:mbUz9bpL5YMzGTP6tgnci+dAZEA=
Xref csiph.com comp.arch.embedded:28664

Show key headers only | View raw

xyman8@gmail.com writes:
> In a production run of 100 boards here, all boards failed.  We bought
> 6000 of these chips.  I find it hard to believe that Renesas would
> have as many as 6000 failures

Maybe you could contact Renesas and offer to pay them to examine some of
those chips and see if they are legit.

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

Thread

H8S2676 faulty chips xyman8@gmail.com - 2019-05-29 01:23 -0700
  Re: H8S2676 faulty chips Dimiter_Popoff <dp@tgi-sci.com> - 2019-05-29 19:22 +0300
    Re: H8S2676 faulty chips xyman8@gmail.com - 2019-05-30 04:18 -0700
      Re: H8S2676 faulty chips Mike Perkins <spam@spam.com> - 2019-05-30 19:39 +0100
        Re: H8S2676 faulty chips Chris <xxx.syseng.yyy@gfsys.co.uk> - 2019-05-31 13:02 +0100
          Re: H8S2676 faulty chips Theo <theom+news@chiark.greenend.org.uk> - 2019-05-31 17:18 +0100
            Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-07 01:50 -0700
              Re: H8S2676 faulty chips Theo <theom+news@chiark.greenend.org.uk> - 2019-06-07 12:56 +0100
                Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-08 15:50 -0700
                Re: H8S2676 faulty chips Paul Rubin <no.email@nospam.invalid> - 2019-06-08 17:44 -0700
                Re: H8S2676 faulty chips Rick C <gnuarm.deletethisbit@gmail.com> - 2019-06-08 20:43 -0700
                Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-08 22:40 -0700
                Re: H8S2676 faulty chips Paul Rubin <no.email@nospam.invalid> - 2019-06-08 23:03 -0700
                Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-08 23:08 -0700
                Re: H8S2676 faulty chips Rick C <gnuarm.deletethisbit@gmail.com> - 2019-06-09 12:46 -0700
                Re: H8S2676 faulty chips Paul Rubin <no.email@nospam.invalid> - 2019-06-09 12:53 -0700
                Re: H8S2676 faulty chips Rick C <gnuarm.deletethisbit@gmail.com> - 2019-06-09 13:27 -0700
                Re: H8S2676 faulty chips Theo <theom+news@chiark.greenend.org.uk> - 2019-06-11 14:05 +0100
                Re: H8S2676 faulty chips xyman8@gmail.com - 2019-06-12 01:11 -0700
                Re: H8S2676 faulty chips Stef <stef33d@yahooI-N-V-A-L-I-D.com.invalid> - 2019-06-11 11:10 +0200

csiph-web