Giter Site home page Giter Site logo

micro_benchmark's People

Contributors

anaszameer-rs avatar github-actions[bot] avatar hammadshabbir-rs avatar tangxifan avatar usmanali-rs avatar usmankiani-rs avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar

Forkers

usmankiani-rs

micro_benchmark's Issues

Naming convention for counter designs

Is your feature request related to a problem? Please describe.
As we are enriching the counter RTL designs in https://github.com/tangxifan/micro_benchmark/tree/main/simple_registers/counters ,
it is time to establish naming convention for counters.
As such, developers can identify critical technical features from the name of a counter design.

Describe the solution you'd like
A naming convention could be

   counter[down]<size>_[async|sync]_[set|reset|setb|resetb]
  • keyword down represent a counting down counter
  • size is an integer, indicating the number of bits for a counter
  • async and sync represent the feature of reset and set signal
  • set, reset, setb and resetb indicates the existence of reset/set signal as well as polarity.

For instance,

counterdown8_async_resetb

shows a counter with the following features:

  • counting down
  • 8-bit in width
  • Asynchronous active-low reset

Redundant counter designs

Describe the bug
A clear and concise description of what the bug is.

Which part of the project is buggy

  • RTL

After merging #11 , there are some redundant counter designs which can be removed at simple_registers/counters/

To Reproduce
Steps to reproduce the behavior:

  1. Clone repository and checkout commit id: aa7374d

Screenshots
image

dut reference argument in subroutines(async functions other than @cocotb.test)

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy any microbenchmark's benchmark into dv flow of alkaid_efpga
  2. run the test and find the result failing
  3. Cross check the converted testbench in dv/preconfig_cocotb/...

Expected behavior
Bitstreams should not be forced each time we call a subroutine

Screenshots
image
as you can see bitstream is forced and dut is used in reference, it gives object error, since reset_dut does not have dut in its scope
Enviornment (please complete the following information):

  • OS:
  • Ubuntu 18.04
  • Tool:
  • Synopsys IC Compiler
  • Version:

Additional context
Add any other context about the problem here.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.