Give one producer different isolation behavior for two receivers, while leaving its same-supply receiver untouched.
Hardware context: A producer feeding receivers on three supplies. Select and resolve isolation per path while preserving shared-supply data.
Give one producer different isolation behavior for two receivers, while leaving its same-supply receiver untouched.
The RTL contains no isolation cells. Your UPF adds them at the selected paths. Read the contract table before editing.
The supplied UPF file already defines the domains and their supplies. Keep that file loaded.
Full specification
| Requirement | Contract |
|---|---|
| Always-on receiver | u_a receives clamp 1 under iso_a, active high. |
| Switchable receiver | u_b receives clamp 0 under iso_b, active high. |
| Same-supply receiver | u_same always receives the raw producer value while powered. |
| Supply filters | Every set_isolation command must name source SRC, its sink set and -diff_supply_only TRUE. |
| Cell budget | Insert exactly the two required isolation paths, with no extra power cells. |
| Cell power and placement | Both cells use AON and request fanout. Keep the provided domains and supply network. |
Simulator note: OpenPA checks requested location metadata. Its simulation rewrites connections in the parent; this task does not prove physical placement.
What the Grader Checks
OpenPA reads your file. A refusal ends the check with OpenPA's message and line. Otherwise every row below must pass.
| Row | Rule |
|---|---|
| Data, isolation and supply sequence | public scenario: Run shows it |
| Additional sequence B | hidden scenario |
| Additional sequence C | hidden scenario |
| Intent equals the reference | the domain of every instance; the primary supply of every domain; supply ports, nets and their connections; isolation cells (clamp, enable, sense, supply); where each isolation cell is placed |
| UPF forms | no a strategy without source SRC; no a strategy without its receiver filter; no a strategy without explicit different-supply selection |
| Power cells | at most 2 |
The Design
The power-unaware RTL your UPF describes (top fan_soc). Open a file to read it.
fan.sv
module producer(input logic d, output wire q); assign q=d; endmodule
module receiver(input logic d, output wire q); assign q=d; endmodule
module fan_soc(input logic d, iso_a, iso_b, output wire a,b,same);
wire link;
producer u_src(.d(d),.q(link));
receiver u_a(.d(link),.q(a));
receiver u_b(.d(link),.q(b));
receiver u_same(.d(link),.q(same));
endmodule
Given UPF Files
Your file may load these with load_upf. The grader uses the same text.
fan.upf
upf_version 4.0
set_design_top fan_soc
create_power_domain PD_TOP -include_scope
create_power_domain PD_SRC -elements {u_src}
create_power_domain PD_B -elements {u_b}
create_power_domain PD_SAME -elements {u_same}
create_supply_port VA -direction in
create_supply_port VT -direction in
create_supply_port VB -direction in
create_supply_port VG -direction in
create_supply_net NA
create_supply_net NT
create_supply_net NB
create_supply_net NG
connect_supply_net NA -ports {VA}
connect_supply_net NT -ports {VT}
connect_supply_net NB -ports {VB}
connect_supply_net NG -ports {VG}
create_supply_set AON -function {power NA} -function {ground NG}
create_supply_set SRC -function {power NT} -function {ground NG}
create_supply_set B -function {power NB} -function {ground NG}
associate_supply_set AON -handle PD_TOP.primary
associate_supply_set SRC -handle PD_SRC.primary
associate_supply_set B -handle PD_B.primary
associate_supply_set SRC -handle PD_SAME.primary
The Public Scenario
Data, isolation and supply sequence. Run checks its output and shows the expected lines and any failure.
tb.sv (public scenario)
`timescale 1ns/1ps
module tb;
import UPF::*;
logic d=0, iso_a=0, iso_b=0; wire a,b,same;
fan_soc dut(.*);
task show(input string s); $display("%s a=%b b=%b same=%b",s,a,b,same); endtask
initial begin
void'(supply_on("VA",1.0)); void'(supply_on("VT",1.0)); void'(supply_on("VB",1.0)); void'(supply_on("VG",0.0));
#5;
d=1; #2; show("live"); iso_b=1; #2; show("second"); iso_a=1; #2; d=0; #2; show("both");
#5; $finish;
end
endmodule
Examples
Example 1
The Starter Report- Input
The starter UPF, read by OpenPA
- OpenPA reports (recorded)
Strategies
Read the report before making the first edit.
Example 2
Before Adding Strategies- Input
The supplied domains and rails, without isolation strategies
- OpenPA reports (recorded)
Strategies
Supply wiring alone does not insert isolation.
Example 3
The Sample Sequence- Input
The reference UPF on the public bench
- The bench prints (recorded)
live a=1 b=1 same=1 second a=1 b=0 same=1 both a=1 b=0 same=0
Data passes while isolation is inactive. The later rows exercise the output contract.
Constraints and Contract
- Submit the complete UPF answer. Keep the provided load_upf command.
- Use the signals and supply sets named in the table. Hidden sequences change data and control timing.
Hints
Hint 1
Trace the driver and each receiver separately. A port name and an instance name have different precedence.
Hint 2
Check active polarity before changing the clamp value. Inspect the static report as well as the output.
Hint 3
Start with the transparent case, then assert isolation before switching off a rail.
What the grader checks: The judge checks power intent and simulated values. Location metadata is checked, but physical placement and port attributes are outside this model.
Run checks the public scenario only and never accepts. Submit runs every row. OpenPA is our open power-aware tool: it reads the UPF, writes a power-aware copy of the RTL, and Icarus runs that copy.
See all 2 problems on this path