On Saturday 06 May 2017 03:40:55 Nicklas Karlsson wrote: > On Fri, 5 May 2017 21:05:47 -0400 > > Gene Heskett <[email protected]> wrote: > > Greetings folks; > > > > What I see by "strace linuxcnc -l" > > > > rt_sigaction(SIGINT, {0x4ec90, [], SA_RESTORER, 0x76dc8180}, > > {0x65f60, [], SA_RESTORER, 0x76dc8180}, 8) = 0 > > wait4(-1, Note: Using POSIX realtime > > hm2: loading Mesa HostMot2 driver version 0.15 > > Unknown board: HOST???? > > hm2_rpspi: rtapi_app_main: Operation not permitted (-1) > > ./hm2-7i90-stepper.hal:38: waitpid failed /usr/bin/rtapi_app > > hm2_rpspi ./hm2-7i90-stepper.hal:38: /usr/bin/rtapi_app exited > > without becoming ready > > ./hm2-7i90-stepper.hal:38: insmod for hm2_rpspi failed, returned -1 > > I would guess it fail to load the "hm2_rpspi" kernel module. There are > shell commands to load manually and these might be useful. trying to decode that line 38, and do it in halrun, first loadrt hostmot2 which works but loadrt hm2_rpspi fails: halcmd: loadrt hostmot2 Note: Using POSIX realtime hm2: loading Mesa HostMot2 driver version 0.15 halcmd: loadrt hm2_rpspi Unknown board: HOST???? hm2_rpspi: rtapi_app_main: Operation not permitted (-1) <stdin>:2: waitpid failed /usr/bin/rtapi_app hm2_rpspi <stdin>:2: /usr/bin/rtapi_app exited without becoming ready <stdin>:2: insmod for hm2_rpspi failed, returned -1
and changing the order to loadrt hm2_7i90 loadrt hm2_rpspi gets this: halcmd: loadrt hm2_7i90 hm2_7i90: loading HostMot2 Mesa 7i90 driver version 0.3 halcmd: loadrt hm2_rpspi HAL: ERROR: duplicate component name 'hm2_rpspi' rtapi_app: caught signal 11 - dumping core <stdin>:4: waitpid failed /usr/bin/rtapi_app hm2_rpspi <stdin>:4: /usr/bin/rtapi_app exited without becoming ready <stdin>:4: insmod for hm2_rpspi failed, returned -1 And here is something I discovered about an hour back, the hm2-7i90-stepper.hal file had been replaced by the one from examples! Discrepancy discovered by an ls -l in the config directory. So I overwrote it with a May 1st version I had saved out of the non-bootable sd card, but that made zip difference. Turning DEBUG in the ini file up to 0X7fffffff and saving a debug-fail.log, gets this: LINUXCNC - 2.8.0-pre1-2771-gdc2ff49 Machine configuration directory is '/home/pi/linuxcnc/configs/sheldon-lathe' Machine configuration file is '7i90-axis.ini' Starting LinuxCNC... (time=1494085454.747501,pid=12207): Registering server on TCP port 5005. (time=1494085454.748054,pid=12207): running server for TCP port 5005 (connection_socket = 3). iocontrol: machine: 'HM2_rpspi-Stepper' version 'unknown' Found file(REL): ./hm2-7i90-stepper.hal Note: Using POSIX realtime Unknown board: HOST???? hm2_rpspi: rtapi_app_main: Operation not permitted (-1) ./hm2-7i90-stepper.hal:32: waitpid failed /usr/bin/rtapi_app hm2_rpspi ./hm2-7i90-stepper.hal:32: /usr/bin/rtapi_app exited without becoming ready ./hm2-7i90-stepper.hal:32: insmod for hm2_rpspi failed, returned -1 Shutting down and cleaning up LinuxCNC... I have now tried quite a few variations in the (BOARD) definition's spelling, but on May 2nd it worked with [HOSTMOT2] DRIVER=hm2_rpspi BOARD=7i90 CONFIG="num_encoders=4 num_pwmgens=1 num_stepgens=4" in the ini file. Could this be an indicator of a total failure of the 7i90 card? I do have one more that I was saving for installation in the new, total isolation box I'm going to put an rpi and the last 7i90 card in, with noise filters and signal snubbers to prevent the noise from damaging the last 7i90 I have. I'm going to build snubbers in wholesale qty's on some pcb's for that purpose, with the incoming signals hitting those as soon as they enter the box. The point is that this worked flawlessly except for the mouse & keyboard priorities, on May 2nd. Thats usually alleviated by a reboot. I think its putting keyboard and mouse stuff in swap, and the response is then slow, and it misses keyup events. The difference between working well and non-booting was a sudo apt update; sudo apt list --upgradable; sudo apt upgrade. The upgrade did 15 files, including one or more that pretty well replaced everything in the /boot directory. I restored by dd'ing raspi3-linuxcnc-hm2-rpspi-8GB.img to a 32Gb card, then putting the linuxcnc/configs/sheldon-lathe tree in from the card that was in the pi when the upgrade of those 15 files was done. Putting that card in the pi, I had apt install synaptic, then upgraded linuxcnc a friends. This install image is the same image that was put on the card originally, and which I used for the jog-dial development, until the upgrade of those 15 files broke it. I have restored the hosts file, the hostname, and setup the networking exactly as it was. It should Just Work(TM). I could see a board error if it was misspelled, which it currently is exactly the same as it was the morning of May 2nd. I just overwrote it all with the May 2nd versions. Same board and HOST??? error: Unknown board: HOST???? hm2_rpspi: rtapi_app_main: Operation not permitted (-1) I'm half burned out on this. Again. And I'm getting tired of doing almost all of the machete work cutting this trail to making a pi run something. Martinjack must have written the driver, but has since disappeared, so I'm the one swinging a corn knife to open the trail. I need to get some standoffs from mpj. If some rs485 stuff can run a 7i90 so someone doesn't have to write an hm2_upspi.so driver, that $109 up computer, which is a quad core atom, running a little faster than the pi, is sure looking tasty. I have some 485 thingy's on order, but no driver exists. Thanks guys. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
