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.

TMS320F28377S: Trouble halting target CPU error Uniflash & CCS

Part Number: TMS320F28377S
Other Parts Discussed in Thread: UNIFLASH,

Hi,

I'm trying to figure out how to configure the DCSM on TMS320F28377S microcontroller with UniFlash. For that, I need to load a program into the core to see the data but I get this error :

 I use the Jtag probe xds100v2 and xds100v3, both give the same result.

I tryed to reset, change the cable, change the probe and the board nothing worked. 

I think it's important to mention that I already loaded programs in the core. 

I get the same error on CCS. Please help me solve this problem because I get it  very often since I started working on security. Are there steps that I should follow in order to avoid this problem?

Thank you

  • Loic,

    It is Thanksgiving week in US. Most of the TI engineers are on vacation. Please expect delay in response.

    I would realistically expect a response back from TI early next week.

    Regards,
    Manoj
  • Loic,

    If you have enabled the security on device by programming the password then you may not be able to connect to device because ECSL trips the JTAG connection whenever CPU halts with PC pointing to secure memory. To enable JTAG connection you need to use WaitBOOT mode and then connect. Basically set the BOOTMODE pin setting to WaitBOOT and then power-up the device and try to connect the JTAG. Please refer the device TRM for WaitBOOT setting.

    Regards,

    Vivek Singh
  • Hi, 

    Thank you for your reply. Your solution seems to work with the xds100v3, however with the xds100v2 I get this error:

    Error connecting to the target:
    (Error -215 @ 0x0)
    The semaphore for the test bus controller is in a time-out state.
    Unified-SCIF was unable to acquire the semaphore used to
    express ownership of a controller by a utility or debugger.
    You may have to exit other clients because the timeout occurred.
    (Emulation package 7.0.188.0)

    Do you have any idea what it could be? 

    Thanks

  • It should work for both emulator. Can you double check that you are following same steps in both case.
  • Can you confirm my question in last post?