• State
  • Locked Locked
  • Replies 14 replies
  • Subscribers 84 subscribers
  • Views 716 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.

TMS320F28388D: C2000

@vince
Intellectual 651 points

Part Number: TMS320F28388D
Other Parts Discussed in Thread: TMDSCNCD28388D

Through the emulator, download the program to the circuit board, showing that the download is unsuccessful. details as following:

The circuit board is designed to imitate TMDSCNCD28388D. The first version of the design has a problem. Every time the program runs, you need to press the reset button before it can run.

The second edition of the design, imitating the TMDSCNCD28388D design the boot selection circuit. When both GPIO72 and GPIO84 are in the high state, the downloaded program will run the program from FLASH.


However, this version has a new problem. When downloading the program, it cannot be downloaded, and the situation in the picture above always appears.

I am very anxious, and I don’t know what caused it. I’m here to ask, thank you.

  • 0
    Intellectual 651 points

    C28xx_CPU1: Failed to retrieve the Wait in Reset Mode: (Error -6311) PRSC module failed to write to a register. (Emulation package 9.2.0.00002)
    C28xx_CPU1: Error connecting to the target: (Error -6001) Internal Error: PRSC module detected an unknown failure. (Emulation package 9.2.0.00002)

  • 0
    Intellectual 651 points

    1、The DIP switch in the boot selection circuit is set to FLASH state (switch is open)

    The debug routine reports an error in RAM

    Fullscreen The debug routine reports an error in RAM.txt Download 
    C28xx_CPU1: Failed CPU Reset: (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) 
C28xx_CPU1: Error: (Error -1135 @ 0x3FD2AE) 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) 
C28xx_CPU1: Unable to determine target status after 20 attempts
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
C28xx_CPU1: GEL: Error while executing OnReset(-1): Could not write 0x0005FB00@Data: target is not connected
	 at *((int *) 0x5FB00)=0 [f28388d_cpu1.gel:27]
	 at OnReset(-(1))
C28xx_CPU1: Error occurred during flash operation: CPU Reset error. Error code -1
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005FB00@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00007029@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read register ST1: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register ST1: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register ST1: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x700B0@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error initializing flash programming: Interface returned from dll, but flash is not available on this device.

    Error report from debug to FLASH

    Fullscreen Error report from debug to FLASH.txt Download 
    C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: GEL Output: 
... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: 
... DCSM Initialization Done ...
C28xx_CPU1: GEL Output: 
 CPU2 is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CPU2 to reach wait boot loop.)
C28xx_CPU1: GEL Output: 
 CM is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CM to reach wait boot loop.)
C28xx_CPU1: Failed CPU Reset: (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) 
C28xx_CPU1: Error: (Error -1135 @ 0x3FD2AE) 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) 
C28xx_CPU1: Unable to determine target status after 20 attempts
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
C28xx_CPU1: GEL: Error while executing OnReset(-1): Could not write 0x0005FB00@Data: target is not connected
	 at *((int *) 0x5FB00)=0 [f28388d_cpu1.gel:27]
	 at OnReset(-(1))
C28xx_CPU1: Error occurred during flash operation: CPU Reset error. Error code -1
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005FB00@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00007029@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read register ST1: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register ST1: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register ST1: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x700B0@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error initializing flash programming: Interface returned from dll, but flash is not available on this device.

    2、The dial switch in the boot selection circuit is set to the Parallel IO state (switch closed) (the circuit board and the emulator are both powered off and then powered on again)

    The debug routine reports an error in RAM

    (You can successfully debug into the RAM, but click Run, you will get an error) The error is as follows:

    Trouble Halting Target CPU:
    (Error -1156 @ 0x0)
    Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.
    (Emulation package 9.2.0.00002)

    Debug to FLASH error report (in the case of debug to RAM error, reselect debug to enter FLASH)

    Trouble Halting Target CPU:
    (Error -1156 @ 0x0)
    Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.
    (Emulation package 9.2.0.00002)Trouble Halting Target CPU:Trouble Halting Target CPU:
    (Error -1156 @ 0x0)
    Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.
    (Emulation package 9.2.0.00002): Unable to determine target status after 20 attempts
    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
    Trouble Halting Target CPU:Trouble Halting Target CPU:

    After a while, I tried to debug again to enter FLASH, and the following error occurred:

    Trouble Reading Register PC:
    (Error -1156 @ 0x0)
    Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.
    (Emulation package 9.2.0.00002)

    The following figure is the state table corresponding to the high and low levels of GPIO72 and GPIO84

  • 0
    Intellectual 651 points

    This circuit board, when we turn the DIP switch to the closed state (when the FLASH is started), when debugging the program, it will directly report an error, as described below:

    Error connecting to the target:
    (Error -6311) PRSC module failed to write to a register.
    (Emulation package 9.2.0.00002)

  • 0
    TI__Prodigy 440 points

    Please expect some delay in the response as 31-May is a TI Holiday

  • 0 in reply to Karthik Rajakumar
    TI__Guru 50611 points

    Vince,

    Is this custom board or TI EVM?

    Usually, this error is due to improper power applied to the device, or a device being held in reset or improper clock being routed to the device. Please take a look at this link:

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#prsc-errors

  • 0 in reply to Santosh Jha
    Intellectual 651 points

    hi，Santosh Jha

    It is a circuit board imitated by the 28388D evaluation board.

    At present, we are looking for reasons based on these situations.

    thanks

    vince

  • 0 in reply to Santosh Jha
    Intellectual 651 points

    HI,Santosh Jha

    thanks

    I checked the equipment level and it was within the normal range.

    vince

  • 0 in reply to @vince
    TI__Guru 50611 points

    Vince,

    I am assigning to system expert. Please expect response by tomorrow.

  • 0 in reply to @vince
    TI__Guru* 82570 points

    Vince,

    Santosh alerted me to this thread, as I know we have one as well https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1006588/tms320f28388d-c2000

    Have you had a chance to isolate the instruction that causes the RAM loaded code to crash the emulation connection?

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Intellectual 651 points

    HI,MatthewPate

    You mean, find the code that caused the failure, comment out this part of the code, and run it again?

    thanks

    vince

  • 0 in reply to @vince
    TI__Guru* 82570 points

    Vince,

    Or just make note of it and reply back to this thread with that info.  I'm suspecting it will be on some type of HW change instruction like setting the PLL or the first jump into code in a certain memory block, etc.

    You can try to remove the offending code, and keep running as well but depending on the issue you may not see it resolve.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Intellectual 651 points

    HI，MatthewPate

    trying  it.

    thanks

    vince