The RTLery site is open to all qualified RTL design and verification engineers working for fabless companies, design and verification service providers, EDA companies and chipmakers as well as individual freelancers. The preferred way to register would be using a corporate email address where the benefit of using group purchase of credits is available. RTLery site is not targeted for engineering students and should not be used for academic work purposes. Therefore, each registering user would be verified by RTLery site administration and users who cannot be verified as corporate or freelance users would unfortunately have to be rejected.

The benefits you get as a logic designer from using the site are the ability to expand the knowledge and design capabilities using examples of different designs and algorithms widely used in the industry. The code examples provide you with fast and safe implementation of the knowledge in your block. Using the available components allows you to concentrate on your block functionality and architectural requirements, rather than the details of implementing and debugging low level components.

Design teams can use the site as a library of pre-designed and pre-verified design components. the library is maintained and updated with the latest timing and verification requirements and can serve to reduce the variation of implementations across the team as well as preventing the risky "cut-modify-use" practice of code re-use within the design team. The library would have its own coding style so designs can be easily understood among the team members.

The site contain many types of components, please see the menu on the front page or the above components drop-down on the main menu.

The quality of a design component is always only as good as its verification planning and execution. The RTLery components are verified to a very high standard and you get a copy of the verification plan done for the component along with the downloaded information. The overall quality of you design would increase as typically when your block is verified as a whole, the level of details you would find in the verification plan would not be reached.

The RTLery components documentation contains a detailed list of assumptions regarding the external interfaces of the components and their respective logical behaviour and restrictions. This information should be used to check that the surrounding logic does not violate the component assumptions. The functionality you expect the component to perform should be verified in the context of your block environment where you can check that the component does its expected architectural function. It is your responsibility to make sure there is no mismatch between your expectation of the component functionality and its actual functionality in the context of your application!.

The download code is an example and its main purpose is to allow you to modify it for your specific needs.

Credits are used in the site for the actual download of code examples. Each new registered user will be given some credits, so he can try out the site and check for himself the offered code examples.

The typical purchasing process of large organization goes through purchase orders and few levels of management confirmations before it is executed. Therefore, you should interest your team and your managers in buying credits using a “group credit package”. This would allow one person in the team to get the credits and distribute them to the different users. Alternatively, if you can get refunded for the purchase and have your manager approval, you can purchase some credits yourself through the site credit packages page using your Paypal account or credit card.

The available credit packages list is available under the buy credit menu item. Typically there would be a quantity discount for the larger packages and group packages, but you can buy the package most suitable for you. Your minimal package would be of 15 credits.

Team credits are distributed to the team members by transferring a certain amount of credits to each user in the team by the team account owner. This method allows your team the flexibility to use credits by whoever needs them. the team account owner can be a manager, team leader or a purchasing representative and may be an active user of the site or a user registered for the purpose of distributing the credits among the team members.