SOPC Address Funny

That's the unfortunate thing about native addressing and is why I always recommend to people creating new components to stick with dynamic slaves (use byte enables). Masters provide byte addresses and slaves provide word addresses (except for tri-state slaves which use byte addresses as well).

I could see this issue happening if you have two masters connecting to a native slave port. The fabric uses slave side arbitration so when you connect two masters to a slave port conceptually you can think of that as being like a shared bus. If you can attach a screenshot we might have some suggestions you can try.