Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

> John you have Linuxcnc working on a BBB using a Mesa ethernet card ?
> 
> If so would you mind if I started a new topic to pick your brain.
> 
> To the OP please accept my apologies for going so far off topic.
> 
> 
> Cheers
> 
> Rob

Hi Rob,

Not quite and given the problems I've had with the Linux I out into a dual boot 
laptop this week (i686 and mesaflash RTAI that predates 7i92) my guess is that 
although I can talk to the 7i92 with the mesaflash on the beagle I doubt it 
will actually run.  That beagle isn't a machinekit OS.  Just normal Stretch for 
developing Lazarus Free Pascal code for CAN bus.  (That's another project and 
story).

The attached very preliminary install instructions for setting up the Pi4 to 
work with the 7i92 I followed to the letter on the Beagle.  And to my amazement 
it worked.  Especially since the Beagle had a pretty strange IP number.  And it 
worked without needing the --addr 192.168.1.121.

Thing is.  The Beagle with the PRU's can do very simple CNC when using 
MachineKit which I understand has even itself split with all the work done on 
the bottom end and nothing on the actual LinuxCNC part so it's apparently a bit 
long on the tooth.

But now with the Pi4  4GB for about $70  compared to a Beagle for about $60 the 
extra capability of the MESA family by far outweighs what you can do with the 
Beagle without adding yet more I/O and being stuck with a crappy slow HDMI 
video interface. 

Now having said that, and this _is_ off topic, with an SPI + I2C based touch 
screen in the 7" to 10" size a Beagle with a cape that does the rest of what my 
ELS does would be a great solution since a lathe has only two axis and needs 
really only quadrature encoder support and for the most part PWM for 0-10V.  
But whether that sits on top of MachineKit instead of Axis and is an ELS with 
some limited G-Code capability is the question.  Is it worth it?  One saves the 
money spent on a 7i92 and frees up all sorts of pins without the HDMI.  In fact 
the pocket beagle at even less money would probably be great.   

So I wouldn't use a Beagle with the 7i92.  A Pi4 4GB + 7i92 is a better and 
cheaper solution since you get more I/O along with the support.  And if you 
haven't yet bought a PMDX or CNC4PC or other $160 BoB then one of the other 
Mesa Ethernet products might be the best choice with the Pi4.

My two cents.  And I really have spent way more than that in time trying to get 
the 7i92 to talk to the Pi.

John


> -Original Message-
> From: Robert Murphy [mailto:robert.mur...@gmx.com]
> Sent: June-11-21 9:06 PM
> To: emc-users@lists.sourceforge.net
> Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> 
> Sorry a bit OT
> 
> 
> 
> On 12/6/21 1:33 pm, John Dammeyer wrote:
> >> From: Peter C. Wallace [mailto:p...@mesanet.com]
> >> On Fri, 11 Jun 2021, John Dammeyer wrote:
> >>
> >>> Date: Fri, 11 Jun 2021 17:05:53 -0700
> >>> From: John Dammeyer 
> >
> >>>> I don't think this is his problem, since his rpi Linuxcnc talks to the 
> >>>> 7i92 just fine. Only mesaflash is having trouble.
> >>>>
> >>>> Have you tried explicitly specifying --addr 192 168.1.121?
> >>>>
> >>>> -- Ralph
> >>>>
> >>> There is no electrical difference.  Just one DB connector and one header 
> >>> for
> >>> the non H variety.  It turns out setting the address as --addr 
> >>> 192.168.1.121
> >>> or if the W5 and W6 are changed to reflect EEROM IP address of default
> >>> 10.10.10.10 then all commands must have --addr 10.10.10.10.
> >>>
> >>> Reading the manual again it appears that --addr is only needed if the 
> >>> default
> >>> 192.168.1.121 is not in use on the 7i92.  That's incorrect with a Pi4.  
> >>> It's
> >>> correct with a PC and a Beaglebone.
> >> Looking at the code, thats pretty strange. The address default is just
> >> "192.168.1.121" Have you tried without the "sudo"? That's not needed
> >> for Ethernet connected cards
> > Makes no difference if the sudo is there or not.
> > First just to show that from a physical perspective the 7i92 is there on 
> > 192.168.1.121
> >
> > pi@linuxcnc:~/mesaflash $ ping 192.168.1.121
> > PING 192.168.1.121 (192.168.1.121) 56(84) bytes of data.
> > 64 bytes from 192.168.1.121: icmp_seq=1 ttl=64 time=0.120 ms
> >
> > But the mesaflash software doesn't know it's supposed to use the default ip.
> > pi@linuxcnc:~/mesaflash $ ./mesaflash  --device 7i92 --readhmid
> > lbp16_access.send_packet: Resource temporarily unavailable
> > Aborted
> > pi@linuxcnc:~/m

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Robert Murphy]

Sorry a bit OT


John you have Linuxcnc working on a BBB using a Mesa ethernet card ?

If so would you mind if I started a new topic to pick your brain.

To the OP please accept my apologies for going so far off topic.


Cheers

Rob

On 12/6/21 1:33 pm, John Dammeyer wrote:

From: Peter C. Wallace [mailto:p...@mesanet.com]
On Fri, 11 Jun 2021, John Dammeyer wrote:


Date: Fri, 11 Jun 2021 17:05:53 -0700
From: John Dammeyer 



I don't think this is his problem, since his rpi Linuxcnc talks to the 7i92 
just fine. Only mesaflash is having trouble.

Have you tried explicitly specifying --addr 192 168.1.121?

-- Ralph


There is no electrical difference.  Just one DB connector and one header for
the non H variety.  It turns out setting the address as --addr 192.168.1.121
or if the W5 and W6 are changed to reflect EEROM IP address of default
10.10.10.10 then all commands must have --addr 10.10.10.10.

Reading the manual again it appears that --addr is only needed if the default
192.168.1.121 is not in use on the 7i92.  That's incorrect with a Pi4.  It's
correct with a PC and a Beaglebone.

Looking at the code, thats pretty strange. The address default is just
"192.168.1.121" Have you tried without the "sudo"? That's not needed
for Ethernet connected cards

Makes no difference if the sudo is there or not.
First just to show that from a physical perspective the 7i92 is there on 
192.168.1.121

pi@linuxcnc:~/mesaflash $ ping 192.168.1.121
PING 192.168.1.121 (192.168.1.121) 56(84) bytes of data.
64 bytes from 192.168.1.121: icmp_seq=1 ttl=64 time=0.120 ms

But the mesaflash software doesn't know it's supposed to use the default ip.
pi@linuxcnc:~/mesaflash $ ./mesaflash  --device 7i92 --readhmid
lbp16_access.send_packet: Resource temporarily unavailable
Aborted
pi@linuxcnc:~/mesaflash $ ./mesaflash  --device 7i92 --addr 192.168.1.121 
--readhmid
Configuration Name: HOSTMOT2

General configuration information:

   BoardName : MESA7I92
   FPGA Size: 9 KGates
   FPGA Pins: 144


BTW.  The upside is that now we have something reproducible.   It may well be 
something outside of mesaflash but the issue doesn't show up with older 
versions of the OS and what really amazed me is it worked on the Beagle.  Has 
me wondering if booted a machinekit onto the beagle would it work?  Probably 
not.  The hm2_eth is probably not compatible with machinekit but just curious.



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

> From: Peter C. Wallace [mailto:p...@mesanet.com]
> On Fri, 11 Jun 2021, John Dammeyer wrote:
> 
> > Date: Fri, 11 Jun 2021 17:05:53 -0700
> > From: John Dammeyer 


> >> I don't think this is his problem, since his rpi Linuxcnc talks to the 
> >> 7i92 just fine. Only mesaflash is having trouble.
> >>
> >> Have you tried explicitly specifying --addr 192 168.1.121?
> >>
> >> -- Ralph
> >>
> >
> > There is no electrical difference.  Just one DB connector and one header for
> > the non H variety.  It turns out setting the address as --addr 192.168.1.121
> > or if the W5 and W6 are changed to reflect EEROM IP address of default
> > 10.10.10.10 then all commands must have --addr 10.10.10.10.
> >
> > Reading the manual again it appears that --addr is only needed if the 
> > default
> > 192.168.1.121 is not in use on the 7i92.  That's incorrect with a Pi4.  It's
> > correct with a PC and a Beaglebone.
> 
> Looking at the code, thats pretty strange. The address default is just
> "192.168.1.121" Have you tried without the "sudo"? That's not needed
> for Ethernet connected cards

Makes no difference if the sudo is there or not. 
First just to show that from a physical perspective the 7i92 is there on 
192.168.1.121 

pi@linuxcnc:~/mesaflash $ ping 192.168.1.121
PING 192.168.1.121 (192.168.1.121) 56(84) bytes of data.
64 bytes from 192.168.1.121: icmp_seq=1 ttl=64 time=0.120 ms

But the mesaflash software doesn't know it's supposed to use the default ip.
pi@linuxcnc:~/mesaflash $ ./mesaflash  --device 7i92 --readhmid
lbp16_access.send_packet: Resource temporarily unavailable
Aborted
pi@linuxcnc:~/mesaflash $ ./mesaflash  --device 7i92 --addr 192.168.1.121 
--readhmid
Configuration Name: HOSTMOT2

General configuration information:

  BoardName : MESA7I92
  FPGA Size: 9 KGates
  FPGA Pins: 144


BTW.  The upside is that now we have something reproducible.   It may well be 
something outside of mesaflash but the issue doesn't show up with older 
versions of the OS and what really amazed me is it worked on the Beagle.  Has 
me wondering if booted a machinekit onto the beagle would it work?  Probably 
not.  The hm2_eth is probably not compatible with machinekit but just curious. 



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Peter C. Wallace]

On Fri, 11 Jun 2021, John Dammeyer wrote:


Date: Fri, 11 Jun 2021 17:05:53 -0700
From: John Dammeyer 
Reply-To: "Enhanced Machine Controller (EMC)"

To: "'Enhanced Machine Controller (EMC)'" 
Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H


From: Ralph Stirling [mailto:ralph.stirl...@wallawalla.edu]
I don't think this is his problem, since his rpi Linuxcnc talks to the 7i92 
just fine. Only mesaflash is having trouble.

Is there any difference between a 7i92 and a 7i92h?  I have a straight 7i92 
with one 2x13 and one db25.
Have you tried explicitly specifying --addr 192 168.1.121?

-- Ralph



There is no electrical difference.  Just one DB connector and one header for 
the non H variety.  It turns out setting the address as --addr 192.168.1.121 
or if the W5 and W6 are changed to reflect EEROM IP address of default 
10.10.10.10 then all commands must have --addr 10.10.10.10.


Reading the manual again it appears that --addr is only needed if the default 
192.168.1.121 is not in use on the 7i92.  That's incorrect with a Pi4.  It's 
correct with a PC and a Beaglebone.


Looking at the code, thats pretty strange. The address default is just 
"192.168.1.121" Have you tried without the "sudo"? That's not needed

for Ethernet connected cards



John




___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users



Peter Wallace
Mesa Electronics

(\__/)
(='.'=) This is Bunny. Copy and paste bunny into your
(")_(") signature to help him gain world domination.



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

Any reason why this laptop couldn't run LinuxCNC with the 7i92?  It has 
hardwired Ethernet.  A 64 bit processor.  Or are laptops not a good idea for 
LinuxCNC?

https://www.bestbuy.ca/en-ca/product/acer-aspire-1-15-6-laptop-silver-intel-icd-n4500-64gb-emmc-4gb-ram-windows-10/15458831

Thanks
John



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Gene Heskett]

On Friday 11 June 2021 19:47:39 Ralph Stirling wrote:

> I don't think this is his problem, since his rpi Linuxcnc talks to the
> 7i92 just fine. Only mesaflash is having trouble.
>
> Is there any difference between a 7i92 and a 7i92h? 

Thats a question for Peter.

> I have a straight 
> 7i92 with one 2x13 and one db25. Have you tried explicitly specifying
> --addr 192 168.1.121?
>
> -- Ralph

Well, the answer I'm looking for can be obtained from one 5 character 
command,

 "ip rENTER"

Its been suggested, but hasn't been posted yet by John. It responds like 
this here, see man ip:

pi@rpi4:/media/pi/workspace $ ip r
default via 192.168.71.1 dev eth0 onlink
192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.13

Is that first 
'default" line in the 192.168.1.1 or in the 192.168.0.1 block? Or is it 
someplace in the 169. that avahi returns.

[...]

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

> From: Ralph Stirling [mailto:ralph.stirl...@wallawalla.edu]
> I don't think this is his problem, since his rpi Linuxcnc talks to the 7i92 
> just fine. Only mesaflash is having trouble.
> 
> Is there any difference between a 7i92 and a 7i92h?  I have a straight 7i92 
> with one 2x13 and one db25.
> Have you tried explicitly specifying --addr 192 168.1.121?
> 
> -- Ralph
> 

There is no electrical difference.  Just one DB connector and one header for 
the non H variety.  It turns out setting the address as --addr 192.168.1.121 or 
if the W5 and W6 are changed to reflect EEROM IP address of default 10.10.10.10 
then all commands must have --addr 10.10.10.10.

Reading the manual again it appears that --addr is only needed if the default 
192.168.1.121 is not in use on the 7i92.   That's incorrect with a Pi4.  It's 
correct with a PC and a Beaglebone.

John




___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

So answer is below.  The issue is in the mesaflash code and how it decides what 
UDP packets to listen to.

> From: Gene Heskett [mailto:ghesk...@shentel.net] 
> On Friday 11 June 2021 15:14:07 John Dammeyer wrote:
> > Gene.
> > No difference with WiFi on or off.  I thought it might have mattered
> > since the Beagle and the PC don't have additional Ethernet. John
> >
> Turning off the radio didn't help on my pi3 or pi4, avahi still pulled a
> default address in the 169 block out of someplace.
> 
> Thats why I said you have to render it non-executable.

The clue was when I changed the jumper on the Beagle connected 7i92H to set 
10.10.10.10 like Peter Wallace suggested.  However I couldn't figure out 
quickly how to change the Beagle IP and since it was a way off number from 
192.168.1.1 anyway and yet still talked it had to be something different.  

Once I set it to 10.10.10.10 mesaflash couldn't find the 7i92H anymore.  I 
could ping that IP but no luck at all with mesaflash.  What worked before with 
the PC and the Beagle was:

debian@ebb:~/mesaflash $ sudo ./mesaflash  --device 7i92 --addr 10.10.10.10
ETH device 7I92 at ip=10.10.10.10

And that worked with the Pi4 too.
pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --addr 192.168.1.121
ETH device 7I92 at ip=192.168.1.121

So although it wasn't needed with the PC nor the Beaglebone when the Beagle was 
set at 192.168.1.121 for some reason when I add --addr 192.168.1.121 to the 
command line for the Pi4 or 10.10.10.10 for the Beagle it now works.  It looks 
like all commands executed on the Pi4 require the --addr while on the Beagle 
only if it's not 192.168.1.121

pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --addr 192.168.1.121 
--readhmid
Configuration Name: HOSTMOT2

General configuration information:

  BoardName : MESA7I92
  FPGA Size: 9 KGates
  . . . stripped because it doesn't need to be in this posting.
12 32   IOPort   QCount   1Quad-IDX 
   (In)
13 33   IOPort   None

pi@linuxcnc:~/mesaflash $


So I should theoretically be able to program the FPGA now but will have to 
include --addr on the command line.  There's still something wrong with 
mesaflash on the Pi4 that is different from a PC running LinuxCNC and a Beagle 
running debian 4.14 Stretch.  The PC LinuxCNC  is 4.9 PREEMPT RT so a bit older 
too.

Perhaps something new happened with 4.19 that mesaflash has issues with and the 
slightly older OS doesn't.

Inside the HAL file for LinuxCNC we set what the IP # is.  That's probably why 
LinuxCNC doesn't have issues with the 7i92H.   But on some systems the --addr 
is needed and not on others depending on the ip number.

Thanks for everyone's contributions.
John





___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[andy pugh]

This is looking like a puzzle for micges.

But it seems that github.com/micge is empty, so perhaps he has retired
from Mesaflash support?

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Ralph Stirling]

I don't think this is his problem, since his rpi Linuxcnc talks to the 7i92 
just fine. Only mesaflash is having trouble.

Is there any difference between a 7i92 and a 7i92h?  I have a straight 7i92 
with one 2x13 and one db25.
Have you tried explicitly specifying --addr 192 168.1.121?

-- Ralph

On Jun 11, 2021 4:05 PM, Gene Heskett  wrote:
CAUTION: This email originated from outside the Walla Walla University email 
system.


On Friday 11 June 2021 15:14:07 John Dammeyer wrote:

> Gene.
> No difference with WiFi on or off.  I thought it might have mattered
> since the Beagle and the PC don't have additional Ethernet. John
>
Turning off the radio didn't help on my pi3 or pi4, avahi still pulled a
default address in the 169 block out of someplace.

Thats why I said you have to render it non-executable.

> > -Original Message-
> > From: Gene Heskett [mailto:ghesk...@shentel.net]
> > Sent: June-11-21 11:02 AM
> > To: emc-users@lists.sourceforge.net
> > Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> >
> > On Friday 11 June 2021 12:05:38 John Dammeyer wrote:
> > > Sam,
> > > Here's the ifconfig output generated from putty running on my
> > > WIN-7 workstation via remote desktop from my WIN-10 ZBook.
> > > Ethernet cable from Pi4 to 7i92 is 2' long.
> > >
> > > And with or without LinuxCNC running this is what I get:
> > > pi@linuxcnc:~ $ cd mesaflash
> > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92
> > > --readhmid lbp16_access.send_packet: Operation not permitted
> > > Aborted
> > >
> > > John
> > >
> > > pi@linuxcnc:~ $ ifconfig
> > > eth0: flags=4163  mtu 1500
> > > inet 192.168.1.1  netmask 255.255.255.0  broadcast
> > > 192.168.1.255 ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
> > > RX packets 29442387  bytes 2826463726 (2.6 GiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 58886151  bytes 1122489823 (1.0 GiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > lo: flags=73  mtu 65536
> > > inet 127.0.0.1  netmask 255.0.0.0
> > > inet6 ::1  prefixlen 128  scopeid 0x10
> > > loop  txqueuelen 1000  (Local Loopback)
> > > RX packets 595  bytes 40144 (39.2 KiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 595  bytes 40144 (39.2 KiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > wlan0: flags=4163  mtu 1500
> > > inet 192.168.0.97  netmask 255.255.255.0  broadcast
> > > 192.168.0.255 inet6 fe80::9d66:1b85:f539:da50  prefixlen 64
> > > scopeid 0x20 ether dc:a6:32:1e:30:f2  txqueuelen 1000
> > > (Ethernet) RX packets 9  bytes 3535970 (3.3 MiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 3108  bytes 415864 (406.1 KiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > I see one possibility, Ralph.
> >
> > This doesn't show the default route. But "ip r" will. You are eth0
> > at 192.168.1.x and wlan0 at 192.168.0.x. If the default route is
> > thru wlan0, mesaflash will probably fail.
> >
> > I'm using a 7i90 over spi, so my eth0 or whatever name its using
> > this week is free for normal use, but that's just one of the reasons
> > I keep the #@%## radios turned off, once avahi gets it in its mind
> > to use the radio, ip can't or won't fix it, so you have to manually
> > nuke the avahi executable and reboot. In your case, rename it to
> > rumplestiltskin or whatever so you can restore it if I'm wrong.
> >
> > Take care and stay well.
> >
> > [...]
> >
> > 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)
> > If we desire respect for the law, we must first make the law
> > respectable. - Louis D. Brandeis
> > Genes Web page 
> > <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgeneslinuxbox.net%3A6309%2Fgenedata=04%7C01%7Cralph.stirling%40wallawalla.edu%7C86f0a42aef3241b3187608d92d2d5660%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C1%7C637590495035239484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=Yrcv7AZJ1dJToFIjBiBIShfTJpkqKyGxtWN7ncjZYeQ%3Dreserved=0>
> >
> >
> > 

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Gene Heskett]

On Friday 11 June 2021 15:14:07 John Dammeyer wrote:

> Gene.
> No difference with WiFi on or off.  I thought it might have mattered
> since the Beagle and the PC don't have additional Ethernet. John
>
Turning off the radio didn't help on my pi3 or pi4, avahi still pulled a 
default address in the 169 block out of someplace.

Thats why I said you have to render it non-executable.

> > -Original Message-
> > From: Gene Heskett [mailto:ghesk...@shentel.net]
> > Sent: June-11-21 11:02 AM
> > To: emc-users@lists.sourceforge.net
> > Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> >
> > On Friday 11 June 2021 12:05:38 John Dammeyer wrote:
> > > Sam,
> > > Here's the ifconfig output generated from putty running on my
> > > WIN-7 workstation via remote desktop from my WIN-10 ZBook. 
> > > Ethernet cable from Pi4 to 7i92 is 2' long.
> > >
> > > And with or without LinuxCNC running this is what I get:
> > > pi@linuxcnc:~ $ cd mesaflash
> > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92
> > > --readhmid lbp16_access.send_packet: Operation not permitted
> > > Aborted
> > >
> > > John
> > >
> > > pi@linuxcnc:~ $ ifconfig
> > > eth0: flags=4163  mtu 1500
> > > inet 192.168.1.1  netmask 255.255.255.0  broadcast
> > > 192.168.1.255 ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
> > > RX packets 29442387  bytes 2826463726 (2.6 GiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 58886151  bytes 1122489823 (1.0 GiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > lo: flags=73  mtu 65536
> > > inet 127.0.0.1  netmask 255.0.0.0
> > > inet6 ::1  prefixlen 128  scopeid 0x10
> > > loop  txqueuelen 1000  (Local Loopback)
> > > RX packets 595  bytes 40144 (39.2 KiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 595  bytes 40144 (39.2 KiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > wlan0: flags=4163  mtu 1500
> > > inet 192.168.0.97  netmask 255.255.255.0  broadcast
> > > 192.168.0.255 inet6 fe80::9d66:1b85:f539:da50  prefixlen 64 
> > > scopeid 0x20 ether dc:a6:32:1e:30:f2  txqueuelen 1000 
> > > (Ethernet) RX packets 9  bytes 3535970 (3.3 MiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 3108  bytes 415864 (406.1 KiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > I see one possibility, Ralph.
> >
> > This doesn't show the default route. But "ip r" will. You are eth0
> > at 192.168.1.x and wlan0 at 192.168.0.x. If the default route is
> > thru wlan0, mesaflash will probably fail.
> >
> > I'm using a 7i90 over spi, so my eth0 or whatever name its using
> > this week is free for normal use, but that's just one of the reasons
> > I keep the #@%## radios turned off, once avahi gets it in its mind
> > to use the radio, ip can't or won't fix it, so you have to manually
> > nuke the avahi executable and reboot. In your case, rename it to
> > rumplestiltskin or whatever so you can restore it if I'm wrong.
> >
> > Take care and stay well.
> >
> > [...]
> >
> > 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)
> > If we desire respect for the law, we must first make the law
> > respectable. - Louis D. Brandeis
> > Genes Web page <http://geneslinuxbox.net:6309/gene>
> >
> >
> > ___
> > Emc-users mailing list
> > Emc-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-users
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Peter C. Wallace]

On Fri, 11 Jun 2021, John Dammeyer wrote:


Date: Fri, 11 Jun 2021 13:44:51 -0700
From: John Dammeyer 
Reply-To: "Enhanced Machine Controller (EMC)"

To: "'Enhanced Machine Controller (EMC)'" 
Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H

Try to set the jumpers for 192.168.1.121 and your pi4 at 192.168.1.1 or .10...

Something in the mesaflash is having issues that LinuxCNC isn't.  At this 
point no idea what it is and whether WiFi is on or off doesn't seem to matter.


John



LinuxCNC does some network modifications that mesaflash does not
so this still suggests  some kind of network setup issue on your RPI

Did you try setting the host address to 10.10.10.100 and the 7I92 to 10.10.10.10
This is less likely to have routing issues (and is suggested in general to 
avoid overlaps with common NAT ranges)










-Original Message-
From: Peter C. Wallace [mailto:p...@mesanet.com]
Sent: June-11-21 11:04 AM
To: Enhanced Machine Controller (EMC)
Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H


I dont see this issue (though if have my 7I92 at 10.10.10.10 and the RPI at
10.10.10.100)

pi@raspberrypi:/boot $ uname -a
Linux raspberrypi 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT Thu Jan 23 16:59:28 PST 
2020 armv7l GNU/Linux
pi@raspberrypi:/boot $ mesaflash --device 7i92 --addr 10.10.10.10 --readhmid
Configuration Name: HOSTMOT2

General configuration information:

   BoardName : MESA7I92
   FPGA Size: 9 KGates
   FPGA Pins: 144
   Number of IO Ports: 2
   Width of one I/O port: 17
   Clock Low frequency: 100. MHz
   Clock High frequency: 200. MHz
   IDROM Type: 3
   Instance Stride 0: 4
   Instance Stride 1: 64
   Register Stride 0: 256
   Register Stride 1: 256

Modules in configuration:

   Module: DPLL
   There are 1 of DPLL in configuration
   Version: 0
   Registers: 7
   BaseAddress: 7000
   ClockFrequency: 100.000 MHz
   Register Stride: 256 bytes
   Instance Stride: 4 bytes

   Module: WatchDog
   There are 1 of WatchDog in configuration
   Version: 0
   Registers: 3
   BaseAddress: 0C00
   ClockFrequency: 100.000 MHz
   Register Stride: 256 bytes
   Instance Stride: 4 bytes

   Module: IOPort
   There are 2 of IOPort in configuration
   Version: 0
   Registers: 5
   BaseAddress: 1000
   ClockFrequency: 100.000 MHz
   Register Stride: 256 bytes
   Instance Stride: 4 bytes

   Module: QCount
   There are 1 of QCount in configuration
   Version: 2
   Registers: 5
   BaseAddress: 3000
   ClockFrequency: 100.000 MHz
   Register Stride: 256 bytes
   Instance Stride: 4 bytes

   Module: SSerial
   There are 1 of SSerial in configuration
   Version: 0
   Registers: 6
   BaseAddress: 5B00
   ClockFrequency: 100.000 MHz
   Register Stride: 256 bytes
   Instance Stride: 64 bytes

   Module: StepGen
   There are 5 of StepGen in configuration
   Version: 2
   Registers: 10
   BaseAddress: 2000
   ClockFrequency: 100.000 MHz
   Register Stride: 256 bytes
   Instance Stride: 4 bytes

   Module: LED
   There are 1 of LED in configuration
   Version: 0
   Registers: 1
   BaseAddress: 0200
   ClockFrequency: 100.000 MHz
   Register Stride: 256 bytes
   Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P2
Pin#  I/O   Pri. funcSec. func   Chan  Pin funcPin Dir

  1  0   IOPort   StepGen  0Dir/Table2  (Out)
14  1   IOPort   StepGen  0Step/Table1 (Out)
  2  2   IOPort   StepGen  1Dir/Table2  (Out)
15  3   IOPort   StepGen  1Step/Table1 (Out)
  3  4   IOPort   StepGen  2Dir/Table2  (Out)
16  5   IOPort   StepGen  2Step/Table1 (Out)
  4  6   IOPort   StepGen  3Dir/Table2  (Out)
17  7   IOPort   StepGen  3Step/Table1 (Out)
  5  8   IOPort   StepGen  4Dir/Table2  (Out)
  6  9   IOPort   StepGen  4Step/Table1 (Out)
  7 10   IOPort   SSerial  0TXData0 (Out)
  8 11   IOPort   SSerial  0RXData0 (In)
  9 12   IOPort   SSerial  0TXData1 (Out)
10 13   IOPort   SSerial  0RXData1 (In)
11 14   IOPort   QCount   0Quad-IDX(In)
12 15   IOPort   QCount   0Quad-B  (In)
13 16   IOPort   QCount   0Quad-A  (In)

IO Connections for P1
Pin#  I/O   Pri. funcSec. func   Chan  Pin funcPin Dir

  1 17   IOPort   None
14 18   IOPort   None
  2 19   IOPort   None
15 20   IOPort   None
  3 21   IOPort   None
16 22   IOPort   None
  4 23   IOPort   None
17 24   IOPort   None
  5 25   IOPort   None
  6 26   IOPort   None
  7 27   IOPort   None
  8 28   IOPort   None

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

Try to set the jumpers for 192.168.1.121 and your pi4 at 192.168.1.1 or .10...

Something in the mesaflash is having issues that LinuxCNC isn't.  At this point 
no idea what it is and whether WiFi is on or off doesn't seem to matter.

John




> -Original Message-
> From: Peter C. Wallace [mailto:p...@mesanet.com]
> Sent: June-11-21 11:04 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> 
> 
> I dont see this issue (though if have my 7I92 at 10.10.10.10 and the RPI at
> 10.10.10.100)
> 
> pi@raspberrypi:/boot $ uname -a
> Linux raspberrypi 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT Thu Jan 23 16:59:28 PST 
> 2020 armv7l GNU/Linux
> pi@raspberrypi:/boot $ mesaflash --device 7i92 --addr 10.10.10.10 --readhmid
> Configuration Name: HOSTMOT2
> 
> General configuration information:
> 
>BoardName : MESA7I92
>FPGA Size: 9 KGates
>FPGA Pins: 144
>Number of IO Ports: 2
>Width of one I/O port: 17
>Clock Low frequency: 100. MHz
>Clock High frequency: 200. MHz
>IDROM Type: 3
>Instance Stride 0: 4
>Instance Stride 1: 64
>Register Stride 0: 256
>Register Stride 1: 256
> 
> Modules in configuration:
> 
>Module: DPLL
>There are 1 of DPLL in configuration
>Version: 0
>Registers: 7
>BaseAddress: 7000
>ClockFrequency: 100.000 MHz
>Register Stride: 256 bytes
>Instance Stride: 4 bytes
> 
>Module: WatchDog
>There are 1 of WatchDog in configuration
>Version: 0
>Registers: 3
>BaseAddress: 0C00
>ClockFrequency: 100.000 MHz
>Register Stride: 256 bytes
>Instance Stride: 4 bytes
> 
>Module: IOPort
>There are 2 of IOPort in configuration
>Version: 0
>Registers: 5
>BaseAddress: 1000
>ClockFrequency: 100.000 MHz
>Register Stride: 256 bytes
>Instance Stride: 4 bytes
> 
>Module: QCount
>There are 1 of QCount in configuration
>Version: 2
>Registers: 5
>BaseAddress: 3000
>ClockFrequency: 100.000 MHz
>Register Stride: 256 bytes
>Instance Stride: 4 bytes
> 
>Module: SSerial
>There are 1 of SSerial in configuration
>Version: 0
>Registers: 6
>BaseAddress: 5B00
>ClockFrequency: 100.000 MHz
>Register Stride: 256 bytes
>Instance Stride: 64 bytes
> 
>Module: StepGen
>There are 5 of StepGen in configuration
>Version: 2
>Registers: 10
>BaseAddress: 2000
>ClockFrequency: 100.000 MHz
>Register Stride: 256 bytes
>Instance Stride: 4 bytes
> 
>Module: LED
>There are 1 of LED in configuration
>Version: 0
>Registers: 1
>BaseAddress: 0200
>ClockFrequency: 100.000 MHz
>Register Stride: 256 bytes
>Instance Stride: 4 bytes
> 
> Configuration pin-out:
> 
> IO Connections for P2
> Pin#  I/O   Pri. funcSec. func   Chan  Pin funcPin Dir
> 
>   1  0   IOPort   StepGen  0Dir/Table2  (Out)
> 14  1   IOPort   StepGen  0Step/Table1 (Out)
>   2  2   IOPort   StepGen  1Dir/Table2  (Out)
> 15  3   IOPort   StepGen  1Step/Table1 (Out)
>   3  4   IOPort   StepGen  2Dir/Table2  (Out)
> 16  5   IOPort   StepGen  2Step/Table1 (Out)
>   4  6   IOPort   StepGen  3Dir/Table2  (Out)
> 17  7   IOPort   StepGen  3Step/Table1 (Out)
>   5  8   IOPort   StepGen  4Dir/Table2  (Out)
>   6  9   IOPort   StepGen  4Step/Table1 (Out)
>   7 10   IOPort   SSerial  0TXData0 (Out)
>   8 11   IOPort   SSerial  0RXData0 (In)
>   9 12   IOPort   SSerial  0TXData1 (Out)
> 10 13   IOPort   SSerial  0RXData1 (In)
> 11 14   IOPort   QCount   0Quad-IDX(In)
> 12 15   IOPort   QCount   0Quad-B  (In)
> 13 16   IOPort   QCount   0Quad-A  (In)
> 
> IO Connections for P1
> Pin#  I/O   Pri. funcSec. func   Chan  Pin funcPin Dir
> 
>   1 17   IOPort   None
> 14 18   IOPort   None
>   2 19   IOPort   None
> 15 20   IOPort   None
>   3 21   IOPort   None
> 16 22   IOPort   None
>   4 23   IOPort   None
> 17 24   IOPort   None
>   5 25   IOPort   None
>   6 26   IOPort   None
>   

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

Gene.
No difference with WiFi on or off.  I thought it might have mattered since the 
Beagle and the PC don't have additional Ethernet.
John


> -Original Message-
> From: Gene Heskett [mailto:ghesk...@shentel.net]
> Sent: June-11-21 11:02 AM
> To: emc-users@lists.sourceforge.net
> Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> 
> On Friday 11 June 2021 12:05:38 John Dammeyer wrote:
> 
> > Sam,
> > Here's the ifconfig output generated from putty running on my WIN-7
> > workstation via remote desktop from my WIN-10 ZBook.  Ethernet cable
> > from Pi4 to 7i92 is 2' long.
> >
> > And with or without LinuxCNC running this is what I get:
> > pi@linuxcnc:~ $ cd mesaflash
> > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > lbp16_access.send_packet: Operation not permitted
> > Aborted
> >
> > John
> >
> > pi@linuxcnc:~ $ ifconfig
> > eth0: flags=4163  mtu 1500
> > inet 192.168.1.1  netmask 255.255.255.0  broadcast
> > 192.168.1.255 ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
> > RX packets 29442387  bytes 2826463726 (2.6 GiB)
> > RX errors 0  dropped 0  overruns 0  frame 0
> > TX packets 58886151  bytes 1122489823 (1.0 GiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > lo: flags=73  mtu 65536
> > inet 127.0.0.1  netmask 255.0.0.0
> > inet6 ::1  prefixlen 128  scopeid 0x10
> > loop  txqueuelen 1000  (Local Loopback)
> > RX packets 595  bytes 40144 (39.2 KiB)
> > RX errors 0  dropped 0  overruns 0  frame 0
> > TX packets 595  bytes 40144 (39.2 KiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > wlan0: flags=4163  mtu 1500
> > inet 192.168.0.97  netmask 255.255.255.0  broadcast
> > 192.168.0.255 inet6 fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid
> > 0x20 ether dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)
> > RX packets 9  bytes 3535970 (3.3 MiB)
> > RX errors 0  dropped 0  overruns 0  frame 0
> > TX packets 3108  bytes 415864 (406.1 KiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> I see one possibility, Ralph.
> 
> This doesn't show the default route. But "ip r" will. You are eth0 at
> 192.168.1.x and wlan0 at 192.168.0.x. If the default route is thru
> wlan0, mesaflash will probably fail.
> 
> I'm using a 7i90 over spi, so my eth0 or whatever name its using this
> week is free for normal use, but that's just one of the reasons I keep
> the #@%## radios turned off, once avahi gets it in its mind to use the
> radio, ip can't or won't fix it, so you have to manually nuke the avahi
> executable and reboot. In your case, rename it to rumplestiltskin or
> whatever so you can restore it if I'm wrong.
> 
> Take care and stay well.
> 
> [...]
> 
> 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)
> If we desire respect for the law, we must first make the law respectable.
>  - Louis D. Brandeis
> Genes Web page <http://geneslinuxbox.net:6309/gene>
> 
> 
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[johnd]

When I get back from doggy walk I'll try switching off wifi.   Odd that 
LinuxCNC works though. Sent from my Samsung S10
 Original message From: Gene Heskett  
Date: 2021-06-11  11:04 a.m.  (GMT-08:00) To: emc-users@lists.sourceforge.net 
Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H On Friday 11 June 2021 
12:05:38 John Dammeyer wrote:> Sam,> Here's the ifconfig output generated from 
putty running on my WIN-7> workstation via remote desktop from my WIN-10 ZBook. 
 Ethernet cable> from Pi4 to 7i92 is 2' long.>> And with or without LinuxCNC 
running this is what I get:> pi@linuxcnc:~ $ cd mesaflash> 
pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid> 
lbp16_access.send_packet: Operation not permitted> Aborted>> John>> 
pi@linuxcnc:~ $ ifconfig> eth0: flags=4163  mtu 
1500> inet 192.168.1.1  netmask 255.255.255.0  broadcast> 192.168.1.255 
ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)> RX packets 
29442387  bytes 2826463726 (2.6 GiB)> RX errors 0  dropped 0  overruns 
0  frame 0> TX packets 58886151  bytes 1122489823 (1.0 GiB)> TX 
errors 0  dropped 0 overruns 0  carrier 0  collisions 0>> lo: 
flags=73  mtu 65536> inet 127.0.0.1  netmask 
255.0.0.0> inet6 ::1  prefixlen 128  scopeid 0x10> loop  
txqueuelen 1000  (Local Loopback)> RX packets 595  bytes 40144 (39.2 
KiB)> RX errors 0  dropped 0  overruns 0  frame 0> TX packets 
595  bytes 40144 (39.2 KiB)> TX errors 0  dropped 0 overruns 0  carrier 
0  collisions 0>> wlan0: flags=4163  mtu 1500>  
   inet 192.168.0.97  netmask 255.255.255.0  broadcast> 192.168.0.255 inet6 
fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid> 0x20 ether 
dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)> RX packets 9  bytes 
3535970 (3.3 MiB)> RX errors 0  dropped 0  overruns 0  frame 0> 
TX packets 3108  bytes 415864 (406.1 KiB)> TX errors 0  dropped 0 
overruns 0  carrier 0  collisions 0I see one possibility, Ralph.This doesn't 
show the default route. But "ip r" will. You are eth0 at 192.168.1.x and wlan0 
at 192.168.0.x. If the default route is thru wlan0, mesaflash will probably 
fail.I'm using a 7i90 over spi, so my eth0 or whatever name its using this week 
is free for normal use, but that's just one of the reasons I keep the #@%## 
radios turned off, once avahi gets it in its mind to use the radio, ip can't or 
won't fix it, so you have to manually nuke the avahi executable and reboot. In 
your case, rename it to rumplestiltskin or whatever so you can restore it if 
I'm wrong.Take care and stay well.[...]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)If we desire respect for the law, we 
must first make the law respectable. - Louis D. BrandeisGenes Web page 
<http://geneslinuxbox.net:6309/gene>___Emc-users
 mailing 
listEmc-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-users
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[johnd]

Latest github version. Sent from my Samsung S10
 Original message From: Ralph Stirling 
 Date: 2021-06-11  11:04 a.m.  (GMT-08:00) To: 
"Enhanced Machine Controller (EMC)"  Subject: 
Re: [Emc-users] Pi4 issues with MESA 7i92H Old version of mesaflash perhaps?On 
Jun 11, 2021 10:06 AM, John Dammeyer  wrote:CAUTION: 
This email originated from outside the Walla Walla University email system.> 
From: Ralph Stirling [mailto:ralph.stirl...@wallawalla.edu]>> I have no problem 
using 192.168.1.1 for eth0 on pi4 with 7i92.I don't either with LinuxCNC moving 
motors.  But it's the mesaflash software that is having an issue.  But only on 
a Pi.  I've downloaded the software from github on a PC, Beagle and Pi4.  Only 
on the Pi4 does it have issues.Now I can use the PC or the Beagle to flash the 
appropriate pin file into the Pi4 but that's not really the point here.  Very 
puzzled.John>> On Jun 11, 2021 9:30 AM, Sam Sokolik  
wrote:> CAUTION: This email originated from outside the Walla Walla University 
email system.>>> That would be something to try..  Maybe mesaflash doesn't know 
how to> handle the 192.168.1.1 ip address?  Set the pie to something else like> 
192.168.1.10>> On Fri, Jun 11, 2021 at 11:25 AM Mark Wendt 
 wrote:>> > On Fri, Jun 11, 2021 at 12:09 PM John 
Dammeyer > > wrote:> >> > > Sam,> > > Here's the 
ifconfig output generated from putty running on my WIN-7> > > workstation via 
remote desktop from my WIN-10 ZBook.  Ethernet cable from> > > Pi4 to 7i92 is 
2' long.> > >> > > And with or without LinuxCNC running this is what I get:> > 
> pi@linuxcnc:~ $ cd mesaflash> > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash 
--device 7i92 --readhmid> > > lbp16_access.send_packet: Operation not 
permitted> > > Aborted> > >> > > John> > >> > > pi@linuxcnc:~ $ ifconfig> > > 
eth0: flags=4163  mtu 1500> > > inet 
192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255> > > ether 
dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)> > > RX packets 29442387 
 bytes 2826463726 (2.6 GiB)> > > RX errors 0  dropped 0  overruns 0  
frame 0> > > TX packets 58886151  bytes 1122489823 (1.0 GiB)> > >   
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0> > >> > > lo: 
flags=73  mtu 65536> > > inet 127.0.0.1  netmask 
255.0.0.0> > > inet6 ::1  prefixlen 128  scopeid 0x10> > >
 loop  txqueuelen 1000  (Local Loopback)> > > RX packets 595  bytes 
40144 (39.2 KiB)> > > RX errors 0  dropped 0  overruns 0  frame 0> > >  
   TX packets 595  bytes 40144 (39.2 KiB)> > > TX errors 0  dropped 
0 overruns 0  carrier 0  collisions 0> > >> > > wlan0: 
flags=4163  mtu 1500> > > inet 
192.168.0.97  netmask 255.255.255.0  broadcast 192.168.0.255> > > inet6 
fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid 0x20> > > ether 
dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)> > > RX packets 9  
bytes 3535970 (3.3 MiB)> > > RX errors 0  dropped 0  overruns 0  frame 
0> > > TX packets 3108  bytes 415864 (406.1 KiB)> > > TX errors 
0  dropped 0 overruns 0  carrier 0  collisions 0> > >> > > pi@linuxcnc:~ $> > 
>> >> > Do you have any other network devices on the 192.168.1.x network?  The> 
> 192.168.1.1 address is usually reserved for routers in that subnet.> >> > 
Mark> >> > ___> > Emc-users mailing 
list> > Emc-users@lists.sourceforge.net> > 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc->
 
usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7Cc116f028f6ee43e610df08d92cf63ad6%7Cd958f048e43142779c8>
 
debfb75e7aa64%7C0%7C0%7C637590258342182689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC>
 
JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=N5XTffg5bbWkolc%2FRmAIrAAMc6JWGk6iNLmN0Nz18%2BU%3Dres>
 erved=0> >>> ___> Emc-users 
mailing list> Emc-users@lists.sourceforge.net> 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc->
 
usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7Cc116f028f6ee43e610df08d92cf63ad6%7Cd958f048e43142779c8>
 
debfb75e7aa64%7C0%7C0%7C637590258342182689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC>
 
JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=N5XT

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Peter C. Wallace]

I dont see this issue (though if have my 7I92 at 10.10.10.10 and the RPI at 
10.10.10.100)


pi@raspberrypi:/boot $ uname -a
Linux raspberrypi 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT Thu Jan 23 16:59:28 PST 
2020 armv7l GNU/Linux
pi@raspberrypi:/boot $ mesaflash --device 7i92 --addr 10.10.10.10 --readhmid
Configuration Name: HOSTMOT2

General configuration information:

  BoardName : MESA7I92
  FPGA Size: 9 KGates
  FPGA Pins: 144
  Number of IO Ports: 2
  Width of one I/O port: 17
  Clock Low frequency: 100. MHz
  Clock High frequency: 200. MHz
  IDROM Type: 3
  Instance Stride 0: 4
  Instance Stride 1: 64
  Register Stride 0: 256
  Register Stride 1: 256

Modules in configuration:

  Module: DPLL
  There are 1 of DPLL in configuration
  Version: 0
  Registers: 7
  BaseAddress: 7000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: WatchDog
  There are 1 of WatchDog in configuration
  Version: 0
  Registers: 3
  BaseAddress: 0C00
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: IOPort
  There are 2 of IOPort in configuration
  Version: 0
  Registers: 5
  BaseAddress: 1000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: QCount
  There are 1 of QCount in configuration
  Version: 2
  Registers: 5
  BaseAddress: 3000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: SSerial
  There are 1 of SSerial in configuration
  Version: 0
  Registers: 6
  BaseAddress: 5B00
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 64 bytes

  Module: StepGen
  There are 5 of StepGen in configuration
  Version: 2
  Registers: 10
  BaseAddress: 2000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: LED
  There are 1 of LED in configuration
  Version: 0
  Registers: 1
  BaseAddress: 0200
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P2
Pin#  I/O   Pri. funcSec. func   Chan  Pin funcPin Dir

 1  0   IOPort   StepGen  0Dir/Table2  (Out)
14  1   IOPort   StepGen  0Step/Table1 (Out)
 2  2   IOPort   StepGen  1Dir/Table2  (Out)
15  3   IOPort   StepGen  1Step/Table1 (Out)
 3  4   IOPort   StepGen  2Dir/Table2  (Out)
16  5   IOPort   StepGen  2Step/Table1 (Out)
 4  6   IOPort   StepGen  3Dir/Table2  (Out)
17  7   IOPort   StepGen  3Step/Table1 (Out)
 5  8   IOPort   StepGen  4Dir/Table2  (Out)
 6  9   IOPort   StepGen  4Step/Table1 (Out)
 7 10   IOPort   SSerial  0TXData0 (Out)
 8 11   IOPort   SSerial  0RXData0 (In)
 9 12   IOPort   SSerial  0TXData1 (Out)
10 13   IOPort   SSerial  0RXData1 (In)
11 14   IOPort   QCount   0Quad-IDX(In)
12 15   IOPort   QCount   0Quad-B  (In)
13 16   IOPort   QCount   0Quad-A  (In)

IO Connections for P1
Pin#  I/O   Pri. funcSec. func   Chan  Pin funcPin Dir

 1 17   IOPort   None 
14 18   IOPort   None
 2 19   IOPort   None 
15 20   IOPort   None
 3 21   IOPort   None 
16 22   IOPort   None
 4 23   IOPort   None 
17 24   IOPort   None

 5 25   IOPort   None
 6 26   IOPort   None
 7 27   IOPort   None
 8 28   IOPort   None
 9 29   IOPort   None 
10 30   IOPort   None 
11 31   IOPort   None 
12 32   IOPort   None 
13 33   IOPort   None


pi@raspberrypi:/boot $

Peter Wallace
Mesa Electronics

(\__/)
(='.'=) This is Bunny. Copy and paste bunny into your
(")_(") signature to help him gain world domination.



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Gene Heskett]

On Friday 11 June 2021 12:05:38 John Dammeyer wrote:

> Sam,
> Here's the ifconfig output generated from putty running on my WIN-7
> workstation via remote desktop from my WIN-10 ZBook.  Ethernet cable
> from Pi4 to 7i92 is 2' long.
>
> And with or without LinuxCNC running this is what I get:
> pi@linuxcnc:~ $ cd mesaflash
> pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> lbp16_access.send_packet: Operation not permitted
> Aborted
>
> John
>
> pi@linuxcnc:~ $ ifconfig
> eth0: flags=4163  mtu 1500
> inet 192.168.1.1  netmask 255.255.255.0  broadcast
> 192.168.1.255 ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
> RX packets 29442387  bytes 2826463726 (2.6 GiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 58886151  bytes 1122489823 (1.0 GiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1000  (Local Loopback)
> RX packets 595  bytes 40144 (39.2 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 595  bytes 40144 (39.2 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> wlan0: flags=4163  mtu 1500
> inet 192.168.0.97  netmask 255.255.255.0  broadcast
> 192.168.0.255 inet6 fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid
> 0x20 ether dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)
> RX packets 9  bytes 3535970 (3.3 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 3108  bytes 415864 (406.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I see one possibility, Ralph.

This doesn't show the default route. But "ip r" will. You are eth0 at 
192.168.1.x and wlan0 at 192.168.0.x. If the default route is thru 
wlan0, mesaflash will probably fail.

I'm using a 7i90 over spi, so my eth0 or whatever name its using this 
week is free for normal use, but that's just one of the reasons I keep 
the #@%## radios turned off, once avahi gets it in its mind to use the 
radio, ip can't or won't fix it, so you have to manually nuke the avahi 
executable and reboot. In your case, rename it to rumplestiltskin or 
whatever so you can restore it if I'm wrong.

Take care and stay well.

[...]

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Ralph Stirling]

Old version of mesaflash perhaps?

On Jun 11, 2021 10:06 AM, John Dammeyer  wrote:
CAUTION: This email originated from outside the Walla Walla University email 
system.


> From: Ralph Stirling [mailto:ralph.stirl...@wallawalla.edu]
>
> I have no problem using 192.168.1.1 for eth0 on pi4 with 7i92.

I don't either with LinuxCNC moving motors.  But it's the mesaflash software 
that is having an issue.  But only on a Pi.  I've downloaded the software from 
github on a PC, Beagle and Pi4.  Only on the Pi4 does it have issues.

Now I can use the PC or the Beagle to flash the appropriate pin file into the 
Pi4 but that's not really the point here.  Very puzzled.

John


>
> On Jun 11, 2021 9:30 AM, Sam Sokolik  wrote:
> CAUTION: This email originated from outside the Walla Walla University email 
> system.
>
>
> That would be something to try..  Maybe mesaflash doesn't know how to
> handle the 192.168.1.1 ip address?  Set the pie to something else like
> 192.168.1.10
>
> On Fri, Jun 11, 2021 at 11:25 AM Mark Wendt  wrote:
>
> > On Fri, Jun 11, 2021 at 12:09 PM John Dammeyer 
> > wrote:
> >
> > > Sam,
> > > Here's the ifconfig output generated from putty running on my WIN-7
> > > workstation via remote desktop from my WIN-10 ZBook.  Ethernet cable from
> > > Pi4 to 7i92 is 2' long.
> > >
> > > And with or without LinuxCNC running this is what I get:
> > > pi@linuxcnc:~ $ cd mesaflash
> > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > > lbp16_access.send_packet: Operation not permitted
> > > Aborted
> > >
> > > John
> > >
> > > pi@linuxcnc:~ $ ifconfig
> > > eth0: flags=4163  mtu 1500
> > > inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
> > > ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
> > > RX packets 29442387  bytes 2826463726 (2.6 GiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 58886151  bytes 1122489823 (1.0 GiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > lo: flags=73  mtu 65536
> > > inet 127.0.0.1  netmask 255.0.0.0
> > > inet6 ::1  prefixlen 128  scopeid 0x10
> > > loop  txqueuelen 1000  (Local Loopback)
> > > RX packets 595  bytes 40144 (39.2 KiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 595  bytes 40144 (39.2 KiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > wlan0: flags=4163  mtu 1500
> > > inet 192.168.0.97  netmask 255.255.255.0  broadcast 192.168.0.255
> > > inet6 fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid 0x20
> > > ether dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)
> > > RX packets 9  bytes 3535970 (3.3 MiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 3108  bytes 415864 (406.1 KiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > pi@linuxcnc:~ $
> > >
> >
> > Do you have any other network devices on the 192.168.1.x network?  The
> > 192.168.1.1 address is usually reserved for routers in that subnet.
> >
> > Mark
> >
> > ___
> > Emc-users mailing list
> > Emc-users@lists.sourceforge.net
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-
> usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7Cc116f028f6ee43e610df08d92cf63ad6%7Cd958f048e43142779c8
> debfb75e7aa64%7C0%7C0%7C637590258342182689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC
> JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=N5XTffg5bbWkolc%2FRmAIrAAMc6JWGk6iNLmN0Nz18%2BU%3Dres
> erved=0
> >
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-
> usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7Cc116f028f6ee43e610df08d92cf63ad6%7Cd958f048e43142779c8
> debfb75e7aa64%7C0%7C0%7C637590258342182689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC
> JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=N5XTffg5bbWkolc%2FRmAIrAAMc6JWGk6iNLmN0Nz18%2BU%3Dres
> erved=0
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7C80e7caa73bba49fbd7a608d92cfb3513%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0%7C637590279707645822%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=yZQam%2FPst8b%2FYnuTxqyxXuohcFtZYY2idlYffoA%2B71w%3Dreserved=0



___
Emc-users mailing list
Emc-users@lists.sourceforge.net

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

> From: Ralph Stirling [mailto:ralph.stirl...@wallawalla.edu]
> 
> I have no problem using 192.168.1.1 for eth0 on pi4 with 7i92.

I don't either with LinuxCNC moving motors.  But it's the mesaflash software 
that is having an issue.  But only on a Pi.  I've downloaded the software from 
github on a PC, Beagle and Pi4.  Only on the Pi4 does it have issues. 

Now I can use the PC or the Beagle to flash the appropriate pin file into the 
Pi4 but that's not really the point here.  Very puzzled.

John


> 
> On Jun 11, 2021 9:30 AM, Sam Sokolik  wrote:
> CAUTION: This email originated from outside the Walla Walla University email 
> system.
> 
> 
> That would be something to try..  Maybe mesaflash doesn't know how to
> handle the 192.168.1.1 ip address?  Set the pie to something else like
> 192.168.1.10
> 
> On Fri, Jun 11, 2021 at 11:25 AM Mark Wendt  wrote:
> 
> > On Fri, Jun 11, 2021 at 12:09 PM John Dammeyer 
> > wrote:
> >
> > > Sam,
> > > Here's the ifconfig output generated from putty running on my WIN-7
> > > workstation via remote desktop from my WIN-10 ZBook.  Ethernet cable from
> > > Pi4 to 7i92 is 2' long.
> > >
> > > And with or without LinuxCNC running this is what I get:
> > > pi@linuxcnc:~ $ cd mesaflash
> > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > > lbp16_access.send_packet: Operation not permitted
> > > Aborted
> > >
> > > John
> > >
> > > pi@linuxcnc:~ $ ifconfig
> > > eth0: flags=4163  mtu 1500
> > > inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
> > > ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
> > > RX packets 29442387  bytes 2826463726 (2.6 GiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 58886151  bytes 1122489823 (1.0 GiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > lo: flags=73  mtu 65536
> > > inet 127.0.0.1  netmask 255.0.0.0
> > > inet6 ::1  prefixlen 128  scopeid 0x10
> > > loop  txqueuelen 1000  (Local Loopback)
> > > RX packets 595  bytes 40144 (39.2 KiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 595  bytes 40144 (39.2 KiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > wlan0: flags=4163  mtu 1500
> > > inet 192.168.0.97  netmask 255.255.255.0  broadcast 192.168.0.255
> > > inet6 fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid 0x20
> > > ether dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)
> > > RX packets 9  bytes 3535970 (3.3 MiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 3108  bytes 415864 (406.1 KiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > >
> > > pi@linuxcnc:~ $
> > >
> >
> > Do you have any other network devices on the 192.168.1.x network?  The
> > 192.168.1.1 address is usually reserved for routers in that subnet.
> >
> > Mark
> >
> > ___
> > Emc-users mailing list
> > Emc-users@lists.sourceforge.net
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-
> usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7Cc116f028f6ee43e610df08d92cf63ad6%7Cd958f048e43142779c8
> debfb75e7aa64%7C0%7C0%7C637590258342182689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC
> JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=N5XTffg5bbWkolc%2FRmAIrAAMc6JWGk6iNLmN0Nz18%2BU%3Dres
> erved=0
> >
> 
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-
> usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7Cc116f028f6ee43e610df08d92cf63ad6%7Cd958f048e43142779c8
> debfb75e7aa64%7C0%7C0%7C637590258342182689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC
> JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=N5XTffg5bbWkolc%2FRmAIrAAMc6JWGk6iNLmN0Nz18%2BU%3Dres
> erved=0
> 
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Ralph Stirling]

I have no problem using 192.168.1.1 for eth0 on pi4 with 7i92.

On Jun 11, 2021 9:30 AM, Sam Sokolik  wrote:
CAUTION: This email originated from outside the Walla Walla University email 
system.


That would be something to try..  Maybe mesaflash doesn't know how to
handle the 192.168.1.1 ip address?  Set the pie to something else like
192.168.1.10

On Fri, Jun 11, 2021 at 11:25 AM Mark Wendt  wrote:

> On Fri, Jun 11, 2021 at 12:09 PM John Dammeyer 
> wrote:
>
> > Sam,
> > Here's the ifconfig output generated from putty running on my WIN-7
> > workstation via remote desktop from my WIN-10 ZBook.  Ethernet cable from
> > Pi4 to 7i92 is 2' long.
> >
> > And with or without LinuxCNC running this is what I get:
> > pi@linuxcnc:~ $ cd mesaflash
> > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > lbp16_access.send_packet: Operation not permitted
> > Aborted
> >
> > John
> >
> > pi@linuxcnc:~ $ ifconfig
> > eth0: flags=4163  mtu 1500
> > inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
> > ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
> > RX packets 29442387  bytes 2826463726 (2.6 GiB)
> > RX errors 0  dropped 0  overruns 0  frame 0
> > TX packets 58886151  bytes 1122489823 (1.0 GiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > lo: flags=73  mtu 65536
> > inet 127.0.0.1  netmask 255.0.0.0
> > inet6 ::1  prefixlen 128  scopeid 0x10
> > loop  txqueuelen 1000  (Local Loopback)
> > RX packets 595  bytes 40144 (39.2 KiB)
> > RX errors 0  dropped 0  overruns 0  frame 0
> > TX packets 595  bytes 40144 (39.2 KiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > wlan0: flags=4163  mtu 1500
> > inet 192.168.0.97  netmask 255.255.255.0  broadcast 192.168.0.255
> > inet6 fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid 0x20
> > ether dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)
> > RX packets 9  bytes 3535970 (3.3 MiB)
> > RX errors 0  dropped 0  overruns 0  frame 0
> > TX packets 3108  bytes 415864 (406.1 KiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > pi@linuxcnc:~ $
> >
>
> Do you have any other network devices on the 192.168.1.x network?  The
> 192.168.1.1 address is usually reserved for routers in that subnet.
>
> Mark
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7Cc116f028f6ee43e610df08d92cf63ad6%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0%7C637590258342182689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=N5XTffg5bbWkolc%2FRmAIrAAMc6JWGk6iNLmN0Nz18%2BU%3Dreserved=0
>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7Cc116f028f6ee43e610df08d92cf63ad6%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0%7C637590258342182689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=N5XTffg5bbWkolc%2FRmAIrAAMc6JWGk6iNLmN0Nz18%2BU%3Dreserved=0

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

> From: Mark Wendt [mailto:wendt.m...@gmail.com]

> 
> Do you have any other network devices on the 192.168.1.x network?  The
> 192.168.1.1 address is usually reserved for routers in that subnet.
> 
> Mark

Nope.  Only the one short cable.  

Here's the odd thing.  A BeagleBone black directly connected to a 7i92H has no 
trouble running mesaflash and talking to the unit.  It can ping 192.168.1.121 
which works.

And a sudo ifconfig reports
Eth0 as 169.254.139.127  mask 255.255.0.0 and broadcast 169.254.255.255
Doesn't even appear like it's on the same network but I can query and do things 
with the 7i92.

The LinuxCNC PC also doesn't have any issues with mesaflash and the 7i92.  

Go figure.  What's up with the Pi4 to 7i92 that is so different and yet it runs 
LinuxCNC and moves motors?

Very strange.
John





___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

> From: Sam Sokolik [mailto:samco...@gmail.com]
> Sent: June-11-21 9:30 AM
> That would be something to try..  Maybe mesaflash doesn't know how to
> handle the 192.168.1.1 ip address?  Set the pie to something else like
> 192.168.1.10
> 

Alas no.  Doesn't work either.  And after a reboot ifconfig does show the pi as 
192.168.1.10.  Unless the mesaflash software itself was having trouble with a 
.1 address but seems not.

But it was worth a try.

John




___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Sam Sokolik]

That would be something to try..  Maybe mesaflash doesn't know how to
handle the 192.168.1.1 ip address?  Set the pie to something else like
192.168.1.10

On Fri, Jun 11, 2021 at 11:25 AM Mark Wendt  wrote:

> On Fri, Jun 11, 2021 at 12:09 PM John Dammeyer 
> wrote:
>
> > Sam,
> > Here's the ifconfig output generated from putty running on my WIN-7
> > workstation via remote desktop from my WIN-10 ZBook.  Ethernet cable from
> > Pi4 to 7i92 is 2' long.
> >
> > And with or without LinuxCNC running this is what I get:
> > pi@linuxcnc:~ $ cd mesaflash
> > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > lbp16_access.send_packet: Operation not permitted
> > Aborted
> >
> > John
> >
> > pi@linuxcnc:~ $ ifconfig
> > eth0: flags=4163  mtu 1500
> > inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
> > ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
> > RX packets 29442387  bytes 2826463726 (2.6 GiB)
> > RX errors 0  dropped 0  overruns 0  frame 0
> > TX packets 58886151  bytes 1122489823 (1.0 GiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > lo: flags=73  mtu 65536
> > inet 127.0.0.1  netmask 255.0.0.0
> > inet6 ::1  prefixlen 128  scopeid 0x10
> > loop  txqueuelen 1000  (Local Loopback)
> > RX packets 595  bytes 40144 (39.2 KiB)
> > RX errors 0  dropped 0  overruns 0  frame 0
> > TX packets 595  bytes 40144 (39.2 KiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > wlan0: flags=4163  mtu 1500
> > inet 192.168.0.97  netmask 255.255.255.0  broadcast 192.168.0.255
> > inet6 fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid 0x20
> > ether dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)
> > RX packets 9  bytes 3535970 (3.3 MiB)
> > RX errors 0  dropped 0  overruns 0  frame 0
> > TX packets 3108  bytes 415864 (406.1 KiB)
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >
> > pi@linuxcnc:~ $
> >
>
> Do you have any other network devices on the 192.168.1.x network?  The
> 192.168.1.1 address is usually reserved for routers in that subnet.
>
> Mark
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Mark Wendt]

On Fri, Jun 11, 2021 at 12:09 PM John Dammeyer 
wrote:

> Sam,
> Here's the ifconfig output generated from putty running on my WIN-7
> workstation via remote desktop from my WIN-10 ZBook.  Ethernet cable from
> Pi4 to 7i92 is 2' long.
>
> And with or without LinuxCNC running this is what I get:
> pi@linuxcnc:~ $ cd mesaflash
> pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> lbp16_access.send_packet: Operation not permitted
> Aborted
>
> John
>
> pi@linuxcnc:~ $ ifconfig
> eth0: flags=4163  mtu 1500
> inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
> ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
> RX packets 29442387  bytes 2826463726 (2.6 GiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 58886151  bytes 1122489823 (1.0 GiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1000  (Local Loopback)
> RX packets 595  bytes 40144 (39.2 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 595  bytes 40144 (39.2 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> wlan0: flags=4163  mtu 1500
> inet 192.168.0.97  netmask 255.255.255.0  broadcast 192.168.0.255
> inet6 fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid 0x20
> ether dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)
> RX packets 9  bytes 3535970 (3.3 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 3108  bytes 415864 (406.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> pi@linuxcnc:~ $
>

Do you have any other network devices on the 192.168.1.x network?  The
192.168.1.1 address is usually reserved for routers in that subnet.

Mark

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

Sam,
Here's the ifconfig output generated from putty running on my WIN-7 workstation 
via remote desktop from my WIN-10 ZBook.  Ethernet cable from Pi4 to 7i92 is 2' 
long.

And with or without LinuxCNC running this is what I get:
pi@linuxcnc:~ $ cd mesaflash
pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
lbp16_access.send_packet: Operation not permitted
Aborted

John

pi@linuxcnc:~ $ ifconfig
eth0: flags=4163  mtu 1500
inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
ether dc:a6:32:1e:30:f1  txqueuelen 1000  (Ethernet)
RX packets 29442387  bytes 2826463726 (2.6 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 58886151  bytes 1122489823 (1.0 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 595  bytes 40144 (39.2 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 595  bytes 40144 (39.2 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163  mtu 1500
inet 192.168.0.97  netmask 255.255.255.0  broadcast 192.168.0.255
inet6 fe80::9d66:1b85:f539:da50  prefixlen 64  scopeid 0x20
ether dc:a6:32:1e:30:f2  txqueuelen 1000  (Ethernet)
RX packets 9  bytes 3535970 (3.3 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 3108  bytes 415864 (406.1 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@linuxcnc:~ $

> -Original Message-
> From: Sam Sokolik [mailto:samco...@gmail.com]
> Sent: June-11-21 4:55 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> 
> The IP address of your pi is 192.168.1.121?  That is the normal IP address
> of the 7i92...  Might be your problem.   Also what subnet is your wireless
> network?  If it is also 192.168.1.x it also could cause problems.   That is
> why I normally set the jumper on the mesa so it is 10.10.10.10
> 
> On Fri, Jun 11, 2021, 2:59 AM John Dammeyer  wrote:
> 
> > Thanks Sam,
> > I'll check it out.  Just got out of the shop.  I remove the PC and plugged
> > the Pi4 back into the system.  Homed, then G0 X0 Y0 Z0 A0,  after that ran
> > a G-Code that cut a spiral.  All nice and smooth and quiet with the servos.
> > Closed LinuxCNC.  Then into terminal and cd ~/mesaflash.  Same thing.
> >
> > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > lbp16_access.send_packet: Resource temporarily unavailable
> > Aborted
> >
> > I'll check your link.   Has to be something really simple I think.  The
> > fact that the mesaflash compiles and runs on a PC and a BeagleBone (that I
> > didn't expect) suggests to me the problem isn't with mesaflash.
> >
> > ...
> >
> > OK.
> > Static ip_address=192.168.1.1
> >
> > I don't have the /24 but my 7i92 is 192.168.1.121 and the fact that I can
> > use the CNC suggest all is good.
> >
> > I can try adding that /24 to see if it makes a difference but first I'd
> > like to know why it's needed.
> > ...
> > No change.  LinuxCNC still moves things.  But mesaflash comes up with the
> > same error.
> >
> > John
> >
> >
> >
> > > -Original Message-
> > > From: Sam Sokolik [mailto:samco...@gmail.com]
> > > Sent: June-11-21 12:19 AM
> > > To: Enhanced Machine Controller (EMC)
> > > Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> > >
> > > I just used mesaflash the other day on the rpi4 for the 7i92.   It has
> > been
> > > a while but I think I followed the network directions here...
> > >
> > > https://gnipsel.com/linuxcnc/uspace/rpi4-eth.html
> > >
> > > On Fri, Jun 11, 2021, 12:58 AM Ralph Stirling <
> > ralph.stirl...@wallawalla.edu>
> > > wrote:
> > >
> > > > Did you set a static ip for the pi in /etc/dhcpcd.conf?  It worked for
> > me
> > > > after I did this.
> > > >
> > > > -- Ralph
> > > >
> > > > On Jun 10, 2021 8:02 PM, John Dammeyer  wrote:
> > > > CAUTION: This email originated from outside the Walla Walla University
> > > > email system.
> > > >
> > > >
> > > > Peter Wallace and I have been working on getting the Pi4 to work with
> > the
> > > > 7i92 mesaflash program.
> > > >
> > > > He asked me to do this but I get the error below.
> > > > pi@linuxcnc:~/mesaflash

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

Sorry.  I thought I was asked what the ip was of the 7i92.  That's 
192.68.1.121.  The Pi is 182.168.1.1 I believe.  They aren't the same.  
Remember.  LinuxCNC works and moves motors.

Once I had the Pi running the only thing I had to 'repair' in the INI file was 
the speed of the Z axis.  The last time I ran the Pi the machine still had a 
stepper motor and Gecko on the knee.   Now it has the 750 Bergerda instead and 
can do 150 ipm instead of 24 ipm.  So the ratios and max speed/accel were 
different.

After that full speed ahead.  And then shut down linuxcnc and try from the 
terminal again and still no luck.

John


> -Original Message-
> From: Sam Sokolik [mailto:samco...@gmail.com]
> Sent: June-11-21 4:55 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> 
> The IP address of your pi is 192.168.1.121?  That is the normal IP address
> of the 7i92...  Might be your problem.   Also what subnet is your wireless
> network?  If it is also 192.168.1.x it also could cause problems.   That is
> why I normally set the jumper on the mesa so it is 10.10.10.10
> 
> On Fri, Jun 11, 2021, 2:59 AM John Dammeyer  wrote:
> 
> > Thanks Sam,
> > I'll check it out.  Just got out of the shop.  I remove the PC and plugged
> > the Pi4 back into the system.  Homed, then G0 X0 Y0 Z0 A0,  after that ran
> > a G-Code that cut a spiral.  All nice and smooth and quiet with the servos.
> > Closed LinuxCNC.  Then into terminal and cd ~/mesaflash.  Same thing.
> >
> > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > lbp16_access.send_packet: Resource temporarily unavailable
> > Aborted
> >
> > I'll check your link.   Has to be something really simple I think.  The
> > fact that the mesaflash compiles and runs on a PC and a BeagleBone (that I
> > didn't expect) suggests to me the problem isn't with mesaflash.
> >
> > ...
> >
> > OK.
> > Static ip_address=192.168.1.1
> >
> > I don't have the /24 but my 7i92 is 192.168.1.121 and the fact that I can
> > use the CNC suggest all is good.
> >
> > I can try adding that /24 to see if it makes a difference but first I'd
> > like to know why it's needed.
> > ...
> > No change.  LinuxCNC still moves things.  But mesaflash comes up with the
> > same error.
> >
> > John
> >
> >
> >
> > > -Original Message-
> > > From: Sam Sokolik [mailto:samco...@gmail.com]
> > > Sent: June-11-21 12:19 AM
> > > To: Enhanced Machine Controller (EMC)
> > > Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> > >
> > > I just used mesaflash the other day on the rpi4 for the 7i92.   It has
> > been
> > > a while but I think I followed the network directions here...
> > >
> > > https://gnipsel.com/linuxcnc/uspace/rpi4-eth.html
> > >
> > > On Fri, Jun 11, 2021, 12:58 AM Ralph Stirling <
> > ralph.stirl...@wallawalla.edu>
> > > wrote:
> > >
> > > > Did you set a static ip for the pi in /etc/dhcpcd.conf?  It worked for
> > me
> > > > after I did this.
> > > >
> > > > -- Ralph
> > > >
> > > > On Jun 10, 2021 8:02 PM, John Dammeyer  wrote:
> > > > CAUTION: This email originated from outside the Walla Walla University
> > > > email system.
> > > >
> > > >
> > > > Peter Wallace and I have been working on getting the Pi4 to work with
> > the
> > > > 7i92 mesaflash program.
> > > >
> > > > He asked me to do this but I get the error below.
> > > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > > > lbp16_access.send_packet: Resource temporarily unavailable
> > > > Aborted
> > > >
> > > > When I do this on the PC with the same 7i92 it dumps the Pins table.
> > The
> > > > 7i92 is communicating with the board.  It can ping it.  It can detect
> > what
> > > > type of board it is.  But the --readhmid parameter always returns this
> > > > access.send_packet error.
> > > >
> > > > Any ideas on how to solve this problem?  It appears to be some sort of
> > > > network issue.  The Pi4 has successfully run my CNC hardware through
> > the
> > > > 7i92 so Ethernet works.  At least from LinuxCNC to the Pi.   Clearly
> > not
> > > > from the mesaflash to the pi.
> > > >
> > > > To get mesaflash onto the Pi4 you have to do the following.
> > > > pi@linuxcnc:~ $ sudo git clon

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Sam Sokolik]

The IP address of your pi is 192.168.1.121?  That is the normal IP address
of the 7i92...  Might be your problem.   Also what subnet is your wireless
network?  If it is also 192.168.1.x it also could cause problems.   That is
why I normally set the jumper on the mesa so it is 10.10.10.10

On Fri, Jun 11, 2021, 2:59 AM John Dammeyer  wrote:

> Thanks Sam,
> I'll check it out.  Just got out of the shop.  I remove the PC and plugged
> the Pi4 back into the system.  Homed, then G0 X0 Y0 Z0 A0,  after that ran
> a G-Code that cut a spiral.  All nice and smooth and quiet with the servos.
> Closed LinuxCNC.  Then into terminal and cd ~/mesaflash.  Same thing.
>
> pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> lbp16_access.send_packet: Resource temporarily unavailable
> Aborted
>
> I'll check your link.   Has to be something really simple I think.  The
> fact that the mesaflash compiles and runs on a PC and a BeagleBone (that I
> didn't expect) suggests to me the problem isn't with mesaflash.
>
> ...
>
> OK.
> Static ip_address=192.168.1.1
>
> I don't have the /24 but my 7i92 is 192.168.1.121 and the fact that I can
> use the CNC suggest all is good.
>
> I can try adding that /24 to see if it makes a difference but first I'd
> like to know why it's needed.
> ...
> No change.  LinuxCNC still moves things.  But mesaflash comes up with the
> same error.
>
> John
>
>
>
> > -Original Message-
> > From: Sam Sokolik [mailto:samco...@gmail.com]
> > Sent: June-11-21 12:19 AM
> > To: Enhanced Machine Controller (EMC)
> > Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> >
> > I just used mesaflash the other day on the rpi4 for the 7i92.   It has
> been
> > a while but I think I followed the network directions here...
> >
> > https://gnipsel.com/linuxcnc/uspace/rpi4-eth.html
> >
> > On Fri, Jun 11, 2021, 12:58 AM Ralph Stirling <
> ralph.stirl...@wallawalla.edu>
> > wrote:
> >
> > > Did you set a static ip for the pi in /etc/dhcpcd.conf?  It worked for
> me
> > > after I did this.
> > >
> > > -- Ralph
> > >
> > > On Jun 10, 2021 8:02 PM, John Dammeyer  wrote:
> > > CAUTION: This email originated from outside the Walla Walla University
> > > email system.
> > >
> > >
> > > Peter Wallace and I have been working on getting the Pi4 to work with
> the
> > > 7i92 mesaflash program.
> > >
> > > He asked me to do this but I get the error below.
> > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > > lbp16_access.send_packet: Resource temporarily unavailable
> > > Aborted
> > >
> > > When I do this on the PC with the same 7i92 it dumps the Pins table.
> The
> > > 7i92 is communicating with the board.  It can ping it.  It can detect
> what
> > > type of board it is.  But the --readhmid parameter always returns this
> > > access.send_packet error.
> > >
> > > Any ideas on how to solve this problem?  It appears to be some sort of
> > > network issue.  The Pi4 has successfully run my CNC hardware through
> the
> > > 7i92 so Ethernet works.  At least from LinuxCNC to the Pi.   Clearly
> not
> > > from the mesaflash to the pi.
> > >
> > > To get mesaflash onto the Pi4 you have to do the following.
> > > pi@linuxcnc:~ $ sudo git clone
> > >
> >
> https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgithub.com%2Flinuxcnc%2Fmesaflashdata=04%7C01
> > %7Cralph.stirling%40wallawalla.edu
> %7C4f063130e6174fe6087c08d92c856741%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0
> >
> %7C637589773748714746%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M
> >
> n0%3D%7C1000sdata=yZ4IL4wTuuULCOB%2Fg9S9T3q2E1szCUPkKe5gaC2oIoc%3Dreserved=0
> > > pi@linuxcnc:~/mesaflash $ sudo apt-get install libpci-dev
> > > pi@linuxcnc:~/mesaflash $ sudo make
> > >
> > > Once that's all done:
> > > pi@linuxcnc:~/mesaflash $ ./mesaflash
> > > Mesaflash version 3.4.0~pre1
> > > Configuration and diagnostic tool for Mesa Electronics
> > > PCI(E)/ETH/EPP/USB/SPI boards
> > > Try 'mesaflash --help' for more information
> > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --addr
> > > 192.168.1.121
> > > ETH device 7I92 at ip=192.168.1.121
> > >
> > > Any suggestions are welcome.
> > > Thanks
> > > John Dammeyer
> > >
> > >
> > > "ELS! 

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

Thanks Sam,
I'll check it out.  Just got out of the shop.  I remove the PC and plugged the 
Pi4 back into the system.  Homed, then G0 X0 Y0 Z0 A0,  after that ran a G-Code 
that cut a spiral.  All nice and smooth and quiet with the servos.
Closed LinuxCNC.  Then into terminal and cd ~/mesaflash.  Same thing.

pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
lbp16_access.send_packet: Resource temporarily unavailable
Aborted

I'll check your link.   Has to be something really simple I think.  The fact 
that the mesaflash compiles and runs on a PC and a BeagleBone (that I didn't 
expect) suggests to me the problem isn't with mesaflash.

...

OK.
Static ip_address=192.168.1.1

I don't have the /24 but my 7i92 is 192.168.1.121 and the fact that I can use 
the CNC suggest all is good.

I can try adding that /24 to see if it makes a difference but first I'd like to 
know why it's needed.
...
No change.  LinuxCNC still moves things.  But mesaflash comes up with the same 
error.

John



> -Original Message-
> From: Sam Sokolik [mailto:samco...@gmail.com]
> Sent: June-11-21 12:19 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> 
> I just used mesaflash the other day on the rpi4 for the 7i92.   It has been
> a while but I think I followed the network directions here...
> 
> https://gnipsel.com/linuxcnc/uspace/rpi4-eth.html
> 
> On Fri, Jun 11, 2021, 12:58 AM Ralph Stirling 
> wrote:
> 
> > Did you set a static ip for the pi in /etc/dhcpcd.conf?  It worked for me
> > after I did this.
> >
> > -- Ralph
> >
> > On Jun 10, 2021 8:02 PM, John Dammeyer  wrote:
> > CAUTION: This email originated from outside the Walla Walla University
> > email system.
> >
> >
> > Peter Wallace and I have been working on getting the Pi4 to work with the
> > 7i92 mesaflash program.
> >
> > He asked me to do this but I get the error below.
> > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > lbp16_access.send_packet: Resource temporarily unavailable
> > Aborted
> >
> > When I do this on the PC with the same 7i92 it dumps the Pins table.  The
> > 7i92 is communicating with the board.  It can ping it.  It can detect what
> > type of board it is.  But the --readhmid parameter always returns this
> > access.send_packet error.
> >
> > Any ideas on how to solve this problem?  It appears to be some sort of
> > network issue.  The Pi4 has successfully run my CNC hardware through the
> > 7i92 so Ethernet works.  At least from LinuxCNC to the Pi.   Clearly not
> > from the mesaflash to the pi.
> >
> > To get mesaflash onto the Pi4 you have to do the following.
> > pi@linuxcnc:~ $ sudo git clone
> >
> https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgithub.com%2Flinuxcnc%2Fmesaflashdata=04%7C01
> %7Cralph.stirling%40wallawalla.edu%7C4f063130e6174fe6087c08d92c856741%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0
> %7C637589773748714746%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M
> n0%3D%7C1000sdata=yZ4IL4wTuuULCOB%2Fg9S9T3q2E1szCUPkKe5gaC2oIoc%3Dreserved=0
> > pi@linuxcnc:~/mesaflash $ sudo apt-get install libpci-dev
> > pi@linuxcnc:~/mesaflash $ sudo make
> >
> > Once that's all done:
> > pi@linuxcnc:~/mesaflash $ ./mesaflash
> > Mesaflash version 3.4.0~pre1
> > Configuration and diagnostic tool for Mesa Electronics
> > PCI(E)/ETH/EPP/USB/SPI boards
> > Try 'mesaflash --help' for more information
> > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --addr
> > 192.168.1.121
> > ETH device 7I92 at ip=192.168.1.121
> >
> > Any suggestions are welcome.
> > Thanks
> > John Dammeyer
> >
> >
> > "ELS! Nothing else works as well for your Lathe"
> > Automation Artisans Inc.
> > www dot autoartisans dot com
> >
> >
> > ___
> > Emc-users mailing list
> > Emc-users@lists.sourceforge.net
> >
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-
> usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7C4f063130e6174fe6087c08d92c856741%7Cd958f048e43142779c
> 8debfb75e7aa64%7C0%7C0%7C637589773748724742%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
> CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=maLrElZOTYs0pWjJlpt1FpNKzGRGca8Yhuz1Yjny8Q0%3Dreserved=0
> >
> > ___
> > Emc-users mailing list
> > Emc-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-users
> >
> 
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Sam Sokolik]

I just used mesaflash the other day on the rpi4 for the 7i92.   It has been
a while but I think I followed the network directions here...

https://gnipsel.com/linuxcnc/uspace/rpi4-eth.html

On Fri, Jun 11, 2021, 12:58 AM Ralph Stirling 
wrote:

> Did you set a static ip for the pi in /etc/dhcpcd.conf?  It worked for me
> after I did this.
>
> -- Ralph
>
> On Jun 10, 2021 8:02 PM, John Dammeyer  wrote:
> CAUTION: This email originated from outside the Walla Walla University
> email system.
>
>
> Peter Wallace and I have been working on getting the Pi4 to work with the
> 7i92 mesaflash program.
>
> He asked me to do this but I get the error below.
> pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> lbp16_access.send_packet: Resource temporarily unavailable
> Aborted
>
> When I do this on the PC with the same 7i92 it dumps the Pins table.  The
> 7i92 is communicating with the board.  It can ping it.  It can detect what
> type of board it is.  But the --readhmid parameter always returns this
> access.send_packet error.
>
> Any ideas on how to solve this problem?  It appears to be some sort of
> network issue.  The Pi4 has successfully run my CNC hardware through the
> 7i92 so Ethernet works.  At least from LinuxCNC to the Pi.   Clearly not
> from the mesaflash to the pi.
>
> To get mesaflash onto the Pi4 you have to do the following.
> pi@linuxcnc:~ $ sudo git clone
> https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgithub.com%2Flinuxcnc%2Fmesaflashdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7C4f063130e6174fe6087c08d92c856741%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0%7C637589773748714746%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=yZ4IL4wTuuULCOB%2Fg9S9T3q2E1szCUPkKe5gaC2oIoc%3Dreserved=0
> pi@linuxcnc:~/mesaflash $ sudo apt-get install libpci-dev
> pi@linuxcnc:~/mesaflash $ sudo make
>
> Once that's all done:
> pi@linuxcnc:~/mesaflash $ ./mesaflash
> Mesaflash version 3.4.0~pre1
> Configuration and diagnostic tool for Mesa Electronics
> PCI(E)/ETH/EPP/USB/SPI boards
> Try 'mesaflash --help' for more information
> pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --addr
> 192.168.1.121
> ETH device 7I92 at ip=192.168.1.121
>
> Any suggestions are welcome.
> Thanks
> John Dammeyer
>
>
> "ELS! Nothing else works as well for your Lathe"
> Automation Artisans Inc.
> www dot autoartisans dot com
>
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
>
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7C4f063130e6174fe6087c08d92c856741%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0%7C637589773748724742%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=maLrElZOTYs0pWjJlpt1FpNKzGRGca8Yhuz1Yjny8Q0%3Dreserved=0
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Ralph Stirling]

Did you set a static ip for the pi in /etc/dhcpcd.conf?  It worked for me after 
I did this.

-- Ralph

On Jun 10, 2021 8:02 PM, John Dammeyer  wrote:
CAUTION: This email originated from outside the Walla Walla University email 
system.


Peter Wallace and I have been working on getting the Pi4 to work with the 7i92 
mesaflash program.

He asked me to do this but I get the error below.
pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
lbp16_access.send_packet: Resource temporarily unavailable
Aborted

When I do this on the PC with the same 7i92 it dumps the Pins table.  The 7i92 
is communicating with the board.  It can ping it.  It can detect what type of 
board it is.  But the --readhmid parameter always returns this 
access.send_packet error.

Any ideas on how to solve this problem?  It appears to be some sort of network 
issue.  The Pi4 has successfully run my CNC hardware through the 7i92 so 
Ethernet works.  At least from LinuxCNC to the Pi.   Clearly not from the 
mesaflash to the pi.

To get mesaflash onto the Pi4 you have to do the following.
pi@linuxcnc:~ $ sudo git clone 
https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgithub.com%2Flinuxcnc%2Fmesaflashdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7C4f063130e6174fe6087c08d92c856741%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0%7C637589773748714746%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=yZ4IL4wTuuULCOB%2Fg9S9T3q2E1szCUPkKe5gaC2oIoc%3Dreserved=0
pi@linuxcnc:~/mesaflash $ sudo apt-get install libpci-dev
pi@linuxcnc:~/mesaflash $ sudo make

Once that's all done:
pi@linuxcnc:~/mesaflash $ ./mesaflash
Mesaflash version 3.4.0~pre1
Configuration and diagnostic tool for Mesa Electronics PCI(E)/ETH/EPP/USB/SPI 
boards
Try 'mesaflash --help' for more information
pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --addr 192.168.1.121
ETH device 7I92 at ip=192.168.1.121

Any suggestions are welcome.
Thanks
John Dammeyer


"ELS! Nothing else works as well for your Lathe"
Automation Artisans Inc.
www dot autoartisans dot com


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-usersdata=04%7C01%7Cralph.stirling%40wallawalla.edu%7C4f063130e6174fe6087c08d92c856741%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0%7C637589773748724742%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=maLrElZOTYs0pWjJlpt1FpNKzGRGca8Yhuz1Yjny8Q0%3Dreserved=0

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

> -Original Message-
> From: Peter C. Wallace [mailto:p...@mesanet.com]
> Sent: June-10-21 9:38 PM
> On Thu, 10 Jun 2021, John Dammeyer wrote:
> 
> > BTW, used the same process for the BBB to install mesaflash.
> >
> > Attached file shows the result.  Works like a charm so the issue isn't the
> > mesaflash program and ARM libraries nor PC running LinuxCNC.  The issue is
> > probably with the Pi4 libaries used by the mesaflash.
> >
> > John
> >
> 
> I would think its more likely a host network setup issue. I'll try mesaflash 
> on
> a RPI4 with a Ethernet card tommorow but I do know mesaflash works properly on
> SPI connected FPGAs card on the RPI4. (and linuxCNC runs fine with Mesa 
> Ethernet
> cards on the RPI4)
> 
 
> Peter Wallace
> Mesa Electronics

With the Beagle I didn't bother setting up the host.  I shutdown the beagle. 
Plugged in the Ethernet cable to the 7i92 and then started up the beagle.  Once 
(finally) running I did a ping to 192.168.1.121 and that worked.  And so did 
the rest of it.

BTW, the Pi4 1GB I'm running has successfully run LinuxCNC with a 7i92 and cut 
metal.  So the Ethernet connection to the Pi4 works for that.  But maybe I 
screwed up something while setting up the 7i92 Ethernet connection.  I must 
admit I haven't tried running LinuxCNC with it since.

And the Pi4 does properly ping the 7i92 and can ask if it's a 7i92.  Looking 
forward to your tests.

John



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[Peter C. Wallace]

On Thu, 10 Jun 2021, John Dammeyer wrote:


Date: Thu, 10 Jun 2021 21:25:35 -0700
From: John Dammeyer 
Reply-To: "Enhanced Machine Controller (EMC)"

To: "'Enhanced Machine Controller (EMC)'" 
Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H

BTW, used the same process for the BBB to install mesaflash.

Attached file shows the result.  Works like a charm so the issue isn't the 
mesaflash program and ARM libraries nor PC running LinuxCNC.  The issue is 
probably with the Pi4 libaries used by the mesaflash.


John



I would think its more likely a host network setup issue. I'll try mesaflash on 
a RPI4 with a Ethernet card tommorow but I do know mesaflash works properly on 
SPI connected FPGAs card on the RPI4. (and linuxCNC runs fine with Mesa Ethernet 
cards on the RPI4)





-Original Message-
From: John Dammeyer [mailto:jo...@autoartisans.com]
Sent: June-10-21 8:02 PM
To: Enhanced Machine Controller (EMC)
Subject: [Emc-users] Pi4 issues with MESA 7i92H

Peter Wallace and I have been working on getting the Pi4 to work with the 7i92 
mesaflash program.

He asked me to do this but I get the error below.
pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
lbp16_access.send_packet: Resource temporarily unavailable
Aborted

When I do this on the PC with the same 7i92 it dumps the Pins table.  The 7i92 
is communicating with the board.  It can ping it.  It can
detect what type of board it is.  But the --readhmid parameter always returns 
this access.send_packet error.

Any ideas on how to solve this problem?  It appears to be some sort of network 
issue.  The Pi4 has successfully run my CNC
hardware through the 7i92 so Ethernet works.  At least from LinuxCNC to the Pi. 
  Clearly not from the mesaflash to the pi.

To get mesaflash onto the Pi4 you have to do the following.
pi@linuxcnc:~ $ sudo git clone http://github.com/linuxcnc/mesaflash
pi@linuxcnc:~/mesaflash $ sudo apt-get install libpci-dev
pi@linuxcnc:~/mesaflash $ sudo make

Once that's all done:
pi@linuxcnc:~/mesaflash $ ./mesaflash
Mesaflash version 3.4.0~pre1
Configuration and diagnostic tool for Mesa Electronics PCI(E)/ETH/EPP/USB/SPI 
boards
Try 'mesaflash --help' for more information
pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --addr 192.168.1.121
ETH device 7I92 at ip=192.168.1.121

Any suggestions are welcome.
Thanks
John Dammeyer


"ELS! Nothing else works as well for your Lathe"
Automation Artisans Inc.
www dot autoartisans dot com


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users




Peter Wallace
Mesa Electronics

(\__/)
(='.'=) This is Bunny. Copy and paste bunny into your
(")_(") signature to help him gain world domination.



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Pi4 issues with MESA 7i92H

[John Dammeyer]

BTW, used the same process for the BBB to install mesaflash.

Attached file shows the result.  Works like a charm so the issue isn't the 
mesaflash program and ARM libraries nor PC running LinuxCNC.  The issue is 
probably with the Pi4 libaries used by the mesaflash.

John


> -Original Message-
> From: John Dammeyer [mailto:jo...@autoartisans.com]
> Sent: June-10-21 8:02 PM
> To: Enhanced Machine Controller (EMC)
> Subject: [Emc-users] Pi4 issues with MESA 7i92H
> 
> Peter Wallace and I have been working on getting the Pi4 to work with the 
> 7i92 mesaflash program.
> 
> He asked me to do this but I get the error below.
> pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> lbp16_access.send_packet: Resource temporarily unavailable
> Aborted
> 
> When I do this on the PC with the same 7i92 it dumps the Pins table.  The 
> 7i92 is communicating with the board.  It can ping it.  It can
> detect what type of board it is.  But the --readhmid parameter always returns 
> this access.send_packet error.
> 
> Any ideas on how to solve this problem?  It appears to be some sort of 
> network issue.  The Pi4 has successfully run my CNC
> hardware through the 7i92 so Ethernet works.  At least from LinuxCNC to the 
> Pi.   Clearly not from the mesaflash to the pi.
> 
> To get mesaflash onto the Pi4 you have to do the following.
> pi@linuxcnc:~ $ sudo git clone http://github.com/linuxcnc/mesaflash
> pi@linuxcnc:~/mesaflash $ sudo apt-get install libpci-dev
> pi@linuxcnc:~/mesaflash $ sudo make
> 
> Once that's all done:
> pi@linuxcnc:~/mesaflash $ ./mesaflash
> Mesaflash version 3.4.0~pre1
> Configuration and diagnostic tool for Mesa Electronics PCI(E)/ETH/EPP/USB/SPI 
> boards
> Try 'mesaflash --help' for more information
> pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --addr 192.168.1.121
> ETH device 7I92 at ip=192.168.1.121
> 
> Any suggestions are welcome.
> Thanks
> John Dammeyer
> 
> 
> "ELS! Nothing else works as well for your Lathe"
> Automation Artisans Inc.
> www dot autoartisans dot com
> 
> 
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
debian@ebb:~$ cd mesaflash
debian@ebb:~/mesaflash$ sudo ./mesaflash --device 7i92 --readhmid
[sudo] password for debian: 
Configuration Name: HOSTMOT2

General configuration information:

  BoardName : MESA7I92
  FPGA Size: 9 KGates
  FPGA Pins: 144
  Number of IO Ports: 2
  Width of one I/O port: 17
  Clock Low frequency: 100. MHz
  Clock High frequency: 200. MHz
  IDROM Type: 3
  Instance Stride 0: 4
  Instance Stride 1: 64
  Register Stride 0: 256
  Register Stride 1: 256

Modules in configuration:

  Module: DPLL
  There are 1 of DPLL in configuration
  Version: 0
  Registers: 7
  BaseAddress: 7000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: WatchDog
  There are 1 of WatchDog in configuration
  Version: 0
  Registers: 3
  BaseAddress: 0C00
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: IOPort
  There are 2 of IOPort in configuration
  Version: 0
  Registers: 5
  BaseAddress: 1000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: QCount
  There are 1 of QCount in configuration
  Version: 2
  Registers: 5
  BaseAddress: 3000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: SSerial
  There are 1 of SSerial in configuration
  Version: 0
  Registers: 6
  BaseAddress: 5B00
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 64 bytes

  Module: StepGen
  There are 5 of StepGen in configuration
  Version: 2
  Registers: 10
  BaseAddress: 2000
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

  Module: LED
  There are 1 of LED in configuration
  Version: 0
  Registers: 1
  BaseAddress: 0200
  ClockFrequency: 100.000 MHz
  Register Stride: 256 bytes
  Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P2
Pin#  I/O   Pri. funcSec. func   Chan  Pin func 
   Pin Dir

 1  0   IOPort   StepGen  0Dir/Table2   
   (Out)
14  1   IOPort   StepGen  0Step/Table1  
   (Out)
 2  2   IOPort   StepGen  1Dir/Table2   
   (Out)
15  3   IOPort   StepGen  1Step/Table1  
   (Out)
 3  4   IOPort   StepGen  2Dir/Table2   
   (Out)
16  5   IOPort   StepGen  2Step/Table1  
   (Out)
 4  6   IOPort   StepGen  3Dir/Table2   
   (Out)
17  7   IOPort   StepGen  3Step/Table1  
   (Out)
 5  8   IOPort