• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 296 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Programmer issue

Rahul Poonarkar
Prodigy 30 points

Part Number: TMS320F28377D

We are trying to program the C2000 series TMS320F28377D delfino Microcontroller, but there is error in programming and we cannot find the solution. The error log file is attached please check.

Please check the log file and revert ASAP.

Thanks & Regards

Rahul Ponarkar

Fullscreen ErrorLog.txt Download 
[3/4/2019, 5:54:03 PM] [INFO] C28xx_CPU2: GEL Output: Memory Map Initialization Complete
[3/4/2019, 5:54:03 PM] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete
[3/4/2019, 5:54:05 PM] [INFO] C28xx_CPU2: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
[3/4/2019, 5:54:05 PM] [INFO] C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
[3/4/2019, 5:54:08 PM] [ERROR] C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.100.0)
[3/4/2019, 5:54:08 PM] [ERROR] C28xx_CPU1: Trouble Halting Target CPU: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.100.0)
[3/4/2019, 5:54:08 PM] [ERROR] C28xx_CPU1: Unable to determine target status after 20 attempts
[3/4/2019, 5:54:08 PM] [ERROR] C28xx_CPU1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
[3/4/2019, 5:54:10 PM] [ERROR] C28xx_CPU2: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.100.0)
[3/4/2019, 5:54:10 PM] [ERROR] C28xx_CPU2: Error: (Error -1135 @ 0x3FEC52) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.100.0)
[3/4/2019, 5:54:10 PM] [ERROR] C28xx_CPU2: Unable to determine target status after 20 attempts
[3/4/2019, 5:54:10 PM] [ERROR] C28xx_CPU2: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x00130@Program: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: File Loader: Memory write failed: Unknown error
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read register PC: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash. If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x5D200@Program: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D22E@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D222@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D214@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash. If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[3/4/2019, 5:54:28 PM] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected

  • 0
    TI__Guru** 116971 points

    Hi Rahul,

    Few things to check -

    1. If this is your custom board, please make sure you have all the JTAG signals connected properly.
    2. Please check that you are setting BOOTMODE other than flash boot so that device is no in reset loop.
    3. Also are you able to connect to CCS. Basically launch the target configuration file and then connect to target instead of programming the device.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 30 points

    Hello Vivek ,

    Thank you very much for the feedback , We have tried the Points you discussed in the above blog as follows

    1)   If this is your custom board, please make sure you have all the J TAG signals connected properly.

    yes this is our Custom board , we have tested all the connections and tracks. JTAG track is properly connected as per the DATASHEET.

    2)Please check that you are setting BOOT MODE other than flash boot so that device is no in reset loop.

    TRST PIN  is always LOW while XDS110 is connected to Uni Flash in 2 Boards , So it is not programming.

    the Other board which we areFlashing the TRST Pin will be high , We are facing problem in only 2 boards.

    rest all board is programming.

    Please guide

    3) Also are you able to connect to CCS. Basically launch the target configuration file and then connect to target instead of programming the device.

    we have done this and Attached the file please see to it

    Fullscreen Test Conections.txt Download 
    [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)]------------------------------------

C:\Users\ADMINI~1.RDE\AppData\Local\TEXASI~1\
    CCS\ti\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 'jioxds110.dll'.
The library build date was 'Nov 21 2018'.
The library build time was '00:08:45'.
The library package version is '8.0.903.2'.
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).

-----[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 XDS110 USB Debug Probe]

  • 0 in reply to Rahul Poonarkar
    Prodigy 30 points

    Please do Reply .....!!

  • 0 in reply to Rahul Poonarkar
    TI__Guru** 116971 points

    Rahul,

    TRST PIN  is always LOW while XDS110 is connected to Uni Flash in 2 Boards , So it is not programming.

    Sorry for late reply.  TRSTn pin is input to device. If this is low then you'll not be able to connect to device. Since it's driven by emulator, and same emulator works on other board, I would still suspect the board issue. Please check the trace for TRSTn pin on the board.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Guru** 116971 points

    I hope you were able to find the issue on board and it's resolved. I am marking this closed. If you still have the issue, please open a new post with more detail.