Forums

Loss of processor clock when trying to connect through the JTAG port

Started by cmackinnon44 May 17, 2008
I can't connect to my DSP through the JTAG port. The message that CCS
gives me is that it has lost the processor clock and the device is
operating in low power mode. The clock signal going in is 20 MHz (pin
90) and coming out of the XCLKOUT pin is 2.5 MHz initially. As soon as
I try to connect through my JTAG device (Signum Systems JTAGJET - TMS),
the XCLKOUT signal disappears. I've checked all connectivity between
the JTAG header and the JTAG pins on the DSP and everything looks ok.
Prior to connecting, I've run the JTAG autodetect and verify and it
sees the device in the JTAG chain. I don't see any DSP resets or
anything occuring while I'm try to connect. The silicon revision
appears to be the same as on a previous generation board and I have no
issues connecting to it (so it appears the my programmer is ok).
GPIO18, 29 & 34 have been configured to boot from RAM. If anyone else
has seen this before and knows what's going, your help would be much
appreciated.

OMAP35x EVM jump-starts low-power apps
The modular and extensible OMAP35x Evaluation Module (EVM) enables developers to start building applications based on the OMAP35x architecture: http://www.DSPRelated.com/omap35x
Hi,

I usually get same error when JTAG hangs up during debugging. Usually
helps to reset (disconnect/connect) JTAG and target voltage then run
Debug->Reset Emulator in CCS.

Sometimes I feel more like ghost buster than programmer when I work with
TI CCS :)

cmackinnon44 napsal(a):
> I can't connect to my DSP through the JTAG port. The message that CCS
> gives me is that it has lost the processor clock and the device is
> operating in low power mode. The clock signal going in is 20 MHz (pin
> 90) and coming out of the XCLKOUT pin is 2.5 MHz initially. As soon as
> I try to connect through my JTAG device (Signum Systems JTAGJET - TMS),
> the XCLKOUT signal disappears. I've checked all connectivity between
> the JTAG header and the JTAG pins on the DSP and everything looks ok.
> Prior to connecting, I've run the JTAG autodetect and verify and it
> sees the device in the JTAG chain. I don't see any DSP resets or
> anything occuring while I'm try to connect. The silicon revision
> appears to be the same as on a previous generation board and I have no
> issues connecting to it (so it appears the my programmer is ok).
> GPIO18, 29 & 34 have been configured to boot from RAM. If anyone else
> has seen this before and knows what's going, your help would be much
> appreciated.


OMAP35x EVM jump-starts low-power apps
The modular and extensible OMAP35x Evaluation Module (EVM) enables developers to start building applications based on the OMAP35x architecture: http://www.DSPRelated.com/omap35x
Hello!

I've a similar problem: I'm using the F2811 via SD XDS510PP JTAG-Emu and also get the message 'Lost processor clock' and the follow-up-error when trying to get it out of 'sleep-mode'.
I was not messing around with low power modes. (Almost classic:) Yesterday everything worked fine: flashing, operation, debugging but now I can't get it working. I've already tried to reconnect all the cables and power-supply, but no success.
By the way: the Diagnostic-function of SDConfig works.

Can you help me???

regards,
Thomas

_____________________________________
I can't connect to my DSP through the JTAG port. The message that CCS
>gives me is that it has lost the processor clock and the device is
>operating in low power mode. The clock signal going in is 20 MHz (pin
>90) and coming out of the XCLKOUT pin is 2.5 MHz initially. As soon as
>I try to connect through my JTAG device (Signum Systems JTAGJET - TMS),
>the XCLKOUT signal disappears. I've checked all connectivity between
>the JTAG header and the JTAG pins on the DSP and everything looks ok.
>Prior to connecting, I've run the JTAG autodetect and verify and it
>sees the device in the JTAG chain. I don't see any DSP resets or
>anything occuring while I'm try to connect. The silicon revision
>appears to be the same as on a previous generation board and I have no
>issues connecting to it (so it appears the my programmer is ok).
>GPIO18, 29 & 34 have been configured to boot from RAM. If anyone else
>has seen this before and knows what's going, your help would be much
>appreciated.
>
>OMAP35x EVM jump-starts low-power apps
>The modular and extensible OMAP35x Evaluation Module (EVM) enables developers to start building applications based on the OMAP35x architecture: http://www.DSPRelated.com/omap35x
>
>I have a ezdsp28335 with emulator on board, i have the same problem, i see a message .. processor clock and the device is operating in low power mode.
Then next i can`t connect to my target. this message apears:

Error connecting to the target:
Error 0x80000200/-1041
Fatal Error during: OCS,
Device driver: Problem with the Emulation Controller.
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.
I/O Port = 540

Board Name: F28335_eZdsp
Cpu Name: cpu_0

Abort: Close Code Composer Studio.
Retry: Try to connect to the target again.
Cancel: Remain disconnected from the target
Diagnostic: Run diagnostic utility.

I tried re-installing emulator driver, re-installing code composer, reset emulator, but nothing works.
this message apears when i tried to reset emulator:

This utility has selected an XDS560 class product.
This utility will load the program 'xds560.out'.
This utility will operate on port address '0'.
Connect failure

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver.

The value is '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.

The explanation is:
An attempt to access the named emulator via USCIF ECOM has failed.

I change the USB cable and then i could open code composer to conect to my target, i run some examples but it was for a little time because next the same message:
....processor clock and the device is operating in low power mode.
so i want to know if my processor or emulator is broke.

>

_____________________________________