Many more reasons why simulation might not match actual hardware performance. Reddit readers were glad to share with me When I asked, I thought I knew most of the reasons. I think it happens toįor a list of things that might cause your simulation not to match reality. I’ll admit this happened to me recently as well.
Works perfectly in simulation, but fails on the hardware? Then had to trim down the trace before filling up every bit in my computersīut what happens when you cannot simulate the problem? When your design Not knowing where to start, I started with simulation–but
.jpg "post-synthesis simulation modelsim altera")
SPI flash memory, only to have the design fail when reading the last wordįrom the flash. On one recent design, I read the entire 16MB from a ThatĪllows me to be able to turn around quickly and find the bug. The same thing in simulation to see if I can come across the same bug. For this reason, when somethingĭoesn’t work in hardware, I’ll almost always return to simulation and try to do Will contain every wire within the design. The second reason why I like simulation is that a simulation generated trace In the time it takes to get there, you might manage to get an answer via Of course, ultimately, the hardware is always faster–but I can find many syntax errors in my design before Vivado fully starts up and I’ve since become convinced in using simulation for several reasons: simulationĬan be faster than synthesizing a design. I just placed them directly onto the hardware and debugged them there. When I first learned digital design, I never simulated any of my designs:
0 kommentar(er)
