LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Sponsors
  • Mirrors
  • Logos
  • Contact us
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Cores > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: "R. Ramakrishna" <rayaprolu_rk@y...>
    Date: Sun, 27 Jul 2003 23:59:36 -0700 (PDT)
    Subject: [oc] Top-Down Vs Bottom-Up
    Top

    Hi All,
     
    My question may seem very trivial, but it is pretty tricky in my opinion.  I request to be corrected where ever I go wrong.
     
    Question is:  In Basic Digital design, how do we distinguish Top-Down approach and bottom-up approach?  Will there be any difference in the RTL source files I obtain following these apporaches?  If no, then how do we define them, apart from the text-book definition, which says, "In Top-down approach, the algorithmic level of the problem is first stated, then the problem is modularized, so as to use a divide-and-design approach till a possible lowest level is obtained." and "In Bottom-up approach, the existing lowest level module is used in building a superior task and that is further used in building a more superior task and so on". 
    I could define the two terms at the synthesis level (using DC terminology, of-course) as follows: 
    Top-Down compile would mean I would read-in the whole of my design to the memory, apply my optimization constraints at the top-level only and then compile.  In case of a re-compilation, I would still have the top-module as my reference and apply attributes and constraints to my sub-designs using hierarchical definitions.
    Bottom-Up compile would mean I would read-in one sub-module at a time, with my sub-design-specific constraint files, compile each of them independantly, finally read-in my top-module, then link and compile with top-level constraints. 
    Thanks and Regards,
    R. Ramakrishna


    Do you Yahoo!?
    Yahoo! SiteBuilder - Free, easy-to-use web site design software

    ReferenceAuthor
    Re: [oc] MPU Core vs. Coldfire etc...Kland

    Follow upAuthor
    Re: [oc] Top-Down Vs Bottom-UpRudolf Usselmann
    Re: [oc] Top-Down Vs Bottom-UpShawn Tan

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.