• Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 13581 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.

28335 JTAG Device may be operating in low-power mode

Chris Bart
Prodigy 30 points

Other Parts Discussed in Thread: TMS320F28335, UNIFLASH

Hello,

i made a Breakoutboard. And now i try to programm the SM320F28335PTPMEP via JTAG with the experimenters kit Dockingstation

When i do this, i got following message:

Error connecting to the target:
(Error -1155 @ 0x0)
Device may be operating in low-power mode. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 5.1.232.0)

What have i done until now:

- Installe the actual CCS 5.5
- Reduced JTAG frequency
- Enabled/Disabled EMU0 and EMU1
- Measured the 3,3V and 1,9V and Reset = 1
- Tested the JTAG Communication

Is there a programming difference between the TMS320f28335 and the SM320F28335PTPMEP?

Thank you for your help

Chris

This is the JTAG Connection report

The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 512 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 38 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End]

  • Guru 192875 points

    Hi,

    Both of them are same. Did you check with CCS Uniflash? 

    Choose the connection type as XDS v1/v2 and revert.

    Regards,

    Gautam

  • in reply to Gautam Iyer
    Prodigy 30 points

    Hi,

    thank you for your response.

    I have tryed CCS UniFlash. But with the same result.

    Are there andy preconditions for the first programming?

    I tied also a manually reset and pulled the resetpin to gnd. -> no difference

    Regards,

    Christian

  • in reply to Chris Bart
    Guru 192875 points

    Hi,

    There seems to be some other issue! Check if there's any overheating of controller or LDO. Also check voltage levels at certain points on board.

    Regards,

    Gautam

  • in reply to Gautam Iyer
    Prodigy 30 points

    Hi again,

    i found a big mistake. There was no clock ^^ on my board. But now i use a 24 mhz crystal oszillator.

    So i started programming. But now the next problem.

    After start programming i got an error and the programming failed.

    After that i tryed it again, but the 28335 was not reachable via JTAG. (Bootconfig 1111 = Flash)

    So i changed the Bootconfig to SCI-A and tryed it again.

    Programming the rom seems to work, but i am not sure. But the falsh isnt reachable.

    I get the message that i shuld unlock the device !!???

    Thanke you

    Error:

    C28xx: Error connecting to the target: (Error -1135 @ 0x0) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.232.0)
    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: GEL Output:
    ADC Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:
    ADC Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:
    ADC Calibration not complete, check if device is unlocked and recalibrate.C28xx: Breakpoint Manager: Retrying with a AET breakpoint
    C28xx: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x9469: (Error -1066 @ 0x9469) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)
    C28xx: Breakpoint Manager: Retrying with a AET breakpoint
    C28xx: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x938c: (Error -1066 @ 0x938C) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)
    C28xx: GEL Output:
    ADC Calibration not complete, check if device is unlocked and recalibrate.C28xx: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x938b: (Error -1066 @ 0x938B) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 5.1.232.0)
    C28xx: Error: (Error -1135 @ 0x0) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.232.0)
    C28xx: Unable to determine target status after 20 attempts
    C28xx: 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