• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 53 subscribers
  • Views 343 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: TMDSEMU560V2STM-U issue

rei
Mastermind 6135 points
Part Number: TMS320C5505
Other Parts Discussed in Thread: TMDSEMU560V2STM-U, TMDSEMU560V2STM-UE

Tool/software: Code Composer Studio

Hi,
My customers debugging on a custom board using C5505. Previously, They used another JTAG emulator, however in order to improve debugging efficiency, they purchased TMDSEMU560V2STM-U.

TMDSEMU560V2STM-UE (SpectrumDigital) can load the out-file normally. However, TMDSEMU560V2STM-U (BlackHawk) that they purchased has a problem in loading the out-file. If they press the debug button, you will jump to a mysterious function (_args_main function). And there is another mysterious phenomenon.

After loading fails (Reach _args_main () function), pressing the debug button again will load the correct out-file.
We can confirm that they have reached _args_main() function last time.

Debug picture 1st time

Debug picture 2nd time (confirm _args_main() )

Question:
They tried changing and re-installing CCS version. However, it has not been solved. Is this a known issue? Please tell me the solution?

■Environment

CCS v8.3.1

windows10

Regards,
Rei

  • 0
    TI__Guru**** 168297 points

    Rei,

    As a general statement, when the device behaves differently when connecting or running successively, an incomplete hardware initialization done by either the GEL file or the code is usually the root cause. 

    Given your scenario indicates the only difference is swapping the Debug Probe, my suspicion is the Blackhawk may have a default JTAG configuration that is slower or faster than the Spectrum Digital - this could explain why the Blackhawk fails to connect at the first time, given it may not be giving enough time for the hardware to react properly. Again, this may require some tweaking to the GEL file. 

    Can you inspect the Advanced tab of the target configuration file (.ccxml) for both connections and see if there are any differences between them? 

    I am assuming that everything else is identical, including the procedure you are adopting, the Debug Configurations, GEL files, etc. 

    Unfortunately I do not have a 5505 EVM to test the exact same scenario as yours, but the 5517 EVM I have here does not show this behaviour.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Mastermind 6135 points

    Hi Rafael,

    Sorry, they don't have a SpectrumDigital JTAG probe right now.
    Previously we lent our SD probe. But now I got it back.
    Therefore, I don't know if the same target config file is used.
    However, they understood the cause a little.
    They confirmed that the C5505 GEL file was not loaded the first time.

    They thought they needed to specify a GEL file.

    How can we load an arbitrary GEL file (C5505.gel) on the target board when the Debug button is pressed?

    Regards,
    Rei

  • 0 in reply to rei
    TI__Guru**** 168297 points

    Rei, 

    rei said:
    How can we load an arbitrary GEL file (C5505.gel) on the target board when the Debug button is pressed?

    From inside the Target Configuration File, set the connection to a board such as the EVM5505 or the USBSTK5505 instead of the device itself. The boards have the GEL file automatically added to the configuration. 

    Regards,

    Rafael