• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 79 subscribers
  • Views 1217 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.

CC3100BOOST_MQTT-TwitterLED_MSP432P401R Demo program fails

Lance Halsted
Intellectual 335 points

Other Parts Discussed in Thread: CC3100BOOST, CC31XXEMUBOOST, CC3100

I'm using a new MSP432 and CC3100Boost and trying to run the MQTT-TwitterLED demo that is part of MSPWare_2_21_00_39 (using Keil MDK 5 development environment). I made the appropriate changes from the Readme file (SSID_NAME, SEC_TYPE, PASSKEY, etc.), but the program doesn't work. When I modify cli_uart.h by adding #define _USE_CLI_ in order to get debug messages, I see the banner message but nothing after that: 

MQTT Twitter Controlled RGB LED - Version 1.0.0
*******************************************************************************

There should be other status messages that print out.

At one time, I had this demo working with other hardware. Then after testing the old CC3100Boost with the CC31XXEMUBoost, I couldn't get the Twitter demo working again so I eventually bought new hardware even though the CC3100Boost and the MSP432 worked fine with other applications. With the new hardware, the MSP432 runs the Out-Of-The-Box demo fine. Anyway, since I'm using brand new hardware, this looks like a software problem.

It could have something to do with unhandled interrupts. In fact, the interrupt handlers don't appear to have the correct names (CMSIS default) based on the vector table. However, I've tried changing those names and the program still doesn't run. Anyone seen problems with this demo??

  • 0
    TI__Guru* 85400 points
    Hi,

    Please see: e2e.ti.com/.../444995

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Intellectual 335 points
    Hi,

    Thanks for the suggestion. However, this project doesn't seem to use the macro SERVER_ADDRESS at all. When I do a Find in Files, I get

    Searching for 'SERVER_ADDRESS'...
    Lines matched: 0 Files matched: 0 Total files searched: 130

    This application goes through a public MQTT Broker before connecting to the IBM Bluemix Node-RED Server.

    It seems that the application fails to return from the function call:

    mode = sl_Start(0, 0, 0);

    in configureSimpleLinkToDefaultState(). Somehow, the MSP432 can't initialize the CC3100 Boost. Does the MSP432 provide enough current for the CC3100Boost or do I need to power the CC3100Boost from its own USB also? I have 2 sets of hardware both sets are failing the same way.

    Thanks,
    Lance Halsted
  • 0
    Intellectual 335 points

    The problem seems to be related to the Keil version of the demo code. I tried out the CCS Cloud version of the same demo and it works on both my sets of hardware. With the Keil version, the program fails before completing configureSimpleLinkToDefaultState() and typically ends up in the Hard Fault handler. 

    So my hardware is definitely working. The code works under CCS Cloud tools, but not under Keil. Since I plan to use Keil MDK, I'd still like to figure out what the problem is with that version. I've tried clean installs and it continues to fail. Thanks for any ideas.Any Keil experts?

  • 0 in reply to Lance Halsted
    TI__Guru* 85400 points
    Moving to MSP430 Forum

    Regards,
    Gigi Joseph
  • 0
    Intellectual 335 points

    I finally got this working with the Keil tools. The problems all have to do with the startup_msp432.s (Startup) file. The names of the interrupt handlers used in the program are not entered into the vector table as they are in the CCS Cloud tools. I left the names in the vector table alone and changed the interrupt handler names to match. However, I made that change many days ago and still couldn't get it working. The change that finally made things work was to increase  the stack size from 0x200 to 0x400!

    Stack_Size      EQU     0x00000400

    Apparently, there was a stack overflow with the default stack size. Now it works well. Very frustrating problem.

**Attention** This is a public forum