• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 824 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.

CCS/LAUNCHXL-F28069M: Lab 11e Error - 2131 @ 0x0

Kalpesh Mhase
Intellectual 825 points
Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: TMS320F28069, MOTORWARE

Tool/software: Code Composer Studio

Hello,

I am having issue while debugging Lab 11e but their is no issue for other labs like Lab3a. The programs debugs correctly.

The error message displayed is as follows,

I tried to solve error by,

1. Replacing Cable

2. Comparing "TMS320F28069_xds100v2.ccxml" file with other running project same file.

3. Decreasing JTAG TCLK freq to 100Khz but here the "Test connection" results shows that you don't have hardware to program the JTAG CLK.

What should I do? Please guide me through this!!!

  • 0
    TI__Guru**** 173310 points

    Kalpesh,

    Are these labs you are trying to run from a C2000 workshop? Could you point us to where these labs are from?
    After you receive this error are you able to go back and load programs for other labs successfully?

  • 0 in reply to AartiG
    Intellectual 825 points
    This labs are from Motorware,
    The location for the lab may give you some idea
    "C:\ti\motorware\motorware_1_01_00_18\sw\solutions\instaspin_foc\boards\boostxldrv8301_revB\f28x\f2806xF\projects\ccs\proj_lab11e"
    And, Yes after receiving the error I am able to go back and load programs for other labs successfully.
  • 0 in reply to Kalpesh Mhase
    TI__Guru**** 173310 points
    I suspect the issue may have something to do with board setup/configuration. I will move this thread to the C2000 device forum as the experts there have more knowledge about this lab and target board, and should hopefully be able to assist further.
  • 0 in reply to AartiG
    Intellectual 825 points
    Ok, Thank you.
  • 0 in reply to Kalpesh Mhase
    Intellectual 825 points

    The problem was solved when I uninstalled motorware and reinstalled it.

    I think their might have been some changes in my debug setting which would have been got to default after reinstalling motorware.