• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1817 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.

CCS/TMS320C5505: CCS7.2, xds100v2 after recent updates stopped working

Frank Lueck
Prodigy 30 points

Part Number: TMS320C5505
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hi all specialists,

need a bit of help:The configuration is c55xx--bypass_8. This worked for three years now and is used to preload the c5505 before programming via its rs232. ds speed is 1MHz or lower which does not matter.

Running Kubutu 17.04 ( 16.04 the same ). First, CCS stopped working at all due to segfault after kernel update but this problem is gone since the second last update, may be three weeks ago.  The comments in ./eclipse/ccsstudio.ini are removed.

Now the xds100v2 cannot connect to the target on both systems any more. Error -1063. There is no answer on TDO, even the nops are not seen whereas TDI Signals are given. Tested on several targets. Even the jtag cable is the same.

Using the MAXIM-jtag-progammer ( bypass_38--isp [win7, virtualbox]) the c5505 does its job and pipes through on the same machine, seen on TDO.

What changed? Any help would be apreciated.

Best,

Frank

  • 0
    TI__Guru**** 483791 points
    Hi Frank,
    Just to confirm, was CCS 7.2.0 with your target was all working before the first kernel update with caused the seg fault? And it stopped working since the second update that resolve the seg fault issue?

    Also, what version of the TI Emulators pack do you have installed (Help -> Installation details')?

    Thanks
    ki
  • 0 in reply to Ki
    Prodigy 30 points
    Hi Ki,

    the emulators are 6.0.628.3 and after update 7.0.48.0.
    I cannot tell you exactly when the segfault was solved because I had the -vm lines commented out in the ccstudio,ini to have a temporarily workaround. We swapped to ccs7 because the ccs6.1 also crashed.

    After the xds100v2 stopped working yesterday I removed the comments and found ccs7 working again with various kernels. We do not use the xds every day because once programmed, the board can be updated via serial port. Except ccs which is used recently. I remember an ccs-update last week which might have caused this behavior.

    What is odd the cxml - test-connection always reports exactly 86.3% whatever configuration is used. Then I tested an other board which is bp_38-bp_8-c55xx and c55xx-bp_8-bp_38. The same situation. I'm afraid something changed in Jtag initialization timing. I do not see any response on the chain's TDO line using the xds. Speed is set to 1MHz whereas the bp_38-MAXIM configuration is 2MHz without problems.

    Hope this helps to investigate,
    Best
    Frank
  • 0 in reply to Frank Lueck
    TI__Guru**** 483791 points

    Thanks. I am using a C5505EZDSP with integrated XDS100v2 probe. I don't seem to have any issues with that environment. I assume your environment is a custom C5505 board with an external XDS100v2 debug probe.

    Frank Lueck said:
    What is odd the cxml - test-connection always reports exactly 86.3% whatever configuration is used.


    which scan is 86.3%? The JTAG integrity scan for IR or DR? Or both? That, combined with the -1063 error that pops up seems to point to robustness issues with the connectivity between the probe and the target (connection, noise, etc). Can you try lowering the TCLK frequency to 0.5 just to see if that helps?


    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 30 points
    Hi Ki,

    your suggestions are right. It turned out that the XDS100v2 was broken, laying around but powered up.

    Caught a brand new XDS110 today and all is working fine again.

    Thank you again for your help!

    Best regards
    Frank
  • 0 in reply to Frank Lueck
    TI__Guru**** 483791 points
    Good to hear. Thanks for the update!