I am using a IXP425 and a custom PCI target device, The device enumeration and configuration all go well in redboot, but sometimes (one in 200 reboots or so) I get a data abort exception that ends up in the GDB stubs when I try to read from the PCI device using PCI Memory Window transactions (reading/writing to/from (0x49000000+offset)). I I get past this stage, the unit will stay up forever happily serving PCI access. Only the reboots are dangerous.
When this happens, I have used gdb to read the pci configuration parameters from the PCI target controller (0xC0000000 ->), and all is as it should be (except that the PCI fatal error flag is raised) . What I wonder is what can cause this behaviour, and how I should handle it. Can this be caused by my PCI device doing an abort, by some MMU/cache setting in the IXP425 or similar? -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
