mesaflash - default interface
13 Aug 2020 05:12 #178065
by lrak
mesaflash - default interface was created by lrak
I have things basically working - but this computer has two network interfaces -
I can ping the 7i93 with out problem .
But if the other interface is up - mesaflash can not see the card.
Using ipdown - I shut down the main LAN interface and things work.
<time passes>
I tried changing the ip address of the 7i93 to 192.168.10.10 - with the appropriate interfaces settings - no joy.
Now I can't reach the card even with the other interface down.
My hunch is mesaflash isn't using the correct interface(as in NIC card)?
I can ping the 7i93 with out problem .
But if the other interface is up - mesaflash can not see the card.
Using ipdown - I shut down the main LAN interface and things work.
<time passes>
I tried changing the ip address of the 7i93 to 192.168.10.10 - with the appropriate interfaces settings - no joy.
Now I can't reach the card even with the other interface down.
My hunch is mesaflash isn't using the correct interface(as in NIC card)?
Please Log in or Create an account to join the conversation.
13 Aug 2020 05:56 #178066
by PCW
Replied by PCW on topic mesaflash - default interface
In general, if you have two interfaces you need to guarantee that there is no
address overlap. This is why the 10.10.10.10 address is suggested for the Mesa card,
since it does not overlap normal local NAT address ranges.
address overlap. This is why the 10.10.10.10 address is suggested for the Mesa card,
since it does not overlap normal local NAT address ranges.
The following user(s) said Thank You: lrak
Please Log in or Create an account to join the conversation.
13 Aug 2020 21:26 - 13 Aug 2020 21:27 #178140
by lrak
Replied by lrak on topic mesaflash - default interface
I'm not following???
The LAN network is 192.168.1.0/24
The network for the mesa card is 192.169.10.0/24
Nothing overlaps.
The address space 192.168.0.0 – 192.168.255.255 consists of 256 contiguous class C networks - so these are clearly on different networks
If we go to 10.0.0.0 – 10.255.255.255 - it is a single class A network
So could be a limitation of mesaflash? and might be the same for linuxcnc?
I found various versions of mesaflash - there isn't a way to get a version number, but by looking at the size (code almost always gets bigger over time) the version I got from github appears to be the latest. ( I built a deb package to keep the install clean if anyone is interested).
<time passes>
I did a nmap scan and found the i793 - at 192.168.1.121
About to try again - I can use 10.10.10.10 - is there some limitation to the addresses one can set?
The LAN network is 192.168.1.0/24
The network for the mesa card is 192.169.10.0/24
Nothing overlaps.
The address space 192.168.0.0 – 192.168.255.255 consists of 256 contiguous class C networks - so these are clearly on different networks
If we go to 10.0.0.0 – 10.255.255.255 - it is a single class A network
So could be a limitation of mesaflash? and might be the same for linuxcnc?
I found various versions of mesaflash - there isn't a way to get a version number, but by looking at the size (code almost always gets bigger over time) the version I got from github appears to be the latest. ( I built a deb package to keep the install clean if anyone is interested).
<time passes>
I did a nmap scan and found the i793 - at 192.168.1.121
About to try again - I can use 10.10.10.10 - is there some limitation to the addresses one can set?
Last edit: 13 Aug 2020 21:27 by lrak.
Please Log in or Create an account to join the conversation.
13 Aug 2020 21:50 #178144
by PCW
Replied by PCW on topic mesaflash - default interface
I did not know what netmasks you were using...
I suspect the issue with not using the 10.10.10.10 range is that the 7I93s
default EEPROM netmask is not /24. (the default netmask at the hardwired
192.168.1.121 IP address is /24)
I suspect the issue with not using the 10.10.10.10 range is that the 7I93s
default EEPROM netmask is not /24. (the default netmask at the hardwired
192.168.1.121 IP address is /24)
The following user(s) said Thank You: lrak
Please Log in or Create an account to join the conversation.
14 Aug 2020 04:18 - 14 Aug 2020 04:30 #178149
by lrak
Replied by lrak on topic mesaflash - default interface
Don't think I follow you:
You said "Default EEPROM is not /24" then
"(the default netmask at the hardwired 192.168.1.121 IP address is /24)"
??
OK - out of the box - the 7i93 has W2 and W3 down - manual says "FIXED 192.168.1.121" Default
I think "FIXED" here means not DHCP? It still can be changed this the following?
$ mesaflash --device 7i93 set ip=10.10.10.10
I also tried
$ mesaflash --device 7i93 set 10.10.10.10
Without the ip= as documented via mesaflash --help
(If someone updates the --help you might want to also put a version/date code there or with a -V)
Never could set the IP to 10.10.10.10
Digging further - using --verbose - I see that while in default - but only the first time(strange) - I did change the IP for "space 2" to 192.168.10.10
More testing - could only change ip address once - don't know why. (could be that --fallback = Space 7 = default ? Or not?),
Anyway - not clear how this was supposed to work - but I now have the Ethernet to 7i93 working now with the NICs on different interfaces.
Next
I'm going to need some clues on the rest of the firmware setup - Where might I find a deb package for HOSTMOT2 or should I build my own package from github? Everything looks 4 years old?
I think the next bit would be figuring out what code should be in the 7i93 for the attached block diagram.
The verbose from mesaflash is:
For /etc/networking/interfaces.d/local
You said "Default EEPROM is not /24" then
"(the default netmask at the hardwired 192.168.1.121 IP address is /24)"
??
OK - out of the box - the 7i93 has W2 and W3 down - manual says "FIXED 192.168.1.121" Default
I think "FIXED" here means not DHCP? It still can be changed this the following?
$ mesaflash --device 7i93 set ip=10.10.10.10
I also tried
$ mesaflash --device 7i93 set 10.10.10.10
Without the ip= as documented via mesaflash --help
(If someone updates the --help you might want to also put a version/date code there or with a -V)
Never could set the IP to 10.10.10.10
Digging further - using --verbose - I see that while in default - but only the first time(strange) - I did change the IP for "space 2" to 192.168.10.10
More testing - could only change ip address once - don't know why. (could be that --fallback = Space 7 = default ? Or not?),
Anyway - not clear how this was supposed to work - but I now have the Ethernet to 7i93 working now with the NICs on different interfaces.
Next
I'm going to need some clues on the rest of the firmware setup - Where might I find a deb package for HOSTMOT2 or should I build my own package from github? Everything looks 4 years old?
I think the next bit would be figuring out what code should be in the 7i93 for the attached block diagram.
The verbose from mesaflash is:
# mesaflash --verbose --addr 192.168.10.10 --device 7i93
ETH device 7I93 at ip=192.168.10.10
Communication:
transport layer: ethernet IPv4 UDP
ip address: 192.168.10.10
mac address: 00:60:1B:14:00:4A
protocol: LBP16 version 3
Board info:
Flash size: 16Mb (id: 0x14)
Connectors count: 2
Pins per connector: 24
Connectors names: P2 P1
FPGA type: 6slx9tqg144
Number of leds: 4
Board firmware info:
memory spaces:
0: HostMot2 (registers, RW, 32-bit) [size=64K]
1: KSZ8851 (registers, RW, 16-bit) [size=256]
2: EtherEEP (EEPROM, RW, 16-bit) [size=128], page size: 1, erase size: 1
3: FPGAFlsh (flash, RW, 32-bit) [size=16M], page size: 256, erase size: 65536
4: Timers (memory, RW, 16-bit) [size=16]
6: LBP16RW (memory, RW, 16-bit) [size=16]
7: LBP16RO (memory, RO, 16-bit) [size=16]
[space 0] HostMot2
[space 2] Ethernet eeprom:
mac address: 00:60:1B:14:00:4A
ip address: 192.168.10.10
board name: 7I93
user leds: eth debug
[space 3] FPGA flash eeprom:
flash size: 16Mb (id: 0x14)
[space 4] timers:
uSTimeStampReg: 0xDC62
WaituSReg: 0x0000
HM2Timeout: 0x0000
[space 6] LBP16 control/status:
packets received: all 28, UDP 22, bad 0
packets sent: all 24, UDP 22, bad 0
parse errors: 0, mem errors 0, write errors 0
error flags: 0x0000
debug LED ptr: 0x0008
scratch: 0x0000
[space 7] LBP16 info:
board name: 7I93
LBP16 protocol version 3
board firmware version 16
IP address jumpers at boot: fixed from EEPROMFor /etc/networking/interfaces.d/local
#linuxCNC mesa interface
auto enp2s0
iface enp2s0 inet static
address 192.168.10.10/24
# address 192.168.1.240/24
# hardware−irq−coalesce−rx−usecs 0
Last edit: 14 Aug 2020 04:30 by lrak. Reason: adding detail - error on svg file..
Please Log in or Create an account to join the conversation.
14 Aug 2020 13:32 - 14 Aug 2020 13:32 #178184
by PCW
Replied by PCW on topic mesaflash - default interface
1. If you change the card IP address you need to power cycle the card and
clear the ARP cache on the host or you will not have card access. (and perhaps adjust
the hosts fixed IP address)
2. You can verify that you can change the IP address if you re-write it with
mesaflash --device somecard --addr currentaddr --set ip=n.n.n.n
and verify that the EEPROM has been updated by running
mesaflash --device somecard --verbose
_without_ power cycling or reloading the card
I just did this about 10 times without issue
The "FIXED" IP address is the 192.168.1.121 "ROM" address that cannot be changed
For your setup, the 7i93_svss4_8d.bit firmware would be appropriate, so you do not need to build any firmware. If you do , the source is here: www.mesanet.com/software/parallel/hostmot2.zip
clear the ARP cache on the host or you will not have card access. (and perhaps adjust
the hosts fixed IP address)
2. You can verify that you can change the IP address if you re-write it with
mesaflash --device somecard --addr currentaddr --set ip=n.n.n.n
and verify that the EEPROM has been updated by running
mesaflash --device somecard --verbose
_without_ power cycling or reloading the card
I just did this about 10 times without issue
The "FIXED" IP address is the 192.168.1.121 "ROM" address that cannot be changed
For your setup, the 7i93_svss4_8d.bit firmware would be appropriate, so you do not need to build any firmware. If you do , the source is here: www.mesanet.com/software/parallel/hostmot2.zip
Last edit: 14 Aug 2020 13:32 by PCW.
Please Log in or Create an account to join the conversation.
16 Aug 2020 04:17 #178349
by lrak
Replied by lrak on topic mesaflash - default interface
Thanks - I should have thought about the arp cache.. wasn't thinking.
Just to be super clear for the next guy -
When you were changing the IP which mode were you in Default or From-Eprom ? Or does it matter?
For someone following along -
Clear arp cache with
Just to be super clear for the next guy -
When you were changing the IP which mode were you in Default or From-Eprom ? Or does it matter?
W2 W3 IP ADDRESS
DOWN DOWN FIXED 192.168.1.121 ( not programable) (DEFAULT)
DOWN UP FIXED FROM EEPROMFor someone following along -
Clear arp cache with
ip -s -s neighPlease Log in or Create an account to join the conversation.
16 Aug 2020 05:46 #178353
by lrak
Replied by lrak on topic mesaflash - default interface
PCW said -
Looking at the output of :
This is from sources-list :
deb linuxcnc.org/ buster base
Not seeing 7i93 ? where would I find that package?
For your setup, the 7i93_svss4_8d.bit firmware would be appropriate, so you do not need to build any firmware.
Looking at the output of :
wajig listall hostmo
hostmot2-firmware-3x20-1 HostMot2 firmware images for Mesa 3x20-1
hostmot2-firmware-4i65 HostMot2 firmware images for Mesa 4i65
hostmot2-firmware-4i68 HostMot2 firmware images for Mesa 4i68
hostmot2-firmware-5i20 HostMot2 firmware images for Mesa 5i20
hostmot2-firmware-5i22-1 HostMot2 firmware images for Mesa 5i22-1
hostmot2-firmware-5i22-1.5 HostMot2 firmware images for Mesa 5i22-1.5
hostmot2-firmware-5i23 HostMot2 firmware images for Mesa 5i23
hostmot2-firmware-7i43-2 HostMot2 firmware images for Mesa 7i43-2
hostmot2-firmware-7i43-4 HostMot2 firmware images for Mesa 7i43-4
hostmot2-firmware-all Meta-package to install all hostmot2 firmwaresThis is from sources-list :
deb linuxcnc.org/ buster base
Not seeing 7i93 ? where would I find that package?
Please Log in or Create an account to join the conversation.
16 Aug 2020 14:05 #178407
by PCW
Replied by PCW on topic mesaflash - default interface
7I93 firmware source and bitfiles would be in the 7i93.zip file from Mesa:
www.mesanet.com/software/parallel/7i93.zip
It doesn't matter what IP address or address source you are using when you
change the EEPROM address, as long as you have access to the card
(host setup an ARP cache correct)
Possible exception is bootp, if you select bootp and don't have a bootp server,
the card will hang in a loop forever trying to get a server response
www.mesanet.com/software/parallel/7i93.zip
It doesn't matter what IP address or address source you are using when you
change the EEPROM address, as long as you have access to the card
(host setup an ARP cache correct)
Possible exception is bootp, if you select bootp and don't have a bootp server,
the card will hang in a loop forever trying to get a server response
The following user(s) said Thank You: lrak
Please Log in or Create an account to join the conversation.
- nighteagle
- Offline
- Senior Member
-
Less
More
- Posts: 72
- Thank you received: 6
09 Feb 2022 19:26 #234410
by nighteagle
Replied by nighteagle on topic mesaflash - default interface
Hello,
I'm a newbie on LinuxCNC and on MESA-Cards.
It is very difficult to find the right inforamtions - to find the right image also difficult - because if you use the wiki you find broken links and old links with very old images.
So after two times i installed a 2.8.2 Preempt RT Image.
Then i want to configure the MESA 7i97 - ant the simple things don't work.
I waste know one hour to change the ip-address - not working.
My Way:
Connect 7i97 to ethernet and 5V Power-Supply
Jumper W16 and W17 both down - means IP is 192.168.1.121
LinuxCNC have the IP 192.168.1.160/24
Have connection i think - can use the command
mesaflash --device 7i97 --vebose
And see parameters..
Then i think i can change the ip of the EEprom (Factory 10.10.10.10)
So use the command:
mesaflash --device 7i97 set ip=192.168.8.161
Response from MECA-Card:
ETH device 7i97 at ip=192.168.1.121
Okay... i use
mesaflash --device 7i97 --vebose
But ip is still 10.10.10.10 in eeprom.
Have power-cycle the card and also change the jumper to affect eeprom reading...
but it is not working.
If i ping 10.10.10.10 then is okay - but i can't connect with the card??
So how is the correct way to change the ip with the correct syntax?
I'm a newbie on LinuxCNC and on MESA-Cards.
It is very difficult to find the right inforamtions - to find the right image also difficult - because if you use the wiki you find broken links and old links with very old images.
So after two times i installed a 2.8.2 Preempt RT Image.
Then i want to configure the MESA 7i97 - ant the simple things don't work.
I waste know one hour to change the ip-address - not working.
My Way:
Connect 7i97 to ethernet and 5V Power-Supply
Jumper W16 and W17 both down - means IP is 192.168.1.121
LinuxCNC have the IP 192.168.1.160/24
Have connection i think - can use the command
mesaflash --device 7i97 --vebose
And see parameters..
Then i think i can change the ip of the EEprom (Factory 10.10.10.10)
So use the command:
mesaflash --device 7i97 set ip=192.168.8.161
Response from MECA-Card:
ETH device 7i97 at ip=192.168.1.121
Okay... i use
mesaflash --device 7i97 --vebose
But ip is still 10.10.10.10 in eeprom.
Have power-cycle the card and also change the jumper to affect eeprom reading...
but it is not working.
If i ping 10.10.10.10 then is okay - but i can't connect with the card??
So how is the correct way to change the ip with the correct syntax?
Please Log in or Create an account to join the conversation.
Time to create page: 0.165 seconds