Hello everyone,
I've encountered an interesting problem, and would like to ask how could I resolve it.
I'm trying to get started on a new 6I25 board (default configuration in 5I25 compatibility mode)
(installed using the LinuxCNC 2.8.2 Debian 10 Buster PREEPT-RT ISO)
After going through the pcnconfig and setting up some permissions, linuxcnc fails with the following output:
Code:
LINUXCNC - 2.8.2-11-g6a3d0a434
Machine configuration directory is '/home/test/linuxcnc/configs/gantry_test_setup'
Machine configuration file is 'gantry_test_setup.ini'
Starting LinuxCNC...
Found file(REL): ./gantry_test_setup.hal
Note: Using POSIX non-realtime
hm2: loading Mesa HostMot2 driver version 0.15
hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
hm2_pci: discovered 5i25 at 0000:07:00.0
hm2/hm2_5i25.0: Low Level init 0.15
hm2/hm2_5i25.0: invalid cookie, got 0xFFFFFFFF, expected 0x55AACAFE
hm2/hm2_5i25.0: FPGA failed to initialize, or unexpected firmware?
hm2_5i25.0: board fails HM2 registration
RTAPI_PCI: Unmapped 65536 bytes at 0x7f13a4491000
Driver probe function failed!
hm2_pci: error registering PCI driver
hm2_pci: rtapi_app_main: Operation not permitted (-1)
./gantry_test_setup.hal:9: waitpid failed /usr/bin/rtapi_app hm2_pci
./gantry_test_setup.hal:9: /usr/bin/rtapi_app exited without becoming ready
./gantry_test_setup.hal:9: insmod for hm2_pci failed, returned -1
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
hm2: unloading
Note: Using POSIX non-realtime
LinuxCNC terminated with an error. You can find more information in the log:
/home/test/linuxcnc_debug.txt
and
/home/test/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
I thought I need to update the firmware on the board so i tried doing that with mesaflash:
Code:
sudo mesaflash --device 5i25 --write 5i25_7i78x2.bit
the output of that command is the following:
Code:
Checking file... OK
File type: BIT file
Error: BootSector is invalid
Then tried the same with the fix-boot-block flag:
Code:
sudo mesaflash --device 5i25 --fix-boot-block --write 5i25_7i78x2.bit
And this command just halts and spins the cpu on 100%.(left it alone for an hour a couple times)
This is the output from it:
Code:
Checking file... OK
File type: BIT file
Erasing sector 0 for boot block
Anyone has any idea what could cause getting stuck? Or am I going the wrong direction with mesaflash?
Any Ideas welcome!
Cheers,
Tamas
