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.

TMS570LS3137 in Daisy chain and Segger JTAG problem

Hey guys,

     I have a question related to the Hercules mcu and a jtag toolchain. We have the daisy chain which contains STM32, Eth driver, Hercules and Altera (in this order). This chain works fine with JTAG by TI and CC5 but it does´t work with the J-Link by SEGGER. What is quite strange is that there is no problem to connect to the STM32 (flash that and debug) on the same daisy chain. The problem occures when selecting the Hercules mcu and trying to flash it.

I´ve already written a post to SEGGER, but I wonder if someone from this community happen to have a similar trouble with the JTAG. Daisy chain is electrically OK, it´s a question of JTAG and SW.

Thanks a lot.

Alex.

  • Alex,

    Could you please describe the way you daisy chain the TCLK on the Hercules device?

    Thanks and Regards,

  • Hi Jean-Marc,

            we connect TCK parallel to all devices as well as TMS and TRST signal. We've already tried to unconnect and pull TRST up but with no effect. Funny think is that it works fine with JTAG by TI but not with the j-link by segger.

    Alex.

  • Additional info:

    There is STM32F205 uC (it is reporting itself as 2 devices, 4+5 bit long registers, Ethernet driver TLK100 (4 bits), Hercules uC TMX5703137 (6 bits) and Altera Cyclone III(10 bits). The only device we can communicate with (usink Jlink) is STM32F205. But Jlink reports:

    VTarget = 3.280V

    Info: TotalIRLen = 29,

    IRPrint = 0x01110555

    Info: Found Cortex-M3 r2p0, Little endian.

    Info: TPIU fitted.

    Info: ETM fitted.

    Info: FPUnit: 6 code (BP) slots and 2 literal slots

    Found 5 JTAG devices, Total IRLen = 29:  

    #0 Id: 0x020F40DD, IRLen: 08, Unknown device  

    #1 Id: 0x0B8A002F, IRLen: 06, IRPrint: 0x1, TI ICEPick  

    #2 Id: 0x0B84F02F, IRLen: 06, IRPrint: 0x1, TI ICEPick  

    #3 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)  

    #4 Id: 0x06411041, IRLen: 05, IRPrint: 0x1, STM32 Boundary Scan

    Cortex-M3 identified. JTAG speed: 100 kHz

     

    Flashing of Hercules from CCS5 with TMDSEMU100 version 1 in chain works fine, following steps decsribed here http://processors.wiki.ti.com/index.php/J-Link_Emulator_Support#Downloads does not help (works only if we have single uC only = no chain). Electrically is everything OK for sure (checked via oscilloscope on bits level), we are able to flash Altera in chain (again using another Jtag interface), therefore we expect problem in Jlink settings or driver.

  • Ales,

    What is the status on your post? Did I answered your question?

    If so, can you mark it as "Verified Answer" so I can close this thread?

  • I am sorry, but I do not see any answer in this thread. :-)

  • Pavel,

    I did some research on Segger forum and found the following answer to your post:

    ============================================================================

    Hi,

    Currently daisy-chaining for the TMS570 series is not supported for automatic usage since this is a difficult case for this device.
    The TMS570 series have an ICE-Pick device on then which requires to be initialized first in order to make the CPU accessible (this also dynamically changes the JTAG chain length).
    Unfortunately, full-auto detection is not possible here.

    In order to use your setup, you need to write a so called J-Link script file which setups the complete JTAG chain and also handles the connect (which configures the ICEPick)
    as well as the reset (which also needs to be performed in a special way on the TMS570).

    For more information about J-Link script files in general , please refer to
    http://www.segger.com/admin/uploads/prod…01_JLinkARM.pdf
    Chapter 5.10

    Sample script files can be found at $JLINK_INST_DIR$\Samples\JLink\Scripts


    Best regards
    Alex

    ==============================================================================

    Have you tried their solution using a script to configure the IcePick module as it is suggested?

    Please let me know.

  • Jean-Marc,

      the post on the Segger forum is actually my post and it really works. I'm sorry that I forgot to close this post. Guys from Segger really help us.

    Alex.