7i92 firmware issue
- unknown
 - Offline
 - Platinum Member
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 731
 - Thank you received: 243
 
			
	
						11 Apr 2025 16:15				#326079
		by unknown
	
	
		
			
	
			
			 		
													
	
				7i92 firmware issue was created by unknown			
			
				Building 7i92 firmware for a custom board. I've had to play around with
Turn on board everything seems ok, user leds count packets
IP set to 192.168.1.121
Responds to pings
When jumpered for bootp an ip address is received and I can ping it.
This has me stumped 7i92 mac is ff:ff:ff:ff:ff:ff
$ mesaflash --device 7i92 --addr 192.168.1.121 --verbose
Unsupported ethernet device ��������������������z at 192.168.1.121
No 7I92 board found
��������������������z bit will change on each mesaflash run
Wireshark dump
32 7.057855358 192.168.1.20 192.168.1.121 UDP 46 50697 → 27181 Len=4
Frame 32: 46 bytes on wire (368 bits), 46 bytes captured (368 bits) on interface ens5, id 0
Ethernet II, Src: UniversalGlo_3e:7d:ac (cc:52:af:3e:7d:ac), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 192.168.1.20, Dst: 192.168.1.121
User Datagram Protocol, Src Port: 50697, Dst Port: 27181
Data (4 bytes)
Data: 01420001
[Length: 4]
33 7.058018908 192.168.1.121 192.168.1.20 UDP 60 27181 → 50697 Len=4
Frame 33: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface ens5, id 0
Ethernet II, Src: Broadcast (ff:ff:ff:ff:ff:ff), Dst: UniversalGlo_3e:7d:ac (cc:52:af:3e:7d:ac)
Internet Protocol Version 4, Src: 192.168.1.121, Dst: 192.168.1.20
User Datagram Protocol, Src Port: 27181, Dst Port: 50697
Data (4 bytes)
Data: fecaaa55
[Length: 4]
34 7.060132328 192.168.1.20 192.168.1.121 UDP 46 50697 → 27181 Len=4
Frame 34: 46 bytes on wire (368 bits), 46 bytes captured (368 bits) on interface ens5, id 0
Ethernet II, Src: UniversalGlo_3e:7d:ac (cc:52:af:3e:7d:ac), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 192.168.1.20, Dst: 192.168.1.121
User Datagram Protocol, Src Port: 50697, Dst Port: 27181
Data (4 bytes)
Data: 885d0000
[Length: 4]
35 7.060285405 192.168.1.121 192.168.1.20 UDP 60 27181 → 50697 Len=16
Frame 35: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface ens5, id 0
Ethernet II, Src: Broadcast (ff:ff:ff:ff:ff:ff), Dst: UniversalGlo_3e:7d:ac (cc:52:af:3e:7d:ac)
Internet Protocol Version 4, Src: 192.168.1.121, Dst: 192.168.1.20
User Datagram Protocol, Src Port: 27181, Dst Port: 50697
Data (16 bytes)
Data: ffffffffffffffffffffffffffffffff
[Length: 16]
I'm guessing the data in the last packet isn't right.
 			
					Turn on board everything seems ok, user leds count packets
IP set to 192.168.1.121
Responds to pings
When jumpered for bootp an ip address is received and I can ping it.
This has me stumped 7i92 mac is ff:ff:ff:ff:ff:ff
$ mesaflash --device 7i92 --addr 192.168.1.121 --verbose
Unsupported ethernet device ��������������������z at 192.168.1.121
No 7I92 board found
��������������������z bit will change on each mesaflash run
Wireshark dump
32 7.057855358 192.168.1.20 192.168.1.121 UDP 46 50697 → 27181 Len=4
Frame 32: 46 bytes on wire (368 bits), 46 bytes captured (368 bits) on interface ens5, id 0
Ethernet II, Src: UniversalGlo_3e:7d:ac (cc:52:af:3e:7d:ac), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 192.168.1.20, Dst: 192.168.1.121
User Datagram Protocol, Src Port: 50697, Dst Port: 27181
Data (4 bytes)
Data: 01420001
[Length: 4]
33 7.058018908 192.168.1.121 192.168.1.20 UDP 60 27181 → 50697 Len=4
Frame 33: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface ens5, id 0
Ethernet II, Src: Broadcast (ff:ff:ff:ff:ff:ff), Dst: UniversalGlo_3e:7d:ac (cc:52:af:3e:7d:ac)
Internet Protocol Version 4, Src: 192.168.1.121, Dst: 192.168.1.20
User Datagram Protocol, Src Port: 27181, Dst Port: 50697
Data (4 bytes)
Data: fecaaa55
[Length: 4]
34 7.060132328 192.168.1.20 192.168.1.121 UDP 46 50697 → 27181 Len=4
Frame 34: 46 bytes on wire (368 bits), 46 bytes captured (368 bits) on interface ens5, id 0
Ethernet II, Src: UniversalGlo_3e:7d:ac (cc:52:af:3e:7d:ac), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 192.168.1.20, Dst: 192.168.1.121
User Datagram Protocol, Src Port: 50697, Dst Port: 27181
Data (4 bytes)
Data: 885d0000
[Length: 4]
35 7.060285405 192.168.1.121 192.168.1.20 UDP 60 27181 → 50697 Len=16
Frame 35: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface ens5, id 0
Ethernet II, Src: Broadcast (ff:ff:ff:ff:ff:ff), Dst: UniversalGlo_3e:7d:ac (cc:52:af:3e:7d:ac)
Internet Protocol Version 4, Src: 192.168.1.121, Dst: 192.168.1.20
User Datagram Protocol, Src Port: 27181, Dst Port: 50697
Data (16 bytes)
Data: ffffffffffffffffffffffffffffffff
[Length: 16]
I'm guessing the data in the last packet isn't right.
Please Log in or Create an account to join the conversation.
- PCW
 - 
				
											 - Offline
 - Moderator
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 17380
 - Thank you received: 5068
 
			
	
						11 Apr 2025 16:26				#326081
		by PCW
	
	
		
			
	
			
			 		
													
	
				Replied by PCW on topic 7i92 firmware issue			
			
				Sounds like the MAC/cardname/ipaddress/netmask EEPROM has not been programmed			
					Please Log in or Create an account to join the conversation.
- unknown
 - Offline
 - Platinum Member
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 731
 - Thank you received: 243
 
			
	
						11 Apr 2025 16:47				#326085
		by unknown
	
	
		
			
	
			
			 		
													
	
				Replied by unknown on topic 7i92 firmware issue			
			
				Ok much appreciated.
It's 2:45am I best be getting some sleep.
Guess I'll swap the eeprom.
					It's 2:45am I best be getting some sleep.
Guess I'll swap the eeprom.
Please Log in or Create an account to join the conversation.
- PCW
 - 
				
											 - Offline
 - Moderator
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 17380
 - Thank you received: 5068
 
			
	
						11 Apr 2025 20:17		 -  11 Apr 2025 20:27		#326106
		by PCW
	
	
		
			
	
	
			 		
													
	
				Replied by PCW on topic 7i92 firmware issue			
			
				I'm not so much suggesting that the EEPROM is bad, but rather
that the EEPROM is empty. (never been programmed)
					that the EEPROM is empty. (never been programmed)
		Last edit: 11 Apr 2025 20:27  by PCW.			
			Please Log in or Create an account to join the conversation.
- unknown
 - Offline
 - Platinum Member
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 731
 - Thank you received: 243
 
			
	
						11 Apr 2025 20:27				#326109
		by unknown
	
	
		
			
	
			
			 		
													
	
				Replied by unknown on topic 7i92 firmware issue			
			
				Oh the 93c46 has to be programmed separately ?
I thought the firmware did that
					I thought the firmware did that
Please Log in or Create an account to join the conversation.
- unknown
 - Offline
 - Platinum Member
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 731
 - Thank you received: 243
 
			
	
						11 Apr 2025 20:38				#326111
		by unknown
	
	
		
			
	
			
			 		
													
	
				Replied by unknown on topic 7i92 firmware issue			
			
				I understand now, silly me.
Ok found I had to use setname & found the Linux version here
www.forum.linuxcnc.org/27-driver-boards/...board?start=10#65737
and I can communicate.
Thanks again
					Ok found I had to use setname & found the Linux version here
www.forum.linuxcnc.org/27-driver-boards/...board?start=10#65737
and I can communicate.
Thanks again
Please Log in or Create an account to join the conversation.
- PCW
 - 
				
											 - Offline
 - Moderator
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 17380
 - Thank you received: 5068
 
			
	
						11 Apr 2025 21:09				#326113
		by PCW
	
	
		
			
	
			
			 		
													
	
				Replied by PCW on topic 7i92 firmware issue			
			
				Here's a more complete set of utilities:
( note that you should not use Mesa's MAC in the addresses in the scripts )
freeby.mesanet.com/unixfpgainit.zip
 			
					( note that you should not use Mesa's MAC in the addresses in the scripts )
freeby.mesanet.com/unixfpgainit.zip
Please Log in or Create an account to join the conversation.
- unknown
 - Offline
 - Platinum Member
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 731
 - Thank you received: 243
 
			
	
						12 Apr 2025 00:02				#326132
		by unknown
	
	
		
			
	
			
			 		
													
	
				Replied by unknown on topic 7i92 firmware issue			
			
				Wow thanks Pete, was just thinking about how to do this. I really think I owe you a few beers.
Another question, if I may.
[/code]./setmac 00601B168$1/[code]
What's the format for the MAC ?
					Another question, if I may.
[/code]./setmac 00601B168$1/[code]
What's the format for the MAC ?
Please Log in or Create an account to join the conversation.
- PCW
 - 
				
											 - Offline
 - Moderator
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 17380
 - Thank you received: 5068
 
			
	
						12 Apr 2025 00:11				#326133
		by PCW
	
	
		
			
	
			
			 		
													
	
				Replied by PCW on topic 7i92 firmware issue			
			
				12 hex characters (this is from an initialization script so the
last three characters (the $1) are supplied on the command line
that is:
./setmac 00123456789A
etc
Note that "00601B" is Mesas range
					last three characters (the $1) are supplied on the command line
that is:
./setmac 00123456789A
etc
Note that "00601B" is Mesas range
Please Log in or Create an account to join the conversation.
- unknown
 - Offline
 - Platinum Member
 - 
				
			 
		Less
		More
		
			
	
		- Posts: 731
 - Thank you received: 243
 
			
	
						12 Apr 2025 00:44		 -  12 Apr 2025 00:57		#326134
		by unknown
	
	
		
			
	
	
			 		
													
	
				Replied by unknown on topic 7i92 firmware issue			
			
				./newmac: line 8: ./setmac: Text file busy
Reseting Ethernet CPU
waiting for reset
./newmac: line 14: ./setmac: Text file busy
Is that a worry ? Or is that due to network latency ?
Board is behind a switch and I'm working on a laptop connect via wifi, I can ping and readhmid with mesa flash ok
I used ./setmac 00123456789A in the script
Dumb me I should have sourced the file. All is good.
					Reseting Ethernet CPU
waiting for reset
./newmac: line 14: ./setmac: Text file busy
Is that a worry ? Or is that due to network latency ?
Board is behind a switch and I'm working on a laptop connect via wifi, I can ping and readhmid with mesa flash ok
I used ./setmac 00123456789A in the script
Dumb me I should have sourced the file. All is good.
		Last edit: 12 Apr 2025 00:57  by unknown.		Reason: I forgot how to Linux	
			Please Log in or Create an account to join the conversation.
		Moderators: PCW, jmelson	
		Time to create page: 0.103 seconds