• State
  • Locked Locked
  • Replies 14 replies
  • Subscribers 82 subscribers
  • Views 405 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: JTAG Minimum Pin connection to download code from CCS9.

Peter Adamcik
Expert 1425 points
Part Number: TMS320F28377D

Hi Guys, does anyone have a list of minimum PIN setup using the JTAG connector on a standalone F28377D LQFP 176 Pin breakout board.

I'm trying to download code to my breakout board and no luck. I've gone over the JTAG setup connections 5 times now, tested each pin and all is connected when're they should be.

This is pretty urgent so if you have any info please let me know. I just want to download my assembler code to my F28377D Breakout board.

Error code when I click on the DEBUG button is: 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)

Hope to hear from you soon.

Peter

  • 0
    TI__Guru** 109125 points

    Peter,

    This information is available in section "5.9.5 Emulation/JTAG" of device datasheet. You need 5 pin connection and proper pulls also on these pins. 

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Guru 71785 points

    Peter,

    Can you take a screenshot of the target config setup(both the default tab and the "advanced tab"?  If you use the "test connection" button here, can you post the output it gives back to this thread? 

    In cases like these I like to avoid using the "debug" button to launch the connection, since it does a few other housekeeping steps that can cloud the issue.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Expert 1425 points

    Hi Matthew, thanks for the reply. Below is my Test connection info.

    [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]

    Please let me know if know what the problem is.

    Peter

  • 0 in reply to Vivek Singh
    Expert 1425 points

    Hi Vivek, Yes that is how my JTAG is setup. I've checked it 5 times. I did a test connection and this is the report fro CCS9.

    [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]

    Please let me know if you have any ideas.

    Thanks again for your help.

    Peter

  • 0 in reply to Peter Adamcik
    TI__Guru 71785 points

    Peter,

    Would it be possible to place the device in Wait Boot mode according to the datasheet and then try connecting?  This will ensure that the code is in a wait loop and not potentially blocking the emulation access.  I assume from the previous post that this was a new device(un programmed)?

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Expert 1425 points

    Hi Matthew, thanks for the help. Yes the 5x devices I've purchased have not been programmed yet. They're from Digikey.

    Does unprogrammed F28377D micro controllers have a special first time programming mode? 

    I'll try the Wait Boot mode today and see how I go. 

    Thank you so much for the help mate, muchly appreciated.

    Peter

  • 0 in reply to Peter Adamcik
    TI__Guru 71785 points

    Will look if this helps, actually there should be less potential issues with new devices in terms of connecting.  Namely there is no chance that the device is secure, which would disconnect the JTAG connection if an attempt to connect is made.  

    Best,
    Matthew

  • 0 in reply to MatthewPate
    Expert 1425 points

    Hi Matthew, so how do I fix the problem then?

    Peter

  • 0 in reply to MatthewPate
    Expert 1425 points

    Hi Matthew, I tried WAIT mode and I get the same error. I tried GET mode and I get the same error. 

    What could be the problem??????? I'm starting to stress out.

    Peter

  • 0 in reply to Peter Adamcik
    TI__Guru** 109125 points

    Peter,

    You have got the error during test connection which means there is issue with the JTAG signals on the board. You need to do signal integrity check to make sure all the signals are properly connected. 

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 1425 points

    Hi Vivek, I made a whole new JTAG connection on my board and I still get the same error message. I don't understand it. I've checked all the connections over and over with again my multimeter BEEPER. All is soldered correctly and all the pins that need the pull-ups to +3.3v and pull down to GND has the correct values. GND pins are soldered to GND. 

    I tried GET MODE and I tried WAIT MODE. The manual says on unprogrammed devices I need to use WAIT MODE and I still get the same error.

    I'm all out of ideas. Can I PM you or can you PM me and I will reply.

    Peter

     

  • 0 in reply to Peter Adamcik
    TI__Guru** 109125 points

    Peter,

     I tried GET MODE and I tried WAIT MODE. The manual says on unprogrammed devices I need to use WAIT MODE and I still get the same error.

    That is expected, If you have error with TEST CONNECTION then WAIT MODE will not help. Have you checked all the power supply on board to make sure values are as per the spec and stable ?

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 1425 points

    Hi Vivek, I have made another project board from scratch and triple checked every wire, every capacitor as I built the new board.

    Voltages are +3.2V and +1.2V and the correct pins. All power pins have the correct capacitors as the manual explains.

    I'm using WAIT mode because the manual says new devices that have not been programmed yet need to use WAIT mode to be programmed.

    I tested GND to the powerpad GND plane and that BEEPS my multimeter so GND is connecting fine.

    I then ran a connection test and this is the error I get.

    [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]

    I triple checked the JTAG pins and all are correct with the correct pull-ups and pulldown resistors.

    Voltage is correct. +3.2V and +1.2V.

    I was reading about the security on the chip, do I need to set anything special so the security part will grant me access to programme the F28377D?

    Peter

     

  • 0 in reply to Peter Adamcik
    TI__Guru** 109125 points

    Hi Peter,

    Sorry to know that issue is still not resolved.

     I was reading about the security on the chip, do I need to set anything special so the security part will grant me access to programme the F28377D?

    By default security is disable so you should not have issue with security. Did you try different XDS110 emulator ?

    Regards,

    Vivek Singh