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.

Connected LaunchPad (EK-TM4C1294XL) IoT Quickstart bugs

Other Parts Discussed in Thread: EK-TM4C1294XL, EK-LM3S8962, LM3S8962

In examining the source code for the qs-iot example application for the EK-TM4C1294XL Connected LaunchPad and porting that code to the older EK-LM3S8962 Stellaris® LM3S8962 Ethernet+CAN Evaluation Kit board, I uncovered a couple of bugs in the qs-iot code.

 1) TivaWare\examples\boards\ek-tm4c1294xl\drivers\exosite_hal_lwip.c
       Line 680: the wrong size is returned
       Suggest: Line 669: return the value returned by "usprintf()"

 2) TivaWare\examples\boards\ek-tm4c1294xl\qs_iot\requests.c
       Line 324: if "ExtractValueByAlias()" returns false (i.e. no value found for the alias), the following "StatSetVal()" blindly writes to the status item whatever was left in the "pcServerValue" string from a previous use
      Suggest: Line 324: test the return from "ExtractValueByAlias()" to conditionally call "StatSetVal()"

  • I found another bug:

     3) TivaWare\examples\boards\ek-tm4c1294xl\qs_iot\qs-iot.c.c
          Line 1044: "ui32Timeout" will NEVER be 0
          Suggest: Line 1044: test "ui32Timeout" for == 1


  • And yet another bug:

    When running the "tictactoe" game in the "play locally" mode, why does the board request the "gamestate" from Exosite? This can cause a problem in which a delayed state response from Exosite can overwrite the local state of the game, especially when running in a pre-emptive task switching environment such as FreeRTOS.

    Suggest: in TivaWare\examples\boards\ek-tm4c1294xl\qs_iot\tictactoe.c
          Lines 605 to 609, move to before Line 598