Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

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/MSP432P401R: Can't See MSP432 LaunchPad

Part Number: MSP432P401R

Tool/software: Code Composer Studio

I'm just getting started in the Robotics course and having trouble with seeing the MSP432 Launchpad in TExaSdisplay.

The test programs, like InputOutput, compile and load onto the board just fine. The LEDs and switches function correctly.

But I can't see any readout on TExaSdisplay. Here's what I've done:

Tried 3 different USB cables and several USB ports on my desktop.

Closed all ports and reopened (several times)

Uninstalled/Reinstalled CCS. 

I've searched for answers and have seen others with the same issue, but no solutions. Do I have a bad board or am I missing a setting somewhere.

Be patient, this is new tech for me.

Thanks

  • What version of Windows are you running?

    Make sure you have installed the device driver for the MSP432. Plug the board in then go to Device Manager. Under the Ports (COM & LPT) you should see the following entries:
    XDS110 Class Application/User UART
    XDS110 Class Auxiliary Data Port.

    If you don't see these two entries or there is some kind of yellow symbol next to it then there is an issue with the device driver.

    Write down the COM ported associated with "XDS110 Class Application/User UART". In TExaSdisplay go to the Serial port settings and enter the COM port # associated with "XDS110 Class Application/User UART". Make sure the baud rate is set to 115200. Give that a shot.

    If that doesn't work then please share a picture of your Launchpad so I can double check the jumpers.
  • Double check the LaunchPad drivers as previously suggested. Are you seeing the correct COM port show up in TExaSdisplay that matches your LaunchPad?  You can review the TExaSdisplay video https://training.ti.com/ti-rslk-module-1-lab-video-13-running-texas-logic-analyzer?cu=1135347 and run the TExaS example as shown.

  • Everything looks to be set right, but I'm still not seeing anything in TExaSdisplay.

    I'm using Windows 10 Home. Here are some screenshots...

    This is from Device Manager

    From TExaSdisplay. I set the port to 6 to match my Device Manager. Originally, it was set to 0 to search.

    This is the screen I get in TexaSdisplay:

    Finally, here is the LaunchPad. All the jumpers are in the original positions. I haven't seen anything about changing them, so I left them as is.

    I went through the video again, but couldn't find anything I'm doing wrong.

    As I said, the board seems to be working fine. The LEDs respond correctly, but nothing is getting back to TExaSdisplay.

    Thanks for your help, I'm stuck.

    Randy

  • One more screenshot.

    This is the code in the version of TExaS I have. It's a little different than the code in the video, but I'm not sure it makes a difference, if the variables are consistent. I did try changing TExaS_Init(LOGICANALYZER_P1); on line 72 to "P6" to match the port, but it didn't change anything.

  • The module 1 section 1.4.8 has the following note.

    "The first step is to activate the TExaS project, and open the TExaSmain.c file.
    There are three main programs in this project. Edit the LogicAnalyzerMain
    function so it is called main, and edit the other main to be Lab2main. Notice the
    MSP432 will be running at 48 MHz and the logic analyzer is configured to display
    Port 1. When it is running the seven bits of P1.6 – P1.0 will be streamed to the
    PC at 10 kHz. The logic analyzer works whether the pin is an input or output. In
    this example, P1.0 is an output (to the red LED) and P1.1/P1.4 are inputs from "

    Based on your above code it appears that you still need to rename this function to "int main(void)". Give that a shot.
  • That was it! And I feel like an idiot. Can't believe I missed that. I even saw that the code in the video was different.

    I read through that several times and missed it every time.

    Thanks for your help. I'm going to be more careful going forward.

    Randy