• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 1226 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 Debug Session Error : endianness is not correct ?

Hiroyasu Matsubara
Expert 1405 points
Other Parts Discussed in Thread: TMS570LS1227

Hello,

I have a problem about debug session on Code Composer Studio.

When I tried to execute debug session on Code Composer Studio ( version 5.3.0), the error code shown :

CortexR4: GEL Output:  Memory Map Setup for Flash @ Address 0x0CortexR4: GEL: File: C:\XXXXXXXX.out Does not match the target endianness, not loaded. Check build options and target configuration file (ccxml).
CortexR4: Trouble Reading Register REG_ENDIAN: (Error -150 @ 0x88) One of the FTDI driver functions used during configuration returned a invalid status or an error. (Emulation package 5.0.872.0)
CortexR4: Trouble Reading Register REG_ENDIAN: (Error -1044 @ 0xFFFFFF0E) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.872.0)

I could execute the debug session normally when one year ago , using the same CCS and the same CCS project,and the same custom board.

And I have no idea if the endianness is correct or not.(I didn't see the error message when tryied to do it on one year ago)

The MCU is Hercules TMS570LS1227,and the debugger is XDS100V2 ( with FTDI chip FT2232H).

And the PC OS is Windows7 64bit.

Could someone reply to my question ?

I would appriciate if someone could reply.

Regards,

Hiroyasu

  • 0
    TI__Guru 72500 points
    It looks like it did not make the connection to the R4. Can you connect to the debug components individually? (After launching the configuration, right click on the XDS100V2 and select "Show all cores". Expand "Non Debuggable Devices". Now see if you can connect to IcePick alone. Then try the DAP. Finally, try the R4.) If you can connect to the IcePick and DAP, but get an error connecting to the R4, there may be code running on the device that is keeping the emulator from connecting to the CPU.
  • 0 in reply to Bob Crosby
    Expert 1405 points

    Thank you for your reply.

    I could see the "Ice pick" and "DAP" on the debugging configuration ,but could not try to connect only to "Ice pick" or only to "DAP".

    And,I saw another error message on CCS debugging.

    The error message is :

    CortexR4: A fatal error occurred while attempting to remove the remaining debug state that could not be removed at disconnect.  This might have occurred because a breakpoint was set at an address that is no longer valid.  This behaviour may be turned off in the "Debug Properties" tab in the Customize dialog under the Option menu

    Then, I tried to deselected the brakepoints setting on the debugging configuration , but the debug session could not be done.

    And,I could the CCS debug session on one of our custom board (using TMS570LS12) successfully, but couldn't on another custom board.

    If the flash memory on Hercules MCU is protected , the error message above would be shown ?

    Or,the error message causes because of another problem ?

    I would appriciate if you could reply to my question.

    Regards,

    Hiroyasu 

  • 0 in reply to Bob Crosby
    Expert 1405 points

    Hello Bob Crosby,

    This error occured , when I try to start debug session on Hercules MCU while "watchdog communication" started between

    Hercules MCU and TPS65381 (Power Management IC).

    If I try to start debug session "Before" starting watchdog communication between Hercules and Tps65381,

    I could start debug normally.

    Thank you for your reply.

    Regards,

    Hiroyasu