Stats

  • State Not Answered
  • Replies 4
  • Subscribers 161
  • Views 3253
  • Members are here 0
More Content

Loading Footprints keep getting DB Doctor message

Sagetech

Loading new netlist into 23.1 Apparently it does not like many of the specified footprints or padstacks. I have to open the footprint in 231., save the pad stack then save the footprint. This is very time consuming and frustrating to say the least.

I also get the following message

WARNING(SPMHNI-194): Symbol 'SMD_SOD123_ANODE_PIN1' used by RefDes D30 for device 'DIODE_0_SMD_SOD123_ANODE_PIN1_1N4148W-7-F' not found. 

The symbol either does not exist in the library path (PSMPATH) or is an old symbol from a previous release.  
Set the correct library path if not set or use dbdo
     The current version of software is unable to open design smd_sod123_anode_pin1.
The design was last saved using version 16.5 and must be updated using DB Doctor. [help]


Going to DB Doctor does nothing, no option to update a footprint?

Tom


  • 0

    More info. This part is in the path directory and has had both the part itself and the pads saved in 23.1

    Symbol 'SM_S0T363' used by RefDes D49 for device 'SD103ATW_SM_S0T363_SD103ATW' not found. 

    The symbol either does not exist in the library path (PSMPATH) or is an old symbol from a previous release.  
    

    Set the correct library path if not set or use dbdoctor to migrate old symbol
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
			
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
					
    
	
    

		
		
    
					
    When I get the above messages, my only option so far is to open the footprint in 17.4, run DB Doctor on it. Save each padstack, save the part and exit from 17.4. Open 23.1, load the part, run DB Doctor on it, close the part, load the board file and import the netlist. The part will now load but I have probably 100 parts that won't and need this procedure done to get them to load.
    

    There must be a better way...........??
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
			
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to Sagetech
					
									
    
	
    

		
		
    
					
    I experienced the same situation some time ago. The problem and its solution was discussed here.
    

    There is a "separate" executable GUI version of DBDoctor in the \tools\bin (Check that - Not at my CAD computer right now) that can do batch updating of footprints.
    

    What it does is to load each symbol, perform the update and then save them in as newer version.
    

    This version supports wild cards. No need to load each footprint.
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
			
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to Sagetech
					
									
    
	
    

		
		
    
					
    Hi,
    

    With your installation there should be a dbdoctor_ui.exe. You can get that to run on all files in a folder by specifying a wildcard in the input design name
    

    E.g. C:\folder\lib\*.* 
    

    This will update all the design files in the folder specified to the version of the dbdoctor
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
			
		
    
	
    

    

    • 

	





	
			














































Cadence Guidelines







    

        

            

                
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.