Moving Gantry router with 6i25

andypugh wrote:

Just to save confusion, PCW is Mesa tech support.

Oh - I didn't realize that. I also e-mailed Mesa directly, and got a response from someone with initials PCW. Must be the same person.

Tom

Here's some more information. I tried Mesaflash to try to check the firmware. This is what I got:

tom@CNC-Router:~/Desktop/5i25/configs/hostmot2$ ../../utils/linux/mesaflash g540x2.bit info
Checking file g540x2.bit...OK
File type: BIT file
Design name: TopPCITargetHostMot2.ncd;UserID=0xFFFFFFFF
Part name: 6slx9tqg144
Design date: 2012/05/10
Design time: 13:51:20
Config Length: 340604

tom@CNC-Router:~/Desktop/5i25/configs/hostmot2$ ../../utils/linux/mesaflash g540x2.bit verify
mesa 5i25 not found

Looks like Mesaflash can't find the board. Is it a coincidence that the UserID returned by Mesaflash is the same as the invalid cookie returned to HAL?

Regards,
Tom

Its not related to the user ID, thats just a (unused) field in the bitfile

Can you run a lspci -s N:n.0 -x and post the results?

where N:n.0 is the PCI bus and slot number (of the 6I25 (well it will show up as 5I25)
as listed by lspci with no parameters

This may be a BIOS related issue (not enabling access to cards on the other side of a bridge)
Theres a workaround for a similar BIOS issues in the hostmot2 5I20 code

Here you go:

tom@CNC-Router:~$ lspci -s 03:00.0 -x
03:00.0 DPIO module: Device 2718:5125 (rev ff)
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff


Did I get the right device?

Thanks,
Tom

Looks like the right device (2718:5125) but all the config space being FFs sounds like the BIOS never read beyond the Vendor:SSID
in the config space

If this is not a hardware failure on the 6I25 card (and these symptoms would be hard to have with a hardware failure, that is reading some but not all of the config space) then its probably a BIOs error (not initilaizing devices on the other side of a bridge?)
It could also be a suble thing wrong with the PCI core that get triggered by somthing your motherboard does
this would be the first time I've seen this however.

What motherboard is this?

also can you do a lspci | grep -i XIO2001
and dump the config space of the XIO2001 (PCIE-PCI bridge chip on the 6I25)
if this was not setup properly by the BIOS this could cause these symptoms

I get nothing back when I do lspci | grep -i XIO2001. (The first three characters of XIO2001 are letters, right? Not numbers.) Does that make sense?

My motherboard is an Asus A8N-VM-CSM. I bought it about 2005, so maybe it doesn't implement PCI-E correctly?

Tom

Let me find the vendor and SSID of the XIO2001 and maybe try again tommorow

One possibility is trying to update the BIOS on your MB if this cannot be worked around some other way

Also maybe just swapping the 6I25 with a 5I25 would be the easiest solution on the MB (since it has PCI slots)

I'm always wary of updating the BIOS on a PC. If something goes wrong, the motherboard is toast.

Maybe the best solution is to swap for a 5i25. I got the 6i25 because it would be more "future proof", but that's not worth all this complication.

I'm going to be out of town until Friday. I'll get back to you then about possibly swappng.

Thanks,
Tom