• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 449 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

UART & Windows 7 Timeout Issue

Rick Faszold
Expert 1090 points


Hi TI:

Pretty simple issue.  I'm running a Tiva Launchpad.  I'm using the USB connection for all UART0 I/O and PuTTY to talk to the Board.

It runs great; but, I have one tiny issue that may not be related to the Tiva board at all.  So, I'm just soliciting thoughts.

After the PC wakes up from "hibernation", I lose "half" of my connectivity from the Windows 7 PC to the Tiva Board.
 
I wake the PC up and then start hitting <enter> in the PuTTY console in order to get the attention of the Tiva board. 
It should come back with "C:\"...  (I was feeling nostalgic for my old 286 and DOS 2.1.)    Nothing happens.
 
I blink the Tiva LED BLUE when it receives input from the UART.  I can see the LED blinking away.. BLUE.  It looks like it is receiving the <enter> from PuTTY.  HOWEVER, I never receive the "C:\" in return.
 
In order to receive the "C:\" or "full I/O", I have to power down the Tiva and restart the PuTTY session. My feeling is simply that this is related to Windows 7; but, since I do not have a sniffer for this, I can not validate.
 
I try to catch the return codes from the UART Send/Receive; but, once the PC hibernates, everything seems a little angry waking up.    Thus, breakpoints are not working as expected.
 
Any thoughts would be great.
 
 
 
One more thing...  Can the programmers consider looking at a small issue? 
 
 
In Board.h, I see the following..
#define Board_LED                   EK_TM4C123GXL_LED_BLUE
#define Board_LED2                  EK_TM4C123GXL_LED_RED
#define Board_LED3                  EK_TM4C123GXL_LED_GREEN  // I added this line.  Was this a legal add?
 
In EK_TM4C123GXL.h
/*!
*  @def    EK_TM4C123GXL_GPIOName
*  @brief  Enum of GPIO names on the EK_TM4C123GXL dev board
*/
typedef enum EK_TM4C123GXL_GPIOName {
EK_TM4C123GXL_LED_RED = 0,
EK_TM4C123GXL_LED_BLUE,
EK_TM4C123GXL_LED_GREEN,   // this was already defined.....
EK_TM4C123GXL_GPIO_SW1,
EK_TM4C123GXL_GPIO_SW2,  
EK_TM4C123GXL_GPIOCOUNT
}
EK_TM4C123GXL_GPIOName;
 
 
Green seems to be properly defined in EK_TM4C123GXL.h; but, missing in Board.h.
 
Thanks

 

Rick

          

  • 0
    TI__Genius 9035 points

    Are you using the debug link for the UART or are you implementing a USB UART using one of our usb_dev_serial examples?

    Where are those header files coming from(EK_TM4C123GXL and Board.h)?   They are not part of the TivaWare release.

  • 0 in reply to Stellaris Paul
    Expert 1090 points

    Hey Stellaris Paul:

    That you very much for answering these questions.

    I'm not sure that I understand the extent of your first question...  I am using a Debug version of the program.  I will recompile to Release to see if that changes anything.  I did not even think of that.  The UART is connected via a USB cable, the same cable that CC uses to help Debug & send .bin to the Board.  Does that help?   When I close CC, I still have connectivity via PuTTY all the way until the machine hibernates...

    The files that you refer to are automatically installed.  If I create a project called Test and select an empty TI-RTOS "shell", these files are automatically created.  Without touching anything, this is what I start out with:

     

    I think that Board.h is missing the Green LED as defined in EK_TM4C123GXL.h.

     

    Thanks for helping.  Should have thought about the Debug stuff.

    Rick

  • 0 in reply to Rick Faszold
    TI__Genius 9035 points

    I was just wondering if you had implemented your own USB serial device, but it sounds like you are using the debug connection for the serial device.  I'll try and duplicate that here and see if I can figure out what is going on.

    I'll have to look at how those files are generated because they are not from the standard TivaWare release.