• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 2 answers
  • Subscribers 83 subscribers
  • Views 1198 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28069: Error connecting to the target: (Error -1135 @ 0x0) launchxl-f28069m

Hossein Forouzani
Genius 3030 points
Part Number: TMS320F28069

Hi 

I asked this question in another thread some days ago but unfortunately, I didn't find the answer and the issue was not resolved.

The board can't be found by the computer and the result of "Connection Test" is in the .txt file below.

28069.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
The JTAG DR bypass scan-path is stuck-at-ones.
-----[Perform the Integrity scan-test on the JTAG IR]------------------------
This test will use blocks of 64 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I want to know how this issue could be resolved. There are to ideas about this problem.
#1 The device has been locked, if so how could this be solved?
#2 The FTDI (emulator IC) has some problem and it could be fixed with MProg.exe. If so send me related links, please.

Regards,

Hossein

  • 0
    Guru 192875 points

    Hi Hossein,

    Hossein Forouzani said:
    The board can't be found by the computer and the result of "Connection Test" is in the .txt file below.

    How does the Device Manager look like? Does the PC recognize XDS channels or yellow exclamation?

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Genius 3030 points

    Hi Guatam,

    Yes, the windows recognize XDS.

    Hossein

  • 0 in reply to Hossein Forouzani
    Guru 192875 points
    Cool, atleast that is sorted out. So now, how does your target configuration (.ccxml) file look like? Also, can you share the history of the launchpad esp. when was it last working and after what it started throwing errors.
  • 0 in reply to Gautam Iyer
    TI__Guru* 77460 points

    Hossein,

    As Gautam said if the XDS100 is showing up in your windows device manager, then the FTDI is programmed correctly and no need to re-do that.

    The boot mode setting for Wait Mode is detailed from below screen cap from the schematic, if there is a conflict in the CSM this will help.  If the CSM is truly locked, and the password is not known then we will need to get a new EVM/device.  

    Best,
    Matthew

  • 0 in reply to Gautam Iyer
    Genius 3030 points
    Hi Gautam,

    Thank you for your participation and excuse me because of late replying.
    This is one of my students' issue and as he said the problem created suddenly. Suppose everything had been OK, he turned off the computer and the next day when he turn on the computer, the error was shown while he was trying to the same work with the board.
    I think something on the board should have been changed.

    Thanks again.

    Regards,
    Hossein
  • 0 in reply to MatthewPate
    Genius 3030 points
    Hi Matthew,

    Thank you for your replying.

    From your post, I find that the device went to the Wait mode because of undesired accidentally changing in this dip switch mode. If so how this could be fixed? By changing from Wait mode to Emulation Boot mode??
    Correct me I if I misunderstand.

    Would you please send me any related links about Code Security Module (CSM)?


    Regards,
    Hossein
  • 0 in reply to Hossein Forouzani
    TI__Guru* 77460 points

    Hossein,

    Putting the device into wait mode, will keep any flashed code from executing.  This should allow you to connect the emulator before the device begins executing code from a potentially locked device/CSM.  The issue if the device is locked is that the CSM will terminate the emulation connection if the code is currently in a secure region.

    Emulation boot is automatically active when the JTAG emulator is plugged in and CCS attempts to "connect".  This pulls TRSTn high in an attempt to access the test logic.  On a new device this is all that is needed, i.e. the other boot pins are don't cares "x".  

    For more information on CSM please see http://www.ti.com/lit/ug/spruh18g/spruh18g.pdf section 1.3.

    Best,
    Matthew

  • 0 in reply to MatthewPate
    Genius 3030 points
    Matthew,

    Thank you for your response.

    I just want to find a way for testing emulator test connection success. In order to do that, I'll put the device into wait mode, then I'll do the "test connection".Does thid work?


    BR,
    Hossein
  • 0 in reply to MatthewPate
    Genius 3030 points

    Another matter is that I don't think "Emulation boot is automatically active when the JTAG emulator is plugged", as you said because there is a switch on the board with 3 different switches and one of them is for TRSTn. So if I pull this down, the device will go to Stand-Alone Boot Mode even if the emulator is plugged in.

    Hossein

  • 0 in reply to Hossein Forouzani
    TI__Guru* 77460 points
    Hossein,
    Yes, you are correct, if the switch is placed so that the it doesn't allow the emulator header to connect to TRSTn then it will never go into emulation boot. I believe this switch position should be left in the "on" state when debugging so that the emulator can control TRSTn as needed. Once debug is complete, and the LP is in a more "system" type environment you can put to "off" to prevent any spurious noise from over-driving the pull down.

    Matt