• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 83 subscribers
  • Views 1747 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.

CCS/TMS320F28377S: Error in flashing loading

Pietro Ciammaichella
Prodigy 60 points
Part Number: TMS320F28377S
Other Parts Discussed in Thread: TPS5420, LMR10510

Tool/software: Code Composer Studio

Hi,

we developed a small board based on the tms320f28377s. On the first board we were able to load and run programs on both ram and internal flash memory. On the other boards that we realized, using the same debug test bench (CCS v8, XDS 110 debug probe) If we try to  program the device on the internal ram memory it works fine but when we try to flash the project on the internal flash memory we get the following error:

C28xx_CPU1: Error: (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.188.0)
C28xx_CPU1: Trouble Halting Target CPU: (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.188.0)
C28xx_CPU1: Error: (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.188.0)

When we program the internal ram we use the wait boot mode (GPIO 72=1, GPIO 84=0). To program the flash we tried wih both, wait mode and get mode but we get the same error.

We upgraded the debug probe firmware to the latest version avaliable on the ti site.

We experimented that during the flash loading, before that the flash erasing occour, a reset signal is generated by the device. The reset works fine during the normal ram operations.

We also checked all the power supplys quality and we couldnt find any noise or glitches.

Please find attached the log with the full error message.

Thanks.

  • 0
    Prodigy 60 points

    C28xx_CPU1: Error: (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.188.0)
    C28xx_CPU1: Trouble Halting Target CPU: (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.188.0)
    C28xx_CPU1: Error: (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.188.0)
    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: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x00130@Program: target is not connected
    C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
    C28xx_CPU1: File Loader: Memory write failed: Unknown error
    C28xx_CPU1: GEL: File: C:\Users\Pietro Ciammaichella\workspace_v8\epwm_deadband_cpu01\CPU1_FLASH\epwm_deadband_cpu01.out: Load failed.
    C28xx_CPU1: Error occurred during flash operation: Could not read register PC: 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 write 0x0005FC00@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x00000064@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg
    C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
    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.
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D22E@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D222@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D214@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected
    C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D216@Data: target is not connected

  • 0 in reply to Pietro Ciammaichella
    TI__Mastermind 30255 points
    Hello

    An engineer is assigned and will assist soon.

    Best regards
    Chris
  • 0 in reply to Christopher Chiarella
    TI__Genius 15385 points
    Hi Pietro,

    Can you provide more information on what kind of board you designed which does not? What is the Max current supported by the voltage regulator that you are using? Also, is the part that you are using to Flash the device the same or different?

    Thanks & Regards,
    Nirav
  • 0 in reply to Nirav Ginwala
    Prodigy 60 points

    Hi Nirav,

    the board is based on the tms320f28377s device, in particular we referred to the LAUNCHXL-F28377S. We decided to put on the board only the JTAG connector and use the XDS110 probe for test and program activities.

    The board will be used as controller for a full bribge converter to generate 4 PWM signal, ADC conversion for two voltage and two current and SPI communication toward a centralized controller; in order to have more flexibility for future application, we put on the schematic also a external flash and a RAM that at the moment are not populated. Also an external oscillator has been inserted but for this application is not required.

    For the power section we receive a 24V, by means a TPS5420 a 3.3V (2A) is generated; the 1.2V is generated by means a LMR10510 (1A) step down converter.

    For the programming we use always the same XDS110 probe, however we modified a launch pad in order to use its on-board programmer and we obtained the same results.

    Waiting for your suggestion, we will substitute the 1.2V converter with an external power supply.

    Thanks for the support.

    Regards

    Pietro

  • 0 in reply to Pietro Ciammaichella
    Prodigy 60 points

    Hi Nirav,

    even if we don't get any glitch on the internal board supply, using an external power supply for the 1.2V we were able to load the internal flash. We changed the feebback network of the LMR10510 to obtain a 1.23V.

    In these conditions all the board works fine and the flash is loaded.

    Maybe the problem is related to the internal PLL unlock?

    This behaviour would generate a WD that reset the device and broke the loading process.

    Thank very much

    Pietro Ciammaichella

  • 0 in reply to Pietro Ciammaichella
    TI__Genius 15385 points
    Hi Pietro,

    Yes when you switch the PLL clock to System it will have high instantaneous current that needs to be supported by 1.2V power supply. I am glad it worked, let me know if you have any more questions.

    Regards,
    Nirav