SOPC Address Overlap error

I guess that the addresses each side of the pipeline bridge have to match - but the 'auto-assign' address doesn't know that.

If you manually assign the base addresses you can group things sanely - and probably avoid the warning about code blocks being separated by more than 28 bits.

I'd also avoid the 'clock crossing bridge' by using the s1 and s2 ports of the internal memory blocks.

This happens, when you connect a component once through a bridge and once around it.

The bridge adds an offset to the address space, so that it's cleanly separated.

So the component is seen by some periphereals at it's real address and once via the bridges offset.

I usually circumvent this by adding a second bridge into the "direct" connection, and giving that the same base address (thus adding the same offset).

You can check this easily via the "Address map" button below the SOPC scheme. It will show you which Avalon master sees which avalon slave at which address space.

The NIOS EDS can not handle multiple addresses for the same Avalon slave interface, so the should match for all masters that need to address one slave.