Thread Details

  • State Verified Answer
  • Replies 6 replies
  • Subscribers 4 subscribers
  • Views 325 views
  • Users 0 members are here
Options
 
Related Content

        

            Post
             Go back to editing
        

    

    


    

    









		


















	
	
			
	
			
		
	
	
		

	    
	    
	    		
TSN IEEE 802.1AS , ADIN6310 gPTP Slave Fails to Detect/Sync to AM62 Master (BMCA Conflict)

		
	
				

			

									
					    Dhevak
					
							

            
            			
				
									
											
			
			
				
    
			
			
			    	
			                    
                
				                on Oct 6, 2025 
				
			
			
		
    
		
		                    	    
    
        	    
    Thread Summary
    
                The user is experiencing PTP synchronization failure between ADIN6310 and AM62 in Peer-to-Peer mode. The issue was resolved by configuring a valid IP address for the eth0 interface on the AM62 and correcting the destination MAC address format in ptp.cfg to use colons (01:80:C2:00:00:0E). The ADIN6310 now correctly transitions to the SLAVE state and synchronizes with the AM62 Grandmaster.
                        	    
    
                
                     AI Generated Content
                
    	    
    
             
				
        		
    
		    
		    		    
    
		      		            		        
    Category: Software
    
    		        		            		    
    Product Number:  ADIN6310 
    
    		        		        		        
    Software Version: version 5.1.0
    
    		    		    
    
		    		    
		    			
    
			    
    ADIN6310(Master) with -AM62 (as slave) (Peer-to-Peer Mode)

    ADIN 6310 as Master configuration

    ref :image 1
    

     

    Am62 configuration as Slave 

    command: ptp4l -i eth0 -H -2 -m -q -l 6 -f gptp_custom.cfg

    gptp_custom.cfg
    [global]
    transportSpecific        1
    domainNumber           0
    clientOnly                   1
    logSyncInterval          -3
    logAnnounceInterval    0
    priority1                        255
    delay_mechanism        P2P

    output status 
     Adin 6310 ref iamge 2.
    

     
     AM62 output:
        ptp4l[4534.688]: selected /dev/ptp0 as PTP clock
        ptp4l[4534.742]: port 1 (eth0): INITIALIZING to LISTENING on INIT_COMPLETE
        ptp4l[4534.742]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on INIT_COMPLET
        ptp4l[4538.549]: port 1 (eth0): LISTENING to UNCALIBRATED on RS_SLAVE
        ptp4l[4539.024]: port 1 (eth0): UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
        ptp4l[4539.650]: rms 163212 max 324892 freq -38074 +/- 14495 delay   240 +/-   0
        ptp4l[4540.650]: rms 3896 max 5970 freq -25301 +/- 5287 delay   241 +/-   0
        ptp4l[4541.650]: rms 6489 max 6804 freq -13500 +/- 1711 delay   240 +/-   0
        ptp4l[4542.649]: rms 4105 max 5459 freq -11222 +/- 166 delay   241 +/-   0
        ptp4l[4543.649]: rms 1326 max 2193 freq -12485 +/- 481 delay   240 +/-   0
        ptp4l[4544.649]: rms  237 max  369 freq -13884 +/- 302 delay   240 +/-   0
        ptp4l[4545.649]: rms  390 max  406 freq -14558 +/- 104 delay   240 +/-   0
        ptp4l[4546.649]: rms  257 max  333 freq -14715 +/-  11 delay   240 +/-   0
        ptp4l[4547.649]: rms   86 max  144 freq -14640 +/-  34 delay   240 +/-   0
        ptp4l[4548.649]: rms   24 max   33 freq -14529 +/-  23 delay   239 +/-   0
        ptp4l[4549.649]: rms   28 max   33 freq -14490 +/-   6 delay   241 +/-   0
        ptp4l[4550.649]: rms   12 max   18 freq -14493 +/-   5 delay   241 +/-   0
        ptp4l[4551.649]: rms    6 max   11 freq -14495 +/-   5 delay   241 +/-   0
        ptp4l[4552.649]: rms    6 max   11 freq -14490 +/-   5 delay   241 +/-   0
        ptp4l[4553.649]: rms    9 max   12 freq -14478 +/-   6 delay   241 +/-   0
        ptp4l[4554.649]: rms    5 max    7 freq -14487 +/-   7 delay   242 +/-   0
        ptp4l[4555.649]: rms    7 max   15 freq -14488 +/-   9 delay   242 +/-   0

    pcap LOG :
        84 7.849925 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        85 7.850069 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        86 7.974904 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        87 7.975067 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        88 7.999743 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Announce Message
        89 7.999857 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 78 Signalling Message
        90 8.000015 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
        91 8.000133 08:04:b4:31:12:42 LLDP_Multicast PTPv2 68 Peer_Delay_Resp Message
        92 8.000206 08:04:b4:31:12:42 LLDP_Multicast PTPv2 68 Peer_Delay_Resp_Follow_Up Message
        93 8.099926 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        94 8.100109 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        95 8.224866 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        96 8.225059 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        97 8.331701 08:04:b4:31:12:42 LLDP_Multicast PTPv2 68 Peer_Delay_Req Message
        98 8.331933 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Resp Message
        

    ADIN6310 with -AM62 (Peer-to-Peer Mode)

    Component                 Role    MAC Address            Sync Interval
    Grandmaster (GM)    AM62 Host    c0:d6:0a:f9:69:c9    1/8 s (125 ms)
    Network Device    ADIN6310 Switch    7a:c6:bb:11:11:13    Intended Slave/Boundary Clock

    The ADIN6310 is configured in P2P (Peer-to-Peer) mode and intended to be a Slave to the AM62 Master. 
    Synchronization is failing because the ADIN is running as a competing Master or Grandmaster (GM).

    The packet trace shows the ADIN (7a:c6:bb:11:11:13) is actively transmitting its own Sync and Follow_Up messages, 
    which should only be done by the elected GM. The AM62's Announce messages are being ignored, and the ADIN is not transitioning to the Slave state.

    ADIN 6310 as Slave configuration

    ref :image 3
    

     

    Am62 configuration as Slave 

    command: ptp4l -2 -H -i eth0 -m -l 6 -f gptp_custom_master.cfg

    gptp_custom_master.cfg

    [global]
    transportSpecific       1
    domainNumber            0
    priority1               10
    logSyncInterval         -3
    logAnnounceInterval     0
    delay_mechanism         P2P

    output status 
     
     AM62 output:
        ptp4l[1356.082]: selected /dev/ptp0 as PTP clock
        ptp4l[1356.116]: port 1 (eth0): INITIALIZING to LISTENING on INIT_COMPLETE
        ptp4l[1356.116]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on INIT_COMPLETE
        ptp4l[1356.116]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING on INIT_COMPLETE
        ptp4l[1357.919]: port 1 (eth0): new foreign master 7ac6bb.1111.110000-1
        ptp4l[1359.529]: port 1 (eth0): LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
        ptp4l[1359.529]: selected local clock 0804b4.fffe.3112ea as best master
        ptp4l[1359.529]: port 1 (eth0): assuming the grand master role
     
     Adin 6310 ref iamge 4.
    

     
     
    PCAP LOG

         30.688251 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         30.688370 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         30.813268 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         30.813323 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         30.938289 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         30.938340 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         30.961916 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 78 Signalling Message
         30.962056 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
         30.962141 c0:d6:0a:f9:69:c9 LLDP_Multicast PTPv2 68 Peer_Delay_Resp Message
         30.962184 c0:d6:0a:f9:69:c9 LLDP_Multicast PTPv2 68 Peer_Delay_Resp_Follow_Up Message
         30.962578 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Announce Message
         31.000973 c0:d6:0a:f9:69:c9 LLDP_Multicast PTPv2 68 Peer_Delay_Req Message
         31.001231 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Resp Message
         31.001330 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Resp_Follow_Up Message
         31.056993 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         31.057204 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         31.063326 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         31.063371 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         31.182004 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         31.182200 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         31.188345 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         31.188398 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         31.307013 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         31.307199 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         31.307376 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 78 Announce Message
         31.313373 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         31.313428 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         31.432004 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         31.432197 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         31.438402 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         31.438457 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         31.556998 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         31.557195 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         31.563437 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         31.563500 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         31.682008 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         31.682194 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         31.688472 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         31.688519 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         31.806995 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         31.807192 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         31.813493 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         31.813547 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         31.931989 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         31.932189 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         31.938513 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         31.938562 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         31.961865 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Announce Message
         31.961981 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 78 Signalling Message
         31.962140 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
         31.962180 c0:d6:0a:f9:69:c9 LLDP_Multicast PTPv2 68 Peer_Delay_Resp Message
         31.962216 c0:d6:0a:f9:69:c9 LLDP_Multicast PTPv2 68 Peer_Delay_Resp_Follow_Up Message
         32.000978 c0:d6:0a:f9:69:c9 LLDP_Multicast PTPv2 68 Peer_Delay_Req Message
         32.001196 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Resp Message
         32.001312 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Resp_Follow_Up Message
         32.056986 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         32.057186 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         32.063543 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         32.063592 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         32.181985 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         32.182185 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         32.188566 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         32.188615 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
         32.306990 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
         32.307183 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
         32.307395 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 78 Announce Message
         32.313594 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Sync Message
         32.313644 c0:d6:0a:f9:69:c9 IeeeI&MS_00:00:00 PTPv2 58 Follow_Up Message
    
			
    
			
									
		                                 
    Thread Notes  
    
                
    
        
                                        
                        

    
    
                                            
                 TSN
                
                                                    
                 software
                
                                                    
                 802.1AS
                
                                                    
                 ADIN6310
                
                                                    
                 version 5.1.0
                
                                
            
    
    
    
		
    

				
				        
        		
    
			
						
									
												
			
			
                        
                                    
                        
                        
                        
            
			            
						
						
			
			
			
			
		
    

        
        
        
    
					
    
			
    


    
















    
	
    
	
    
					



			


				
	









	
      
	

    • 
	
      



	
			
		
	



      
	
      
		
      
							
					
      
		
      
		    
		    		    
			
				
									
							        
			
			
			
      •  Analog Employees  
      
            
						
                            
            
            				
            
                on Oct 8, 2025 3:30 AM
            
            
						
			            		
      
		
										+1
					
	
      

		
		
      
		
      
                                
                                                            
      
					
      Hi Dhevak,

      Are you currently using software version v5.1.0?

      We tested the same scenario using v5.1.0, where a Linux PC was configured as the GM and connected to ADIN6310 physical port 2 (PTP port 3). It appears to be working well, the ADIN6310 is successfully synchronizing with the Grandmaster (Linux PC). Could you please share a Wireshark capture from your setup?

      I’m also attaching screenshots showing the configuration, where the ADIN6310 is set to TimeReceiver mode and the Linux PC is acting as the Grandmaster for your reference.

      ADIN6310 Candidate page:
       
      

      Status page:
      

       
      

      GM configuration:
      

        
      

      

      Regards,
      Himanshu
      
			
      

		
			
	      

		
		
	
      
	
      
		
      
			
		
      
	
      
	
      
		
						
				
						
						
				
				
		
		
      
			
		
      
	
      

      

      • 

	

    • 
	
      



	
		
	
	



      
	
      
		
      
							
					
      
		
      
		    
		    		    
			
				
									
							        
			
			
			
        
            
						
                            
            
            				
            
                on Oct 13, 2025 3:41 AM
            
            
												
						in reply to Hseth
					
										
			            		
        
		
										0
					
	
        

		
		
        
		
        
                                
                                                            
        
					
        Hello Himanshu,
        

        Thank you for confirming your successful test using v5.1.0. We are also using v5.1.0, the issue persists in our setup. The ADIN6310 is not synchronizing with our Grand master (AM62 linux processor) connected to physical port 2.
        

        

        ADIN configuration
        

          
        

        configuration status
        

         
        

        AM62 configuration and status
        

        ptp.cfg 

        [global]
        gmCapable                          1
        priority1                               10
        priority2                               255
        logAnnounceInterval           0
        logSyncInterval                  -3
        syncReceiptTimeout           3
        neighborPropDelayThresh   800
        min_neighbor_prop_delay -20000000
        assume_two_step              1
        path_trace_enabled           1
        follow_up_info                    1
        transportSpecific                 0x1
        ptp_dst_mac                       7A:C6:BB:11:11:13
        network_transport               L2
        delay_mechanism               P2P
        

        Command output-
        

        ptp4l -i eth0 -m -l 6 -f ptp.cfg 
        

        ptp4l[3069.217]: selected /dev/ptp0 as PTP clock
        ptp4l[3069.252]: port 1 (eth0): INITIALIZING to LISTENING on INIT_COMPLETE
        ptp4l[3069.252]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on INIT_COMPLETE
        ptp4l[3069.253]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING on INIT_COMPLETE
        ptp4l[3072.879]: port 1 (eth0): new foreign master 7ac6bb.1111.110000-1
        ptp4l[3073.153]: port 1 (eth0): LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
        ptp4l[3073.153]: selected local clock 0804b4.fffe.311242 as best master
        ptp4l[3073.153]: port 1 (eth0): assuming the grand master role
        ptp4l[3074.879]: selected best master clock 7ac6bb.1111.110000
        ptp4l[3074.879]: port 1 (eth0): assuming the grand master role
        ptp4l[3079.084]: port 1 (eth0): received SYNC without timestamp
        

        

        To help isolate the discrepancy between our setups, I have captured the network traffic also- using tcpdump.
        

        

        3280 101.698993 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3281 101.699192 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3282 101.788112 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3283 101.788199 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3284 101.823986 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3285 101.824191 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3286 101.913161 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3287 101.913252 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3288 101.948999 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3289 101.949191 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3290 101.993864 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Announce Message
        3291 101.993979 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 78 Signalling Message
        3292 101.994133 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
        3293 101.994184 08:04:b4:31:12:42 LLDP_Multicast PTPv2 68 Peer_Delay_Resp Message
        3294 101.994230 08:04:b4:31:12:42 LLDP_Multicast PTPv2 68 Peer_Delay_Resp_Follow_Up Message
        3295 102.038166 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3296 102.038202 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3297 102.073982 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3298 102.074184 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3299 102.163195 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3300 102.163235 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3301 102.199014 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3302 102.199184 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3303 102.272906 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Announce Message
        3304 102.288226 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3305 102.288284 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3306 102.323995 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3307 102.324182 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3308 102.370812 08:04:b4:31:12:42 LLDP_Multicast PTPv2 68 Peer_Delay_Req Message
        3309 102.371030 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Resp Message
        3310 102.371152 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Resp_Follow_Up Message
        3311 102.413265 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3312 102.413326 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3313 102.448979 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3314 102.449181 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3315 102.538277 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3316 102.538319 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3317 102.573974 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3318 102.574179 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3319 102.663295 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3320 102.663333 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3321 102.698975 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3322 102.699177 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3323 102.788328 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3324 102.788387 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3325 102.823971 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3326 102.824176 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3327 102.913379 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3328 102.913462 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3329 102.948970 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3330 102.949173 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3331 102.993848 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Announce Message
        3332 102.993964 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 78 Signalling Message
        3333 102.994120 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
        3334 102.994159 08:04:b4:31:12:42 LLDP_Multicast PTPv2 68 Peer_Delay_Resp Message
        3335 102.994197 08:04:b4:31:12:42 LLDP_Multicast PTPv2 68 Peer_Delay_Resp_Follow_Up Message
        3336 103.038385 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3337 103.038418 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3338 103.073972 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3339 103.074173 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3340 103.163426 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3341 103.163480 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3342 103.198966 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3343 103.199170 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3344 103.272904 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Announce Message
        3345 103.288443 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3346 103.288480 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3347 103.323970 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3348 103.324171 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3349 103.370852 08:04:b4:31:12:42 LLDP_Multicast PTPv2 68 Peer_Delay_Req Message
        3350 103.371081 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Resp Message
        3351 103.371197 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 72 Peer_Delay_Resp_Follow_Up Message
        3352 103.413480 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3353 103.413537 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3354 103.448961 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3355 103.449163 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        3356 103.538489 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 58 Sync Message
        3357 103.538525 08:04:b4:31:12:42 7a:c6:bb:11:11:13 PTPv2 90 Follow_Up Message
        3358 103.573956 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 64 Sync Message
        3359 103.574163 7a:c6:bb:11:11:13 LLDP_Multicast PTPv2 94 Follow_Up Message
        
Here i have followed your configuration but still i am facing BMCA detectetion fails,
        

        were am i going wrong.
        
			
        

		
			
	      

		
		
	
        
	
        
		
        
			
		
        
	
        
	
        
		
						
						
				
						
				
				
		
		
        
			
		
        
	
        

        

        • 

	

      • 
	
        



	
		
	
	



        
	
        
		
        
							
					
        
		
        
		    
		    		    
			
				
									
							        
			
			
			
        •  Analog Employees  
        
            
						
                            
            
            				
            
                on Oct 16, 2025 5:08 AM
            
            
												
						in reply to Dhevak
					
										
			            		
        
		
										0
					
	
        

		
		
        
		
        
                                
                                                            
        
					
        Hi Dhevak,

        Thank you for sharing the details.

        Upon reviewing attached ptp.cfg capture, I noticed that the "ptp_dst_mac" is currently set to the unicast MAC address "7A:C6:BB:11:11:13", which is not in line with the expected configuration. According to the AS2020 standard, the PTP destination MAC address should be set to "01-80-C2-00-00-0E". Using a unicast MAC address will result in the switch dropping the PTP packets, thereby preventing synchronization with the GM.

        I kindly request you to update the ptp_dst_mac to "01-80-C2-00-00-0E" as per the standard and try again.

        Regards,
        Himanshu 




        
			
        

		
			
	      

		
		
	
        
	
        
		
        
			
		
        
	
        
	
        
		
						
						
				
						
				
				
		
		
        
			
		
        
	
        

        

        • 

	

      • 
	
        



	
		
	
	



        
	
        
		
        
							
					
        
		
        
		    
		    		    
			
				
									
							        
			
			
			
          
            
						
                            
            
            				
            
                on Oct 22, 2025 6:58 AM
            
            
												
						in reply to Hseth
					
										
			            		
          
		
										0
					
	
          

		
		
          
		
          
                                
                                                            
          
					
          Hai ,
          

          i have tried the configuration u mentions but still that master not detected in ADIN
          

          Configuration -
          

          [global]
gmCapable               1
priority1               10
priority2               255
logAnnounceInterval     0
logSyncInterval         -3
syncReceiptTimeout      3
neighborPropDelayThresh   800
min_neighbor_prop_delay -20000000
assume_two_step         1
path_trace_enabled      1
follow_up_info          1
transportSpecific       0x1
ptp_dst_mac             01-80-C2-00-00-0E
network_transport       L2
delay_mechanism         P2P

 ptp4l -i eth0 -l 6 -m -q
ptp4l[2069.626]: selected /dev/ptp0 as PTP clock
ptp4l[2069.637]: port 1 (eth0): INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[2069.638]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[2069.638]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[2076.388]: port 1 (eth0): LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[2076.388]: selected local clock 0804b4.fffe.311242 as best master
ptp4l[2076.388]: port 1 (eth0): assuming the grand master role

          PACP log-

          1 0.000000 0.0.0.0 224.0.1.129 PTPv2 86 Sync Message
          2 0.000179 0.0.0.0 224.0.1.129 PTPv2 86 Follow_Up Message
          3 0.156142 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 78 Signalling Message
          4 0.156267 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
          5 1.000077 0.0.0.0 224.0.1.129 PTPv2 86 Sync Message
          6 1.000217 0.0.0.0 224.0.1.129 PTPv2 86 Follow_Up Message
          7 1.000272 0.0.0.0 224.0.1.129 PTPv2 106 Announce Message
          8 1.156055 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 78 Signalling Message
          9 1.156202 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
          10 2.000156 0.0.0.0 224.0.1.129 PTPv2 86 Sync Message
          11 2.000277 0.0.0.0 224.0.1.129 PTPv2 86 Follow_Up Message
          12 2.156093 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 78 Signalling Message
          13 2.156234 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
          14 3.000262 0.0.0.0 224.0.1.129 PTPv2 86 Sync Message
          15 3.000408 0.0.0.0 224.0.1.129 PTPv2 86 Follow_Up Message
          16 3.000468 0.0.0.0 224.0.1.129 PTPv2 106 Announce Message
          17 3.156030 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 78 Signalling Message
          18 3.156171 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
          19 4.000283 0.0.0.0 224.0.1.129 PTPv2 86 Sync Message
          20 4.000380 0.0.0.0 224.0.1.129 PTPv2 86 Follow_Up Message
          21 4.156059 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 78 Signalling Message
          22 4.156200 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
          23 5.000393 0.0.0.0 224.0.1.129 PTPv2 86 Sync Message
          24 5.000515 0.0.0.0 224.0.1.129 PTPv2 86 Follow_Up Message
          25 5.000569 0.0.0.0 224.0.1.129 PTPv2 106 Announce Message
          26 5.155999 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 78 Signalling Message
          27 5.156137 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
          28 6.000479 0.0.0.0 224.0.1.129 PTPv2 86 Sync Message
          29 6.000614 0.0.0.0 224.0.1.129 PTPv2 86 Follow_Up Message
          30 6.156039 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 78 Signalling Message
          31 6.156168 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
          32 7.000578 0.0.0.0 224.0.1.129 PTPv2 86 Sync Message
          33 7.000721 0.0.0.0 224.0.1.129 PTPv2 86 Follow_Up Message
          34 7.000778 0.0.0.0 224.0.1.129 PTPv2 106 Announce Message
          35 7.155992 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 78 Signalling Message
          36 7.156109 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message
          37 8.000677 0.0.0.0 224.0.1.129 PTPv2 86 Sync Message
          38 8.000815 0.0.0.0 224.0.1.129 PTPv2 86 Follow_Up Message
          39 8.156007 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 78 Signalling Message
          40 8.156136 7a:c6:bb:11:11:14 LLDP_Multicast PTPv2 72 Peer_Delay_Req Message

          
			
          

		
			
	      

		
		
	
          
	
          
		
          
			
		
          
	
          
	
          
		
						
						
				
						
				
				
		
		
          
			
		
          
	
          

          

          • 

	

        • 
	
          



	
		
	
	



          
	
          
		
          
							
					
          
		
          
		    
		    		    
			
				
									
							        
			
			
			
          •  Analog Employees  
          
            
						
                            
            
            				
            
                on Oct 28, 2025 1:02 AM
            
            
												
						in reply to Dhevak
					
										
			            		
          
		
										0
					
	
          

		
		
          
		
          
                                
                                                            
          
					
          Hi Dhevak,

          Thank you for sharing the configuration details.
          

          In the PCAP log, the source address appears as 0.0.0.0. Packets with this source address will be dropped by the switch.
          

          Could you please verify this behavior and try again?
          


          Regards,
          Himanshu



          
			
          

		
			
	      

		
		
	
          
	
          
		
          
			
		
          
	
          
	
          
		
						
						
				
						
				
				
		
		
          
			
		
          
	
          

          

          • 

	

        • 
	
          



	
			
		
	



          
	
          
		
          
							
					
          
		
          
		    
		    		    
			
				
									
							        
			
			
			
            
            
						
                            
            
            				
            
                on Nov 1, 2025 3:44 AM
            
            
												
						in reply to Hseth
					
										
			                            
                     Contains AI Generated Content
                
            		
            
		
										+1
					
	
            

		
		
            
		
            
                                
                                                            
            
					
            

            

            

            Hi Himanshu,
            

            Thank you for the crucial feedback regarding the 0.0.0.0 source address in the PCAP log. That insight was key to resolving the issue.
            

            I have implemented the following changes on the AM62 side:
            

              

            • 

              IP Configuration: An IP address was successfully configured for the eth0 interface on the AM62 side. This corrected the 0.0.0.0 source address problem.
              

              • 

            • 

              MAC Address Format: The destination MAC address in ptp.cfg was corrected to use colons (01:80:C2:00:00:0E) instead of hyphens (01-80-C2-00-00-0E). This ensures proper Layer 2 (Ethernet) framing, which was likely the cause of the packets being dropped or misprocessed.
              

              • 

            

            

             PTP Synchronization Status: Working Fine
            

            The result is successful PTP synchronization:
            

              

            • 

              Status Confirmation: The ADIN6310 GUI status page now correctly confirms that the Primary Clock is found and lists the AM62 clock identity (fffe.311242). The ADIN6310 has transitioned to the SECONDARY state.
              

              • 

            

            

            New PCAP Trace Data (Verification)
            

            The new PCAP trace now shows the expected PTP multicast traffic and communication:
            

            

            

            

            

            


            
PTP Message Type
Source IP
Destination IP
Key Observation

            
            


            
Announce
192.168.1.100 (AM62 Primary)
224.0.1.129 (PTP Multicast)
Confirms the AM62 is correctly advertising its clock.

            

            
Sync/Follow_Up
192.168.1.100 (AM62 Primary)
224.0.1.129 (PTP Multicast)
The essential timing messages are now being sent with a valid Source IP.

            

            
Delay_Req
<ADIN6310-IP> (ADIN6310 Secondary)
192.168.1.100 (AM62 Primary)
Confirms the ADIN6310 is actively communicating back to the AM62 Primary.

            
            

            

            

            

            

            

            

            

            

            

            

            

            

            

            

            

            

            The issue is resolved. Thank you again for pointing out the source address problem—that guided the correction of the network stack configuration.
            

            Regards, Dhevak A
            
			
            

		
			
	      

		
		
	
            
	
            
		
            
			
		
            
	
            
	
            
		
						
				
						
						
				
				
		
		
            
			
		
            
	
            

            

            •