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.

HDK TMSLS3137 connection failure

Other Parts Discussed in Thread: HALCOGEN

 I had an accidental power failure and both power supply of HDK and my laptop has stopped for some time during debug. Now that I restarted everything I cannot load a program to HDK, it started with sending a strange error of endiannes mismath in CCS debug. I guess the previous debug state is hanging or something. Not that I have powercycled the board, pressed both reset buttons and created a new Halcogen + CCS project I get the following rudeness:

IcePick: Error connecting to the target: (Error -154 @ 0x0) One of the FTDI driver functions used to write data returned bad status or an error. (Emulation package 5.0.747.0)

Is there a way to make a full reset to be able to load a new code to HDK (via normal CCS debug)?

  • Current status:

    CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Trouble Reading Register REG_ENDIAN: (Error -1044 @ 0xFFFFFF2B) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.747.0)
    CortexR4: Trouble Reading Register REG_ENDIAN: (Error -1044 @ 0xFFFFEC76) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.747.0)
    CortexR4: GEL: File: C:\DEV\WORKSPACE\DASH_dev_test5\Debug\DASH_dev_test5.out Does not match the target endianness, not loaded. Check build options and target configuration file (ccxml).
    CortexR4: Error: (Error -1044 @ 0xFFFFEC76) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.747.0)
    CortexR4: Unable to determine target status after 20 attempts
    CortexR4: 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

  • Kirill,

    Are the power LEDS on after you have tried to recover.   By this, I mean the LEDs near the power jack of the HDK.

    The LEDS near the USB jack are powered by the USB bus.     But the LEDs near the power jack will tell you if you blew the fuse on the HDK when you had the power outage.

    There should be something like 4 LEDS near the power jack labeled +12V, +5V, +3.3V, +1.2V.

    If any of these are out then likely the fuse is blown.  The fuse F1 is very small,  on my board the label of F1 is over an inductor but the fuse itself is to the right of this inductor and the F1 label.  It is maybe 0402 size...

    Of course this problem could be unrelated.  But you said you had a power failure so I'd start with the power supply.

  • Hello Anthony,

    Thank you for reply. My power LEDs are all ok. It should be a soft error certainly

  • Some 10 or more banal resets as well as different target reset configs of debugger finally resolved the issue.

    Thank you all!