MSPM0C1104: I want to use SWD pins as a PWM

Yuvaraj S

Part Number: MSPM0C1104
Other Parts Discussed in Thread: UNIFLASH, , SYSCONFIG

Tool/software:

Hi All,

I'm using MSPM0C1104SDDFR SoT23-8 8 pin microcontroller . I upon referring the reference manual of the MSPMC1104 IC I understood that i can disable SWD pins in software and access them as a GPIO Pin, and can can enable them only by POR (Power on Reset ) .

In my code i Disabled the SWD pins using the API " DL_SYSCTL_disableSWD();" with delay cycles 10000000 "delay_cycles(10000000);" assuming it as 10 sec . After this is configered those pins as a PWM pin by the following api's

" DL_GPIO_initPeripheralOutputFunction(IOMUX_PINCM21,IOMUX_PINCM21_PF_TIMA0_CCP0);

DL_GPIO_enableOutput(GPIOA, DL_GPIO_PIN_20);

DL_GPIO_initPeripheralOutputFunction(IOMUX_PINCM20,IOMUX_PINCM20_PF_TIMA0_CCP2);

DL_GPIO_enableOutput(GPIOA, DL_GPIO_PIN_19);

DL_GPIO_setDigitalInternalResistor(IOMUX_PINCM21, (IOMUX_PINCM_PIPU_DISABLE | IOMUX_PINCM_PIPD_DISABLE));

DL_GPIO_setDigitalInternalResistor(IOMUX_PINCM20, (IOMUX_PINCM_PIPU_DISABLE | IOMUX_PINCM_PIPD_DISABLE));

DL_TimerA_setCCPDirection(TIMA0 , DL_TIMER_CC0_OUTPUT | DL_TIMER_CC2_OUTPUT ); "

I flashed the 8pin microcontroller in my custom board i waited for 10 sec No pulse where produced from the PWM pin (previously SWD Pins) . I already checked this program of PWM with MSPMC11041 launch pad ( except the SWD pin change to GPIO).

Since No pulse produced from my 8 pin microcontroller . I tried to flash it again by proceeding with the POR ( by removing and plugging the 4pin of microcontroller from 3.3V source which holding the RESET for more than 5 sec) but i can't able to flash the microcontroller from then on. Plz point out my mistakes and help me out .

my requirement is that I wanted to disable the SWD pin and use that pin as PWM pins . after POR i want the SWD to be enabled for 5 to 10 sec .

Fullscreen 8358.main.c Download

/*
 * Copyright (c) 2021, Texas Instruments Incorporated
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * *  Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 *
 * *  Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 *
 * *  Neither the name of Texas Instruments Incorporated nor the names of
 *    its contributors may be used to endorse or promote products derived
 *    from this software without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
 * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
 * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
 * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
 * OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
 * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
 * OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 */

#include <ti/driverlib/m0p/dl_interrupt.h>
#include "ti_msp_dl_config.h"

bool pulseTerminal=0 ;



int main(void)
{

    SYSCFG_DL_init();


    for(uint32_t i=0 ; i<100 ;i++)
     delay_cycles(10000000);
    DL_SYSCTL_disableSWD();

  DL_GPIO_initPeripheralOutputFunction(IOMUX_PINCM21,IOMUX_PINCM21_PF_TIMA0_CCP0);
  DL_GPIO_enableOutput(GPIOA, DL_GPIO_PIN_20);
  DL_GPIO_initPeripheralOutputFunction(IOMUX_PINCM20,IOMUX_PINCM20_PF_TIMA0_CCP2);
  DL_GPIO_enableOutput(GPIOA, DL_GPIO_PIN_19);
    
	DL_GPIO_setDigitalInternalResistor(IOMUX_PINCM21,  (IOMUX_PINCM_PIPU_DISABLE | IOMUX_PINCM_PIPD_DISABLE));
	DL_GPIO_setDigitalInternalResistor(IOMUX_PINCM20,   (IOMUX_PINCM_PIPU_DISABLE | IOMUX_PINCM_PIPD_DISABLE));
   DL_TimerA_setCCPDirection(TIMA0 , DL_TIMER_CC0_OUTPUT | DL_TIMER_CC2_OUTPUT );
    NVIC_EnableIRQ(TIMA0_INT_IRQn);

    DL_Timer_startCounter(TIMA0);


    while (1)
    {

    }
}





void TIMA0_IRQHandler(void)
{
  pulseTerminal =! pulseTerminal;
  if(pulseTerminal)
   DL_Timer_setCCPOutputDisabledAdv(TIMA0, DL_TIMER_CCP0_DIS_OUT_ADV_SET_BY_OCTL| DL_TIMER_CCP1_DIS_OUT_ADV_FORCE_LOW| \
                                        DL_TIMER_CCP2_DIS_OUT_ADV_FORCE_LOW | DL_TIMER_CCP3_DIS_OUT_ADV_FORCE_LOW);
  else
  {
    DL_Timer_setCCPOutputDisabledAdv(TIMA0, DL_TIMER_CCP0_DIS_OUT_ADV_FORCE_LOW| DL_TIMER_CCP1_DIS_OUT_ADV_FORCE_LOW| \
                                          DL_TIMER_CCP2_DIS_OUT_ADV_SET_BY_OCTL | DL_TIMER_CCP3_DIS_OUT_ADV_FORCE_LOW);
  }

  
}

over 1 year ago

0 Dennis Lehman over 1 year ago

TI__Guru 71216 points

Hi Yuvaraj,

I think your issue is you are not waiting long enough before disabling the SWD pins.

I checked your calculations. 10,000,000 does not provide a 10s delay. Based on the bus clock of 24Mhz, if you used delay_cycles(24000000), this would equal 1sec. So if you want 10 sec, you need to do something like this -> delay_cycles(24000000 * 10)

This may be part of your problem. You need to give the programmer adequate time to connect to the target. 2-3 seconds is typical, but you may need more so you may have to experiment a bit to determine what delay works best for your setup.

You can also considering setting up one of the timers as a "one-shot" and interrupt enabled. That way you put CPU in sleep mode while waiting for the Timer interrupt to occur.

If your application needs this timer, you can reconfigure it during runtime.

Now, to get your M0 talking again, you need run the "Factory Erase" scripts to clear the device. The simplest way is to use Uniflash, connect to the target, click "Settings and Utilities", then scroll down to expose all the choices. You are looking for "Factory Reset auto" button under the DSSM Factory Reset group.

0 Yuvaraj S over 1 year ago in reply to Dennis Lehman

Prodigy 40 points

Thanks for your reply Dennis Lehman ,

I have two queries has follows .

As I mentioned earlier I No pulse where produced from the PWM pin (previously SWD Pins) why.
I can't able to factory reset the MCU . I tried program as per your suggestion "delay_cycles(24000000 * 10)" this time in my launch pad itself . unfortunately same issue continues . And now i can't able to reset the MCU in the Launch pad.

I think the MCU became undetectable.

0 Dennis Lehman over 1 year ago in reply to Yuvaraj S

TI__Guru 71216 points

Hi Yuvaraj,

Try this - > Remove power, then hold NRST low, apply power while continuing to hold NRST low > 1 second, then release NRST. See if you can get Uniflash to connect to the device and if successful run "Factory Reset Auto" script.

The reason for holding NRST low > 1 sec during a POR (cycle power) then releasing prevents the device from running the application and instead remains in an infinite loop in the Boot Routine. This allows the programmer to connect. See attached. Here is a snippet for convenience.

MSPM0 how to re-purpose nrst swd instructions_v1.pdf

0 Yuvaraj S over 1 year ago in reply to Dennis Lehman

Prodigy 40 points

Hi Dennis Lehman

I tried this POR procedure before itself . this doesn't work for me . I tried once again hoping for something good but it doesn't . Uniflash connects to Launchpad but factory reset auto is not working for me.

0 Dennis Lehman over 1 year ago in reply to Yuvaraj S

TI__Guru 71216 points

Hi Yuvaraj,

Does the programmer have access to the NRST pin in addition to SWD pins? The Factory reset script needs access to the NRST.

0 Yuvaraj S over 1 year ago in reply to Dennis Lehman

Prodigy 40 points

Hi Dennis Lehman

yes, Since i have testing this procedure in LaunchPad of course it has reset button

0 Dennis Lehman over 1 year ago in reply to Yuvaraj S

TI__Guru 71216 points

Ok. Based on your initial description I assumed a custom PCB

Yuvaraj S said:
I'm using MSPM0C1104SDDFR SoT23-8 8 pin microcontroller

But I do see later you say the following, so I apologize for the misunderstanding.

Yuvaraj S said:
Uniflash connects to Launchpad but factory reset auto is not working for me.

Ok, let me check with our tools team. I should get a response from them within the next couple of hours, or they will respond directly to this post.

0 Yuvaraj S over 1 year ago in reply to Dennis Lehman

Prodigy 40 points

My situation now is MSPM0C1104SDDFR SoT23-8 4 nos got bricked and a Launchpad too.

+1 Yuvaraj S over 1 year ago in reply to Yuvaraj S

Prodigy 40 points

Hi Dennis Lehman

Finally, I found a way to make the MSPM0C1104 in lauhpad to talk . I followed the instruction from this following forum

MSPM0C1103: about use together SWIO/CLK and IO PINS - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

I made the mistake by only holding the reset button for few seconds and released the button . after releasing the reset i tried to i pressed the factory reset button in uniflash .

Actual procedure should be as

1.Press the nRST button while power on.

2. Connect the launch pad in UNIFlash and start the Factory reset auto

3.wait till you see "CS_DAP_0: GEL Output: Command execution completed".

4. Now Release the nRST button . Then console shows output like this "CORTEX_M0P: GEL Output: Factory Reset executed. Please terminate debug session, power-cycle and restart debug session".

Okay , Now I know how to make my controller talk once it got brick. Now I want to know why i can't able to generate PWM after i disabled the SWD pins .

0 Dennis Lehman over 1 year ago in reply to Yuvaraj S

TI__Guru 71216 points

Let me see if I can duplicate the issue.

0 Dennis Lehman over 1 year ago in reply to Dennis Lehman

TI__Guru 71216 points

Hi Yuvaraj,

I am able to disable the SWD pin functions and re-assign as GPIO and toggle the pins, but for some reason, like you, I cannot seem to get the PWM outputs on these pins. Let me reach out to our design team to see if there is a missing step.

0 Zoey Wei over 1 year ago in reply to Yuvaraj S

TI__Genius 15081 points

Hi Yuvaraj S,

To workaround:

1. disable the SWD pin in sysconfig,

2. Configure the IOMUX in TIMER-PWM

Please refer to (+) *****)? - Arm-based microcontrollers - INTERNAL forum - Arm-based microcontrollers - INTERNAL - TI E2E support forums for more details.

Regards,

Zoey

0 Yuvaraj S over 1 year ago in reply to Zoey Wei

Prodigy 40 points

Hi Zoey Wei

I can't able to access the link provided by you.

0 Zoey Wei over 1 year ago in reply to Yuvaraj S

TI__Genius 15081 points

Hi Yuvaraj,

Oh... But can you use the method I mentioned to have a try?

Regards,

Zoey

0 Yuvaraj S over 1 year ago in reply to Zoey Wei

Prodigy 40 points

Hi Zoey Wei

I tried the method you mentioned

i disabled the SWD pins
Configure the IOMUX in TIMER-PWM

Still the PWM is not generating from these pins

0 Zoey Wei over 1 year ago in reply to Yuvaraj S

TI__Genius 15081 points

Hi Yuvaraj,

After DL_GPIO_setDigitalInternalResistor(IOMUX_PINCM20, (IOMUX_PINCM_PIPU_DISABLE | IOMUX_PINCM_PIPD_DISABLE));

Please add function:

DL_GPIO_initPeripheralOutputFunction

This is because, once you call the DL_GPIO_setDigitalInternalResistor function, the IOMUX will be changed back to the normal GPIO function, so you need to call the DL_GPIO_initPeripheralOutputFunction and change the IOMUX PF register back to the timer function.

Regards,

Zoey