infineon4engineers Facebook

infineon@google+ Google+

infineon@linkedin linkedin

infineon4engi@twitter twitter

infineon@youtube youtube

+ Reply to Thread
Results 1 to 2 of 2

Thread: Mini Wiggler and TC1796

  1. #1
    New Member New Member Gince is on a distinguished road
    Join Date
    May 2018

    Mini Wiggler and TC1796

    Hello, can anyone share few ideas about Mini Wiggler V3 and TriCore TC1796? I'm trying to read it via JTAG, using following pads - TDI / TDO / TCK / TMS / VREF / TRST.
    I also connect PORST to PIN10 (reset) on miniwiggler. Also on JTAG pads there is BRKIN BRKOUT. I use DAS server - running UDAS server, DAS JDS miniwiggler V3.1 recognized.

    I power up my target board, MCU has stable 3.3V . I check with oscilloscope TMS / TDO / TDI - high level, TCK and TRST - low level. Before opening MemTool I check on DAS Basic Client
    if it sees my target - green light is blinking which indicates that Mini Wiggler is scanning for active devices, another green light is stable indicating that target device is powered.
    Any ideas why my target is not communicating with mini wiggler?

    On TC1796 I see HDRST, PORST, TSTRES. I use the one that is on JTAG pad - PORST.

  2. #2
    New Member New Member
    Infineon Employee
    Infineon Employee
    MoD is on a distinguished road
    Join Date
    Feb 2012
    per default is the miniWiggler in DAP mode and expect a device which is able to communicate via DAP. TC1796 has only JTAG, therefore the CPU can't answer the DAP telegrams. You must switch the miniWiggler in JTAG mode. If you don't have the 20 pin JTAG connector on your board and can't connect 1:1 (this is was I expect) then you must set the miniWiggler to JTAG mode by connect pin 19 of the 20 pin JTAG connector to ground. Pin 17 of the connector is e.g. ground.
    I am not sure that the latest UDAS supports the TC1796 but you can check this by the described solution.
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

+ Reply to Thread

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.

Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.