MPC5748G can not attach JTAG

cancel
Showing results for 
Search instead for 
Did you mean: 

MPC5748G can not attach JTAG

3,957 Views
kimyoungsu
Contributor III

hi

 

Abnormal reboot during flash programming (use C55 Flash Driver- c55_FlashProgram(), c55_FlashCheckStatus()).

after My JTAG cannot attached MPC5748G.

 

how to solve this problem?

and Do you plan to make improvements in this area in the future?(chip revision??)


					
				
			
			
				
			
			
				
			
			
			
			
			
			
		
Labels (1)
6 Replies

1,271 Views
virbhadrahankun
Contributor I

Hi, here is the another same problem with this kind of Issue.

I am using S32 design studio and openSDA debudder to dubug sample application. It worked for 2 3 hours and after that the board is giving problem to load the programme.

It is stucks at verification of block. have a look at screen shot. 

Connection from "127.0.0.1" via 127.0.0.1
Copyright 2017 P&E Microcomputer Systems,Inc.
Command Line :C:\NXP\S32DS_Power_v2017.R1\eclipse\plugins\com.pemicro.debug.gdbjtag.ppc_1.7.2.201709281658\win32\pegdbserver_power_console -device=MPC5748G -startserver -singlesession -serverport=7224 -gdbmiport=6224 -interface=OPENSDA -speed=5000 -resetÌ

CMD>RE

Initializing.
MPC574xC Device detected.
Target has been RESET and is active.
CMD>CM C:\NXP\S32DS_Power_v2017.R1\eclipse\plugins\com.pemicro.debug.gdbjtag.ppc_1.7.2.201709281658\win32\gdi\P&E\nxp_mpc5748g_1x32x1520k_cflash.pcp

Initializing.
MPC574xC Device detected.
Initialized.

;version 1.05, 06/26/2017, Copyright P&E Microcomputer Systems, www.pemicro.com [5748G_6080k]

;device NXP, MPC5748G, 1x32x1520k, desc=CFlash

;begin_cs device=$00F90000, length=$005F0000, ram=$40000000

Loading programming algorithm ...

WARNING - Selected .PCP file has been modified. CRC16 = $5A63
Done.
CMD>VC
Verifying object file CRC-16 to device ranges ...
block 00FA0000-00FA0007 ...

0 Kudos

1,271 Views
stanish
NXP Employee
NXP Employee

Hi all

This problem should be fixed by Pemicro Eclipse Plugin Update v1.6.9.

The HSM memory access was removed from the default Flash programming algorithms.

See the thread below for the instructions how to install Pemicro update. It's related to ARM version of the tools but for Power version simply select e200 item.

https://community.nxp.com/thread/447395?commentID=890477#comment-890477 

The updated Pemicro plugin will be included in S32DS for Power Update 2 that is going to be released by the end of July 2017.

Regards,

Stan

1,271 Views
ludwigschreier
Contributor IV

Hi Stanislav,

was this update verified? I have latest S32DS and updates, but it seems I just bricked devkit. Further comment in in https://community.nxp.com/message/952150?commentID=952150#comment-952150

Best,

Ludwig

0 Kudos

1,271 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

I can see in the history that we was already talking about reset escalation feature (MPC5748G Cannot attached JTAG after erase all? ) That's the first reason that could explain such problem.

Second reason is following:

If I can understand your description, the flash operation (program/erase) has been terminated by unexpected reset, so the flash has been left in undetermined state. That leads to ECC errors in affected flash blocks.

There are two HSM code blocks in the memory:

pastedImage_162.png

If there are ECC errors in these blocks, the device may stuck in reset. During reset, the SSCM module searches for valid boot header. If it reads corrupted data from HSM blocks, it will not exit the reset. This is security feature and there's no way to recover. It is not sufficiently documented yet, the work related to this behavior is still ongoing. I hope this information will be included in next release of the reference manual. The workaround is: program the HSM blocks only in factory where it is possible to ensure that the programming will not be terminated by unexpected reset or power-off.

Regards,

Lukas

1,271 Views
clementchassagn
Contributor II

What do you mean by "no way to recover" ? do you mean I can trash the board ?

0 Kudos

1,271 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Unfortunately, yes. There's no way how to make it working again.

Regards,

Lukas

0 Kudos