Sreenath- > Thanks for your quick response. > Actually we have 4 target boards and 2 JTAG XDS560 emulators.I tried > all the combinations but still the same problem. > This was a working setup for 1 year.I am facing this problem after > changing my Setup from existing lab to new lab.Will there be any > problem wih the new power supplies or ESD in this new lab?Do these > factors really impact the JTAG communication or Target frequencies? Based on this information, I would test your XDS560 setup with a basic vanilla DSK board ASAP. Sounds like there is something in the lab -- PC, power, cosmic rays, etc. -Jeff > --- In code-comp@code..., Jeff Brower <jbrower@s...> wrote: > > Sreenath- > > > > I suggest that you try the XDS560 emulator with a DSK board or > other, known working > > board. You are spending a lot of time to debug, but your first > step should be to > > narrow the problem: XDS560 setup vs. your board. > > > > If it turns out to be your board and XDS560 is fine, then check > your TCK line. How > > many cm is the TCK line from the JTAG connector to the DSP? Do you > have a buffer on > > the TCK line? > > > > -Jeff > > > > sreenath_ys wrote: > > > > > > Hi all, > > > I am working with XDS560 emualator connected to my Target using > > > JTAG.My target board is based on C5410A TI DSP. When I am opening > the > > > Code Composer it is giving following initialization error: > > > ========== > > > "This error is generated by TI's USCIF driver. > > > The error's value is: `-291'. > > > The error's title is: `SC_ERR_TST_AUTOMATIC'. > > > > > > The error's explanation is: > > > The utility or debugger has requested the PLL generating the JTAG > > > clock to automatically select a frequency by using an auto-ranging > > > algorithm. The built-in scan-path test has repeatedly failed. > > > This indicates that the auto-ranging algorithm cannot find > > > a frequency that will allow the JTAG controller to reliably > > > communicate with the target DSP's and micro-controllers. > > > Try using the legacy frequency or a known good specific > frequency." > > > ========== > > > I tried changing the TCLK frequency from Automatic to Legacy but > > > still the problem is not recovered. > > > I did the JTAG scan path test using XDSPROBE utility ,this is the > > > result I got: > > > ==== > > > The error's value is: `-237'. > > > The error's title is: `SC_ERR_PTH_BROKEN'. > > > > > > The error's explanation is: > > > An attempt to scan the JTAG scan-path has failed. > > > The target's JTAG scan-path appears to be broken > > > with a stuck-at-ones or stuck-at-zero fault. > > > === > > > > > > Did any one of you had faced this problem before? > > > Any suggestion to recover from this problem will be of great help. > > > > > > Thanks > > > Sreenath

Hi Jeff, Thanks for your quick response. Actually we have 4 target boards and 2 JTAG XDS560 emulators.I tried all the combinations but still the same problem. This was a working setup for 1 year.I am facing this problem after changing my Setup from existing lab to new lab.Will there be any problem wih the new power supplies or ESD in this new lab?Do these factors really impact the JTAG communication or Target frequencies? Thanks a lot. Regards Sreenath --- In code-comp@code..., Jeff Brower <jbrower@s...> wrote: > Sreenath- > > I suggest that you try the XDS560 emulator with a DSK board or other, known working > board. You are spending a lot of time to debug, but your first step should be to > narrow the problem: XDS560 setup vs. your board. > > If it turns out to be your board and XDS560 is fine, then check your TCK line. How > many cm is the TCK line from the JTAG connector to the DSP? Do you have a buffer on > the TCK line? > > -Jeff > > sreenath_ys wrote: > > > > Hi all, > > I am working with XDS560 emualator connected to my Target using > > JTAG.My target board is based on C5410A TI DSP. When I am opening the > > Code Composer it is giving following initialization error: > > ========== > > "This error is generated by TI's USCIF driver. > > The error's value is: `-291'. > > The error's title is: `SC_ERR_TST_AUTOMATIC'. > > > > The error's explanation is: > > The utility or debugger has requested the PLL generating the JTAG > > clock to automatically select a frequency by using an auto-ranging > > algorithm. The built-in scan-path test has repeatedly failed. > > This indicates that the auto-ranging algorithm cannot find > > a frequency that will allow the JTAG controller to reliably > > communicate with the target DSP's and micro-controllers. > > Try using the legacy frequency or a known good specific frequency." > > ========== > > I tried changing the TCLK frequency from Automatic to Legacy but > > still the problem is not recovered. > > I did the JTAG scan path test using XDSPROBE utility ,this is the > > result I got: > > ==== > > The error's value is: `-237'. > > The error's title is: `SC_ERR_PTH_BROKEN'. > > > > The error's explanation is: > > An attempt to scan the JTAG scan-path has failed. > > The target's JTAG scan-path appears to be broken > > with a stuck-at-ones or stuck-at-zero fault. > > === > > > > Did any one of you had faced this problem before? > > Any suggestion to recover from this problem will be of great help. > > > > Thanks > > Sreenath

Sreenath- I suggest that you try the XDS560 emulator with a DSK board or other, known working board. You are spending a lot of time to debug, but your first step should be to narrow the problem: XDS560 setup vs. your board. If it turns out to be your board and XDS560 is fine, then check your TCK line. How many cm is the TCK line from the JTAG connector to the DSP? Do you have a buffer on the TCK line? -Jeff sreenath_ys wrote: > > Hi all, > I am working with XDS560 emualator connected to my Target using > JTAG.My target board is based on C5410A TI DSP. When I am opening the > Code Composer it is giving following initialization error: > ========== > "This error is generated by TI's USCIF driver. > The error's value is: `-291'. > The error's title is: `SC_ERR_TST_AUTOMATIC'. > > The error's explanation is: > The utility or debugger has requested the PLL generating the JTAG > clock to automatically select a frequency by using an auto-ranging > algorithm. The built-in scan-path test has repeatedly failed. > This indicates that the auto-ranging algorithm cannot find > a frequency that will allow the JTAG controller to reliably > communicate with the target DSP's and micro-controllers. > Try using the legacy frequency or a known good specific frequency." > ========== > I tried changing the TCLK frequency from Automatic to Legacy but > still the problem is not recovered. > I did the JTAG scan path test using XDSPROBE utility ,this is the > result I got: > ==== > The error's value is: `-237'. > The error's title is: `SC_ERR_PTH_BROKEN'. > > The error's explanation is: > An attempt to scan the JTAG scan-path has failed. > The target's JTAG scan-path appears to be broken > with a stuck-at-ones or stuck-at-zero fault. > === > > Did any one of you had faced this problem before? > Any suggestion to recover from this problem will be of great help. > > Thanks > Sreenath

Hi all, I am working with XDS560 emualator connected to my Target using JTAG.My target board is based on C5410A TI DSP. When I am opening the Code Composer it is giving following initialization error: ========== "This error is generated by TI's USCIF driver. The error's value is: `-291'. The error's title is: `SC_ERR_TST_AUTOMATIC'. The error's explanation is: The utility or debugger has requested the PLL generating the JTAG clock to automatically select a frequency by using an auto-ranging algorithm. The built-in scan-path test has repeatedly failed. This indicates that the auto-ranging algorithm cannot find a frequency that will allow the JTAG controller to reliably communicate with the target DSP's and micro-controllers. Try using the legacy frequency or a known good specific frequency." ========== I tried changing the TCLK frequency from Automatic to Legacy but still the problem is not recovered. I did the JTAG scan path test using XDSPROBE utility ,this is the result I got: ==== The error's value is: `-237'. The error's title is: `SC_ERR_PTH_BROKEN'. The error's explanation is: An attempt to scan the JTAG scan-path has failed. The target's JTAG scan-path appears to be broken with a stuck-at-ones or stuck-at-zero fault. === Did any one of you had faced this problem before? Any suggestion to recover from this problem will be of great help. Thanks Sreenath