• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 84 subscribers
  • Views 855 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.

Error connecting to target (TMS320F28335)

Steve Guardyak
Prodigy 10 points

Other Parts Discussed in Thread: TMS320F28035

HELP!

Can anyone explain how to resolve this error?  I'm using CCS v3.3.81.28 and a XDS510PP emulator and did not have any problems connecting until now.

Error connecting to the target:
Error 0x80000206/-1156
Fatal Error during: Memory, Register, OCS,
Lost processor clock. Device may be operating
in a low-power mode.  Do you want to bring it
out of this mode?

I/O Port = 378

Board Name: HE2
Cpu Name: TMS320F2800_0

If answer is yes to the above question, the following error occurs.

Error connecting to the target:
Error 0x00000020/-2011
Error during: Execution,
An internal error occurred in which an illegal action (0x00000000) was requested while disconnected.

 

thanks, Steve

 

  • 0
    TI__Guru* 87155 points

    Steve,

    I know three possible reasons for this error to occur.  

    1) External clock to the device is missing 

    2) One of the VDD or VDDIO rails are not powered

    3) Device is kept  in low power  mode using idle instruction

    If you have already checked the above three possibilities, I am not sure what else could cause this.

    Regards,
    Vamsi

     

  • 0 in reply to Vamsi Gudivada
    Prodigy 20 points

    Hello,

    I have the delfino experimenter kit and i had the same problem.

    I think that the reason of this problem is the source code of the user. may be it functions in some way that provocate

    unexpected behaviour of the processor. So if the source code is loaded in flash memory, on power up, the processor executes the "bad code" and go to undetermined state.

    So, the emulator will not be able to communicate with the processor in this state.

    any way, the solution is to make the processor escape executing the "bad code" by booting from another memory where is located this bad code. in my case the flash memory.

    so I configured boot options to be from RAM and i turned off and then on the board and then Emulator could communicate this time with processor !!!! great

     

    sami MOHAMMAD

  • 0 in reply to Vamsi Gudivada
    Prodigy 130 points

    I have the similar issue on my prototype board. I have made up my own board with a TMS320F28035. The fact is I had to solder myself the controller which is a little bit hard. At the beginning, I had no problem to connect the XDS510PP to my target and to run my code. Unfortunately, one of the VDD pin is not solder properly and lost contact. It is at this moment I started getting trouble the eumlator with similar messages than above. I checked VDD and I got 2.6V instead of 1.8V and of course 0V on one VDD pin. After some corrections, I have now 2.8V on each of the VDD pins and it doesn't work anymore. I guess my controller is gone. So, make sure all pins are connected properly.

    Chris