Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
OceanLake
Level 1
Level 1
10 replies posted 10 sign-ins 5 replies posted

Dear All. When I using the PLS UAD2 pro connect with Aurix TC364 ECU,

Error will be reported as follow picture:

OceanLake_0-1700710587831.png

How to solve this problem?

Looking forward to your reply.

0 Likes
1 Solution
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @OceanLake  ,
In my opinion, it's too hard to confirm your assumption, as there's no other debug interfacing or porting for testing on the ECU unless unsoldering the chip to another platform for testing.
Moreover, I'd like to suggest you consider alternative ways to reflash the chip to get rid of the issue.
BR,
Jeremy

View solution in original post

0 Likes
16 Replies
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @OceanLake ,
1) How to solve this problem?
-- To be prudent, I'd like to know the context information of the issue, so can you give a brief introduction、
BR,
Jeremy

0 Likes

Thaks Jeremy,

Our product is used for motor control,The following is the background information of the problem,

1、Firstly, the workshop will write a test program for the ECU, which includes BMHD. After the operation is completed, the software will run normally.

2、Afterwards, the ECU will be used for motor related testing, and the software runs normally throughout the entire testing process.

3、After the test is completed, the shipping program will be refreshed. After connecting the flashing tool, erase the PFLASH area code, and the flashing tool will no longer be connected.

Approximately 1000 products will result in 6 failed pieces.

OceanLake

 

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @OceanLake 
Thanks for your information.
I'd like to know the phase in which t the above issue raises, further, the failure rate.
BR,
Jeremy

0 Likes

Hi @Jeremy 

Thank you for your thoughtful reply.

The issue raise at step 3

"3、After the test is completed, the shipping program will be refreshed. After connecting the flashing tool, erase the PFLASH area code, and the flashing tool will no longer be connected.".

And the failure rate is zero point six percent(0.6%).

OceanLake

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @OceanLake 
Does this ECU also be designed by your company? Further, there are other debug interfaces or ports for testing on the ECU, such as, can you try this tool to connect the ECU?
Lastly, you can compare the voltage level of the JTAG pins between the good and failure ECU, if available, please tell me the testing result.
BR,
Jeremy

0 Likes

Hi @Jeremy 

The ECU is designed by my company, unfortunately, No other debug interfaces or ports for testing on the ECU.

Following table is my test result, Voltage and resistance.

Status of ECU  TRST TMS TCK TDO TDI
Normal ECU 5V 0V 0V 0.5V 5V
Bad ECU 5V 0V 0V 0.5V 5V

Resistance.

Status of ECU TRST TMS TCK TDO TDI
Normal ECU 0Ω 6.7KΩ 21.6KΩ 0Ω 0Ω
Bad ECU 0Ω 6.7KΩ 21.8KΩ 0Ω 0Ω

BR,

OceanLake

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @OceanLake 
When measuring the voltage level (TRSI, TMS, TCK, TDO, TDI), please ensure the PLS UAD2 pro connects the debug port first, then, power on the ECU, capture the voltage level during PLS UAD2 pro try to establish the connection with the ECU, if the JTAG port has a fault, the voltage level usually behaves differently from the normal ECU.
BR,
Jeremy

0 Likes

Hi @Jeremey

The following is my test detail phenomenon. 

RESET_EMU:

f9d4d045-a885-4185-b92e-e195563f4c1b.jpg

When powered on, it presents a high level, and when the debugger is connected, it generates two resets.

TRST:

52866b35-cefa-4148-84fe-c593afcf70c7.jpg

When powered on, there will be a high level, and there will be some level changes when the debugger is connected.

TDO:

d6e32240-0c06-465b-8529-8a87addf0483.jpg

When powered on, there are high-level pulses, and when the debugger is connected, it will generate two high-level flat pulses.

TCK:

571895c0-0990-444a-aac2-40b835b0cbd1.jpg

When the debugger is connected, there may be occasional clock generation.

TMS:

6653f58e-61d2-49a6-9464-e64dba9671e9.jpg

When the debugger is connected, there will be communication.

TDI:

Always at low level when powered on or connected to the debugger.

BR,

OceanLake

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @OceanLake 
Was the testing implemented on the bad ECU? Or both normal and bad ECU?
Are the testing results identical on normal and bad ECUs?
BR,
Jeremy

0 Likes

Hi @Jeremy

The testing implemented on the bad ECU.

BR,

OceanLake

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @OceanLake 
I'd highly recommend you do the same testing with the normal ECU and compare the results to the bad ECU.
BR,
Jeremy

 

0 Likes

Hi @Jeremy 

Sorry for replying so late,The following information is for a normal ECU:

TMS:

afdcefe2-140c-4832-8b18-2c82866467ab.jpg.

0af6259c-2f8e-4274-b09d-66660f5673f7.jpg

TCK:

0af6259c-2f8e-4274-b09d-66660f5673f7.jpg

TDO:

48b61f5a-4e31-418b-98e9-d3bf5f7e9289.jpg

TRST:

82f04c65-1f4e-4fb7-9f87-8fbfc0c9f596.jpg

RESET_ECU:

1d7300c4-045e-41bc-9743-562d28cf1e91.jpg

TDI:

c9311939-c35c-4ada-b745-a8838b187eaf.jpg.

BR,

OceanLake

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @OceanLake 
According to the testing result, it seems like the JTAG port is not damaged.
I remembered that the issue was raised after step 3, and I'd like to know whether Bad ECU runs well after reflashing the demo code after step 3.
Further, can you tell me what flashing tool you used?

BR
Jeremy

0 Likes

Hi @Jeremy 

After the step 3 is completed, the code in the ECU has been erased, and there is no program for the running current of the ECU. At this time, the debugger cannot be connected, and I cannot confirm whether the code in the ECU has been completely erased, not erased, or only partially erased.

My flashing tool is PLS UAD 2pro.

BR,

OceanLake

0 Likes
Jeremy_Z
Moderator
Moderator
Moderator
1000 replies posted 250 sign-ins 100 likes received

Hi @OceanLake  ,
In my opinion, it's too hard to confirm your assumption, as there's no other debug interfacing or porting for testing on the ECU unless unsoldering the chip to another platform for testing.
Moreover, I'd like to suggest you consider alternative ways to reflash the chip to get rid of the issue.
BR,
Jeremy

0 Likes
Translation_Bot
Community Manager
Community Manager
Community Manager

1. First check whether the power supply is stable, whether the current is sufficient, low voltage, and insufficient current will also lock the chip debugging port

2. When the chip burns the program, whether to set encryption protection

3. The BMI header is not set correctly, or there is a problem with the UCB modification.

4. Solution: Try connecting via miniwigger.

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/AURIX/TC364-JTAG-%E6%8E%A5%E5%8F%A3%E5%B7%B2%E9%94%81%E5%AE%9A/m-p/646916

0 Likes