My company has a number of CodeWarrior TAP (CWH-CTP-BASE-HE) for flash programming QoriQ P-series and T-series processors. The TAPs we have are a mix of rev.B and rev.E modules. Throughout the time these have been used (circa 15 years) we have experienced endless JTAG related problems that lead to programming failures. These tend to be 'JTAG scan chain fail' or 'failed to configure the JTAG'. Recently I was presented the opportunity to try a newer TAP which is rev.H. This newer TAP rev.H performed problem free throughout a lot of programming attempts. It appears that our historic flash programming problems using the CodeWarrior TAP may have been due to the older module revisions. Could you give any information for what we could do to sort this? Is there anything we can do with our rev.B and rev.E modules? Or are we stuck with purchasing new CodeWarrior TAP (rev.H)? Thanks for your help.
We have resolved our programming problems by purchase of a new CodeWarrior TAP (CWH-CTP-BASE-HE). The new TAP is identified as rev.H. I have repeated numerous flash programming of P1025 and T1024 dev boards and experienced no errors or problems. Thanks for all your help.
Thanks for the CCS update. I've tried the update you sent using CodeWarrior 10.5.2 and a CWTAP rev.E. I still get the same JTAG problems. Odd that I don't get any problems when I use a CWTAP rev.H. Is this different hardware? Thanks
Ok thanks. I need to downgrade my CWTAP rev.E back to OS v1.0.4. If I put the original CCS back in CodeWarrior, will the 'updatecwtap' restore the old firmware?
P.S. I assume from this conversation that the CWTAP rev.H is different hardware.
I've have tried flash programming using our CWTAP rev.E with OS v.1.0.5 and with CCS from CodeWarrior 10.5.2. No change, we are still getting the same JTAG problems.
I've not had any luck with any combination - CWTAP rev.E with OS 1.0.5 and old/new CCS. I restored my CWTAP rev.E to OS 1.0.4 using 'updatecwtap --force'. This worked OK and I can communicate with it.
