On Wednesday 21 December 2016 23:42:56 Gene Heskett wrote: > On Wednesday 21 December 2016 20:29:49 Gene Heskett wrote: > > On Wednesday 21 December 2016 18:32:40 andy pugh wrote: > > > On 21 December 2016 at 23:14, Gene Heskett <[email protected]> > > wrote: > > > > But that is being a cast iron bitch. > > > > > > Simplify. > > > > > > Open a terminal window. > > > > > > halrun > > > loadrt hostmot2 > > > loadrt hm2_rpspi {normal parameters, if any} > > > > > > what do you see? > > > > I just now did that, without any params, so I get the whole config: > > > > pi@raspberrypi:~ $ halcmd loadrt hostmot2 > > Note: Using POSIX realtime > > hm2: loading Mesa HostMot2 driver version 0.15 > > pi@raspberrypi:~ $ halcmd loadrt hm2_rpspi > > Base:hm2_7i90.0hm2/hm2_7i90.0: 72 I/O Pins used: > > hm2/hm2_7i90.0: IO Pin 000 (P1-01): StepGen #0, pin Step > > (Output) hm2/hm2_7i90.0: IO Pin 001 (P1-03): StepGen #0, pin > > Direction (Output) hm2/hm2_7i90.0: IO Pin 002 (P1-05): StepGen > > #1, pin Step (Output) hm2/hm2_7i90.0: IO Pin 003 (P1-07): > > StepGen #1, pin Direction (Output) hm2/hm2_7i90.0: IO Pin 004 > > (P1-09): Encoder #0, pin A (Input) hm2/hm2_7i90.0: IO Pin 005 > > (P1-11): Encoder #2, pin A (Input) hm2/hm2_7i90.0: IO Pin 006 > > (P1-13): Encoder #0, pin B (Input) hm2/hm2_7i90.0: IO Pin 007 > > (P1-15): Encoder #2, pin B (Input) hm2/hm2_7i90.0: IO Pin 008 > > (P1-17): Encoder #0, pin Index (Input) hm2/hm2_7i90.0: IO Pin > > 009 (P1-19): Encoder #2, pin Index (Input) hm2/hm2_7i90.0: IO > > Pin 010 (P1-21): Encoder #1, pin A (Input) hm2/hm2_7i90.0: IO > > Pin 011 (P1-23): Encoder #3, pin A (Input) hm2/hm2_7i90.0: IO > > Pin 012 (P1-25): Encoder #1, pin B (Input) hm2/hm2_7i90.0: IO > > Pin 013 (P1-27): Encoder #3, pin B (Input) hm2/hm2_7i90.0: IO > > Pin 014 (P1-29): Encoder #1, pin Index (Input) hm2/hm2_7i90.0: > > IO Pin 015 (P1-31): Encoder #3, pin Index (Input) hm2/hm2_7i90.0: > > IO Pin 016 (P1-33): StepGen #2, pin Step (Output) hm2/hm2_7i90.0: > > IO Pin 017 (P1-35): StepGen #2, pin Direction (Output) > > hm2/hm2_7i90.0: IO Pin 018 (P1-37): StepGen #3, pin Step > > (Output) hm2/hm2_7i90.0: IO Pin 019 (P1-39): StepGen #3, pin > > Direction (Output) hm2/hm2_7i90.0: IO Pin 020 (P1-41): PWMGen > > #0, pin Out0 (PWM or Up) (Output) hm2/hm2_7i90.0: IO Pin 021 > > (P1-43): PWMGen #0, pin Out1 (Dir or Down) (Output) hm2/hm2_7i90.0: > > IO Pin 022 (P1-45): PWMGen #1, pin Out0 (PWM or Up) (Output) > > hm2/hm2_7i90.0: IO Pin 023 (P1-47): PWMGen #1, pin Out1 (Dir or > > Down) (Output) [...] > > hm2/hm2_7i90.0: IO Pin 071 (P3-47): IOPort > > hm2/hm2_7i90.0: registered > > pi@raspberrypi:~ $ > > > > Followed by, to check param response; > > pi@raspberrypi:~ $ halcmd unloadrt hm2_rpspi > > pi@raspberrypi:~ $ halcmd loadrt hm2_rpspi config="num_pwmgens=1 > > num_encoders=1 num_stepgens=2" Base:hm2_7i90.0hm2/hm2_7i90.0: 72 I/O > > Pins used: > > hm2/hm2_7i90.0: IO Pin 000 (P1-01): StepGen #0, pin Step > > (Output) hm2/hm2_7i90.0: IO Pin 001 (P1-03): StepGen #0, pin > > Direction (Output) hm2/hm2_7i90.0: IO Pin 002 (P1-05): StepGen > > #1, pin Step (Output) hm2/hm2_7i90.0: IO Pin 003 (P1-07): > > StepGen #1, pin Direction (Output) hm2/hm2_7i90.0: IO Pin 004 > > (P1-09): Encoder #0, pin A (Input) hm2/hm2_7i90.0: IO Pin 005 > > (P1-11): IOPort hm2/hm2_7i90.0: IO Pin 006 (P1-13): Encoder #0, > > pin B (Input) hm2/hm2_7i90.0: IO Pin 007 (P1-15): IOPort > > hm2/hm2_7i90.0: IO Pin 008 (P1-17): Encoder #0, pin Index > > (Input) hm2/hm2_7i90.0: IO Pin 009 (P1-19): IOPort > > hm2/hm2_7i90.0: IO Pin 010 (P1-21): IOPort > > hm2/hm2_7i90.0: IO Pin 011 (P1-23): IOPort > > hm2/hm2_7i90.0: IO Pin 012 (P1-25): IOPort > > hm2/hm2_7i90.0: IO Pin 013 (P1-27): IOPort > > hm2/hm2_7i90.0: IO Pin 014 (P1-29): IOPort > > hm2/hm2_7i90.0: IO Pin 015 (P1-31): IOPort > > hm2/hm2_7i90.0: IO Pin 016 (P1-33): IOPort > > hm2/hm2_7i90.0: IO Pin 017 (P1-35): IOPort > > hm2/hm2_7i90.0: IO Pin 018 (P1-37): IOPort > > hm2/hm2_7i90.0: IO Pin 019 (P1-39): IOPort > > hm2/hm2_7i90.0: IO Pin 020 (P1-41): PWMGen #0, pin Out0 (PWM or > > Up) (Output) hm2/hm2_7i90.0: IO Pin 021 (P1-43): PWMGen #0, pin > > Out1 (Dir or Down) (Output) hm2/hm2_7i90.0: IO Pin 022 (P1-45): > > IOPort > > hm2/hm2_7i90.0: IO Pin 023 (P1-47): IOPort > > [...] > > hm2/hm2_7i90.0: IO Pin 071 (P3-47): IOPort > > hm2/hm2_7i90.0: registered > > pi@raspberrypi:~ $ > > > > So that all works, UNTIL I do the same thing in linuxcnc, then it > > bitches about the boards. > > > > So I go pokeing around in some of the other *.ini files, and the > > config string always includes the boards firmware name, like this > > from a 7i43-big.ini > > > > CONFIG="firmware=hm2/7i43-4/SVST4_4.BIT num_encoders=0 > > num_pwmgens=0 num_stepgens=3" > > > > I could add that firmware= if I could determine which bit file I put > > in it. The firmwares default creates the first listing above, but > > all I can do is go down the list since we apparently don't have a > > r-pi version of mesaflash. I did that burn around 90 days ago, from > > a parport on an old dell. > > > > I did just now, move the /lib/firmware/hm2/7i90 directory to the > > r-pi, so I guess I try each of the spi versions until it works I > > guess. > > > > I suspect its not going to work though. If it does, I'll be back. > > > > Cheers, Gene Heskett > > Maybe I could simplify the search, if Peter C. Wallace recognizes the > content on the first list above, and can tell me the name of the BIT > file installed in that 7i90HD that responded with that first pin list > above, with 4 encoders, 4 stepgens, and 2 pwmgens. > > Cheers, Gene Heskett
The frustration continues. I built another sd card and followed Matsche's latest recipe, and when done, I put this line in the hal file to do that loadrt of the hm2_rpspi driver, in place of the all indirect loadrt it had. This is right after the loadrt hostmot2 line. And while it works perfectly in the halrun;halcmd scene, it fails in the hal file in exactly the same manner. loadrt hm2_rpspi config="num_pwmgens=1 num_encoders=1 num_stepgens=2" At this point, I can only come to one conclusion, that while I was broke down waiting of parts, specifically another r-pi 3b, or maybe even before, and update to the 2.8 pre for armhf was done sometime in late November, that broke it. The version I just installed again this evening is: LINUXCNC - 2.8.0-pre1-2771-gdc2ff49 which looks suspiciously like an x86 version number as I sure don't see an armhf indicator anyplace in this that I have looked at. My x86 mill is running the same build LINUXCNC - 2.8.0-pre1-2771-gdc2ff49 So, is this the correct entry's to get the armhf builds from the buildbot? Poking around in the buildbot, I don't see a way to spec that its for armhf, which is why I am asking if the sources.list lines below are indeed correct? deb http://buildbot.linuxcnc.org/ jessie master-sim deb-src http://buildbot.linuxcnc.org/ jessie master-sim 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> ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
