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.
normally soft macros is coding, it can be implemented in different process easily.
hard macros is implemented in a process, and is optimized for the process. normally it is gds2 file, it is hard to be implemented in another process,
Hi ,
Hard Macro's are usually custom cells / IP which we get from other IP vendors, It is an abstracted view of the IP/Custom cell ,we no need to do design closure with in this hard macro. We just use them like any other standard cell.
hard macro are some module fully implemented and P &R only gdsII and lib will be given by vendor.so that that macro architecture cannot be understand by other customers..
you just import lib and gdsII file in you design..
you just call that component in your netlist and while bounding it will use that component from standard cell library where you imported lib and gdsII file.
hard macros are blocks,for example RAM that are included in a design without knowing actual functionality.So,while performing DFT,these blocks have to be skipped over.
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.
