I'm a about-to-be-a-Computer Engineering-graduate working on an AXI4-Lite to APB4 bridge as a personal RTL design and verification project.
I've implemented much of the basic architecture, including independent AW/W/AR buffering, read/write arbitration, an APB dispatch queue, and separate AXI response FIFOs. I'm now working on timeout handling and recovery when an APB peripheral fails to assert PREADY.
This has led me down a rabbit hole of trying to account for every possible behaviour of the upstream AXI manager.
For example, suppose an APB transaction times out. My bridge returns SLVERR and enters a fault-containment state, preventing further APB transactions. However, there may still be AXI requests that the bridge accepted before the timeout.
Two scenarios are giving me particular trouble:
Partially accepted writes: The bridge has accepted AW but not W (or vice versa). If the manager never supplies the missing half, how should the bridge handle this during recovery? It cannot generate BVALID until both handshakes have occurred.
Response backpressure: The bridge generates SLVERR responses for previously accepted transactions, but the manager never asserts BREADY or RREADY. The bridge can hold the responses indefinitely, but with finite buffering, it cannot necessarily finish draining every outstanding request.
I understand that AXI permits arbitrary delays in these handshakes, and that my bridge must remain protocol-compliant regardless. But I'm struggling with where to draw the line between what the hardware must guarantee and what can reasonably be treated as an assumption about the surrounding system.
In an actual industry RTL design, how would engineers approach this?
Is it acceptable to explicitly specify liveness assumptions, such as the manager eventually supplying both halves of an accepted write and eventually accepting outstanding responses?
Would these assumptions normally be documented as integration requirements or formal verification assumptions?
How would you design a timeout-recovery mechanism when complete cleanup might depend on upstream behaviour outside the bridge's control?
At what point does accounting for every possible corner case become unnecessary overengineering?
I'm trying to make this a realistic, defensible design rather than just something that works under ideal conditions.
I WANT TO LEARN TO THINK LIKE AN ENGINEER (I have had no co-op/work experience, so I have had to learn to think for myself in regards to situations like this)