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.

TM4C1294NCPDT: LaunchPad debug problem.

Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL

Hi team,

     I am using the TM4C1294NCDPT launchpad unable to debug the program.

/*CORTEX_M4_0: Error connecting to the target: Unable to communicate with the device. Please check your connection. */   

During working in pwm program.

Next what we ca do !!!

Thanks and Regards,

Aravind.S.R

  • HI,

      Is this the first time you are trying to connect to the LaunchPad or it has been working before until today?

      If the LaunchPad has been working before, then do you know what is the latest program that is currently in the flash? Is that the stock TivaWare pwm program or some other program you had modified? If you modified the program then what did you modify?

      I will suggest you first try to unlock the device and see if you can recover the chip. See below screenshot and Unlock the device to its factory setting, 

  • HI TEAM,

    //*****************************************************************************
    //
    // blinky.c - Simple example to blink the on-board LED.
    //
    // Copyright (c) 2013-2020 Texas Instruments Incorporated. All rights reserved.
    // Software License Agreement
    //
    // Texas Instruments (TI) is supplying this software for use solely and
    // exclusively on TI's microcontroller products. The software is owned by
    // TI and/or its suppliers, and is protected under applicable copyright
    // laws. You may not combine this software with "viral" open-source
    // software in order to form a larger program.
    //
    // THIS SOFTWARE IS PROVIDED "AS IS" AND WITH ALL FAULTS.
    // NO WARRANTIES, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT
    // NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    // A PARTICULAR PURPOSE APPLY TO THIS SOFTWARE. TI SHALL NOT, UNDER ANY
    // CIRCUMSTANCES, BE LIABLE FOR SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
    // DAMAGES, FOR ANY REASON WHATSOEVER.
    //
    // This is part of revision 2.2.0.295 of the EK-TM4C1294XL Firmware Package.
    //
    //*****************************************************************************

    #include <stdint.h>
    #include <stdbool.h>
    #include "inc/hw_memmap.h"
    #include "driverlib/debug.h"
    #include "driverlib/gpio.h"
    #include "driverlib/sysctl.h"
    #include "driverlib/pin_map.h"

    //*****************************************************************************
    //
    //! \addtogroup example_list
    //! <h1>Blinky (blinky)</h1>
    //!
    //! A very simple example that blinks the on-board LED using direct register
    //! access.
    //
    //*****************************************************************************

    //*****************************************************************************
    //
    // The error routine that is called if the driver library encounters an error.
    //
    //*****************************************************************************
    #ifdef DEBUG
    void
    __error__(char *pcFilename, uint32_t ui32Line)
    {
    while(1);
    }
    #endif

    //*****************************************************************************
    //
    // Blink the on-board LED.
    //
    //*****************************************************************************


    int main(void) {


    SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOQ);

    GPIOPinConfigure(GPIO_PQ4_DIVSCLK);

    GPIODirModeSet(GPIO_PORTQ_BASE, GPIO_PIN_4, GPIO_DIR_MODE_HW);
    GPIOPadConfigSet(GPIO_PORTQ_BASE, GPIO_PIN_4, GPIO_STRENGTH_2MA, GPIO_PIN_TYPE_STD);


    SysCtlClockOutConfig(SYSCTL_CLKOUT_EN | SYSCTL_CLKOUT_SYSCLK, 10);

    while (1) {
    // Main loop
    }
    }

    SysCtlClockOutConfig(SYSCTL_CLKOUT_EN | SYSCTL_CLKOUT_SYSCLK, 10);

    In this line i will change the 10 <=> 100

    Using LM Flash programmer  unable to erase it.....

    Next  what we can do ?

    Thanks and Regards

    Aravind.SR

  • Hi,

      Please refer to this post for details. https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/345762/tiva-c-series-tm4c1294-connected-launchpad. The problem is that PQ4 is driven by the TPS to indicate OC (over current) to the MCU. When configuring PQ4 for DIVSCLK, it messes up the TPS and affects the ICDI emulation. Please either the cut the trace to the OC signal or remove U4 as mentioned as the workaround in the post if you really need to use DIVSCLK in the future for your application. If you have a custom board, this problem may not affect you depending on your use of PQ4.