Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: comp.arch Subject: Re: control co-processor Date: Mon, 05 May 2025 10:02:58 -0400 Organization: A noiseless patient Spider Lines: 11 Message-ID: References: <2025Apr23.194456@mips.complang.tuwien.ac.at> <126700f99b6f97d7483bb5355d68c361@www.novabbs.org> <0b410ad93124778a2b1b3ab8fb6ec62c@www.novabbs.org> <54dcb50f7a378240447d3565f083f0bc@www.novabbs.org> <5j3SP.1331$RXsc.334@fx36.iad> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Mon, 05 May 2025 16:02:59 +0200 (CEST) Injection-Info: dont-email.me; posting-host="bdaa78f04399e06ddae1816e36747ee0"; logging-data="619212"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19zJNLNiZLemndHOKPxha+5nJIisWMnZeg=" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:Z2W8EiFofKKZMZ5CQ/jVx4PpSzM= sha1:UxMeeWT76X4aMBRh7wXqTwEQELs= > Even state-of-the-art CPUs today commonly use scan-chains (via JTAG) > for debuggin. Is there some blog somewhere that explains how scan-chains work (not how they're used, but how they're implemented inside the CPU)? Intuitively they sound very costly to me, because of things like the need to run extra wires all over the place. I'm obviously missing something. Stefan