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.

XDS100 V2 Connection problem with TIVA

Other Parts Discussed in Thread: TMS320F28335, LM3S8962, TMS320F28027, LM3S2110, TM4C1294NCPDT

Hello all,

One of my customer is using TM4C129xx for one of his application. he is facing the problem with our xds100 v2 emulator. the said controller is not getting detected by it. 

I even tried it with Olimex XDS100V2 (14 pin)  emulator, but the result is same.

The observation is  TMS320F28335 experimental board is getting detected with the same xds100.

With ICDI , TIVA is getting detected but not with XDS100V2. 

He purchased 3 XDS100 V2 from olimex,ebay and TI online. None of them is working for TIVA while tested OK for C2000.

Please guide me to address the problem

Regards,

Mandar 

  • Hello Mandar,

    1. Is this a custom board that the customer has?

    2. Can you specify the full model number of the XDS100V2 the customer has tried?

    3. If the IDE is CCS then can you please send the ccxml file for target configuration?

    4. Is the TIVA correctly powered to 3.3V, the VDDC pin is at 1.2V and the External Crystal mounted and Reset to TIVA at logic level 1?

    Regards

    Amit

  • hello Amit,

    1) Rt . now is it our EVM board. Even i have tried on LM3S3862 EVAL board.

    2) Model no: XDS100V2 TI DSP Emulator.

    3) I am attaching the target config file for LM3S8962 EVM. 

    4) The tiva is correctly powered .8255.Stellaris LM3S8962.zip

  • Hi Amit,

     I verified the scheme and found problem with XDS100 customer had purchased. from 3 sources

    1) Olimex

    2) E - Bay

    3) Ti- Online

            All these tools are with 14 pin connector

            All three are functionally tested OK with TMS320F28027 & TMS320F28335. But not able to detect and program TIVA microcontroller.

           we are using LM3S2110 and TIVA board to test these XDS100V2 from customer. 

    ** I had one XDS100V2 14 pin which I tested with TIVA and found OK. This is now shared with cusotmer as stop gap arrangement till the time we are able to find the problem with these XDS100.

          Would like to know hos can we debug these programmer.

    Regards,

    Nishant Dattaram Chorge

     

     

     

     

     

     

  • Hello Mandar,

    I believe all of the above mentioned emulators have a 14-pin JTAG interface, is that right? If not then please attach the datasheet for the emulators

    If yes, then I would ask you to send the JTAG header schematic for the customer board?

    Regards

    Amit

  • Hello Nishant,

    That is what I mentioned in my post as well. It seems that the JTAG header and the customer schematic for interfacing JTAG to the TIVA may not be correct and needs to be reviewed. In the past I have seen this issue due to the fact the emulators have a different pin layout than the target board.

    Regards

    Amit

  • Hi Amit and Nishant,

    I'm experiencing similar problem and I'm not sure if or how the issue was resolved.

    I'm using XDS100v2 with TM4C129xx, running on proprietary board that is connected to the XDS JTAG using the standard signals: TMS, TDI, TDO, TCK, RST_N, VCC (3.3v), GND.

    CCS v6 is configures for the specific MPU and yet I'm getting a constant error while trying to load a program:  

    (Error -2062 @ 0x0) , something about not being able to halt the device.

    From the HW signals monitoring it seems that TCK TDI and TDO working ok, RST_N is constantly high and I don't see any activity on it (tried to connect to nTRST and nReset on the XDS100 side, same result).

    Any idea what might be the problem and how to overcome it?

    Thanks in advance!

    Gal

     

  • Hello Gal,

    Is this the first time you are connecting the XDS100v2 to the TM4C129xx proprietary board? I would ask you to go through the trouble shoot guide

    http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/t/374640.aspx

    http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/t/158121.aspx

    There are some more checks like, de-cap, oscillator pad connections, that I would ask you to confirm.

    Regards

    Amit

  • Hello Amit,

    Thank you for your help and inputs.

    Yes, this is the first connection effort.

    I've briefly went through the suggested articles, one thing that I managed to check is that the "Test Connection" function in the CCS works properly and the test pass.

    Having said that, still the same error is presented. Does this sounds familiar?

    Thanks,

    Gal

    From the article: 'SOLUTION: If using XDS Emulator and CCS IDE, there exists a utility in CCS called "Test Connection". This will tell if the JTAG is hooked up correct by running a serial pattern sequence. If it Passes then the device is alive and JTAG hooked up correctly'

  • Hello Gal,

    JTAG Connection Test merely uses the Bypass mode as per JTAG standard. However it is critical to have the JTAG connected correctly for this to test to pass. So the main hurdle of getting the connectivity is over.

    Now, some more info as I would require is to check if there is a crystal on the board, if yes then is soldered down well, if now then is the OSC0 Pad connected to GND.

    Is the de-cap on the VDDC pin in the range of 2.5-4.5uF (as specifed by the data sheet)?

    What is the JTAG TCK frequency and lastly what is the exact error message,

    Regards

    Amit

  • Hello Amit,

    I've examined the board, herein are the findings

    - OSC0 has clean 25Mhz signal from the external oscillator.

    - OSC1 has 25Mhz signal with some distortion (not as clean as OSC0) .

    - GNDX2 is grounded

    - VDDC decap is exactly as in the DK-TM4C129, 4 capacitors in parallel : 1u , 0.1u, 0.01u, 2.2u 

    - TCLK shows 1Mhz and isn't changeable even though I tried to lower it via the CCS Target Configuration.

    The full error description is :

    CORTEX_M4_0: Error connecting to the target: (Error -2062 @ 0x0) Unable to halt device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.600.0) 

    So, my problem is first of all the TCK that  is not controlled by CCS and I can't lower it.

    Second, I assume there is no real limitation using 1Mhz TCK while trying to connect to an ARM with 25Mhz external oscillator, right?

    Any idea?

    Thanks a lot,

    Gal

  • Hello Gel

    Yes, 1MHz TCK with 25MHz Crystal is fine. At the time of the connect can you scope the VDDC Pin as having the 4 caps is not sufficient but also that the 2.2u should be the closest to the device.

    You can lower the frequency of XDS100V2 in the CCS ccxml file and also try the same.

    Regards

    Amit

  • Gal,

    Did you ever resolve your issue? We are having very similar problems (error message is identical, and the JTAG connection test succeeds) and would appreciate any insight you could offer.

    Thanks!
  • Hello Eric,

    Is this is a custom board (if yes schematic please). What is the device being used, was this the first program attempt? Details are required as we would treat every case as a unique case even if it has the same tell-tale signs

    Regards
    Amit
  • Amit,

    Yes, this is a first programming attempt. We are using a TM4C1294NCPDT. Should I email the schematics to you?

    Thanks,
    Eric
  • Hello Eric,

    Yes you can send it via the "Conversations"

    Regards
    Amit
  • Hi,

    I hope I will be able to help.

    I had two issues:

    1 - using proprietary board, the setup of the TIVA MPU was to use a 25Mhz external oscillator and one of the external signals (Rbias if not mistaken, but not sure) was tied to gnd. In this case, while the MPU flash was empty, the MPU is automatically boots from Ethernet and therefore the jtag is not responding. Had to remove the crystal to overcome this. Amit, correct?

    2-  this one is trivial, every chip is shipped locked and needs to be unlocked using the LM Flash programmer software,

    Best of luck,

    Gal

  • Hello Eric,

    I think the issue is:

    The RBIAS is not connected to GND via 4.87K resistor. There is a known errata for the same

    Hello Gal,

    Yes, remove the crystal and connect OSC0 to GND or add the RBIAS.

    However devices are not locked when they are shipped out.

    Regards
    Amit
  • OK, looks like I had an old version of the errata that did not have the RBIAS issue. Bitten by the errata again!

    If a resistor is added to the RBIAS pin, do I still need to remove the crystal?
  • Hello Eric

    No. If the resistor is added then the crystal removal is not required.

    Regards
    Amit