Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 3866
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem with EM/IR simulation: port name mismatch between SPF file and schematic netlist

ykhuang

Dear all,

I encountered an issue when I tried to run EM/IR simulation. I basically followed the flow on "Voltus Fi GPDK45 DSPF RAK." I've tested this flow with a simple design and it works well. However, when I tried to run the simulation with my design, I received an error in the log file, which is ERROR (SFE-3287): Cannot run the simulation because the port number in SPF file does not match the port number in the schematic netlist.

I guess the issue is due to the usage of the bus definition for the I/O port in the circuit schematic. Some ports are defined as buses; for instance XXX<2:0>. The netlising generates the port name of XXX(0), XXX(1), and XXX(2) instead of XXX<0>, XXX<1>, and XXX<2>. Therefore, it leads to the mismatch between the DSPF port and the schematic port as you can see in the log file. 



Does anyone know how to solve this problem such that the schematic netlisting creates the correct port name? Thank you in advance!  

  • Hi,

    I'm not sure why your schematic port names have changed to ().. by any chance, are you using an extracted view for the DUT instead of schematic?

    If you don't run EMIR flow, what is the delimiter in the netlist (() or <>)? You can look for the subckt definition of your DUT in input.scs. 

    If you are still struggling with a mismatch in bus delimiters, that can be addressed by specifying the characters in bus_delim option of dspf_include command.

    dpsf_include "file.spf"  ...  bus_delim="busdelim_schematic [busdelim_parasitic]"

    In maestro view, you can set it under Simulation Files:

    

    Regards,
    

    Saloni
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
				
				
				
				
				
		
		
    
			
		
    
	
    

    

    • 

	

  • 
	
    






    
	
    
		
    
							
					
    
		
    
			
											
			
				
									
							
						
				
			
												
						in reply to Saloni Chhabra
					
									
    
	
    

		
		
    
					
    Hi Saloni,

    Many thanks for your prompt reply. The solution works. The problem is solved now. 
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
				
				
				
				
				
		
		
    
			
		
    
	
    

    

    • 

	





	
			





























    

        

            

                
Community Guidelines

                The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.