• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 4654 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/TMS320F28335: Device is held in reset, even when changes the boot mode.

Ruben Leon
Prodigy 60 points
Part Number: TMS320F28335


Tool/software: Code Composer Studio

Hi,  I am getting an error when I try to start a debug session.  Target is a TMS320F28335, in a dock station.

(I) The code was a simple Flashingleds example, Imported and built through the TI Resource Explorer.

(II) The communication test for the probe works fine.

(III) The Debug gives some errors about memory range.

(IV) When tries to connect to the target I get this:

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)) [f28335.gel:322]
at C28x_Mode() [f28335.gel:38]
at OnReset(1)
C28xx: Flash Programmer: Warning: The configured device (TMS320F28335), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
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)

I tried to ground the GPIO84/85/86, in order to change the boot mode and surpass the flash memory to A/B/C/D/E but it didnt work. I get the same error.

  • 0
    TI__Guru* 80990 points

    Ruben,

    Thanks for reaching out to the C2000 E2E Forum.

    I'd like for you to confirm that the setting for your session in the Target Configurations setup match both your emulator and the device PN.  Go to View->Target Configurations and then right click on the target you are debugging and make sure everything matches.  That should clear up the memory range errors, etc.

    I think there are two options to get control of the MCU after the program load.  

    1)As you said we can use "check boot" mode on this device to force it to go to a known good location rather than running, below is a picture of the boot pins and what mode they put the device into:

    2)The F28335 device supports Wait In Reset mode, driven by the emulator.  You can see if there is a check box in the Target Configs where you picked the emulator for the session.

    If this doesn't solve the problem I would also launching the debug session using a right click in the Target Configs, vs clicking the "Debug Button"  The debug button has alot of other actions involved(like connecting to target, running to main, etc) that I'd like to not happen until we get the emulation connections under control.  Once you have launched the debug session right click on the F28335 CPU and select connect.  This will connect the debugger without downloading the code.  You can then select to load the program, and then eventually run to see exactly where the problem occurs.

    Let me know what you see and we can proceed from here if necessary.

    Best regards,
    Matthew

  • 0 in reply to MatthewPate
    Prodigy 60 points

    So....

    I manage to exclude some errors on the code, but the device still was on the reset mode.

    I tried to force other boot modes, and none of them suceed.

    The option for Wait in Reset mode wasnt avaiable, and using another "Debug button" didnt solve the problem.

    When clicking on Connect to the device, the same error around the reset mode was popping up.

    Finally I touch the PCB and noticed that is anormally hot. I believe that is another problem, and something is burnt somewhere on it.

    Thank you for the help anyway.

    Ruben