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/TMDSCNCDH52C1: H52C1 Concerto Experimenter Kit is NOT SEEN !

Part Number: TMDSCNCDH52C1

Tool/software: Code Composer Studio

Hi Everyone,

I am trying to use H52C1 Concerto Experimenter Kit ( TMDSCNCDH52C1 ). The Experimenter Kit I use does not seen at Target Configuration. I using together Experimenter’s Kit USB Docking Station with TMDSCNCDH52C1.

. Which ones should I choose in Target Config?

CCS IDE Version: 7.0.0

Screen shot is below. Can someone help me, please ?

Best Regard,



  • In this case please use the device F28M35M52C1 from the drop down, as this is the C2000 MCU on the experimenter kit you have.

    I'm not sure why the experimenter kit is not listed(I don't see it on my install either), but using this device will give the same results as selecting the board.

    I'll look into the latter to understand why we show some and not others in the drop down.



  • As you said, I've loaded XDS100V2 driver, after I have chosen F28M25H52C2 and tested connection, but the result is same.

  • Thanks for the additional info from CCS, I beleive the issue is due to the isolated JTAG implemenation on this control card.

    Looking at the info sheet on page 3, lists the different LEDs.  We want to look at LD1 and LD4 specifially.

    If you see that LD1 is not lit, then this confirms that the control card is not powered.  Since the JTAG is isolated, the control card does not draw power from that USB connection, only the emulation logic.  You will also need to plug the control card into the base board, and power it; either with another USB or a 5V barrel connnector.

    If you do see both LD1 and LD4 lit and still can't connect, we will need to look further down in the signal chain to find the issue, just let me know.



  • Hi Matthew, 

    Firstly, thank you so much for reply. 

    LD4 is lit, LD1 is not lit if only the control card is powered. However LD1 and LD4 are lit when I powered from the Dock Station Card and Control Card. Because, like you said, Control Card has isolators.

    Changes I made on the Control Card:

    1- I've done short circut to resistors(R40,....R46) for pins. (TCK-S, TMS-S, EMU1-S, TDI-S, TDO-S, TRSTn-U32, EMU0-S)

    2- I've done short circuit to J21 jumper for EMU0-S pin. 

    Interestingly, I still couldn't.

    Is there something wrong ?

  • When you run the "test" from the Target Config window after you powered the base board(LD1 is now lit) was the output different from before?  There shouldn't be a reason to change the passives on the PCB at this time.

    It may be helpful to refer to this app note: in terms of debug steps.  This will help us get on the same page; i.e. if you go through the app note and can say I got to step X.X then it will help to narrow down the potential issue.



  • I had mis-interpreted your earlier post; when you populated R40-R46 you have now enabled the XDS100v2 path from the base board to the control card.  So now we will only have 1 USB connection from the PC to the base board; and it will supply both power and emulation.

    There is a jumper J8 on the base board, you will need to make sure that is NOT populated, as it will hold that emulator in reset if shorted.  Also, make sure NOT to plug in the USB to the control card XDS100V2, so we leave it unpowered.  If we have both powered, and the resistors populated there will be contention on the JTAG bus and the device will not connect.

    The alternative config would be to connect 2 USBs, one for power on the base board(and not populating R40-R46), and another to the XDS100V2 USB on the control card itself.  The only item of note here, would be to make sure SW3 Pos 1 is "On" as this gates TRSTn signal from the on-board JTAG.


  • Replying back to see if you have resolved your issue with the above.  I'm going to mark this as TI thinks resolved, but feel free to reply back if that is not the case and we can continue the debug.


  • Hi Matthew,

    Actually, My problem was not solved, but I continue to develop software through our own board.

    Thank you

  • Thanks for the feedback and clarity.  Understand that now you have a debug platform that is the priority vs debugging the controlCARD issue. 

    I'm going to close this on my side; please feel free to reply back or re-post if you want to continue to debug the control CARD connectivity.