• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 30 subscribers
  • Views 382 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.

LP-AM243: IPC_RPmsg_echo example in MCU+SDK is not compiling

Aditya Patel
Prodigy 65 points
Part Number: LP-AM243
Other Parts Discussed in Thread: SYSCONFIG, AM2434

Hi everyone,

I am new to TI microcontrollers ecosystem.I recently started reading about implementing IPC inter-processor communication on my TI AM243xLP board. So i tried to import the example given in the sdk.

Link: https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/EXAMPLES_DRIVERS_IPC_RPMESSAGE_ECHO.html  

When i try to make the imported example i get the following error.

The error is in the config fiile produced by the sysconfig GUI, I havent edited anything inside  source code or sysconfig GUI.

Pleas help me , Thank you in Advance.

  • 0
    TI__Mastermind 46626 points

    Hello Aditya Patel,

    I was on training last week and yesterday was on leave.

    I am catching up all pending issues along with by them looking at your queries, and please give me two or three days to get back to you.

    Regards,

    Anil.

  • 0 in reply to Swargam Anil
    TI__Mastermind 46626 points

    Hello Aditya Patel,

    Sorry for delayed replies.

    Can you please first build the system project rather than build individual projects ?

    Actually, we mostly use the linker cmd files to store variables and code at different memory locations.

    But, recently users have no need to update the linker cmd file instead of that it can be configured from the system cfg file.

    So, current issue with the linker file is not properly generated for IPC memories  .

    Regards,

    Anil.

  • 0 in reply to Swargam Anil
    Prodigy 65 points

    Hello Swargam Anil,

    thank you for your response. I tried to build the system project and there were no linker errors, can you tell me how can i load this example and run it successfully. 

    Thank you in advance.

    Regards,

    Aditya

  • +1 in reply to Aditya Patel
    TI__Mastermind 46626 points

    Hey Adithya,

    Sorry for delayed reply as I was busy in other escalations .

    Good to hear that you have solved the issue.

    Now, loading examples from CCS is easy.

    Just connect to the debugger and connect to each core and load .out file from CCS and run it.

    The chapter below is helpful to load .out files from CCS.

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/09_02_00_50/exports/docs/api_guide_am243x/CCS_LAUNCH_PAGE.html

    Before doing above step, you need to do SOC initializations. If you have already done this step then directly load .out files from the CCS, else you can try to initialize the board with SBL null which will initialize the cores.

    So, then you can connect to the debugger and load all .out files from CCS.

    To initilize the board with the SBL null , you need to go chapter below .

    default_sbl_ospi.cfg - > Here, use sbl_null.cfg file instead of default_sbl_ospi. cfg file

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/09_02_00_50/exports/docs/api_guide_am243x/GETTING_STARTED_FLASH.html

    

    Regards,
    

    Anil.
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Swargam Anil
					
									
    
	
    
	                                    
                      
    
                        
                          Prodigy
                        65 points
                      
    
                          
                   		
		
    
					
    Hi Anil,
    

    sorry for delayed response. i tried to  debug the system project but i get this error:

    MAIN_Cortex_R5_0_0: AM2434_ALX
    MAIN_Cortex_R5_0_0: GEL Output: CPU reset (soft reset) has been issued through GEL.
    MAIN_Cortex_R5_0_1: AM2434_ALX
    MAIN_Cortex_R5_0_1: GEL Output: CPU reset (soft reset) has been issued through GEL.
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 
    MAIN_Cortex_R5_1_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130) 

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
			
		
	









    
	
    
		
    
							
					
    
		
    
			
													+1
							
			
				
									
							
						
				
			
			
			
												
						in reply to Aditya Patel
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Mastermind
                        46626 points
                      
    
                          
                   		
		
    
					
    Hello Adithya,
    

    

    Based on the above error, there might be problems with Core Initializations or jtag cable connection.
    

    Can you please confirm how did you do the SOC initializations ?
    

    If you use sbl_null, then there are no issues, your sbl null will initialize the cores, and later you are able to connect jtag to all cores.
    

    Even with sbl_null, you have problems while connecting the jtag , then power off → remove jtag cable → power on → connect jtag  cable.
    

    If you don't flash the sbl_null for SOC initializations, please use sbl_null.cfg instead of sbl_ospi.cfg and remaing procedure same as sbl_ospi.
    

    Please look at link below  for more details about flashing support.
    

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/GETTING_STARTED_FLASH.html
    

    

    Regards,
    

    Anil.
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Swargam Anil
					
									
    
	
    
	                                    
                      
    
                        
                          Prodigy
                        65 points
                      
    
                          
                   		
		
    
					
    Hi Anil,
    

    i was debuging the entire program instead of loading program to specific cores.The problem is solved , Thanks a lot for your support.

    Kind Regards,
    

    Aditya
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    •