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: Shawn Tan <shawn.tan@a...>
    Date: Mon, 28 Jul 2003 15:33:14 +0800
    Subject: Re: [oc] Top-Down Vs Bottom-Up
    Top

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1
    
    Hi!!
    > 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
    
    I would say that in my limited experience, you'll have different RTL
    files with top-down and bottom-up approach though technically they
    shouldn't be.. Whether topdown or bottomup, depends greatly on what goes
    on in the head of the system architect.. 
    
    Some people find it easier to think topdown, where they get to grasp the
    bigger picture and then isolate and work on the specific functional
    components.. some people find it easier to work bottomup, where they put
    existing pieces of working subcomponents together to form the big
    thing.. but I work both ways at the same time and I believe that a vast
    majority of people use both approaches at the same time, switching from
    topdown to bottomup and vice-versa depending on what mode the brain is
    on at the time..
    
    > 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.  
    
    Yup, that's the definition of topdown and bottomup compiles..
    
    >  
    > Thanks and Regards,
    > R. Ramakrishna
    > 
    > 
    > ---------------------------------
    > Do you Yahoo!?
    > Yahoo! SiteBuilder - Free, easy-to-use web site design software
    
    
    - -- 
    with metta,
    Shawn Tan.
    =======================================================================
    ICQ UIN: 1802628     keyserver.net: F9BA3B9A     counter.li.org: 297959
    
    The people of Gideon have always believed that life is sacred.  That
    the love of life is the greatest gift ... We are incapable of
    destroying or interfering with the creation of that which we love so
    deeply -- life in every form from fetus to developed being.
    		-- Hodin of Gideon, "The Mark of Gideon", stardate 5423.4
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.1 (GNU/Linux)
    
    iD8DBQE/JNG69KUEj/m6O5oRAqf1AJ4gPEfsxggHwo1YLptOHNYRIGrEpQCgthot
    QV58pT2Sq0kYS+6uj5XzXz0=
    =Y6i8
    -----END PGP SIGNATURE-----
    
    
    

    ReferenceAuthor
    Re: [oc] MPU Core vs. Coldfire etc...Kland
    [oc] Top-Down Vs Bottom-UpR Ramakrishna

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