Resource Collisions when installing PCIe DD

Hi Dave, I have the "producer / consumer" test running with my thin Linux device driver ...

You may have an idea on this ... and I assume it is a simple case of understanding how NIOS AVALON MM slave space is reached via

BAR addresses in the Linux device driver.

"The second issue I have relates to setting up the PCIe core Avalon MM -> PCIe address translation .. this is at a table with 2 entries of 4k bytes each.

I am trying to track it down . This Cra register space is accessed via BAR1 and contains the physical address of the system DMA memory address.

For some reason , that BAR1 write is ending up at a different location in IMEM that is just below the Cra space . I have an idea it could be something

to do with the BAR address matching scheme and reference to NIOS address map. The IMEM is at 0x00010000 - 0x0001ffff and the CRA slave is at

0x00020000 - 0x00023fff ... the write to the translation tables at offest 0x00021000 in the CRA space seems to end up at 0x00011000 in the IMEM."

Thanks, Bob