• State
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Subscribers 87 subscribers
  • Views 344 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: Problem Fileloading with Uniflash

Stefan Wersig
Prodigy 10 points
Part Number: TMS320F28377D
Other Parts Discussed in Thread: UNIFLASH

Hello Support - Team,

I actually have a problem to load the files on to the newest series of boards with the TMS320F28377D.

We built several hundred of this board the last few years without any problem.

Actually we set up a new series of 50pcs and I`m not able to programm one of those.

When i take an old one out of the box it is working as allways known.

During my attempts i recognized that the parts are optically quite differrent.

Maybe you can check it?

one "old" one working

one "new" one not working

Additionally i attach the error message from my uniflash:

Fullscreen Error_TMS320F28377D.txt Download 
[17.10.2023 09:24:31] [ERROR] C28xx_CPU1: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002)
[17.10.2023 09:24:44] [ERROR] IcePick_C_0: Power Failure on Target CPU
[17.10.2023 09:24:59] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete
[17.10.2023 09:25:00] [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.
[17.10.2023 09:25:03] [ERROR] C28xx_CPU1: JTAG Communication 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 9.2.0.00002)
[17.10.2023 09:25:04] [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
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x00130@Program: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: File Loader: Memory write failed: Unknown error
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read register PC: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
[17.10.2023 09:25:24] [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.
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x5D200@Program: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D22E@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D222@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D214@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
[17.10.2023 09:25:24] [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.
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
[17.10.2023 09:25:24] [ERROR] C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected

Kind regards

  • 0
    TI__Guru**** 471881 points

    Hello Stefan,

    Try using CCS to run a JTAG connectivity test with one of the devices from the "bad" batch.

    https://dev.ti.com/tirex/explore/node?node=A__AMCrhRy9n80ZsUrBFVdo1Q__ccs_devtools__FUz-xrs__LATEST

    Please post the results here.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 10 points

    Fullscreen JTAG-Test.txt Download 
    [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\STEFAN~1.RIE\AppData\Local\TEXASI~1\
    CCS\ccs730\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 'Dec 11 2017'.
The library build time was '10:23:35'.
The library package version is '7.0.100.1'.
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]

  • 0 in reply to Stefan Wersig
    TI__Guru**** 471881 points

    Thanks. Basic JTAG connections appear to be fine. Given that the issue only occurs with that new batch, it is likely not a tools issue but something specific to that batch.

    I'll bring this thread to the attention of the device experts for further assistance.

    Thansk

    ki

  • 0 in reply to Ki
    TI__Guru* 87155 points

    Hi Stefan,

    Thank you for the details.  We will review and get back to you early next week.

    Thanks and regards,

    Vamsi

  • 0 in reply to Vamsi Gudivada
    Prodigy 10 points

    Thank you, maybe this additional information can help:

  • 0 in reply to Stefan Wersig
    TI__Genius 15000 points

    Hi Stefan,

    Thanks for the additional info. Expert will be back next Wednesday.

    Regards,

    Charles

  • 0 in reply to Stefan Wersig
    TI__Guru* 87155 points

    Hi Stefan,

    I reviewed the error log that you provided - I can say that the flash plugin did not start any operations yet.  This is not a flash programming issue.  Error log shows that there is no power supply for the target. Are you sure that the there is no any difference in the new and old boards/power supply?

    If not flash, are you able to load code to RAM and execute successfully?

    Thanks and regards,
    Vamsi