• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 79 subscribers
  • Views 268 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.

MSP-EXP432P401R: Rev 1.0 not creating USB port on Mac laptop to interface with board

John Mascavage
Prodigy 30 points

Part Number: MSP-EXP432P401R

I have an MSP-EXP432P401R Rev 1.0 board (the dark gray one, before they started being made on a red board). 

I am unable to connect to it with my Mac laptop - no USB port is created.  I have a MSP-EXP432P401R Rev 2.1 board (red colored) that has no issue connecting with the same cable plugged into the same USB port, but swap the boards and it doesn't work.

All jumpers are "jumped" between the XDS110-ET side of the board and the MCU side.

I get a green and red LEDs blinking on the MCU side of the board (the blinking may be may last uploaded program) - the point being that the MCU side of the board is receiving power

BUT the XDS110-ET side of the board has not LEDs lit up - I think a green one is supposed to light up and I get that on the other, Rev 2.1 board.

So it is clear that power is getting to the board as a whole, and the cable works, but the Rev 1.0 board does not seem to be presenting as a USB port, so I don't know how I could refresh firmware or do anything else.

The TI website says that the MSP-EXP432P401R is not supposed to require any drivers on a mac - and the Rev 2.1 connects fine.

Help is appreciated :-) 

  • 0
    TI__Mastermind 32920 points

    Hi,

    1. First you need to check the power supply on Rev 2.1 board is good.

    2. Second you need to check if the Debug MCU(TM4C129) is good. You can to use the debugger on Rev 2.1 board to get access to it.

    3. Make sure the code in the Debug MCU is good. Or you can program it by yourself. 

    I assume it has a relationship with the debug MCU.

    Eason

  • 0
    Guru 88700 points

    As of (I think) v8.1, CCS doesn't support the Black Launchpad. As in: It recognizes it and rejects it.

    I don't see an obvious connection with it not being recognized by the USB driver, but it does limit the value of getting it to work.

  • 0 in reply to Eason Zhou
    Prodigy 30 points

    I am not following why you are referring to the Rev 2.1 board - that board is working fine.  I only mentioned it to demonstrate why I believed there was no issue with my USB cable (sometimes people use cables that only provide power and not all connections for comms, so I wanted to be clear that this was not my issue).  I also mentioned it as a comparison of the LEDs on the Rev 2.1 board that is working and the Rev 1.0 board that is not - I seem to recall reading that a green LED is supposed to light up on the XDS110 side of the board when plugged in, and that happens on the working 2.1 board but not on the 1.0 board.

  • 0 in reply to John Mascavage
    TI__Mastermind 32920 points

    Sorry. I declare it wrong.

    1. First you need to check the power supply on Rev 1.0 board is good.

    2. Check when you plug in Rev 2.0 board, can you find any change in device manager.

    3. Second you need to check if the Debug MCU(TM4C129) is good. You can to use the debugger on Rev 2.1 board to get access to it.

    4. Make sure the code in the Debug MCU on Rev 1.0 board is good. Otherwise you can program it by yourself. 

    I assume it has a relationship with the debug MCU. 

  • 0 in reply to Eason Zhou
    Prodigy 30 points

    how do I use the debugger on the Rev 2.1 (working board) to check the Rev 1.0 (non-working board)?  Is there an article for doing this?  Will connecting through "chaining" the boards in that manner allow we to upload new code?  I believe the MCU itself is likely to be fine and the issue is limited to the emulator side of the board.

  • 0 in reply to John Mascavage
    TI__Mastermind 32920 points

    For the read board, you can find the debug port on the UG:

    I think you can find the same debug port on the black board. As I checked before, the debug port is not locked.

    Eason

**Attention** This is a public forum