Forums

Re: Error when TMS320C6727 is connected using CCS

Started by tms....@gmail.com April 12, 2008
Hi all,
I am also getting the same error, which says:
"Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS, An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR. This will disconnect each target from the emulator. The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target. Sequence ID: 0 Error Code: -1060 Error Class: 0x80000200

Error connecting to the target: Error 0x80000200/-292 Fatal Error during: OCS, This error was generated by TI's USCIF driver. SC_ERR_TST_AUTOMATIC <-292> 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. Sequence ID: 0 Error Code: -292 Error Class: 0x80000200"
Kindly help me out ASAP.
Regards,
tms.techie

Hi All,
>Good morning.
>Kindly help me out in solving the problem.
> I am getting error after I disconnect the target DM642. I am not able to understand the error as there is no breakpoint SET.
>
>The error is as follows:
>" Failed to remove the debug state from the target before disconnecting. There may still be breakpoint opcodes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging."
>I tried to RESET THE EMULATOR and CONNECTed the target again. It is giving some other error....
>
>"Error connecting to the target: Error 0x80000240/-291 Fatal Error during: Initialization, OCS, This error was generated by TI's USCIF driver. SC_ERR_TST_MEASURE The built-in scan-path length measurement has failed. This indicates that the JTAG controller cannot reliably communicate with the target DSP's and micro-controllers at that frequency. Try specifying the scan-path lengths in the board configuration file because the built-in scan-path reliability tests cannot be performed without knowledge of the scan-path length. Sequence ID: 0 Error Code: -291 Error Class: 0x80000240 "
>
>Can anybody explain me why this is coming and what I should do to remove this error.
>
>Thanks & Regards,
>Spoorthy
>
>Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video Transcoding Solution for Commercial & Consumer End Equipment: www.ti.com/dm6467
tms.techie,

On Sat, Apr 12, 2008 at 5:37 AM, wrote:
> Hi all,
> I am also getting the same error, which says:
> "Error connecting to the target: Error 0x80000200/-1060 Fatal Error during:
> OCS, An unknown error prevented the emulator from accessing the processor in
> a timely fashion. It is recommended to RESET EMULATOR. This will disconnect
> each target from the emulator. The targets should then be power cycled or
> hard reset followed by an emureset and reconnect to each target. Sequence
> ID: 0 Error Code: -1060 Error Class: 0x80000200
>
> Error connecting to the target: Error 0x80000200/-292 Fatal Error during:
> OCS, This error was generated by TI's USCIF driver. SC_ERR_TST_AUTOMATIC
> <-292> 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. Sequence ID: 0 Error Code: -292 Error Class: 0x80000200"
>
> Kindly help me out ASAP.

[mld] You didn't mention the version of CCS that you are using - it
could matter.
It appears that you have an XDS560 emulator of some type and you
appear to be getting scan path integrity errors.. Refer to
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
for procedures to run a scan path test using 'xdsprobe.exe'.

mikedunn
> Regards,
> tms.techie
>
> Hi All,
> >Good morning.
> >Kindly help me out in solving the problem.
> > I am getting error after I disconnect the target DM642. I am not able to
> understand the error as there is no breakpoint SET.
> >
> >The error is as follows:
> >" Failed to remove the debug state from the target before disconnecting.
> There may still be breakpoint opcodes embedded in program memory. It is
> recommended that you reset the emulator before you connect and reload your
> program before you continue debugging."
> >I tried to RESET THE EMULATOR and CONNECTed the target again. It is giving
> some other error....
> >
> >"Error connecting to the target: Error 0x80000240/-291 Fatal Error during:
> Initialization, OCS, This error was generated by TI's USCIF driver.
> SC_ERR_TST_MEASURE The built-in scan-path length measurement has failed.
> This indicates that the JTAG controller cannot reliably communicate with the
> target DSP's and micro-controllers at that frequency. Try specifying the
> scan-path lengths in the board configuration file because the built-in
> scan-path reliability tests cannot be performed without knowledge of the
> scan-path length. Sequence ID: 0 Error Code: -291 Error Class: 0x80000240 "
> >
> >Can anybody explain me why this is coming and what I should do to remove
> this error.
> >
> >Thanks & Regards,
> >Spoorthy
> >
> >Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video
> Transcoding Solution for Commercial & Consumer End Equipment:
> www.ti.com/dm6467
> >
> >
>

--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php