• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 1534 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.

CC3220S-LAUNCHXL: Unable to access the DAP error

Carlo
Expert 7715 points

Part Number: CC3220S-LAUNCHXL
Other Parts Discussed in Thread: CC3220S, UNIFLASH

Hello E2E,

Our customer is encountering a problem described below.

I have a CC3220x-LAUNCHXL micro controller. Whenever I try to run the project I am getting an error. (Error -1170 @ 0x0) Unable to access the DAP. I have tried different cables, two different computers, and the cloud IDE for code composer studio. Every time I get the same error.

I verified the SOP was set to 010 and was still experiencing the issue. I then set it to 000 (removing the jumper), was able to build and run the program. However, on a new project I am experiencing the same DAP issue again. Removing the jumper to set the SOP to 000 does not work because it needs to be set 010 to build the project. Every time I run the project I get the error again. If I unplug the board from my computer and plug it back in, the project will run but I have to do it every single time I run the project. This is reproducible every time. I think something might be wrong with the board.

Your assistance is appreciated.

Regards,
Carlo

  • 0
    Guru 80815 points

    Hi Carlo,

    This error is likely that device is at production mode and JTAG is from this reason locked. Please use Uniflash or SysConfig image creator and switch your device into development mode. Another reason may to be switching JTAG pins into alternate function by your code during runtime.

    Jan

  • 0 in reply to Sabeeh Khan1
    TI__Expert 7715 points

    Hello Jan and Sabeeh,

    Thank you for the assistance.

    Our customer has opened the image.syscfg like mentioned, verified it was on development mode, and rerun the program but still receiving the same error.

    The code that the customer is using is straight from the SimpleLink CC32xx SDK -> examples -> Development Tools -> CC3220S LaunchPad -> TI Drivers -> uart2echo -> No RTOS -> CCS Complier -> uart2echo
    The customer has not modified the example code at all.


    Regards,
    Carlo

  • 0 in reply to Carlo
    Guru 80815 points

    Hi Carlo,

    Please provide screenshot of device status from Uniflash (like image below) and provide photo of LP to check jumper settings.

    Jan

  • 0 in reply to Jan D
    TI__Expert 7715 points

    Hello,

    The customer was using the latest version (5.30.00.08) of the SDK, but instead downloaded an older version (4.30.00.06 ). When importing the projects from the older version, they no longer experience this issue and the older version of the SDK does not generate the "image.syscfg" which they think was causing my issue.
    They has just been using CCS and was not able to import the CCS project into Uniflash so they created a blank project in Uniflash.

    Regards,
    Carlo

  • 0 in reply to Carlo
    Guru 80815 points

    Hi Carlo,

    That is pretty interesting that issue was caused by latest SDK version (5.30). Maybe it can be related that your customer uses MAC. Please wait for answer from guys from team.

    btw ... according screenshot and jumper settings is LaunchPad properly configured and your customer should be ready to go...

    Jan

  • 0 in reply to Carlo
    TI__Mastermind 36360 points

    Hi Carlo, 

    If the customer reverts back to the 5.30 SDK, does the issue still occur?

  • 0 in reply to Sabeeh Khan1
    TI__Mastermind 36360 points

    Your customer also mentioned using two different computers, were both apple computers? 

  • 0 in reply to Sabeeh Khan1
    TI__Expert 7715 points

    Hello Sabeeh,

    Please see the response below:

    Yes reverting back to 5.30 produces the issues again.

    One computer is a Mac, the other computer is a Windows PC.

    I just tried the 4.30 version on the PC and experience the same behavior. Two different USB cables and 2 different USB ports, no issues.

    On both computers:

    On the 5.30 version I get the error right off the bat. I am able to unplug the board while the error is popped up and then plug back in and hit retry and the program runs. Once I unplug the first time, I can run the program again without error as long as I don't change anything in the build. Once I change the code and it builds again, the error comes back

    On the 4.30 version I can edit the code, run the program, and repeat and I never get an error.

    Initially when switching from the 5.30 back to the 4.30, I sometimes get the error but I unplug/replug one time and I have no more issues.

    Regards,
    Carlo

  • 0 in reply to Carlo
    TI__Mastermind 36360 points

    Hi Carlo,

    Are you building the "MCU+ Image" or "Debug" configuration? Please switch over to the "Debug" build configuration and attempt again, this should resolve your issue. When executing from CCS, you should be using this configuration. 

    Click the drop down arrow next to the Hammer Icon:

  • 0 in reply to Sabeeh Khan1
    TI__Expert 7715 points

    Hello Sabeeh,

    According to our customer, it appears that when opening a new example from the 5.30 SDK, the default build is set to MCU+Image. Changing the build mode to debug seems to resolve the issue. They still get the error the first time run and have to unplug then plug it back in, but after that, it is good to go.

    Regards,
    Carlo