Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
You can take it as a bridge which connects two different interfaces! Of course, the concept of bridge doesn't just connect two different interfaces, e.g. PCI bridge.
A wrapper is sometimes just to refer to one smaller block used to connect the current inferface to the new interface so that these two different interfaces can be commnunicated now! This ofter happens when you buy a off-the-shelf IP that is not compatible with your current bus! For example, one Wishbone interface and one AHB interface!
When the Wrapper is rather robust/functional/configurable, now it can be conceived of it as a Birdge, more suitble!
For eg, i need to do memBIST, in that case i need to separate the functional logic from the test logic, then i add some muxes around memory, which forms a wrapper
In some cases , you will import an external IP to your system , but the interface will not full satify your reqirements . you have to write some code in order to make the IP work . the code you write is sometimes call " WRAPPER " .
Another very good example for wrapper application is asynhronous synhronous domain mix in a design. Or when we design a GALS besd system we have to think about wrappers.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
