We have a complex design and occasionally forget to initialize a signal. Chisel assigns a random value. But this makes it difficult to trace backwards from the point at which the error is detected, back to the origin. There are warnings about uninitialized signals, but this is not helpful for the reason that there are many signals that we intentionally leave uninitialized because they don't propagate. Only in a tiny few cases, such as for "valid" signals, does an uninitialized signal propagate and cause problems. The ideal would be what verilog does, which is set the value to "x", which allows easily tracing it backwards. Is there any relatively painless way of finding these cases with uninitialized signals that cause problems?
1
There are 1 best solutions below
Related Questions in CHISEL
- Using package.json config object variables under windows
- Package.json not found error when updating using npm-check-updates
- Why do we need to use package.json?
- Pointing package.json to a specific React commit installs react-tools (not react)
- Node.js package.json script code uses local or global libraries?
- What to do to mix coffescript and typescript files in the same nodejs project?
- How to specify browserify extensions in package.json?
- npm: How to just run postinstall?
- How auto package installation of Grunt, Karma, package.json in one process
- Does package.json file require a unique name per site when used in local dev?
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
In Chisel 3, we are currently in the process of adding safety for unconnected signals: https://github.com/ucb-bar/chisel3/issues/413. I'm not sure what the outcome will be, but our goal is to prevent exactly the kind of issues mentioned here.