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.
Code generation scripts prevent this :( And besides, there's no natural location for the forces to reside - I'm forcing configuration registers, not signals coming out of the missing modules. The test input can't be modified.
Except that 1) that would prevent the use of emulators, and I...
I'm using a force to compensate for the fact that I've removed parts of the DUT to speed up testing, and I now need to automate this process. Since not instantiating parts of the DUT is inherently a compile-time decision, the compensation should be too.
So ideally I would like to force signals...
Hi
I understand that it is possible to force a signal at compile time (with NCSIM at least) so that it will have a constant value every simulation without the need for run-time intervention. However, I can't seem to find any documentation for this on Google.
Note I would rather not modify the...
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.