>>>> * But our software returns : 0xFFFFFFFF
> This is reading from your device's memory region.  It looks like the
> device is configured correctly (BAR values are reasonable and memory
> decoding is enabled) and I assume the bridges leading to it are
> configured correctly (if you posted the complete dmesg log we could
> tell for sure).  After that point, Linux is out of the way and it's
> just a question of whether your device responds correctly to the
> memory access.
> Are you sure the device is supposed to return something other than
> 0xFFFFFFFF?

Hi Bjorn,

Yes, the device should return something similar to :
resource file = /sys/bus/pci/devices/0000:02:00.0/resource
base address  = 0xFDFFE000
         0xFDFFE000      0x00000000      0x00000000      0x00000000
         0xFDFFE008      0x00000008      0x00000000      0x00000000
         0xFDFFE010      0x00000010      0x00000001      0x00020000
         0xFDFFE018      0x00000018      0x00000000      0x00000000
         0xFDFFE020      0x00000020      0x00000000      0x00000000
         0xFDFFE028      0x00000028      0x00000000      0x00000000
         0xFDFFE030      0x00000030      0x00000000      0x00000000
         0xFDFFE038      0x00000038      0x00000000      0x00000000
         0xFDFFE040      0x00000040      0x30012009      0x00101449
         0xFDFFE048      0x00000048      0x00000000      0x00000781
         0xFDFFE050      0x00000050      0x00000000      0x00000300
         0xFDFFE058      0x00000058      0xCAFEBABE      0xDEADBEEF

> If it's memory, can you write to it and read the new
> value back?  Can you use a PCIe analyzer and see if the device is
> responding correctly on the bus?
I have tried to write to the FPGA registers but I was always getting 
0xFFFFFFFF
>
> Other than the possible pciehp rescan problem, this just looks like a
> problem with your FPGA.
Can it have a relation with the BIOS?
I attached to you the whole dmesg log.

Cheers,
Ghani