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.

MSPM0G3507: GPIO not working for some LaunchPad Boostpacker pins

Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Using the MSPM0G3507 LaunchPad, I am trying toggle the PA26 BoosterPack pin using GPIO.

Starting with a working Driverlib example for the on-board LEDs, I used Sysconfig to change the port/pin settings from LED1 to PA26/30 using Sysconfig. Keeping the names the same, I didn't have to change my source code.

Running the code, I can see that PINCM59 gets set up correctly. And when toggling the pin, I see DOUT changing correctly. But the Boosterpack pin doesn't change. I first tested the pin by jumpering it to J4 -- which should have toggled LED1. Next, I used a logic analyzer. But in either case, the BoosterPack pin doesn't appear to toggle.

Since I picked PA26 randomly from the BoosterPack pins, I next tried PA24... with the same negative results.

On my third try, PA8 worked as expected. I could see the pin toggle using my logic analyzer. It also blinked LED1 when jumpered to J4.

Is there something obvious that I'm missing?

Why won't PA24 or PA26 (connected to the BoosterPack connector) toggle?

As one final note, I don't have a way to probe the MCU's pin directly. So, I can't tell if this is a problem with the LaunchPad BoosterPack connection or with the MCU itself.

I look forward to your thoughts and ideas!

  • Hi Scott,

    Some of the boosterpack pins will be affected by other circuitry on the board.

    In the case of PA26, the MSPM0's pin is connected to the boosterpack, but it is also connected to two jumper connectors, J18 and J9. Making sure that J18 is disconnected, and that J9 is either disconnected, or the jumper is on positions 1 and 2, should allow you to see the correct behavior on pin PA26 on the boosterpack.

    For PA24, I am wondering if R79 and R80 are both populated, and if C50 is still de-populated. Could you check this? 

    You can see the device schematic here in section 5, please check this for a better understanding of these connections and for future hardware issues when working with the Launchpad.