• State TI Thinks Resolved
  • Locked Locked
  • Replies 20 replies
  • Answers 2 answers
  • Subscribers 84 subscribers
  • Views 2559 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.

TMS320F28377D: Unable to flash brand new MCU

Dainius Narsutis57
Intellectual 495 points
Part Number: TMS320F28377D
Other Parts Discussed in Thread: C2000WARE

Hi,

You are my last hope, been pulling my hair out for last couple of weeks. Got 6 brand new boards built with TMS320F28377D on them, 2 - work, 4 don't. Replaced MCU on one of the boards that did not work - still does not work. Got some very expensive software to rule out JTAG issues - JTAG is fine. Power supplies are fine. +3V3, +1V2 are fine. Grounding is fine. No shorts detected. Nothing is warming up that should not. I can control IOs via the JTAG software.

So down the rabbit hole I go.

1. Set Boot mode pins (GPIO72,GPIO84) to 1,0 respectively to get the MCU into WAIT mode and try to flash the firmware. Output I get is 

C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
C28xx_CPU1: Writing Flash @ Address 0x00080000 of Length 0x00000008 (page 0)
C28xx_CPU1: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Trouble Halting Target CPU: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00130@Program: target is not connected
C28xx_CPU1: PLL configuration status = 0.
C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\ProjectFiles\rimac\obc\src\clp\obc\ccs\OBC_A_Debug\obc.out: Load failed.
C28xx_CPU1: Error occurred during flash operation: Could not read register PC: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash.  If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5D200@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D22E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D214@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash.  If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected

At no point power supplies trip or go low - very unsure as to why the target it not connected.

2. Instead of flashing code, connecting to the MCU via debugger to see what is happening inside (Using the same .ccxml as the Debug Configuration).

I Launched the .ccxml from the Target Configurations in CSS and Connected to the CPU 1 core. Great. Do System Reset then CPU Reset.

Looking at the Disassembly tab, I can see that the Program Counter is at 0x003FF16A. Looking at the Delfino user manual, it seems that this is somewhere within the Secure ROM area.

I let the code execute and it gets itself into ESTOP0, the Program Counter is at 0x003FE2ED which is within the Boot ROM space. The MemoryErrRegs, RomWaitStateRegs and RomPrefetchRegs registers are all 0s.

RESC register shows that XRSn and TRSTn are 1, everything else is 0.

I am using Blackhawk USB560-v2 Debugger, but I tried XDS200 too and it is the same issue.

3. Return Boot Mode pins both to HIGH, so the Boot ROM jumps to Boot from Flash instead of Wait.

Again, Launch Target Configuration connecting to the target, System Reset, CPU Reset, let the code to execute, it stops at ITRAP0 @0x0 from 0x0F189 (GS3 RAM)?

So, what is going on here? I am lost. Any advise on what I am doing wrong, what could be causing what I am seeing would be much appreciated. I can flash the same code with the exact same tools on the other 2 boards and they work, but these 4 are just dead.

Much appreciated


								


				
				

				
			

		

			
						
									
                			    			                        
						
						
			
			
						
			                        
			
			
				
			  
			

			     
			

		


				    			

						
















	

	

					
    
	
    





		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
					
    
	
    
	                                    
                      
    
                        
                          TI__Guru*
                        87145 points
                      
    
                          
                   		
		
    
					
    Dainius,
    

    Which version of CCS are you using? 
    

    Did you try to check for updates in CCS and install the available updates? Please try.
    

    Please take a look at https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/729543?-FAQ-Product-Change-Notice-PCN-20180523001-1-for-TMS320F2837x-and-TMS320F2807x-devices
    

    Thanks and regards,
    Vamsi
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Vamsi Gudivada
					
									
    
	
    
	                                    
                      
    
                        
                          Intellectual
                        495 points
                      
    
                          
                   		
		
    
					
    Hi Vamsi,
    

    I am using:
    

      

    • CCS: 9.1.0.00010
      • 

    • C2000 Device Support 5.0.0.0
      • 

    • Debug Server Flash 9.1.0.1682
      • 

    • Debug Server 9.1.0.1682
      • 

    

    These versions seem to be above the ones stated in your provided link. Thank you.
    

    I had a look at the PARTIDL_1 and PARTIDH_1 registers. This is what I found. Green - Flashed, Red No _Flash.
    

    


    
Board 1
0x10077E80
0x00FF0300

    

    
Board 2
0x10077E80
0x00FF0300

    

    
Board 3
0x10077E80
0x00FF0300

    

    




    
    

    

    I tried to program the Board 3 and I got this:
    

    C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: Flash Programmer: Warning: The configured device (TMS320F28377D), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx_CPU1: Writing Flash @ Address 0x00080000 of Length 0x00000008 (page 0)
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc0eb: (Error -1066 @ 0xC0EB) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: PLL configuration status = 49387.
C28xx_CPU1: Error writing the PLL values. (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: firmware.out: Load failed.
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    

    

    Where do I check which flashing method I am using?
    

    

    Kind regards
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
			
		
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru*
                        87145 points
                      
    
                          
                   		
		
    
					
    Dainius,
    

    Thank you for the update.
    

    Error tells me that the Device Identification registers read by Flash Plugin are incorrect.  In debugger memory window, can you open the memory browser to locations 0x700B0 and 0x700B1 and tell me the values you see there?  In the past, similar debugs ended up as board issues on customers' side (same case - where some boards were fine but others were failing).  Please double check everything on your side.        
    

    Few more things to check:
    

    1. Did you try to update the emulator driver? Please try if not already.
    

    2. Do you see a toggle on the XRSn when you see the Flash operation failure? Asking in case there is a dip in voltage lines during Flash operation.
    

    3. Did you change any settings in the Flash Plugin GUI? OR Are you using the default settings? Like PLL etc. 
    

    

    

    Regarding your question "Where do I check which flashing method I am using?" - I did not understand your question, You are using CCS Flash Plugin.
    

    Thanks and regards,
    Vamsi
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Vamsi Gudivada
					
									
    
	
    
	                                    
                      
    
                        
                          Intellectual
                        495 points
                      
    
                          
                   		
		
    
					
    Hi Vamsi,
    

    On the board that I can flash Memory locations 0x0700B0 and 0x0700B1 have values 0x5303 and 0x7715 respectively.
    On the board that I cannot flash the Memory locations 0x0700B0 and 0x0700B1 have values 0x06BE and 0x7715 respectively.
    

    So I re-checked both MCUs and now the memory locations have the same values on both MCUs: 0x5305 and 0x7715. I still can only flash one of the boards.
    

    I've also noticed that sometimes the value in register 0x700B0 will be 0x0200 on the board that does not flash.
    

    I scoped the XRS line and it was not dropping as I was trying to flash. However When the Boot Mode pins are HIGH the XRS line does this strange pulsing
    

     
    

    I have already updated emulator driver for the USB560-v2. The debugger is using firmware v5.0.573.0 and the Windows Driver is 1.1.0.13.
    

    I have opened the .ccxml file I normally use and clicked the "Restore Defaults" to rule out any erroneus changes I may have made. Still no flash.
    

    edit:
    

    I've taken the blinky project from C2000Ware_2_00_00_02, changed .ccxml to use my Blackhawk and the Blinky Flashed! Great. At this point Boot Mode pins are set to WAIT mode.
    

    If I let the program execute, the debugger seems to disconnect? I see this
    

    

     
    

    The 1V2 does not drop, the 3V3 also does not drop.
    

    I looked the Crystal traces on my PC, I can see 10MHz traces look ok.
    

     
    

    

    I changed Boot Mode pins to to HIGH, so the firmware boots form flash. It cannot write to Flash.
    

    

    When I try to write to Flash I get this
    

    C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: Flash Programmer: Warning: The configured device (TMS320F28377D), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc0eb: (Error -1066 @ 0xC0EB) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Error writing the PLL values. (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\ti\c2000\C2000Ware_2_00_00_02\device_support\f2837xd\examples\cpu1\blinky\cpu01\ccs\CPU1_FLASH\blinky_cpu01.out: Load failed.
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
    

    

    And when I try to use RAM target, the CPU disconnect with No Power/Clock.
    

    

    Sometimes I see this message when trying to run from RAM.
    

    C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: Flash Programmer: Warning: The configured device (TMS320F28377D), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx_CPU1: File Loader: Verification failed: Values at address 0x00000@Program do not match Please verify target memory and memory map.
C28xx_CPU1: GEL: File: C:\ti\c2000\C2000Ware_2_00_00_02\device_support\f2837xd\examples\cpu1\blinky\cpu01\ccs\CPU1_RAM\blinky_cpu01.out: a data verification error occurred, file load failed.

    

    

    Kind regards
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Vamsi Gudivada
					
									
    
	
    
	                                    
                      
    
                        
                          Intellectual
                        495 points
                      
    
                          
                   		
		
    
					
    I am looking a little more in depth at the Device Identification registers on the MCU that I cannot flash. The values do not seem to match the datasheet.
    

     
    

    When I look at the Register, I see this
    

     
    

    It thinks, its a Single Core with 2 EPWM modules?
    

    For comparison, here are the register values for a MCU that I can flash.
    

     
    

    It seems that the data is shifted incorrectly on the non-working MCU which corrupts the Boot process?
    

    

    edit:
    

    Connected to another board that cannot be flashed and the Device identification seems to be corrupt too.
    

     
    

    Kind regards
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru*
                        87145 points
                      
    
                          
                   		
		
    
					
    Dainius,
    

    Thank you for all the info that you provided.
    

    To help you further, I will forward this info (and assign this post) to corresponding experts to check if there is any issue in the Device configuration registers.  
    

    Thanks and regards,
    Vamsi
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Vamsi Gudivada
					
									
    
	
    
	                                    
                      
    
                        
                          Intellectual
                        495 points
                      
    
                          
                   		
		
    
					
    Vamsi,
    

    Thank you. I can also do data dumps if required in helping troubleshoot these issues.
    

    

    Kind regards,
    

    

    Dainius
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru*
                        87145 points
                      
    
                          
                   		
		
    
					
    Dainius,
    

    Ok, our system control expert will ask for them as needed.
    

    Thanks and regards,
    Vamsi
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru**
                        115191 points
                      
    
                          
                   		
		
    
					
    Hi,
    

    Did you reset the board and run the BOOTROM before reading the DCx register. It look like the BOOTROM has not run hence all the values are not populated. After connecting the CCS, issue debug reset from CCS and then click the run icon and after CPU halts, read the DCx register.
    

    Regards,
    

    Vivek Singh
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Vivek Singh
					
									
    
	
    
	                                    
                      
    
                        
                          Intellectual
                        495 points
                      
    
                          
                   		
		
    
					
    Hi Vivek,
    

    Thank you for your input, these are the steps I've carried out:
    

    Launch Target
    

     
    

    Connect tot CPU 1
    

     
    

    

    When the debugger connect to the core, the CPU seems to be reset and the debugger stops at specific memory location.
    

     
    

    

    I then manually pull the XRS line low to reset the device and debugger shows updated registers. Execution starts from the same place too.
    

     
    

    

    When I press the Run button on CCS, the execution gets into ESTOP0 loop.
    

     
    

    

    I can see however that this time the Device Information registers are also configured as the other boards that I can flash.
    

    

    My Boot pins are both HIGH.
    

    

    Kind regards,
    

    Dainius
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru**
                        115191 points
                      
    
                          
                   		
		
    
					
    Hi,
    

    Good. So device configuration is same on both board which is expected. Now, on the board which you are not able to flash, can you try loading the code after all the steps are performed (as you mentioned in post) and device configuration register have proper value. If that works then you need to change the BOOTMODE pin setting so that it's not BOOT to flash (1/1) and try flashing the board again after power-up.
    

    Regards,
    

    Vivek Singh
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Vivek Singh
					
									
    
	
    
	                                    
                      
    
                        
                          Intellectual
                        495 points
                      
    
                          
                   		
		
    
					
    Hi Vivek,
    

    

    So I got to the same stage, of getting to the debugger and connecting to the core. I let the Boot ROM execute by pressing the Run button. The execution stopped at the ESTOP again.
    

    Then I used the Load Program Dialog in CCS and selected my .out file. This is the output I got:
    

    C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: Flash Programmer: Warning: The configured device (TMS320F28377D), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx_CPU1: Writing Flash @ Address 0x00080000 of Length 0x00000008 (page 0)
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc0eb: (Error -1066 @ 0xC0EB) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: PLL configuration status = 49387.
C28xx_CPU1: Error writing the PLL values. (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: fw.out: Load failed.
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    

    After this I change Boot mode pins to 1/0 (WAIT) and did the exact same steps using the Load Program dialog in CCS. This is the output I got.
    

    C28xx_CPU1: Writing Flash @ Address 0x00080000 of Length 0x00000008 (page 0)
C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00130@Program: target is not connected
C28xx_CPU1: PLL configuration status = 0.
C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: fw.out: Load failed.
C28xx_CPU1: Error occurred during flash operation: Could not read register PC: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005FC00@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash.  If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D22E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D214@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash.  If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected


    edit:

    Just for completion I looked at the 0x00800000 address and all memory after it is all 0xFFFF.

     
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru**
                        115191 points
                      
    
                          
                   		
		
    
					
    Can you check the value in RESC register and NMISHDGLF register after you see the error message ?
    

    Vivek Singh
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Vivek Singh
					
									
    
	
    
	                                    
                      
    
                        
                          Intellectual
                        495 points
                      
    
                          
                   		
		
    
					
    Hi,
    

    

    Here are the RESC registers.
    

     
    

    

    And NMISHDGLF
    

     
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru**
                        115191 points
                      
    
                          
                   		
		
    
					
    Values in NMISHDFLG does not make sense. It can be 0xFFFF. Reset value for this one is 0x0 and we can not have all the error status bit set to '1'. Can you check this again.
    

    Regards
    

    Vivek Singh
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Vivek Singh
					
									
    
	
    
	                                    
                      
    
                        
                          Intellectual
                        495 points
                      
    
                          
                   		
		
    
					
    Vivek,
    

    

    I retried, these are the values after I reset the MCU via CCS.
    

     
    

    These are the values when I try to Load Program via CCS.
    

     
    

    The console output is this
    

    C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: Flash Programmer: Warning: The configured device (TMS320F28377D), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx_CPU1: Writing Flash @ Address 0x00080000 of Length 0x00000008 (page 0)
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc0eb: (Error -1066 @ 0xC0EB) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: PLL configuration status = 49387.
C28xx_CPU1: Error writing the PLL values. (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\ProjectFiles\rimac\obc\src\clp\obc\ccs\OBC_A_Debug\obc.out: Load failed.
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Writing Flash @ Address 0x00080000 of Length 0x00000008 (page 0)
C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Trouble Halting Target CPU: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00130@Program: target is not connected
C28xx_CPU1: PLL configuration status = 0.
C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\ProjectFiles\rimac\obc\src\clp\obc\ccs\OBC_A_Debug\obc.out: Load failed.
C28xx_CPU1: Error occurred during flash operation: Could not read register PC: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005FC00@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash.  If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D22E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D214@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash.  If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
			
		
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru**
                        115191 points
                      
    
                          
                   		
		
    
					
    Sorry, but it's bit confusing. Earlier you had very different values and now it look correct. What has changed from earlier setup to this one? If you are getting different value each time then setup is not robust.
    

    Also from below message it look like device ID is not getting read properly but earlier we saw it was ok. 
    

    C28xx_CPU1: Flash Programmer: Warning: The configured device (TMS320F28377D), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file. 
    

    C28xx_CPU1: Writing Flash @ Address 0x00080000 of Length 0x00000008 (page 0) 
    

    

    Have you checked the power supply on board to make sure it's not dipping below spec? 
    

    

    Regards,
    

    Vivek Singh
    

    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Vivek Singh
					
									
    
	
    
	                                    
                      
    
                        
                          Intellectual
                        495 points
                      
    
                          
                   		
		
    
					
    I have taken extreme measures and moved the MCU I cannot flash onto another board that I do know works. When I moved the MCU, it functions as expected. I can flash it with no problems.
    

    I have escalated the issue to our electronics guys to review the differences between the working and not working PCBs.
    

    Thanks for your help.
    

    Dainius
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru**
                        115191 points
                      
    
                          
                   		
		
    
					
    Glad to know there is no issue with device. I'll mark this post resolved. If you have any further query, please start a new post.
    

    Regards,
    

    Vivek Singh
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Dainius Narsutis57
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Guru*
                        87145 points
                      
    
                          
                   		
		
    
					
    Dainius,
    

    Glad that you found it as the board issue. Thanks for taking the time to try the failing device on a working board.
    

    As I mentioned in my early replies on this post -  "In the past, similar debugs ended up as board issues on customers' side (same case - where some boards were fine but others were failing).  Please double check everything on your side."        
    

    FYI for others that may visit this post: If registers or memory locations read back differently (different values) at different instances, it is most probably a board issue.
    

    Thanks and regards,
    

    Vamsi
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    •