Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Sat, 12 Sep 2020 18:42:17 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 08D1WPZJ016040; Sat, 12 Sep 2020 21:32:35 -0400 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 08D1WNHG016036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 12 Sep 2020 21:32:23 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 08D1WKAI024202 for ; Sat, 12 Sep 2020 21:32:22 -0400 Received: from w92extsm1.exchange.mit.edu (18.7.74.52) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sat, 12 Sep 2020 21:32:14 -0400 Received: from oc11exhyb1.exchange.mit.edu (18.9.1.60) by w92extsm1.exchange.mit.edu (18.7.74.52) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sat, 12 Sep 2020 21:32:20 -0400 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.170) by oc11exhyb1.exchange.mit.edu (18.9.1.60) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sat, 12 Sep 2020 21:32:20 -0400 Received: from MWHPR19CA0053.namprd19.prod.outlook.com (2603:10b6:300:94::15) by MWHPR01MB2654.prod.exchangelabs.com (2603:10b6:300:f3::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Sun, 13 Sep 2020 01:32:18 +0000 Received: from CO1NAM03FT058.eop-NAM03.prod.protection.outlook.com (2603:10b6:300:94:cafe::57) by MWHPR19CA0053.outlook.office365.com (2603:10b6:300:94::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16 via Frontend Transport; Sun, 13 Sep 2020 01:32:18 +0000 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (40.92.19.35) by CO1NAM03FT058.mail.protection.outlook.com (10.152.81.107) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16 via Frontend Transport; Sun, 13 Sep 2020 01:32:18 +0000 Received: from DM6NAM11FT068.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4d::4d) by DM6NAM11HT041.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4d::135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Sun, 13 Sep 2020 01:32:17 +0000 Received: from BYAPR06MB4359.namprd06.prod.outlook.com (2a01:111:e400:fc4d::41) by DM6NAM11FT068.mail.protection.outlook.com (2a01:111:e400:fc4d::323) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16 via Frontend Transport; Sun, 13 Sep 2020 01:32:17 +0000 Received: from BYAPR06MB4359.namprd06.prod.outlook.com ([fe80::c8f5:2c85:be0f:26f4]) by BYAPR06MB4359.namprd06.prod.outlook.com ([fe80::c8f5:2c85:be0f:26f4%6]) with mapi id 15.20.3370.016; Sun, 13 Sep 2020 01:32:17 +0000 From: Randy Dawson To: Microcontroller discussion list - Public. , "joshybear@gmail.com" Sender: "piclist-bounces@mit.edu" Date: Sat, 12 Sep 2020 18:32:17 -0700 Subject: Re: [EE] Four Layer Routing Strategy Thread-Topic: [EE] Four Layer Routing Strategy Thread-Index: AQHWiSfz8QHMWslfv0C3EofQYsvivKllxtaG Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: acceptlanguage: en-US received-spf: Pass (protection.outlook.com: domain of hotmail.com designates 40.92.19.35 as permitted sender) receiver=protection.outlook.com; client-ip=40.92.19.35; helo=NAM11-DM6-obe.outbound.protection.outlook.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uj1POA54XUEifaKedkYpzKO2Pj6so6ar39tdkfQDXbw=; b=UdVvVaW4sEwnGsd7vUv2fFFPCxpX54Z3D68GGp5WDf6DlQ+EQu9b9masQkoErDP8OL5wDqWQkIiLt54ivu5NKZUTLTT2OJt11pYljv97uTFT66G9cp/wol2RD9ffzm81AuGjSmsxmqE8TshMgp1IwYSMK9gAi3BRSJ9wna4yifLwlb2/v8lPY5zIMJb+xk8lhi2WlqGr9+nyFuEXrJLRoYCCjbgZ8TM2Iu/Mi/tuJGjff2y8BNsT6GjlxlteljfEHBRcniqr08wVkXQakpnMEZrEerhNwR4Ds+KoxcFXN+3SmFKZxRd2++FCDHHABAei6Y4U1gfth+af1qRLwPr7Vg== authentication-results: spf=pass (sender IP is 40.92.19.35) smtp.mailfrom=hotmail.com; mit.edu; dkim=pass (signature was verified) header.d=hotmail.com; mit.edu; dmarc=pass action=none header.from=hotmail.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Josh, Lets simplify things. Use your two inner layers for the ground and power (your 3.3V) The top and bottom are for your signal routes. A strategy to use, would be for one layer, the top, to be horizontal traces= , and the bottom to be the vertical traces. It is called 'Manhattan routing'. Its just like driving in the city, you go as far as you can to your destina= tion (on top), turn the corner (drop a via) to the bottom, to go vertical t= o complete the route your destination. Randy ________________________________ From: piclist-bounces@mit.edu on behalf of Josh K= offman Sent: Saturday, September 12, 2020 10:10 AM To: Microcontroller discussion list - Public. Subject: [EE] Four Layer Routing Strategy Hi all, I'm working on my first 4 layer board. I feel a bit like I failed cramming it all into two layers, but I recognize that having so many vias on every trace would be less than ideal. I'm using top and bottom for signals, then the inner layers for power. The board isn't anything crazy RF, just some regular digital signals. There is some digital audio on the board, so there are a few "medium" frequency traces. I plan on using the top inner layer for ground. I'll do it like I normally do, which is to route the ground traces manually, then do a pour that connects to the ground trace in one place. On the bottom inner layer I'm going to route my 3.3V traces. There will be a lot of free space on that layer. So the question is, what should I do with the free space on the 3.3V layer? I could do either a 3.3V pour or another ground pour. I lean towards another ground pour but I don't want to inadvertently create a weird capacitor. Any suggestions? Since this is my first time I'd like to not have to re-make the board because of this particular error! Thank you! Josh -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. -Douglas Adams -- http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .