• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 97 subscribers
  • Views 582 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.

Debugging w/IRQ's enabled on TMX320C5515 eZdsp USB Stick

John Westmoreland43
Guru 13945 points

Hello All,

Wanted to ask a question - when running the debugger with interrupts enabled, it seems to be a little unstable.  I have tried this in 'real-time' mode as well but the results seem to be the same.

I think also the usbstk lib supplied by Spectrum Digital isn't reentrant - could be the cause of some of this, maybe not,  but thought I'd mention it.

Has anyone else using the TMX320C5515 on the eZdsp USB stick experienced this?

Thanks,
johnw

  • 0
    TI__Mastermind 30631 points

    Hi John,

    What kind of instability are you seeing?

    The eZdsp uses the XDS100 for emulation, which does not support real-time data exchange (RTDX). See here.

    What do you mean by 'real-time' mode?

    Regards,
    Mark

  • 0 in reply to Mark M
    Guru 13945 points

    Mark,

    Under CCS there is an option to select 'Real-Time' debugging mode - states it will enable real-time debug and IRQ's can be enabled.

    I am not using DSP/BIOS in my code.  If this is a limitation of the XDS-100 - I am surprised the tools don't recognize that.  I tried to enable Trace, and the tools came back and told me that the target does not support Trace capabilities.

    I am not sure at this point if I am up against errata in the silicon or possibly due to using libs that are non-reentrant, or perhaps all of the above.

    The debugger becomes non-responsive, sluggish, slow, etc. when running the app - just trying to figure out what's going on.  There is not much of a stack trace, even when after stopping the debugger it appears to have landed on a valid instruction.  I have a breakpoint set on the reset vector to attempt to trap resets, but that has not yielded anything.

    Thanks,
    John W. 

  • 0 in reply to Mark M
    Guru 13945 points

    Mark,

    Interestingly enough - on the wiki page - also says this isn't supported:

    TMS320C55x+,

    Regards,
    John

     

  • 0 in reply to John Westmoreland43
    TI__Genius 13045 points

    John,

    The TMS320C55x+ is not used on any of the C5500 DSPs.  This is a enhanced CPU only used on some custom devices for a very large customer.  The standard C5500 DSPs all use the C55x CPU, either v2.2 or v3.3.  So that note doesn't apply in this case.

    Regards.

  • 0 in reply to TommyG
    Guru 13945 points

    Hello Tommy,

    Interesting.

    From the outside looking in - one could only surmise that TMS320C55x+ means 'c55x variants such as the'c5515 and that there are typos and/or old information on the wiki.

    Obviously the tools support the 'c55x series, so at first pass it appears to be typo(s) on the wiki without knowing the 'c55x+ series is only for a very large select customer; makes one
    wonder why it is even mentioned.

    Thanks,
    John