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.
That is a very vague question. You can only use ROM/RAM if a suitable application exists. They cannot just replace logic and registers.
DO you have a ram that is being generated with logic? that usually means poor design at the code level. Why not post your problems and the code that causes them?
As an example...supose you have an algorithm that requires 1024 register. You need to access all 1024 registers every clock cycle, in this case they need to be registers. If instead you only need accees to 4 of the registers each clock cycle you coud implement the design as 4 memories that each have 256 of the register values.
A FF or register is equivalent to a 1 bit memory. How you need to access this memory depends on how you design your sequential or combinational state machine as serial or parallel bits.
Since RAM is higher density than an array of FPGA macro-cells of registers, choosing a byte-wide or word-wide state machine might be more economical using RAM/ROM memory than single FF registers.
Finite State Machine "Byte wide" design theory will help you implement parallel register implementations..
I believe it is called "One Hot" method . **broken link removed**
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.
