Error measuring IR length During JTAG Diagnostics Test...

[karunakaranradh]

We are using T2080 based processor board, when try to connect the code warrior in one of our processor board it shows the below error.

but we have two other same design processor boards which was connected properly without any error.

I enabled the JTAG Diagnostics test before connecting the code warrior in the problem board, it shows the below error

JTAG connection section design as same as T2080RDB. This problem was not facing when code warrior was bring up in other two processor board.

Note: Code warrior 10.4 SP1 using for connecting the target processor board.

I could not find the reason for this "Error measuring IR length..." issue.

Kindly suggest us, what are all possible condition for this JTAG Diagnostic Test failed which will help us to debug?

[lunminliang]

Hello Karunakaran Radhakrishnan,

Please make sure the three target boards were tested using the same CodeWarrior installation and the same test steps.

Does the failure board has the same valid RCW as the other two boards? Not destroyed accidentally?

You're only trying to connect core0?

If the three board has the same design, you may try to compare their JTAG waveform?

Have a great day,
Lunmin

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[karunakaranradh]

Hi Lunmin,

Thanks for your reply.

Please make sure the three target boards were tested using the same CodeWarrior installation and the same test steps.

Code warrior step as same as other two connecting boards.

Does the failure board has the same valid RCW as the other two boards?

RCW is valid which is working in other two boards

Not destroyed accidentally?

Failure board is newly populated which is not have any RCW. we are try to program RCW fist time for this failure board.

You're only trying to connect core0?

yes I am using Core0 only.

If the three board has the same design, you may try to compare their JTAG waveform?

During code warrior connection with JTAG diagnostic test , There is no waveform observed from TDO signal which is from processor.

Thanks & Regards

Karunakaran R

[lunminliang]

Hello Karunakaran Radhakrishnan,

Not destroyed accidentally?

Failure board is newly populated which is not have any RCW. we are try to program RCW fist time for this failure board.

Please try to use hard coded RCW option in this case.

Have a great day,
Lunmin

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[karunakaranradh]

Hi Lunmin,

Assembly verification has been done for any soldering or component mount issue. In that verification,there is no observation founded.

In code warrior, "Failed to correctly configure the JTAG chain" error is related to

RCW Input data is not properly configured?

          or

Hardware JTAG chain signals is not properly connected?

Regards

Karunakaran R

[lunminliang · Accepted solution]

Hello Karunakaran Radhakrishnan,

Sorry for late.

To get activity on TDO, you need stable power, and working connections for TDI, TDO, TMS, TCK and TRST_B.  I would first try to verify whether TDO toggles at the SoC, or as close to it as you can get.  Also check TRST_B and make sure it is not stuck low.  If TRST_B is high, then check TCK and TMS to see if they toggle.  Check them both at the JTAG header and at the SoC.  Note that you will only see toggling while a debugger operation is actively running (such as the diagnostics).  You can check TDI as well, although you should be able to see TDO toggle even if TDI is broken, so it’s more likely that the problem is with TCK, TMS or TRST_B.

I was guessing solder problem since only one out of three boards is failing, either disconnect or short. But as you have assembly verification, it seems not to be the problem.

Have a great day,
Lunmin

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[karunakaranradh]

Hi Lunmin,

Thanks for your information,

Your are correct. Processor does not get the stable power supply due to failure of power mosfet which is used for supply power to T2080.

After replaced new one, code warrior connecting properly and also JTAG test is OK.

Thanks,

Karunakaran R

[karunakaranradh]

Hi Lunmin,

Please try to use hard coded RCW option in this case.

Error Message observed in failure board is configured in hard coded RCW mode only.

I have one question:

Is there any possible condition/feature of processor to block the TDO?

Regards

Karunakaran R