Repository navigation
en Home
This manual describes Toffee 2, migrated from XReactor. Legacy Toffee remains on
master; see the migration guide.
A hardware test supplies inputs, waits for results, and checks them against the specification. Toffee expresses these operations as Python tests and helps organize repeated behavior into reusable components. Choose the section that matches your current task; each section can be read independently.
| Your goal | Start here | What you will learn |
|---|---|---|
| Follow a first exercise | Tutorials | Test an 8-bit accumulator with assertions, drivers, automatic checking, and coverage |
| Complete a project task | How-to guides | Connect a DUT, assemble verification components, run regressions, or migrate a project |
| Look up an interface | Reference | Find APIs, defaults, CLI options, and supported behavior |
| Understand the design | Explanation | Understand simulation progress, resource ownership, and what coverage proves |
Start with installation and your first PASS and FAIL. The first exercises use Python without an RTL simulator. Every lesson identifies its source file, command, and expected result, introducing concepts as the exercise needs them.
- Configure simulation: create a backend and release its resources.
- Drive inputs and capture outputs: reuse interface timing.
- Connect a reference model: advance it at acceptance and compare responses.
- Run regressions: select tests, use multiple workers, and diagnose collection failures.
See runnable examples for complete programs and the feature map for implementation and regression links.
内容由 CI 自动同步;请编辑主仓库文档。 Automatically synced by CI; edit the source documentation.
- 首页
- 教程
- 操作指南
- 参考
- 原理说明
- Home
-
Tutorials
- Learning path
- 0. Prepare your environment
- 1. Your first PASS and FAIL
- 2. Inputs and clocks
- 3. More cases and boundaries
- 4. Extract a Driver
- 5. Delayed output and a Monitor
- 6. Assemble an Agent
- 7. Models and the test environment
- 8. Pipelines, batches, and cancellation
- 9. Understand failures
- 10. Functional coverage
- Optional: out-of-order responses
- Optional: native clocks and project DUTs
-
How-to guides
- Find your task
- Simulation and events
- Verification components
- Coverage and regressions
- Migration and maintenance
- Runnable examples
- Reference
- Explanation