Products Mentioned

ADSP-BF527 Production
The high performance 16/32-bit Blackfin embedded processor core, the flexible cache architecture, the enhanced DMA subsystem, and the dynamic power management...
Datasheet
ADSP-BF527 on Analog.com

  • State Verified Answer
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 38 subscribers
  • Views 2496 views
  • Users 0 members are here
Options
Related 

        

            Post
             Go back to editing
        

    

    


    

    









		












	
	
			
	
			
		
	
	
		

		
Porting Project from VisualDSP to CrossCore, Receiving Linker Error cc3089



		

			

									
					    robert87
					
							

			
				
									
											
			
			
				
    
			
			
			    	
			                    
                
				                on Feb 14, 2013 
				
			
			
		
    

				
		
    
		    		    
		    
		    	
			
    Hello,
    
 
    I am porting a VisualDSP Project to CrossCore Embedded Studio. I used the CrossCore import VisualDSP Project 
    
 
    method. When I now want to build the project it throws out the Linker Error: "cc3089: fatal error: Link Failed". 
    
 
    Under VisualDSP it worked.
    
 
    I was first using a custom ldf File. Changing this to the automated generated ldf File, that CrossCore gives me for 
    
 
    the Blackfin 527 did not help.
    
 
    When I create just a blank Project with the Crosscore BF527 ldf File everything works fine. Only after adding my 
    
 
    own source files does the problem appear.
    
 
    When looking at the linker_log.xml it says:
    
 
    <?xml version="1.0" standalone="no"?>
    <?xml-stylesheet type="text/xsl" href="file:///C:/Analog Devices/CrossCore Embedded Studio 1.0.1/System/linker_log.xsl"?>
    <DOCUMENT gen_time='Thu Feb 14 12:34:06 2013
    '>
    <MSG id='01FF7BD8' mid='li1030' type='Error' >
    <TEXT><![CDATA[Can not open input file 'app_startup.doj'.]]></TEXT>
    </MSG>
    <MSG id='0204DB78' mid='li1032' type='Error' >
    <TEXT><![CDATA['.\.' is not a valid input file.]]></TEXT>
    </MSG>
    <MSG id='020898A0' mid='li1030' type='Error' >
    <TEXT><![CDATA[Can not open input file 'app_cplbtab.doj'.]]></TEXT>
    </MSG>
    </DOCUMENT>
    
 
    Both "app_startup.doj" and "app_cplbtab.doj" are compiled and can be opened in the Editor.
    
 

    Some further Info on used Soft- and Hardware:
    - VisualDSP++ 5.0 Update 10 tool chain
    - CrossCore Embedded Studio 1.0.1.0 Tool Version : 6.0.2.28
    - Processor: ADSP-BF527 with 16Mbit of external Flash Memory connected (via SPI-Interface)
    
 
    Maybe you can point something out to help me track the problem down. If you need further Information, please let me now.
    
 
    Sincerley,
    
 
    Robert
    
									
			        
		
    

				
						
        

    
    Tags: 
                                            
                 Audio Signal Processors
                
                                                    
                 adsp-bf527
                
                                                    
                 Blackfin Embedded Processors
                
                                
            
    
    
    

		
    
			
						
									
									
						
						
			
			
			
			
		
    

        
        

					
    
			
    


    
















    
	
    
	
    
					



			








	
	
	
	



Parents
	
      
	

    • 
	
      



	
			
		
	



      
	
      
		
      
							
					
      
		
      
			
													0
							
			
				
									
							        
			
			
			
      •  Analog Employees  
      
            
						
                            
            
            				
            
                on Feb 14, 2013 9:58 AM
            
            
					
      
	
      

		
		
      
					
      Hi Robert,
      
 
      When moving to CCES, you will need to - as you have now done - replace your LDF file, as a custom VisualDSP++ LDF will not link in CCES. Where projects use System-Builder-generated LDFs the CCES tools will replace it with a valid CCES LDF, but if you use a custom one you need to handle the replacement manually.
      
 
      Regarding the Linker error, I would recommend checking the Additional Include directories and search directories specified to the Assembler, Compiler, and Linker under the project options. In particular, it looks like there may be a ".\." path specified to one of the tools that is causing a problem. It's possible that a bad path in the project options is stopping the tools from being able to search the necessary paths for these object files.
      
 
      If the problem persists, we would likely need to take a look at the converted project. If you prefer not to provide this on a public forum, I would ask that you contact private support through the link below, and include a link to this thread.
      
 
      http://www.analog.com/support
      
 
      Regards,
      
 
      Craig.
      
			
      

		
			
	      

		
		
	
      
	
      
		
      
			
		
      
	
      
	
      
		
						
						
						
						
				
				
		
		
      
			
		
      
	
      

      

      • 

	
    



Reply

      


    • 
	
      



	
			
		
	



      
	
      
		
      
							
					
      
		
      
			
													0
							
			
				
									
							        
			
			
			
      •  Analog Employees  
      
            
						
                            
            
            				
            
                on Feb 14, 2013 9:58 AM
            
            
					
      
	
      

		
		
      
					
      Hi Robert,
      
 
      When moving to CCES, you will need to - as you have now done - replace your LDF file, as a custom VisualDSP++ LDF will not link in CCES. Where projects use System-Builder-generated LDFs the CCES tools will replace it with a valid CCES LDF, but if you use a custom one you need to handle the replacement manually.
      
 
      Regarding the Linker error, I would recommend checking the Additional Include directories and search directories specified to the Assembler, Compiler, and Linker under the project options. In particular, it looks like there may be a ".\." path specified to one of the tools that is causing a problem. It's possible that a bad path in the project options is stopping the tools from being able to search the necessary paths for these object files.
      
 
      If the problem persists, we would likely need to take a look at the converted project. If you prefer not to provide this on a public forum, I would ask that you contact private support through the link below, and include a link to this thread.
      
 
      http://www.analog.com/support
      
 
      Regards,
      
 
      Craig.
      
			
      

		
			
	      

		
		
	
      
	
      
		
      
			
		
      
	
      
	
      
		
						
						
						
						
				
				
		
		
      
			
		
      
	
      

      

      • 


    


Children
	
    No Data