• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 79 subscribers
  • Views 969 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 the target:

Kenneth Lindsay
Prodigy 240 points
Other Parts Discussed in Thread: MSP430F5529, MSP430FR5969

Error connecting to the target:
(Error -1063 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver.
(Emulation package 6.0.83.1)

This is the second Launchpad I have gotten this message, within a week.  At this rate it is starting to get expensive

I haven't figured out to recover from this error after googling and looking at all the posts in this forum.

What I am trying to do is create a Static Library that I can link to, from a executable output project.

  • 0
    TI__Guru 56685 points

    Kenneth,

    Can you provide which launchpad you are having issues with? (MSp430F5529, MSP432, MSP430FR5969........)

    Also, please try to download a standard blinky example via CCS/IAR to the device. The IDE should download the correct drivers and possibly update the emulator on the Launchpad to get it working. Once you can download a bare example, you should be good to go after that.

    Alternatively, you can also use CCS Cloud to download an example project at dev.ti.com  .

    Regards,

    JH

  • 0 in reply to Jace H
    Prodigy 240 points

    It is a MSP432P401R.

    After the lock-up I installed "blinky", trying to debug "blinky" is where I got the error message to post.  Since that time

    I followed the instructions in the Code Composer Studio™ 6.1 for MSP432 user guide, "slau575c.pdf.  Their is a "factory reset"

    script that fixed both Launchpads.  I tried following the "factory reset" procedure before but somehow must have skipped a step.

    What would be interesting is to figure out how it happened in the first place so that it wouldn't happen again.

  • 0 in reply to Kenneth Lindsay
    TI__Guru 56685 points

    Kenneth,

    I had a suspicion that it was MSP432LPs that had the issue. The issue is known and is caused with a mismatch of MSPWare and CCS/IAR version. Updates were not completely in sync and some files CCS or MSPWare looks for where moved from their original location during an update. You can read more about it in the following E2E post: https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/460430/1663082#1663082

    This has been addressed, but unfortunately there are still some issues that crop up when using an older project with an updated CCS or MSPWare and vice versa.

    Regards,
    JH

  • 0 in reply to Jace H
    Prodigy 240 points
    For some reason trying to access the link that you gave me "e2e.ti.com/.../467612" gives me an "Access denied" error message.

    What I find interesting is that I now get 2 startup files automatically added to a new project:
    startup_msp432p401r_ccs.c
    system_msp432p401r.c
    Before this there was just one file:
    msp432_startup_ccs.c
  • 0 in reply to Kenneth Lindsay
    TI__Guru 56685 points
    Sorry about that. Wrong link before. Updated with valid link.

    You have identified part of the compatibility problem there. Once everything is updated to the same page. all should be working fine again.

    Regards,
    JH

**Attention** This is a public forum