• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 2024 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.

Code composer Error using MSP-FET for MSP430

m afsar
Prodigy 50 points

Other Parts Discussed in Thread: MSP-FET

During debug configuration getting following error.

Device Manage in Window 10 under Ports show "MSP Debug Interface (COM65) which matches.  Beside, there is no option of configuring debug port# in code composer- where is COM65 coming from- is it hard coded?

MSP430: Can't Initialize Target CPU: **Error**: Serial Communication failed at port: COM65, baud rate:9600!   To use serial monitor, please ensure the following prerequisites are satisfied:  1. Make sure the cable is plugged into both the target and the host on the right COM port.  2. Make sure a compatible target side serial monitor is loaded and running on the target device.

  • 0
    TI__Guru**** 173310 points

    m afsar said:
    MSP430: Can't Initialize Target CPU: **Error**: Serial Communication failed at port: COM65, baud rate:9600!   To use serial monitor, please ensure the following prerequisites are satisfied:  1. Make sure the cable is plugged into both the target and the host on the right COM port.  2. Make sure a compatible target side serial monitor is loaded and running on the target device.

    It sounds like you are selecting a UART Connection instead of a MSP-FET debug connection. Typically the debug connection in the target configuration file should be set to "TI MSP430 USB1" for MSP430 devices. Have you tried using that setting?  

  • 0 in reply to AartiG
    Prodigy 50 points

    Thanks.  It works now

  • 0 in reply to m afsar
    Prodigy 30 points
    Hi
    Thanks for your help.
    I try this you related on your post, but happend the same error.

    Regards
    Manuel