Paolo,
Please post to the group, not me. Others may be able to learn from
information provided.
On 10/27/2011 1:35 PM, p...@tin.it wrote:
>
> Hi Mike,
> I was trying the XDS100v1 using the 6713 DSK but I have problems.
> The connection is established and I'm able to load my program as I do
> via USB in the same DSK board.
> What I see in memory is anyway different, see the pictures.
> Note that CCS doesn't report errors while I'm loading, and in
both
> ways I get the BE (Big Endian) signal on bottom as I expect.
> The words seems in some way "stuck", but it's just an impression :
> 0000082C -> 02000BE2
> 0180002A -> 098C03AA
> You can see they are in some way "similar" (I mean not so many bits
> are different).
> As this is internal memory I suppose it's not an EMIF problem.
I did not see any pictures, but I think that I know what is going on.
1. Go to 'C:\CCStudio_v3.3\drivers\TargetDB\connections' in windows
explorer.
2. There should be a file with a name something like
'TIXDS100_Connection.xml'. I do not remember the exact name, but it
will
be the only connection file with XDS100 in the name.
3. Make a copy of the file 'just in case' and make sure that you
change
the extension from 'xml' on the backup so that CCS will not pick it
up.
4. Just above the last line [ ''] add the following
line:
Value="0" ID="C6000.SCANLOOP"/>
This will disable a JTAG performance feature [called 'ScanLoop'] that
is
not needed with the XDS100 and could be causing problems. This line is
benign to all other devices, so it will not hurt to leave it there.
5. If this does not work, answer the following:
A. If you modify internal memory from CCS, then refresh, does it contain
the correct data??
B. Can you run xdsprobe with the correct output??
> Note I just made a new configuration (.ccs) for using
the XDS100v1 but
> I used the same GEL file of the DSK.
> I also made some changes to the GEL file in order to do things
> manually via CCs just to check some automatic action in the GEL file
> (GEL_Reset) could cause the problem but it seems it's not the case (I
> made reset, then init PLL, then init EMIF, then init CPLD).
> Surprisingly the DSK GEL doesn't set the PLL for the correct speed
> (225 MHz) automatically (init_pll is available via hotmenu but it's
> not inside an "OnXxx" function.
> The TI GEL file is also attached (the modified one just comments the
> GEL_Reset() inside OnPreFileLoaded).
> Regarding the setup file (.ccs) I kept the default settings for the
> XDS100v1, see picture.
> I also tried with 500KHz TCLK but there is no difference on what is
> loaded (I also tried with 5 MHz and I had the same results (as I
> expected).
> I really don't know how to set the other "JTAG nTRST" and
> "Power-On-Reset Boot-Mode", I checked the electrical scheme and I saw
> EMU0 and EMU1 are simply taken "as they are" from the DSP, for this
> reason I kept the default (Disabled - Both EMU pins remains hi-z).
This is correct for the 6713 - the EMU lines should be hi-z
>
> So same board, same appl. program, same GEL but the XDS100v1 loads
> something different.
> Any idea ?
The C6000 emulation driver was developed over 15 years ago and I *think*
that it may contain assumptions about the JTAG behavior of the emulator
that does not hold true for the XDS100. This, and the long scan chain
for the early C6000 devices are likely conspiring to corrupt the JTAG data.
Please let us know your results.
mikedunn
> Thanks in advance,
> Paolo
> ----Messaggio originale----
>
> Da: m...@gmail.com
> Data: 25-ott-2011 0.40
> A: "Proware (tin.it)"
> Ogg: Re: [c6x] Re: Programming TMS320C6713B
>
> Paolo,
>
> On 10/24/2011 5:04 PM, Proware (tin.it) wrote:
>> Hi Mike, thank you!
>>
>> I'm trying this evening at home, but unfortunately I don't
have
>> the target board here.
>> Anyway, I made a configuration and tried to use it, the error I
>> have is this one :
>>
>>
>> /Error connecting to the target:
>> Error 0x80000200/-180
>> Fatal Error during: OCS,
>> This error was generated by TI's USCIF driver./
>> //
>> /SC_ERR_CTL_NO_TRG_POWER <-180>
>> The controller has detected a target power loss.
>> The user must turn-on or connect the power supply for
>> the target./
>>
>> //
>> In my understanding this could be OK for now (without the target
>> board), but you surely know much more than me on this topic.
>
> This is correct - no target power detected.
>> I hope to get one of the boards this week to check it's all OK, I
>> will let you know as soon I will make the test.
>> May be I can use a DSK just to see the XDS100v1 is OK. If I
>> remember well the 6713 DSK beside its internal emulator permits
>> the connection with an external emulator, but I've never tried it
>> in the past neither with the XDS100v1 nor with the XDS510 Plus,
>> but I suppose that if it is there it is available/usable.
>
> Plugging an emulator to the 14 pin connector muxes the JTAG away
> from the on board emulator to the 14 pin connector. It should work
> with a DSK.
>> I also tried without connecting the XDS100v1 to see if the error
>> was different and it is, the one I have is :
>>
>>
>> /Error connecting to the target:
>> Error 0x80000200/-180
>> Fatal Error during: OCS,
>> This error was generated by TI's USCIF driver./
>> //
>> /SC_ERR_CTL_NO_TRG_POWER <-180>
>> The controller has detected a target power loss.
>> The user must turn-on or connect the power supply for
>> the target./
>>
>>
>> For my current setup this is all I can do and it's quite
promising.
>>
>> Again, thank you!
>>
>>
>> Paolo
>>
>>
>>
>> ----- Original Message -----
>> *From:* mikedunn
>> *To:* Proware (tin.it)
>> *Cc:* c...
>> *Sent:* Monday, October 24, 2011 6:24 PM
>> *Subject:* Re: [c6x] Re: Programming TMS320C6713B
>>
>>
>>
>> Paolo,
>> On 10/20/2011 10:31 AM, Proware (tin.it) wrote:
>>
>>>
>>> Hi Mike,
>>> we have 2 XDS510+ but I also have an XDS100v1 that would be
>>> great for working home.
>>> Are you sure we can use the XDS100 with the 6713?
>>> AFAIK this is not supported (driver unavailable), in fact
>>> it's not in the list of supported processors.
>>> Once I read it was possible to use XDS100 with other
>>> processors with CCS 3.3 (that is the one I'm using) via a
>>> trick. May be it was the 64x as it is now supported in CCS 4
>>> and 5, but unfortunately the page I bookmarked doesn't work
>>> anymore.
>>
>> I do not have access to an XDS100v1, but I will provide some
>> info that may help.
>>
>> 1. It is possible that the XDS100 may not work. Without
>> getting too detailed into the internals, I will try to
>> explain a major difference. The newer generation devices [all
>> c64, c28, and c55 devices] use 38 bit scan sequences for all
>> operations. The 6713 uses an older generation scan technology
>> that has about 3500 bits in one of the scan chains. The FTDI
>> FT2232 device [and/or the software] may not support a buffer
>> that large and the software to 'find the correct bits' in
the
>> buffer. However, I do not believe that this is the case.
>> 2. You can run an experiment to see if it works. It will
>> definitely add the option to CCS setup.
>>
>> A. Make sure CCS is not running.
>> B. Create a text file with the following contents
>> ---next line is first line of file------
>> <?xml version="1.0"?>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ------previous line is last line----
>>
>> C. save the file as [make sure you save as ASCII and not
>> Unicode].
>> C:\CCStudio_v3.3\drivers\TargetDB\drivers\tixds100_c67xx.xml
>> - replace 'CCStudio_v3.3' with your CCS v3.3 install
dir
>>
>> D. Open CCS setup and you should see 'TMS320C6710' as one
of
>> the options.
>> E. Try it.
>>
>> Please let me know if this works.
>>
>> Thanx,
>> mikedunn
>>>
>>> Thanks in advance!
>>> Paolo
>>>
>>> From Mike Dunn (in response to Herschel "Programming
>>> TMS320C6713B"
>>> (http://www.dsprelated.com/groups/c6x/show/14839.php):
>>> >CCS v4 + XDS100 JTAG emulator is the most economical
>>> approach [about
>>> $100-150 USD].
>>> >...Texas Instruments is offering Code Composer Studio^(TM)
>>> for FREE for
>>> >use with the USB100v2. Please visit the TI wiki page for
>>> the XDS100 for
>>> >news and details on this offer here:
>>> >http://processors.wiki.ti.com/index.php/XDS100
>>>
>>
>>
