New Contributor
Super ContributorThis is the "default slave" feature of the interconnect. You're accessing an address location outside of the address map of the master, so by default, it accesses the first slave that is in the legal address range. You can choose a different default slave by enabling a hidden column by right-clicking in the System Contents tab.
What behavior are you expecting by accessing address location 0? If you're using the Avalon response signal, you can receive a response from the interconnect that you are accessing at out-of-range slave.
#iwork4intel
New ContributorHi sstrell,
Thanks for your comment.
This is the "default slave" feature of the interconnect. You're accessing an address location outside of the address map of the master, so by default, it accesses the first slave that is in the legal address range. You can choose a different default slave by enabling a hidden column by right-clicking in the System Contents tab.Great, I got it.
What behavior are you expecting by accessing address location 0? If you're using the Avalon response signal, you can receive a response from the interconnect that you are accessing at out-of-range slave.I expected that nothing will be responded since I accessed the out-of-range address. I didn't check the response signal.
By the way, then I tried to implement a mSGDMA at the address of 0x30000, I tried to access this address but there is nothing changed on the Avalon MM interface of this address. I checked this and I found that Quartus inserted interconnect automatically. It seems like I don't understand much about the behavior of interconnect. I found some information in the Platform Designer document. I will check this.
Thank you.
Best Regards,
Trung
