• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 751 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linker 4.9.3 doesn't generate OUTPUT file as expected -- Actually it doesn't generate any OUTPUT sections

Pashan None
Genius 5660 points


Hello Support,

I am attaching a ZIP file.

Please unzip to a folder.

Modify the COMPILER PATH Location within Linker_Output_Bug.bat file as needed for 4.9.3 and 4.6.x Linker of your PC.

Run Linker_Output_Bug.bat file.

dbcBootCAN.MAP file is output of 4.9.3 Linker which will show incorrect contents as shown below:

.boot      0    0000005c    00000000     UNINITIALIZED

dbcBootCAN464.MAP file is output of 4.6.4 Linker which will show correct contents as shown below [Just for Cross-Check]:

.boot      0    0000005c    0000e82c    
                  0000005c    0000a510     dbcBootCAN.lno (.boot_text_below_FLASH_Key:dbcBootCAN_B.lno)
                  0000a56c    00004100     dbcBootCAN.lno (.boot_text_above_FLASH_Key:dbcBootCAN_A.lno)
                  0000e66c    0000021c     dbcBootCAN.lno (.boot_start:bstartup.oba:BSW_Task.lno:dbcBootCAN_A.lno)

dbcBootCAN.lno and all the INPUT files to Linker is compiled using 4.9.3 Compiler.

Please help as there is no outpt produced in my build with 4.9.3 Compiler Toolset.

Thank you.

Regards

Pashan


 

Linker_Output_Bug.zip
  • 0
    TI__Guru**** 251180 points

    I am unable to reproduce your results.  When I try, the v4.9.3 link does produce an .out file.  

    However, I do get several diagnostic messages.  I reproduce those below.  It seems likely these diagnostics are related to your problem.  Do you want to ignore these diagnostics, or try to to address them?


    C:\ti\mytemp\Linker_Output_Bug>"C:\Program Files\Texas Instruments\ccsv4\tools\c
    ompiler\tms470\BIN\cl470.exe" --run_linker --rom_model --be32 --warn_sections --
    xml_link_info=.\dbcBootCAN_464.xml --map_file=.\dbcBootCAN_464.map --output_file
    =.\dbcBootCAN_464.out  --absolute_exe .\linkerw_ti.cmd .\linkerl_ti.cmd  .\linke
    ror_ti.cmd .\linker_ti.cmd .\linkers_ti.cmd .\dbcBootCAN.lno .\rtk_s.lib --searc
    h_path=. --library=.\Weak_Symbol_Library.lib
    <Linking>
    ".\\linker_ti.cmd", line 279: warning: section specifier matches no sections;
       potential matches are consumed by section specifier at ".\\linkerw_ti.cmd",
       line 26
    ".\\linker_ti.cmd", line 290: warning: no matching section
    ".\\linker_ti.cmd", line 352: warning: no matching section
    ".\\linker_ti.cmd", line 392: warning: no matching section
    ".\\linker_ti.cmd", line 399: warning: no matching section
    ".\\linker_ti.cmd", line 420: warning: no matching section
    ".\\linker_ti.cmd", line 488: warning: no matching section
    ".\\linker_ti.cmd", line 508: warning: no matching section
    ".\\linkers_ti.cmd", line 91: warning: no matching section
    ".\\linkers_ti.cmd", line 117: warning: no matching section
    ".\\linkers_ti.cmd", line 127: warning: no matching section
    ".\\linkers_ti.cmd", line 191: warning: no matching section
    ".\\linkers_ti.cmd", line 192: warning: no matching section
    ".\\linkers_ti.cmd", line 193: warning: no matching section
    ".\\linkers_ti.cmd", line 195: warning: no matching section
    ".\\linkers_ti.cmd", line 200: warning: no matching section
    ".\\linkers_ti.cmd", line 201: warning: no matching section
    ".\\linkers_ti.cmd", line 202: warning: no matching section
    ".\\linkers_ti.cmd", line 204: warning: no matching section
    ".\\linkers_ti.cmd", line 209: warning: no matching section
    ".\\linkers_ti.cmd", line 210: warning: no matching section
    ".\\linkers_ti.cmd", line 211: warning: no matching section
    ".\\linkers_ti.cmd", line 213: warning: no matching section
    ".\\linkers_ti.cmd", line 218: warning: no matching section
    ".\\linkers_ti.cmd", line 222: warning: no matching section
    ".\\linkers_ti.cmd", line 225: warning: no matching section
    ".\\linkers_ti.cmd", line 248: warning: no matching section
    ".\\linkers_ti.cmd", line 120: warning: section relative symbols from different
       output sections cannot be mixed; "START_OF_CAL_ROM" is in section ".calhdr",
       "DOT operator" is in section ".calftr"
    ".\\linkers_ti.cmd", line 131: warning: section relative symbols from different
       output sections cannot be mixed; "START_OF_APP_ROM" is in section
       ".opswhdr", "DOT operator" is in section ".opswftr"

    C:\ti\mytemp\Linker_Output_Bug>"C:\Program Files\Texas Instruments\TMS470 Code G
    eneration Tools 4.9.1\BIN\cl470.exe" --run_linker --rom_model --be32 --warn_sect
    ions --xml_link_info=.\dbcBootCAN.xml --map_file=.\dbcBootCAN.map --output_file=
    .\dbcBootCAN.out  --absolute_exe .\linkerw_ti.cmd .\linkerl_ti.cmd  .\linkeror_t
    i.cmd .\linker_ti.cmd .\linkers_ti.cmd .\dbcBootCAN.lno .\rtk_s.lib --search_pat
    h=. --library=.\Weak_Symbol_Library.lib
    <Linking>
    ".\linker_ti.cmd", line 279: warning: section specifier matches no sections;
       potential matches are consumed by section specifier at ".\linkerw_ti.cmd",
       line 26
    ".\linker_ti.cmd", line 290: warning: no matching section
    ".\linker_ti.cmd", line 352: warning: no matching section
    ".\linker_ti.cmd", line 392: warning: no matching section
    ".\linker_ti.cmd", line 399: warning: no matching section
    ".\linker_ti.cmd", line 420: warning: no matching section
    ".\linker_ti.cmd", line 488: warning: no matching section
    ".\linker_ti.cmd", line 508: warning: no matching section
    ".\linkers_ti.cmd", line 91: warning: no matching section
    ".\linkers_ti.cmd", line 117: warning: no matching section
    ".\linkers_ti.cmd", line 127: warning: no matching section
    ".\linkers_ti.cmd", line 191: warning: no matching section
    ".\linkers_ti.cmd", line 192: warning: no matching section
    ".\linkers_ti.cmd", line 193: warning: no matching section
    ".\linkers_ti.cmd", line 195: warning: no matching section
    ".\linkers_ti.cmd", line 200: warning: no matching section
    ".\linkers_ti.cmd", line 201: warning: no matching section
    ".\linkers_ti.cmd", line 202: warning: no matching section
    ".\linkers_ti.cmd", line 204: warning: no matching section
    ".\linkers_ti.cmd", line 209: warning: no matching section
    ".\linkers_ti.cmd", line 210: warning: no matching section
    ".\linkers_ti.cmd", line 211: warning: no matching section
    ".\linkers_ti.cmd", line 213: warning: no matching section
    ".\linkers_ti.cmd", line 218: warning: no matching section
    ".\linkers_ti.cmd", line 222: warning: no matching section
    ".\linkers_ti.cmd", line 225: warning: no matching section
    ".\linkers_ti.cmd", line 248: warning: no matching section
    ".\linkers_ti.cmd", line 120: warning: section relative symbols from different
       output sections cannot be mixed; "START_OF_CAL_ROM" is in section ".calhdr",
       "DOT operator" is in section ".calftr"
    ".\linkers_ti.cmd", line 131: warning: section relative symbols from different
       output sections cannot be mixed; "START_OF_APP_ROM" is in section
       ".opswhdr", "DOT operator" is in section ".opswftr"
    

    Thanks and regards,
    

    -George
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to George Mock
					
									
    
	
    
	                                    
                      
    
                        
                          Genius
                        5660 points
                      
    
                          
                   		
		
    
					
    Hello George,
    

    It does produce the .out file for me also.
    

    Those warnings doesn't matter.
    

    But the problem is that there is no desired output contents within .out file as expected from the input .lno files. Even you can see the MAP file, there is no output for the section .boot as I mentioned in my last e-mail.
    

    That is the problem I am saying.
    

    If you use 4.6.4 Linker, you will see Input FIle contents are there in .out file as well as in MAP file. I mentioned that in the MAIL.
    

    Let  me know if you still get the output .boot section within MAP file or .out file.
    

    In case you do get the expected .boot section contents within either MAP or .out file, please send me back all the files of yours so I can verify where the problem is on my side.
    

    Thank you.
    

    Regards
    

    Pashan
    

     
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
			
		
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Pashan None
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru****
                        251180 points
                      
    
                          
                   		
		
    
					
    Thank you for submitting a test case that clearly demonstrates the problem.  I can reproduce what you describe.  As far as I can tell, there is nothing wrong with the input files or how you are using the linker.  So, I submitted the entry SDSCM00043752 in the SDOWP system to have this looked at.  Feel free to track it with the SDOWP link below in my signature.
    

    Thanks and regards,
    

    -George
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to George Mock
					
									
    
	
    
	                                    
                      
    
                        
                          Genius
                        5660 points
                      
    
                          
                   		
		
    
					
    Hello George,
    

    I see in Clearquest that this SDSCM00043752 item is marked as DUPLICATE.
    

    So, what is the alternate DEFECT TRACKING Number I can view to understand which release of Compiler contains this BUG as fixed item?
    

    Please help with pertinent information.
    

    Thank you.
    

    Regards
    

    Pashan
    

     
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Pashan None
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru****
                        173310 points
                      
    
                          
                   		
		
    
					
    Pashan None said:
    

    I see in Clearquest that this SDSCM00043752 item is marked as DUPLICATE.
    

    So, what is the alternate DEFECT TRACKING Number I can view to understand which release of Compiler contains this BUG as fixed item?
    

    

    It is marked as a duplicate of SDSCM00043713 which is marked as fixed in CGT 4.9.6.
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    •