Moving Gantry router with 6i25

Glad to hear you are getting it sorted out. Let us know how it all works out.

Rick G

Thanks. This forum is turning out to be very useful.

I'm now having trouble getting hm2_pci to initialize. But I see that 2.5.1 has just been released, and claims to have a fix for 6i25 problems. So I'm going to update to 2.5.1 tomorrow and see if that helps.

Regards,
Tom

Can you start your computer via a power cycle and see if you get the same problem? 2.5.1 may have 6I25 support but that should not have any effect on the troubles you have since the default 6I25 firmware is
actually 5I25 firmware so the card "looks" like a 5I25

Also to check things can you download the 5I25 zipfile from www.mesanet.com and extract the utility rpo from /utils/linux. You will have to chmod the utilty to make it executable:

chmod +x rpo

and the run this command:

./rpo 100

and report the results

Thanks

PCW,

You are right. 2.5.1 didn't help. Also, power cycling doesn't help.

I ran rpo, and the result is 0xFFFFFFFF, the same value LinuxCNC complains about. See this snippet from dmesg:

[ 789.047380] hm2: loading Mesa HostMot2 driver version 0.15
[ 789.062155] hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
[ 789.062547] ACPI: PCI Interrupt Link [LNEA] enabled at IRQ 17
[ 789.062553] alloc irq_desc for 17 on node -1
[ 789.062555] alloc kstat_irqs on node -1
[ 789.062567] hm2_pci 0000:03:00.0: PCI INT A -> Link[LNEA] -> GSI 17 (level, low) -> IRQ 17
[ 789.062581] hm2_pci: discovered 5i25 at 0000:03:00.0
[ 789.062767] hm2/hm2_5i25.0: invalid cookie, got 0xFFFFFFFF, expected 0x55AACAFE
[ 789.062772] hm2/hm2_5i25.0: FPGA failed to initialize, or unexpected firmware?
[ 789.062775] hm2_5i25.0: board fails HM2 registration
[ 789.062787] hm2_pci 0000:03:00.0: PCI INT A disabled
[ 789.062794] hm2_pci: probe of 0000:03:00.0 failed with error -22
[ 789.321233] hm2: unloading

Mesa tech support suggested reloading the flash if 2.5.1 didn't correct the problem. Do you think that's what I should try next?

Thanks,
Tom

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