• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 724 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.

Compiler/EK-TM4C1294XL: EK-TM4C1294XL

KISHAN%20PATEL
Intellectual 340 points
Part Number: EK-TM4C1294XL

Tool/software: TI C/C++ Compiler

Welcome to the Connected LaunchPad!!
Internet of Things Demo
Type 'help' for help.

"Current MAC: 001ab603243b
Obtaining IP...
Continuing in offline mode.


> IP Address Acquired: 192.168.43.185
Locating CIK... CIK found in EEPROM storage.

CIK: 598b68e622bf202f4ef78a7bd85c4b01954de72e

Connected! Type 'stats' to see data for this board.
> sta"

After this I can not type anything like stats in COM port window it is stop no update from Serial port I am edit program is like this...

1) In -qs_iot.c file

uint32_t g_ui32SW1Presses = 0;
uint32_t g_ui32SW2Presses = 0;
uint32_t g_ui32InternalTempF = 0;
uint32_t g_ui32InternalTempC = 0;
uint32_t g_ui32TimerIntCount = 0;
uint32_t g_ui32SecondsOnTime = 0;
uint32_t g_ui32LEDD1 = 0;
uint32_t g_ui32LEDD2 = 0;
uint32_t g_ui32LEDD3 = 0;
uint32_t g_ui32LEDD4 = 0;
uint32_t g_ui32LEDD5 = 0;
char g_pcLocation[50] = "";
char g_pcContactEmail[100] = "";
char g_pcAlert[140] = "";

tStat *g_psDeviceStatistics[NUM_STATS]=
{
    &g_sSW1Presses,
    &g_sSW2Presses,
    &g_sInternalTempF,
    &g_sInternalTempC,
    &g_sSecondsOnTime,
    &g_sLEDD1,
    &g_sLEDD2,
    &g_sLEDD3,
    &g_sLEDD4,
    &g_sLEDD5,

    &g_sLocation,
    &g_sBoardState,
    &g_sContactEmail,
    &g_sAlert,
    NULL
};

void
UpdateLEDs(void)
{
    //
    // If either LED's global flag is set, turn that LED on. Otherwise, turn
    // them off.
    //
    if(g_ui32LEDD1)
    {
        ROM_GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_1, GPIO_PIN_1);
    }
    else
    {
        ROM_GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_1, 0);
    }

    if(g_ui32LEDD2)
    {
        ROM_GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_0, GPIO_PIN_0);
    }
    else
    {
        ROM_GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_0, 0);
    }

    if(g_ui32LEDD3)
            {
                ROM_GPIOPinWrite(GPIO_PORTK_BASE, GPIO_PIN_0, GPIO_PIN_0);
            }
            else
            {
                ROM_GPIOPinWrite(GPIO_PORTK_BASE, GPIO_PIN_0, 0);
            }
    if(g_ui32LEDD4)
        {
            ROM_GPIOPinWrite(GPIO_PORTK_BASE, GPIO_PIN_1, GPIO_PIN_1);
        }
        else
        {
            ROM_GPIOPinWrite(GPIO_PORTK_BASE, GPIO_PIN_1, 0);
        }
            if(g_ui32LEDD5)
        {
            ROM_GPIOPinWrite(GPIO_PORTK_BASE, GPIO_PIN_2, GPIO_PIN_2);
        }
        else
        {
            ROM_GPIOPinWrite(GPIO_PORTK_BASE, GPIO_PIN_2, 0);
        }

}

2) In qs_iot.h

#define NUM_STATS                           16

3)In Pinout.c

ROM_GPIOPinTypeGPIOOutput(GPIO_PORTN_BASE, GPIO_PIN_0 | GPIO_PIN_1);
    MAP_GPIOPadConfigSet(GPIO_PORTN_BASE, GPIO_PIN_0 | GPIO_PIN_1,
                             GPIO_STRENGTH_12MA, GPIO_PIN_TYPE_STD);
    ROM_GPIOPinTypeGPIOOutput(GPIO_PORTK_BASE, GPIO_PIN_0 | GPIO_PIN_1 | GPIO_PIN_2);
       MAP_GPIOPadConfigSet(GPIO_PORTK_BASE, GPIO_PIN_0 | GPIO_PIN_1 | GPIO_PIN_2,
                                GPIO_STRENGTH_12MA, GPIO_PIN_TYPE_STD);

    //
    // Default the LEDs to OFF.
    //
    ROM_GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_0 | GPIO_PIN_1, 0);
    ROM_GPIOPinWrite(GPIO_PORTK_BASE, GPIO_PIN_0 | GPIO_PIN_1 | GPIO_PIN_2, 0);

Please help me in this and what is the problem in this.......

  • 0
    Guru 117855 points
    Is this not (very much) the same post you issued a week past - and then abandoned? (after removing your name from the Subject block?)
  • 0
    TI__Guru 72500 points
    If I understand correctly, you modified the example program and now it does not execute properly. You will need to debug your program. Use CCS to step through the code. You will need to understand what the example is doing. (QS_IOT is a very complex example and may not be the best one to start with.) You know the modified program gets to the point that it prints "Connected! Type 'stats' to see data for this board". Find that location in the source code and put a breakpoint there. Execute from reset and you should hit that breakpoint. Now step through the C code to see where things go wrong.

    I know at first there is the temptation to make lots of changes and expect them all to work. Experienced writers of firmware tend to make small changes and verify each part along the way. Keep each change simple, then verify it works as expected before adding the next feature.