• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 729 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Target communication errors with SEED XDS560 emulator ?!?

citizen
Expert 2840 points

Hi all.

I am currently using a SEED XDS560 PLUS emulator from SEEDDSP.COM.
I've followed the XDS560PLUS JTAG Emulator Installation Guide provided.
The emulator is correctly detected by Windows, and I have (what appears to be the case)
correctly configured a target device in CCS4 to connect to our customs target board using a VC5505 DSP.

The problem I am having is what appears to be emulator connection problems to our target board via JTAG.
Sometimes, launching the debugger, then connecting allows us to run the code without any problems, other
times it just does not seem to want to connect to the target board. Often it requires that I reset to move the program
counter back to main(), other times I just need to disconnect leave debugging and restart debugging session.

I am not entirely sure why this is happening as I have not encountered such intermittent problems with JTAG before,
certainly not when using the MSP430s for instance, and never with devices from other vendors such as the AVRs, PICS etc.
I am finding this rather frustrating and interfering with our debugging work as you can imagine.

So basically I would like to know if there are any suggestions for these inconsistent connections we are experiencing when
connecting to our target board. The fact that the emulator does connect and we can run our compiles xyz.out code would
suggest we have setup both the emulator and the target device correctly.

We have also had similar experience with the XDS100 emulator, unplugging the USB and re-plugging the USB cable, then reconnecting
seems to allow reconnection without having to reset the target, however surely having to do this is not the way to work ?!? Could it be a problem on the JTAG connector ?

Maybe we are missing something simple, but I can't see what ! The custom target board was designed by a third party and I am assuming they took all necessary steps to ensure correct JTAG communication on the board they supplied. So would it be an interface problem with CCS4 or other driver problem ? Where to start to identify why this is occurring ?

Thanks in advance for any suggestions.

Regards, M

  • 0
    TI__Genius 14965 points

    Hi,

     

    I understand your question. In order to answer your qustion, I need some infomation from you.

    What version of CCS are you using?  (CCS4 menu--> Help--> About Code Composer Studio --> Version: ???)

    Are you using VC5505 EVM or eZdsp stick?

    You said MSP430s isok. Are you using same CCS4?

     

    Regards,

    Hyun

  • 0 in reply to Hyun Kim
    Expert 2840 points

    Hi,


    4.1.2.00027 semmes to be the version showing up.

    Using EVM5505 in the target configuration.

    I did mention that we never had similar connection problems with MSP430 as we do now with CCSv4 and our custom built VC5505 based DSP board. (we also have an MSP430 microcontroller board where we used the MSP-FETU430 emulator with the CCSv4 / MSP430 version. This version version of CCSv4 is the trial version downloaded for evaluation, however its been giving us alot of trouble in comparison ...

    Regards, M

  • 0 in reply to citizen
    TI__Genius 14965 points

    Hi,

     

    CCS4 trial version works for only XDS100 only. Here is web links http://processors.wiki.ti.com/index.php/XDS100 listed CCS4 and XDS100 Q&As.

    Q: Can I use Code Composer Studio v4 with XDS100?

    A: There is a free license for Code Composer Studio v4 when used with XDS100. Code Composer Studio v4 can be downloaded from the Code Composer Studio v4 page. When you install CCS, you need to select the correct license. See below on how to select the correct license. This license is designed to be use with XDS100 only, and not XDS510 or XDS560 emulators. Please seeActivating_CCS#Generate_and_Install_a_License_File for details.

     

    Regards,

    Hyun

  • 0 in reply to Hyun Kim
    Expert 2840 points

    Hi,


    Yes and we do have a XSD100 cause we have used it, however the evaluation license is fully working for a limited amount of time, so we evaluate with all other emulators then we look at buying. However considering all we would need to be very assured that our investment will provide us with the value that we actually seek from the latest CCSv4    .

    Please read my original post. The question was NOT weather it was compatible with the limited version, but why the temporary version was giving me intermitent errors when using XDS510/XDS560 etc. with our custom board, when other times its ok ?

    Regards,

     

  • 0 in reply to citizen
    TI__Genius 14965 points

    Hi,

    Ok, let's go step by step.

    1. Do you have our VC5505EVM or eZdsp board? If yes, do you see similar behavior with same software?

    2. Can you send me your projects code in order to try over here? Please include your target configuration file as well.

    3. Can you send me your schematic?

    If you don't want to post this forum, you can send me to hyunkim@ti.com.

    Regards,

    Hyun

     

  • 0 in reply to Hyun Kim
    Expert 2840 points

    Hi,

     

    We do not actually have a VC5505EVM or eZdsp board, but can get access to a VC5505EVM to do that same test and see the behaviour. The custom board that we got from our contractors was supplied with the JTAG and dsp etc. all as is, and the code is still being debugged etc. I will look into providing that which you require to try yourself, however let me see if I can first try the same with a VC5505EVM board from our collegues. Thanks for your quick reply.

     

    Kind Regards, M

  • 0 in reply to citizen
    Genius 4630 points

    I am having similar problems with CCS 4.1.2.00027 - it does not matter whether I use an XDS510 clone or the Spectrum Digital XDS100.

    The problem is that CCSv4 will hang, using loads of CPU, waiting to connect to my C5506 board to "remove breakpoints."  I have to use Task Manager to kill both Eclipse and the Java virtual machine to get out of this state.  This problem slows down the development cycle significantly.

    In contrast to the problems you describe, I am always able to connect to my custom board.  It's after I run the firmware and want to stop, reset, or disconnect that I sometimes suffer from CCSv4 hanging.  I can usually get through a few cycles of edit, compile, load, and run before it hangs.  Although there are differences, our situations do seem suspiciously similar.

    Despite the almost clear indication that this is a software error (i.e. I never have to reset the hardware - just restart CCSv4 and everything works), I have noticed one potential hardware problem on my end.  My custom hardware has seen two revisions.  The earlier revision seems to not exhibit this problem, or, at the very least, the problem is much less pronounced.  Other than the position of traces on the board, the only schematic change between these revisions is that I added a pull-up to the TCK pin of the JTAG interface.  I have no idea why this pull-up should cause a problem, since the Texas Instruments documentation suggests that such a pull-up will *reduce* problems with noise.

    The fact that you do not have either of the VC5505EVM or eZdsp boards seems to allow the possibility that there is a slight hardware issue for you, as well.  If you would be willing to share the schematic for your JTAG interface, then perhaps we might get to the bottom of this.

    On the one hand, I believe that Eclipse and CCSv4 should never hang like this, even if there is a slight timing issue with the JTAG interface on reset.  On the other hand, if I can figure out the exact hardware issue, I will gladly revise my main board to make things smoother.