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.

Error connecting to the target when changing the target

Other Parts Discussed in Thread: TMS320F28035

Hello,

I am having a lot of problems in connecting to target TMS320F28035.  I have two TMS320F28035 and after using, let's say, target 1 I want to load the program in target 2. When I try to change the target it does not connect to the new one.

The error that apears is:

"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.
(Release 5.0.429.0)"

If I press Retry button the error that appears is:

Error connecting to the target:
(Error -1041 @ 0xFFFFFF87)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Release 5.0.429.0)

It is like CCS thinks the session in the old target (target 1) is not closed (although I terminated the debug sessions) and I cannot load the same program to the new target (target 2). Despite this, I can connect back to target 1.

I created two different target configurations each one with the corresponding serial number of the emulator (executing xds100serial.exe). But it does not help. I restarted the host PC, unplug and replug the USB cables, restart CCS with no results.

This is happening to me in the last weeks, and I think it happens since I started to program in FLASH (because the program didn't fit in RAM).

Last days, what it was working was to launch the debug session anyway and performing a "Terminate and relaunch" the debug session, but now it does not work anymore.

I am using CCS  Version: 4.2.4.00033.

Any help would be really appreciated.

Thanks in advance!

  • Hello,

    It sounds like you have two F28035 devices connected to your PC via XDS100 emulators, differentiated via serial number. Are you using the control stick with the on board XDS100?

    Thanks

    ki

  • Hi,

    Yes, I have two F28035 connected to my PC with XDS100 emulators. I am using:

    Device 1: an Experimenter's kit + Control Card with on board XDS100

    Device 2: a PCB designed in the company I work for with the same circuit than the Experimenter's kit + Control Card with on board XDS100

    Thanks for the quick response.

    Isaac

  • Thanks for the details

    Isaac Hidalgo Tarras��n said:
    I have two TMS320F28035 and after using, let's say, target 1 I want to load the program in target 2. When I try to change the target it does not connect to the new one.

    What exactly are you doing here? You have both targets connected to your PC. Did you start a debug session for target 1, connected successfully and after some debug you shut down the debug session and then start a debug session for target 2 and cannot connect?

    Did you try unplugging target 1 from the PC and then try to connect to target 2 again?

  • What exactly are you doing here? You have both targets connected to your PC. Did you start a debug session for target 1, connected successfully and after some debug you shut down the debug session and then start a debug session for target 2 and cannot connect?

    Exactly! This is because I have a setup based on target 1 that lets me debug Spi communications with another micro and when the program is debugged, later, I test the program with the final custom made PCB based on target 2.

    Did you try unplugging target 1 from the PC and then try to connect to target 2 again?

    Yes, I tried it, it did not work.

  • I found what was the error.

    In the custom PCB where there is the target 2, we have 2 microcontrollers, being the F28035 the slave. What was happening there was that the master had a bug in its software and was switching off the power supply of the target 2. This is possible because in our custom PCB, the main micro is able to switch off the F28035, just disconnecting the power supply of the slave.

    After correcting the SW bug, now it is possible to switch the debug session from one micro to the other one, even when both are connected.

    Thanks for the support and sorry for the time lost helping!

    It's good to realise in TI you offer quick support!! :)

    Isaac

  • Glad to hear you found the problem. Thanks for the update!