This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

2 devices - XDS 560 v2 Travellers USB cause Target Configuration to crash upon connection

Processors: 6457 (irrelevant because we don't connect yet). 

Spectrum Digital Device 1 : XDS560 v2 travellers USB 

Spectrum Digital Device 2 : XDS560 v2 travellers USB 

Target Configuration: 

Add one device, set I/O Port number to 0

Add another device to same target configuration, I/O Port Number 1.  

Steps to crash:

1.  After setting up the configuration above, in the target configuration window, hit "Connect"  (I think this is the wording) to connect to the emulator(s)?  

2.  Code Composer Studio 5.1 IDE disapears

Note: Same behavior happens in Code Composer 6.  

We really can't move to a newer version at this time.  

Any suggestions?  

  • If you create a target configuration with just one XDS560v2 does that connect OK? 

    One of our guys is going to try to set up a similar environment to reproduce the issue you are seeing.  

    I can understand you being tied to a specific version of CCS.  Is there a chance that you could use your 5.1 version for building your application and then a newer version to Debug?  That way you are not impacting your application image by switching versions.

    Regards,
    John

  • If you create a target configuration with just one XDS560v2 does that connect OK? 

    ixworks - can you do this for each debug probe while both are plugged in at the same time? Basically create two separate ccxml files, one for each probe, differentiated by IO port.

    Thanks

    ki

  • First, thank you both so much for responding so quickly.   Its really great.  

    The I/O Port issue:  TI has a link for "Tech Note 13" which goes to support.spectrumdigital.   This address is invalid.  I don't know how to get this value and set it.  

    When we scanned I/O ports, a few came up as reporting valid data for our ICEs, however when we connected on both, the Image data in the header stated it was the same header  (same checksum, same string that identified which processor the image was reprogrammed on).  There couldn't be an error there because we've run some Built-in-test software that reports versions/checksums and they aren't the same.  

    Can you provide this tech note? 

    Unknown Host (spectrumdigital.com)

    http://support.spectrumdigital.com/ccs40/xds560v2_stm/files/ then "TechNote_13.pdf"

    Spectrum Digital XDS560v2USB

    Multiple Spectrum Digital XDS560v2 debug probes can be differentiated with their Emulator I/O Port number or Serial Number. Instructions on how to determine the port numbers and serial numbers and how to use this information in CCS is documented in this Tech Note documentation from Spectrum Digital.

    The above tech note describes how to differentiate between debug probes attached to the host machine for a single debug probe debug session. For a multi-probe debug session, the steps are similar except for the need create a custom multi-probe target configuration which include all debug probes and the device(s) they are connected to. You must create a custom configuration using the Advanced target configuration editor. The basics of creating custom target configurations is documented in here.

    Once you have added all debug probes (and the device(s) they are connected to), go to EACH debug probe entry and update the Emulator I/O Port Number field as described in the tech note.

  • JohnS, thank you for your fast reply;  my favorite support is TI.  

    We had 5.1 and 6.x.  Because of the situation we have to request versions and then try them in a closed environment;  quite an ordeal.  I also don't have an open area to try this out.   I will ask around because we tried 6.x with that very same thought--if it works, we can support both.  We're using the debug functionality (loadti.bat) to reprogram so we just have to point to a new folder and then support any backward compatibility issues and heterogeniety issues (e.g. we'll have multiple code composer loadti versions).  

    I'll check in on getting 7 or 8 but its certainly not easy. 

    I would like to get Tech Note 13 from the reply below.  Also, if you can duplicate it.  

    I will see about debugging as well;  Do you guys think this link would work for uncovering it, or can you easily do this and recreate the issue I'm seeing? 

    https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html#debug-server-logs

  • can you easily do this and recreate the issue I'm seeing? 

    I believe I can reproduce the crash with CCSv5 and v6. I'm trying to see if everything works with later CCS versions but I seem to be running into a different issue where the debugger is unable to communicate to the second debug probe connected to the target. Are you able to connect to the second probe?

  • Ki is trying to reproduce the same setup.  We also ran into the issue with the link to the tech note not working.  Spectrum Digital is no longer in business.  I archived a lot of content from their site but not that tech note.  Doing a search I did find this link which appears to be the correct document.

    https://dtsheet.com/doc/1696433/this-tech-note-documentation-from-spectrum-digital

  • Outstanding!  Thanks

  • I can connect using these probes, as individuals....but haven't got them to work for separate processors.  I'll take a stab at the Technote approach. 

  • Use the steps documented in the tech note from Spectrum Digital (Thanks to John for digging that up). I can successfully start a multi-emulator debug probe setup for my two XDS560v2 probes and successfully connect to each board when using CCSv8.3.1

    When I try CCSv5.5 and CCSv6.2, CCS crashes when starting up the debug session.

    I would suggest using a later CCS version for debug.

  • When I try CCSv5.5 and CCSv6.2, CCS crashes when starting up the debug session.

    CCSv7.4 also crashed for me.

    I would suggest CCS v8 or later. 

  • The tech note for this spectrum digital xds560v2 worked!  I configured each one using the SD Config utility with their Serial Numbers (I/O port 0 and I/O port 1) with separate ccxml files and was able to do what we needed.   There was no crashing;  I could view memory, modify registers, etc.  

    I still need to run the loadti script, but that's only dependent on a working ccxml file, which we have now.  

    Thank you, Team TI

  • Great to hear!