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.

TMS320F28377D: Stand alone board not being detected. Please help.

Part Number: TMS320F28377D
Other Parts Discussed in Thread: C2000WARE

Hi Guys, I've created my own ( First) breakout board for the F28377D LQFP 176 pin and CCS9 is not detecting it when I try and download code via JTAG using the XDS110 Debug Probe.

My F28377D has been soldered to my breakout board using a reflow oven. I've checked ALL pins to the breakout board pins and all is fine. I did have one bridge in the solder but I fixed that with some flux and the soldering iron.

I've setup the 14PIN JTAG header as to the instructions in the TMS320F28377D manual, page 70. Setup all the correct Capacitor values 0.1uF and 2.2. Setup ALL the 3.3V and 1.2V lines and everything else what the manual says to do but still no detection.

The error code that CCS9 says is this: ERROR CONNECTING TO THE TARGET: (error-2131 @ 0x0) Unable to access device register. 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 9.2.0.00002)

I've checked voltages, all +3.3V and 1.2V are at the correct levels, capacitors are correct and on the correct pins. RESET XRS PIN has a 10K pullup and 22NF ceramic Capacitor to ground.

Oh, boot pins are not connected because the manual says that with default settings if boot pins are LOW then code runs from flash but that shouldn't stop the detection of the F28377D should it?

Any suggestions would be greatly appreciated. In the mean time I'll go over my wiring and soldering yet again to see if I've missed anything.

Thanks guys so much for your help, waiting desperately for any advice.

Peter :)  

  • Peter Adamcik said:
    Oh, boot pins are not connected because the manual says that with default settings if boot pins are LOW then code runs from flash but that shouldn't stop the detection of the F28377D should it?

    You should have boot mode pull resistors. This will not likely keep your board from connecting, but with a little bit of noise your device could boot into the wrong boot mode configuration.

    Have you verified that your device has a clock input?

    What temperature profile did you use with the re-flow oven? These devices are pretty robust, but be damaged by heat if too high of a re-flow profile is used.

    Are you willing to share your schematics?

    Regards,
    Cody 

  • Hi Cody, thanks for your input. Yes I will use pull-ups on the boot pins for sure. BOTH boot pins need to be HIGH to boot from flash.

    With the clock, I've setup the JTAG connections as per the manual and made sure every wire goes to where it goes with the correct pullup and pull down resistors.

    I'm using the XDS110 Debug Probe and using the 14 pin converter to connect to my board. 

    Do you think the 14 Pin converter is NOT the same connections as it shows in the manual for JTAG?

    This is the only thing I can think of at this stage. I've gone over my circuit 5 times now and ALL checks out so it must be the 14 PIN Converter.

    BUT I use the same converter for my F28377D control card with Docking Station and it programs fine using the JTAG connector.

    So thats why I'm asking for help, because I'm stuck at this stage.

    Oh, the reflow oven was set at 180deg so no probs there. I've made many boards at that temp and all the other micro controllers are fine.

    I'll check the clock signals and see how I go. 

    Do you or anyone else have any suggestions?

    Peter

  • Peter,

    I would encourage you to keep an open mind when debugging, its the smallest assumptions that waste the most time. Your problem may not be in the 14 pin header. But nevertheless I can confirm the pinout in the datasheet is correct and does work.

    I would suggest comparing your schematic to the controlCARD's schematic found in C2000Ware. If you share your TI14 JTAG pinout I can review it. 

    What voltage can be observed on the XRSn pin?

    Regards,
    Cody 

  • Hi Cody, thanks for you help, I really and totally appreciate it. Below is how my 14 PIN JTAG header is setup.

    PIN 1: Directly to TMS (PIN 80)

    PIN 2: Directly to TRST (PIN 79) with 2.2K pulldown resistor.

    PIN 3: Directly to TDI (PIN 77)

    PIN 4: Directly to GND

    PIN 5: Directly to +3.3V connected through a 100 Ohm resistor.

    PIN 6: N/C No connection. I've cut this pin on the header so the 14 PIN Converter will connect.

    PIN 7: Directly to TDO (PIN 78)

    PIN 8: GND

    PIN 9: Directly connected to PIN 11 ( TCK )

    PIN 10: GND

    PIN 11: Directly connected to TCK (PIN 81)

    PIN 12: GND

    PIN 13: Directly connect to +3.3v in series to a 4.7K resistor.

    PIN 14: Directly connected to +3.3v in series to a 4.7K resistor.

    I've tested each of the pins with the beeper using my multimeter directly on the pins on my JTAG boards connector to the pins directly on the MCU F28377D itself so I know for a fact they are soldered correctly with no solder breaks. If you say the connections in the manual are correct then my JTAG setup here should also be ok then.

    The XRS Pin is connected to (PIN 124) with a 10k pullup to +3.3v and 0.1 (104) ceramic capacitor to GND just as the manual says to do so.

    I've also tested the powerpad GND plane and GND is connected. Tested with my beeper on my multimeter. I have a large VIA underneath the MCU so I've soldered that to the powerpad GND plane. When I touch the powerpad GND plane with my probe and GND I get a beep from my multimeter so I know for sure GND is connected to the powerpad GND plane.

    Well, as you can see the Voltage on the XRS pin is +3.33 to be exact lol. 

    I'll go over the control cards schematic for some pointers but I have set up my board via the manuals instructions. 

    I've setup and created breakout boards for PIC32 and XMEGA256D3's and they work first time but the F28377D LQFP is certainly a challenge. I don't want to use PIC32 for our product and the TI F28377D is perfect for our product and I mean perfect. I Love the C2000 assembler code. 

    OK, I'll check out the control cards schematic and see for pointers.

    Thanks Cody, hope to hear from you soon for more pointers.

    Peter

  • Hi Cody, I just compared my JTAG pinout with the ControlCARD's JTAG pin out and they are both exactly the same. So the fault is not with the JTAG pinout then. What could it be? Would TI have a list of the minimum steps on setting up the F28377D LQFP 176 PIN to get it to program?

    I've gone over all the 3.3v and 1.2v pins making sure they are the right voltage. GND PAD is connecting and JTAG Pins are correct. Pullups and pulldown resistors on the JTAG pins are correct. Capacitors on the power pins are correct, I triple checked them.

    I think I've checked everything, What else is there to check?

    Obviously there is still something wrong because it won't access the device register.

    I have no idea what to check next.

    Pete

  • Hi Cody, I was just thinking. Maybe it's a software problem in CCS9?

    Do I have to tell CCS9 to expect a stand alone F28377D board and not the F28377D control card?

    If so then how do I go about changing the config?

    Peter

  • Peter,

    Peter Adamcik said:
    I've also tested the powerpad GND plane and GND is connected. Tested with my beeper on my multimeter. I have a large VIA underneath the MCU so I've soldered that to the powerpad GND plane. When I touch the powerpad GND plane with my probe and GND I get a beep from my multimeter so I know for sure GND is connected to the powerpad GND plane.

    Do you have a separate power pad ground plane? If so how is this connected to the normal ground plane? These should be the same, if you have designed your PCB correctly touching a PowerPAD ground and any other digital ground on the board should have ~0Ohms of resistance with or without a device soldered. If I am understanding you correctly I don't think this verifies that your powerPad is soldered correctly. Nevertheless this isn't a very common issue. Why do you suspect your power pad isn't grounded?

    This might sound silly, but did you cut the right pin off of your JTAG header?

    CCS9 shouldn't have any issues. When setting up your target configuration all that matters is that you select the correct debug target (F28379D in your case) and the correct debug probe (which i believe you said you were using XDS 110). If you use the same target configuration as the controlCARD it will not work because the controlCARD uses an XDS100v2 debug probe.

    Regards,
    Cody 

  • Hi Cody, thanks for the reply. Yes my GND plane is all connected. I do not have a seperate GND plane for the MPU. When I touch the PowerPAD GND with external GND my multimeter BEEPS so GND is connecting no probs. Checked all the 3.3V and 1.2V lines with the appropriate capacitors, its crazy !!!

    With CCS9 Target Configuration. I've checked it and its set to this:

    Texas Instruments XDS110 USB Debug Probe

    TMS320F28377D, _IcePick_C_O, Subpath_O. C28xx_CPU1, CPU1_CLA1,ch_child_0

    Subpath_2, C28XXCPU2, CPU2_CLA1,cs_child_1

     

    So CCS is set to XDS110 and not the XDS100v2. 

    *** Should I create a new project and use the XDS110. The project I'm using now works using the JTAG on the ControlCARD Docking Station but not on my board.

    Would that be the problem?

    Oh, YES it is a silly question if I have not cut the wrong pin. LOL. PIN6 (key) is cut or else the 20 to 14 Pin adaptor will not fit on to my 14 PIN JTAG Header.

    I'm building another F28377D board and triple checking every connection I make. I'll see if I get the same error with this new board.

    I still think its a CCS9 connection fault. 

    Oh just one more thing. In the manual it says that XRS should have a 2,2k to 10K pullup resistor. On the ControlCARDS XDS it has a 510k pullup resistor. Which one should I use? the 10k to 510k pull up resistor?

    Thanks again for you help on this mate. :) 

    Peter

  • I've just run a TEST CONNECTION and this is what was in the text window. Let me know if I have to change a few software parameters.

    [Start: Texas Instruments XDS110 USB Debug Probe]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    /Users/a1234/.ti/ccs920/0/0/BrdDat/testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'libjioxds110.dylib'.
    The library build date was 'May 7 2020'.
    The library build time was '20:49:37'.
    The library package version is '9.2.0.00002'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '5' (0x00000005).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the XDS110 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for XDS110 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-233' (0xffffff17).
    The title is 'SC_ERR_PATH_BROKEN'.

    The explanation is:
    The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
    An attempt to scan the JTAG scan-path has failed.
    The target's JTAG scan-path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault.

    [End: Texas Instruments XDS110 USB Debug Probe]

    Pete

  • Peter Adamcik said:
    Oh just one more thing. In the manual it says that XRS should have a 2,2k to 10K pullup resistor. On the ControlCARDS XDS it has a 510k pullup resistor. Which one should I use? the 10k to 510k pull up resistor?

    Please follow the datasheet.

    Peter Adamcik said:
    *** Should I create a new project and use the XDS110. The project I'm using now works using the JTAG on the ControlCARD Docking Station but not on my board.

    it is not necessary to create a new project. Please ensure you are using the correct target configuration file. Can you please describe how you are launching your target configuration?

    Can you show me a picture of your "debug" window after you launch the target configuration?

    Thanks,
    Cody  

  • Pete,

    How have you connected TDI, TDO, TCK, TMS, TRSTn? Please share the circuit. Have you verified the device clock input yet? 

    It seems like you have power and ground, so all you need is clock, the correct connections to the JTAG pins and your hardware should be good to go.

    Thanks,
    Cody 

  • Peter, 

    if you are still having issues with this let me know. If another issue comes up please start another thread.


    Regards,
    Cody 

  • Hi Cody, Thank you for all you help with our issue. We are having our board checked to see if we have missed something.

    Have a great day and thank you again.

    Peter