High-Level Synthesis of Digital Operators¶
The lecture and the three labs are based on the original course by Yves Mathieu (Télécom Paris).
Four sessions: one lecture and three labs. The thread through all of them is one question: given a function written in C++ and a constraint, which hardware should you build, and how do you know? Each lab adds one kind of hardware interface and one more realistic constraint.
| Session | Content | Interface | Design question |
|---|---|---|---|
| 1 | HLS lecture | — | Why and when HLS; how a tool schedules C++; latency and II; loop pipelining and unrolling; interfaces and data types; Intel HLS in practice; design space exploration |
| 2 | Lab 1: a simple counter | Default call/return handshake | What changes the hardware, and what only changes the test? When is HLS the wrong tool? |
| 3 | Lab 2: an audio filter on the DE1-SoC | Avalon streams + one CPU register | What is the smallest filter that keeps up with 48 kHz audio at 50 MHz? |
| 4 | Lab 3: a DES encryption accelerator | Avalon-MM agent + memory host | How much DES hardware is worth building when the data comes from memory? |
How the labs work¶
- Predict, then measure. Before each run you write down what you expect: II, number of multipliers, number of memories. Then you explain the difference with the reports.
- Correct first. Every lab has a self-checking testbench and a golden reference. A smaller design that gives a wrong answer does not count.
- Choose with numbers. Labs 2 and 3 end with a results table and a justified choice. In Lab 2, compare area with the measured frame budget; in Lab 3, compare area with component throughput. The smallest design that meets the requirement is a better choice than speed that the system cannot use.
Before the first lab¶
- Read the lecture slides on latency, initiation interval and loop pipelining. Lab 2 depends on them.
- The labs run on the school's Linux machines. The Makefiles expect the tools under
/comelec/softs/opt/altera/current.
Tool versions¶
The validated lab environment uses Intel HLS Compiler 21.4.0 Build 53.1, Quartus Prime Standard 21.1.1 Build 850 and Questa 2026.2. Attribute names follow the 21.x reference manual: Intel calls the interfaces agent and host (hls_avalon_agent_register_argument, ihc::mm_host). Use the 21.4 documentation: section and table numbers change between releases. Lab 3 HLS testbench agent calls use a direct component invocation; enqueueing this Avalon-MM agent component is rejected by the installed compiler.
Assessment¶
- Lab 2, STEP6: a one-page design space exploration report with its results table and plot, due [date], submitted on [platform].
- Lab 3: [deliverable and date].