• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 1056 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.

CCS/TMS320F28027F: Failed CPU Reset: (Error -1137 @ 0x6) Device is held in reset

Shubham Joshi
Prodigy 90 points
Part Number: TMS320F28027F
Other Parts Discussed in Thread: TMS320F28027, MOTORWARE, C2000WARE

Tool/software: Code Composer Studio

Hi,

I have a custom F28027 board. I have 2 identical boards. 1 board is fine and gets connected to debug session, in other board i am getting following error message during debug connection.

C28xx: GEL Output:
Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: Flash Programmer: Warning: The configured device (TMS320F28027), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx: Failed CPU Reset: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: GEL: Error while executing OnReset(1): Target failed to read register ST1
at (ST1&~(0x0100)) [f28027.gel:283]
at C28x_Mode() [f28027.gel:33]
at OnReset(1)
C28xx: Trouble Writing Memory Block at 0xae0 on Page 1 of Length 0x1: (Error -1137 @ 0xAE1) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE0@Data
C28xx: Trouble Writing Memory Block at 0xae1 on Page 1 of Length 0x1: (Error -1137 @ 0xAE2) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE1@Data
C28xx: Trouble Writing Memory Block at 0xae2 on Page 1 of Length 0x1: (Error -1137 @ 0xAE3) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE2@Data
C28xx: Trouble Writing Memory Block at 0xae3 on Page 1 of Length 0x1: (Error -1137 @ 0xAE4) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE3@Data
C28xx: Trouble Writing Memory Block at 0xae4 on Page 1 of Length 0x1: (Error -1137 @ 0xAE5) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE4@Data
C28xx: Trouble Writing Memory Block at 0xae5 on Page 1 of Length 0x1: (Error -1137 @ 0xAE6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE5@Data
C28xx: Trouble Writing Memory Block at 0xae6 on Page 1 of Length 0x1: (Error -1137 @ 0xAE7) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE6@Data
C28xx: Trouble Writing Memory Block at 0xae7 on Page 1 of Length 0x1: (Error -1137 @ 0xAE8) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 7.0.188.0)
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE7@Data
C28xx: Flash Programmer: Device is locked or not connected. Operation cancelled.
C28xx: File Loader: Memory write failed: Unknown error
C28xx: GEL: File: C:\Users\Pallavi Joshi\Google Drive\BLDC-FOC\CCS_Instapsin\motorware_Torque_V1_2\sw\solutions\instaspin_foc\boards\Torque_V1_2\f28x\f2802xF\projects\ccs\proj_lab05b\Flash\proj_lab05b.out: Load failed.

I have checked status of XRSn pin, though it is pulled up with 2.2k, it shows 0.1V. 

When I test JTAG connection it succeeds.

To rule our possibility of broken controller, I tested controller to another board and it works just fine.

Since the first board is working fine i suspect this to be a soldering/component issue, but I still want to know what is the reason for this problem.

Regards,

Shubham

  • 0
    Prodigy 90 points
    In addition to previous observation .

    Vreg internal voltage is 2.042V. As specified in datasheet, this voltage should not exceed 1.995V
  • 0 in reply to Shubham Joshi
    TI__Prodigy 540 points
    HI Shubham

    Yes, sounds like a soldering/bad component issue.

    If the internal Vreg is enabled, 2.042 is higher than we expect. The 1.995V in the datasheet is the Max voltage when supplying VDD supply externally with Vreg Disabled. VDD should be closer to 1.8V with Vreg enabled.

    1. Can you confirm VREGENZ pin is tied low?
    More details here: www.ti.com/.../detailed-description

    2. When you capture the signal on XRSN on a scope, do you see a fixed voltage or a periodic toggling of the signal. Measure the pullup resistor value is a minimum 2.2Kohm.

    3. Can you check the JTAG and Reset pins are biased correctly with the correct pull resistors? Please refer to reference design files in C2000Ware
    \C2000Ware_1_00_03_00\boards\LaunchPads\LAUNCHXL_F28027\LAUNCHXL_F28027_SCH.pdf

    -Nabil