• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 40 subscribers
  • Views 483 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.

Original question:

CC3135: HTTP POST request doesn't hit SimpleLinkNetAppRequestEventHandler

SimplelinkNetAppEventHandler hit instead of SimpleLinkNetAppRequestEventHandler for HTTP POST requests

SN
Intellectual 265 points
Part Number: CC3135


Hi,

This is a continuation of the previous question I had posted. We were under lockdown so couldn't get to the hardware to flash the ROM before.

Anyway, I flashed the html pages now and found that there are no issues with GET/PUT request. The problem is only during the POST request. I accessed the index.html page and tried to add a new profile. The request does not get served i.e. profile is not getting added. When I tried with my custom HTTP POST request, it hits SimpleLinkNetAppEventHandler instead of SimpleLinkNetAppRequestEventHandler.  SimpleLinkNetAppEventHandler got called with a very weird pNetAppEvent->Id 1054843 for both the custom HTTP POST request and the specific one for profile add.

Wireshark captures the POST request correctly. So there should be no problem with the request per se.

What could the issue be?

Thanks

SN

  • 0
    TI__Guru 63006 points

    Hi,

    I don't know. Are you sure you read the event Id correctly? (not a pointer or something is wrong in the printf pattern).

    Assuming the SimpleLinkNetAppEventHandler was used with SL_NETAPP_EVENT_HTTP_TOKEN_POST (event Id value = 7), this means the resource you used in the HTTP request was found (as a file) in the ROM or in the file system. Can you send the HTTP POST details (either as wireshark file or as a screenshot)?

    Please provide NWP log for us to review (See details in chapter 20.1 in the programmer's guide: https://www.ti.com/lit/swru455 ).

    Br,

    Kobi

  • 0 in reply to Kobi Leibovitch
    Intellectual 265 points

    Hi Kobi,

    I updated the service pack and also had to modify the HTTP request. Now I am able to receive the request in SimpleLinkNetAppRequestEventHandler sometimes but most of the times it results in SimpleLinkFatalErrorEventHandler with SL_DEVICE_EVENT_FATAL_DRIVER_ABORT which keeps recurring even if I reboot the NWP and don't send any HTTP requests.

    What may be the cause of this?

    Thanks,

    SN

  • 0 in reply to SN
    TI__Guru 63006 points

    Hi

    It is probably due to some wrong handling of your application in response to the NetAppRequest event (DRIVER_ABORT means that this is the result of an assert on the host side and not in the NWP).

    You can check the trigger if you put a breakpoint in the SimpleLinkFatalErrorEventHandler and check the call stack for the failed assertion condition. 

    br,

    Kobi 

  • 0 in reply to Kobi Leibovitch
    Intellectual 265 points

    Hi Kobi,

    I can confirm that the occurrence of fatal error event is not related to the response to NetAppRequestEvent because I am getting the error even when I just try to connect to the device in AP mode.

    The call stack seems to show that the error arises from sl_Task.

    sl_Task -> _SlInternalSpawnTaskEntry -> _SlInternalSpawnWaitforEvent ->_SlDrvMsgReadSpawn -> _SlDrvMsgRead -> _SlDrvHandleFatalError -> SimpleLinkFatalErrorEventHandler

    I am unable to attach the picture here.

  • 0 in reply to SN
    TI__Guru 63006 points

    This may indicate on some porting issue in regards to your driver.

    What is your host MCU?

    Can you check the exact point of failure in _SlDrvMsgRead?