On Tue, Feb 24, 2009 at 11:23 AM, saurabh joshi wrote:
> Thanks for suggestions. My JTAG connections are less
than 2000 mils. I run
> the sdconfig at 12 Mhz which is max for my xds .I will check TCLK . It
> be an issue. Please let me know one thing more . What will be the effect of
> various config settings. Can it cause such type of issues?
The config settings probably will not be a problem - they usually give
a cannot connect to target message.
You could possibly be experiencing an 'ARDY hang' - make sure that it
is not tied to always indicate a 'not ready condition'.
You could also be experiencing the old 'C6x run away and execute
garbage' problem if you are setup for 'no boot' mode.
For debug on the c6713, you can configure the c6713 for 'HPI boot'.
You do not need an HPI connection, but 'HPI boot' mode will hold the
target in reset until the emulator tries to connect. The emulator
driver will issue 'DSP_INT' causing the DSP to be released from reset
and it will halt at add 0, allowing the emulator to take control.
> On Tue, Feb 24, 2009 at 9:51 PM, Michael Dunn
>> On Tue, Feb 24, 2009 at 2:33 AM, wrote:
>> > I am using TMS320c6713B custom board along with Spectrum Digital
>> > EMulator
>> > xds510usb. While Connecting with my custom board using sdconfig utility
>> > I
>> > got ok results. It can scan pattern and verfiy patterns also . However
>> > when
>> > i start CCS studio i found a message " An unknown error prevented the
>> > Emulator in a timely fashion. " I have checked with Reset also . It
>> > seems
>> > fine too. I am using TPS70345 as power device and is giving a power on
>> > reset
>> > to DSP. However on the same time it can work fine with DSK6713. Now I am
>> > not
>> > able to locate the problem. If its an integrity issue why sdconfig
>> > passes
>> > all tests ? As my application is very small i am not using SDRAM .Dose
>> > this
>> > has any role ? Please advice ...
>> On your second question, simpler is better. There are no worries about
>> no SDRAM as long as you do not use a GEL file that tries to access it.
>> 1. Sdconfig has verified that the connections are proper and that you
>> can get data across JTAG.
>> 2. The 'CCS JTAG connect process' is comprised of several long JTAG
>> scans. On a marginal JTAG link, I have seen this sequence fail when
>> sdconfig passes.
>> 3. When you have problems like this, make sure that you run sdconfig
>> at the maximum speed, then reconfigure it for the minimum speed [as a
>> test] to try a CCS connection. If it works, gradually increase the
>> 4. I assume that you have made the JTAG signal path length very short
>> from the connect to the device. If not that could be trouble.
>> 5. If all else has failed, break out a good scope and put it on TCLK
>> on the JTAG connector [note:you might find that it does not fail with
>> a scope connected to TCLK] and look for a 'non-linear' rise or fall
>> time. The high impedance of the 6713B can react [see a signal edge]
>> to reflections that show up as 'small humps' in the clock edges.