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.

TMS320F28069: XDS560v2 can not access to F28069 after a reset occurred during flash programming

Part Number: TMS320F28069

Hi Champs,

A customer has been facing a trouble as follows:

An external HW reset occurred during flash programming with XDS560v2.
After that, CCS shows the error message below and it never connect to the board.

Error connecting to the target:
(Error - 180 @ 0x0)
The controller has detected a target power loss.
The user must turn-on or connect the power supply for the target.
(Emulation package 6.0.407.3)

The voltage between VTREF and GND on JTAG is approx. 3.295V.
Has there been any known issue?
I would like to know what the customer should check and do for its recovery.

Thank you for your kind check.
Best regards,
Hitoshi



  • Due to US holidays, you can expect a response by 3'rd Dec.

  • Hi Hitoshi,

    Are they using a custom board or a TI evaluation board? Is the 'Test Connection' feature within CCS successful for them?

    There's a good Application Report on JTAG connectivity debugging, linked below:

    http://www.ti.com/lit/spracf0

    What are the state of the boot mode pins on the customer's device?

    Best,

    Kevin

  • Hitoshi,

    Seeing if this is still an issue or customer has understood the issue.  Please let us know if there is more action required from us.

    Best,

    Matthew

  • Hi Matthew,

    They are utilizing their custom board.
    After they clicked "Test Connection", the log was as follows:

    [Start: Texas Instruments XDS2xx USB Debug Probe_0]
    Execute the command:
    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
    [Result]
    -----[Print the board config pathname(s)]------------------------------------
    C:\Users\fjk9550\AppData\Local\TEXASI~1\
        CCS\ti\0\0\BrdDat\testBoard.dat
    -----[Print the reset-command software log-file]-----------------------------
    This utility has selected a 560/2xx-class product.
    This utility will load the program 'xds2xxu.out'.
    The library build date was 'Jul 27 2016'.
    The library build time was '17:54:51'.
    The library package version is '6.0.407.3'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '13' (0x0000000d).
    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]-----------------------------
    This emulator does not create a reset log-file.
    -----[Perform the Integrity scan-test on the JTAG IR]------------------------
    This test will use blocks of 64 32-bit words.
    This test will be applied just once.
    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.
    The JTAG IR Integrity scan-test has succeeded.
    -----[Perform the Integrity scan-test on the JTAG DR]------------------------
    This test will use blocks of 64 32-bit words.
    This test will be applied just once.
    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.
    The JTAG DR Integrity scan-test has succeeded.
    [End: Texas Instruments XDS2xx USB Debug Probe_0]

    Pin conditions:
    GPIO37/TDO:  1,  GPIO34: 1, TRST : 0    --> MODE 3 GetMode


    According to the customer, when a reset occurs during flash programming, they have heard that  the access is denied with some devices because of the security.
    With this case, does the device get into the security mode?
    Or is the flash collapsed? 

    Thank you for your kind check.
    Best regards,
    Hitoshi



  • Hi Hitoshi,

    Are they able to connect when TRST is set to 1 for emulation boot mode?

    Hitoshi Sugawara said:
    According to the customer, when a reset occurs during flash programming, they have heard that  the access is denied with some devices because of the security.
    With this case, does the device get into the security mode?
    Or is the flash collapsed? 

    Are the CSM passwords getting programmed and locking the device when this occurs? Address for CSM passwords is 0x3F 7FF8.

    Best,

    Kevin

  • HI Kevin,

    The device has been returned to TI for test.
    It would be treated by our quality team.

    Please close this thread.
    Thank you for your kind advice.

    Best regards,
    Hitoshi