• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 85 subscribers
  • Views 341 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28379D: C28xx_CPU1: Error: (Error -1137 @ 0x0) Device is held in reset.

Yale Li 李耀先
Expert 4660 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE

Hi Team,

The relevant schematic is as follow:

When I load code with ccs, it present follow question.

C28xx_CPU1: GEL Output:
Memory Map Initialization Complete
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.
C28xx_CPU1: Error: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.1.0.00005)
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 read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@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: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\Users\LiuJun\workspace_v9\LAN9252_SPI_379\Debug\LAN9252_SPI_379.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 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 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@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 read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5D200@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@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 write 0x0005D20E@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 0x0005D200@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 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.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 read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected

And the 'MCU_XRSN' signal waveform as follow:

--

Thanks & Regards

Yale

  • 0
    TI__Mastermind 33955 points

    Yale, 

    Are you able to connect to the device/core without loading the code? Which version of CCS are you using?

    Best Regards

    Siddharth

  • 0 in reply to Siddharth Deshpande
    TI__Expert 4660 points

    Yes, it's ok when customer test connection in the Target Configuration. The ccs version is ccs9.

  • 0 in reply to Yale Li 李耀先
    TI__Mastermind 30556 points

    Hi Yale,

    Have they been able to connect to this device in the past? Is it possible to try putting the device in wait boot mode? 

    Also, which JTAG debug probe is the customer using? 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    TI__Expert 4660 points

    NO, the customer have never connected successfully. He put the design in flash boot mode and cannot switch it. He use xds100vs to debug.

    --

    Thanks & Regards

    Yale

  • 0 in reply to Yale Li 李耀先
    TI__Mastermind 30556 points

    Hi Yale,

    Just to confirm, you see this problem when you are just trying to connect to the device, not when you are loading code? 

    Also, the test connection passed for both the IR and DR scans? 

    If you have access to an oscilloscope, could you try probing TDO (yellow), TMS (purple), TCK (blue), and TRST (green) as shown below. The screenshot below was captured using the XDS100, and it was a single-capture triggered on the falling edge of TMS. Could you try doing the same and see if your probed signals look the same when you try to connect?

    Best Regards,

    Ben Collier 

  • 0 in reply to Benjamin Collier
    Prodigy 10 points

    Now i can load the code to device but when i debug the program it will stop at "7625        ESTOP0  “，when i dubeg it in step it will get wrong at the code"ClkCfgRegs.SYSPLLCTL1.bit.PLLCLKEN = 1;" and the Error as follow:

    C28xx_CPU1: Error: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.1.0.00005)
    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_CPU2: Error: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.1.0.00005)
    C28xx_CPU2: Unable to determine target status after 20 attempts
    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

    and i mointor the xrs pin there is present a low pule of 133us

  • 0 in reply to bianshuai
    TI__Expert 4660 points

    Ben,

    卞 帅 -- This is the customer who asked the question. Looking forward to your reply.

    --

    Thanks & Regards

    Yale

  • 0 in reply to bianshuai
    TI__Mastermind 30556 points

    Hi,

    The pulse on the xrs is expected. Please allow me until early next week to look into what could be causing this. 

    Best Regards,
    Ben Collier

  • 0 in reply to Benjamin Collier
    TI__Mastermind 30556 points

    Hi, 

    Just curious, did you start with one of the provided examples in C2000WARE or is this entirely your code? 

    I saw the above description in the TRM. Are you locking the PLL before enabling it? 

    Best Regards,
    Ben Collier

  • 0 in reply to Benjamin Collier
    TI__Genius 10821 points

    Hello Yale,

    Please provide the customer's initialization code so we can review the PLL setup parameters.

    Thanks,
    Ibukun