Resolve overlapping isolation strategies for five ports, including an additive update and an explicit bypass.
Hardware context: A producer feeding receivers on three supplies. Select and resolve isolation per path while preserving shared-supply data.
Resolve overlapping isolation strategies for five ports, including an additive update and an explicit bypass.
The RTL contains no isolation cells. Your UPF adds them at the selected paths. Read the contract table before editing.
The starter names a directly selected port twice. Predict the winner at each port, then repair the strategy selection.
Full specification
| Requirement | Contract |
|---|---|
| Port a | ONE must win and clamp to 1. |
| Ports b and c | PAIR must win and clamp both to 1. Extend PAIR using -update in the same scope. |
| Port z | WIDE must win and clamp to 0. |
| Port spare | PASS must win with -no_isolation, even though DIRECT names the same port. |
| Remaining cell intent | Use iso active high, AON, and parent placement for inserted cells. Keep domains and supplies. |
| No ambiguity | Keep WIDE, ONE, PAIR, PASS and DIRECT. Resolve the equal-precedence collision without relying on command order. |
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 | uses additive refinement of PAIR; uses strategy WIDE; uses strategy ONE; uses strategy PAIR; uses strategy PASS; uses strategy DIRECT |
| Power cells | at most 4 |
| Static report | no forbidden finding |
The Design
The power-unaware RTL your UPF describes (top boundary_soc). Open a file to read it.
island.sv
module island(input logic [4:0] d, output wire a, b, c, z, spare);
assign a=d[0]; assign b=d[1]; assign c=d[2]; assign z=d[3]; assign spare=d[4];
endmodule
module boundary_soc(input logic [4:0] d, input logic iso, iso_n,
output wire a,b,c,z,spare);
island u_tx(.d(d),.a(a),.b(b),.c(c),.z(z),.spare(spare));
endmodule
Given UPF Files
Your file may load these with load_upf. The grader uses the same text.
boundary.upf
upf_version 4.0
set_design_top boundary_soc
create_power_domain PD_TOP -include_scope
create_power_domain PD_TX -elements {u_tx}
create_supply_port VA -direction in
create_supply_port VT -direction in
create_supply_port VG -direction in
create_supply_net NA
create_supply_net NT
create_supply_net NG
connect_supply_net NA -ports {VA}
connect_supply_net NT -ports {VT}
connect_supply_net NG -ports {VG}
create_supply_set AON -function {power NA} -function {ground NG}
create_supply_set TX -function {power NT} -function {ground NG}
associate_supply_set AON -handle PD_TOP.primary
associate_supply_set TX -handle PD_TX.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 [4:0] d=0; logic iso=0, iso_n=1;
wire a,b,c,z,spare;
boundary_soc dut(.*);
task show(input string s); $display("%s a=%b b=%b c=%b z=%b spare=%b",s,a,b,c,z,spare); endtask
initial begin
void'(supply_on("VA",1.0)); void'(supply_on("VT",1.0)); void'(supply_on("VG",0.0));
#5;
d=31; #2; show("live"); iso=1; #2; show("isolated"); d=0; #2; show("changed");
#5; $finish;
end
endmodule
Examples
Example 1
The Starter Report- Input
The starter UPF, read by OpenPA
- OpenPA says (recorded)
Refused: answer.upf:4: port u_tx/a is selected by 2 isolation strategies of equal precedence (ONE at answer.upf:3: -elements names the port, no supply filter; PAIR at answer.upf:4: -elements names the port, no supply filter); it is an error if precedence does not single out one strategy (IEEE 1801-2024 5.7.4, 5.7.10)
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 c=1 z=1 spare=1 isolated a=1 b=1 c=1 z=0 spare=1 changed a=1 b=1 c=1 z=0 spare=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