Forum Discussion
Occasional ContributorAvalon Transaction Responses & Bridges
That was the reason, why we tried the response interface. I also expected the response codes to be propagated back to the master. But when I understand you correct, the Avalon response only works on a single interconnect and is not useable across bridges ist that correct?
Yes, your understanding is correct.
Can you don't use the bridge? Master get the response from slave?
Super ContributorHi Fabian,
what you’re seeing is expected: once “transaction response support” is enabled, the Avalon-MM Pipeline Bridge is no longer fully transparent and may generate an early writeresponsevalid as soon as it accepts a write, rather than waiting for the downstream slave, which breaks strict ordering assumptions. There isn’t a setting to force true pass-through behavior, so if your cmd_ctrl depends on the slave (global_reg) finishing its internal processing before accessing another slave, the correct fix is to enforce completion at the slave side—typically by holding waitrequest high until the write is fully processed, or by adding a status/handshake mechanism—rather than relying on the bridge’s response timing.
