![]() Here, I’ve started by defining relationships between functional blocks. An example with different functional blocks (Blocks 1 through 4) and 9 schematics (labelled A through I) is shown in the image below. The way I like to visualize hierarchical schematic design is in terms of a block diagram. This creates a complicated relationship of dependencies among multiple schematics. In this design methodology, an output (input) port in Schematic A is linked to an input (output) port in Schematic B. Contrast this with hierarchical schematics. In effect, the only connections the schematics share are power and ground connections. The answer can also depend on how you’ve organized your design.Ī set of flat schematics are defined in such a way as to not have any interdependencies signals are not defined as travelling between Schematic A and Schematic B. In general, as your device becomes more complex and includes a large number of discrete components or uses high pin-count components (e.g., FPGAs), you should consider using hierarchical schematics. hierarchical schematics, for example, is one of those questions without a hard answer. Hierarchical Schematics: Which Should You Use?Īs much as we would like, not all responses to engineering-related questions can be hard answers. If you’re still unsure on what each design methodology is and how it works in your design software, then read onwards. Now that I’ve got some experience organizing designs into different functional blocks and modules, it is much easier for me to see when I need to start with a hierarchical schematic structure. When I started working on one of my first projects, and as my design continued to grow in size and complexity, it quickly became obvious that I would never be able to fit all my components and connections into a single schematic, and it became extremely difficult to track nets around my schematic. In PCB design, organization is critical, and it takes a bit of experience to anticipate when you will need to use flat vs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |