Wi-Fi Combo Forum Discussions

Hi,

I still can hit below issue sometimes on SDK-3.7.0-7.

Basically, the device is useless after this issue happened.

If there is still no fix available for now, how can I detect this issue?

I'd like to make the device reboot if this issue happened.

Any callback or notification I can know this issue happened?

Below is the message for reference:

[15:15:28:663] 00:01:09.010928 GKI_create_task func=0x803f5e5  id=1  name=BTU  stack=0x0  stackSize=6144␍␍␊

[15:15:28:669] 00:01:09.018928 GKI_create_task func=0x8040b05  id=0  name=HCISU  stack=0x0  stackSize=4096␍␍␊

[15:15:28:776] 00:01:09.062392 GKI_exception(): Task State Table␍␍␊

[15:15:28:781] 00:01:09.000856 GKI_exception 65527 getbuf: Size is too big␍␍␊

[15:15:28:799] 00:01:09.007856 GKI_exception(): Task State Table␍␍␊

[15:15:28:799] 00:01:09.011856 GKI_exception 65535 Send - Buffer corrupted␍␍␊

[15:15:32:776] 00:01:13.062392 GKI_exception(): Task State Table␍␍␊

[15:15:32:781] 00:01:13.000856 GKI_exception 65527 getbuf: Size is too big␍␍␊

[15:15:32:789] 00:01:13.006856 GKI_exception(): Task State Table␍␍␊

[15:15:32:795] 00:01:13.010856 GKI_exception 65535 Send - Buffer corrupted␍␍␊

[15:15:36:775] 00:01:17.062392 GKI_exception(): Task State Table␍␍␊

[15:15:36:782] 00:01:17.000856 GKI_exception 65527 getbuf: Size is too big␍␍␊

[15:15:36:791] 00:01:17.006856 GKI_exception(): Task State Table␍␍␊

[15:15:36:791] 00:01:17.010856 GKI_exception 65535 Send - Buffer corrupted␍␍␊

[15:15:40:775] 00:01:21.062392 GKI_exception(): Task State Table␍␍␊

[15:15:40:779] 00:01:21.000856 GKI_exception 65527 getbuf: Size is too big␍␍␊

[15:15:40:792] 00:01:21.006856 GKI_exception(): Task State Table␍␍␊

[15:15:40:792] 00:01:21.010856 GKI_exception 65535 Send - Buffer corrupted␍␍␊

[15:15:44:774] 00:01:25.062392 GKI_exception(): Task State Table␍␍␊

[15:15:44:779] 00:01:25.000856 GKI_exception 65527 getbuf: Size is too big␍␍␊

[15:15:44:788] 00:01:25.006856 GKI_exception(): Task State Table␍␍␊

.....

Hi all：

I am trying to reconnect after MQTT disconnected.After several times successful reconnection and I can't reconnect any more. So I print the "_eheap-sbrk_heap_top " to check to RAM size I left everytime I make reconnection . I found it will reduce about 8-12K ram every time I reconnect success. So that may expand how my situation appear . I think it should be the problem of  “Recycling resources” part .I hope the team can explain that.

here is my mqtt connect function.

/*
 * Open a connection and wait for MQTT_REQUEST_TIMEOUT period to receive a connection open OK event
 */
wiced_result_t aws_mqtt_conn_open( wiced_mqtt_object_t mqtt_obj, wiced_mqtt_callback_t callback )
{
    wiced_result_t            ret = WICED_SUCCESS;
    wiced_interface_t         interface = WICED_STA_INTERFACE;
    do {
    wiced_hostname_lookup( aws_app_info->region, &broker_address, 10000 );
    wiced_rtos_delay_milliseconds( 100 );
    }
    while(GET_IPV4_ADDRESS(broker_address)==0);
  WPRINT_APP_INFO(("[MQTT] Connecting to broker %u.%u.%u.%u ...\n\n", (uint8_t)(GET_IPV4_ADDRESS(broker_address) >> 24),
  (uint8_t)(GET_IPV4_ADDRESS(broker_address) >> 16),
  (uint8_t)(GET_IPV4_ADDRESS(broker_address) >> 8),
  (uint8_t)(GET_IPV4_ADDRESS(broker_address) >> 0)));
    wiced_mqtt_init( aws_app_info->mqtt_object );
    WPRINT_APP_INFO(("[MQTT] Connecting to MQTT Broker...\n"));
    ret = wiced_mqtt_connect( mqtt_obj, &broker_address, interface, callback, &security, &conninfo );
    if ( ret != WICED_SUCCESS )
    {
        WPRINT_APP_ERROR(("[MQTT] Failed to connect MQTT Broker\n"));
        ret = WICED_ERROR;
        goto _AWS_MQTT_CONN_OPEN_END;
    }
    if ( mqtt_wait_for( WICED_MQTT_EVENT_TYPE_CONNECT_REQ_STATUS, MQTT_REQUEST_TIMEOUT ) != WICED_SUCCESS )
    {
        WPRINT_APP_ERROR(("[MQTT] Failed to connect MQTT Broker\n"));
        ret = WICED_ERROR;
        goto _AWS_MQTT_CONN_OPEN_END;
    }
    WPRINT_APP_INFO(("[MQTT] Successfully connected MQTT Broker\n"));
_AWS_MQTT_CONN_OPEN_END:
    return ret;
}

do
  {
  ret = aws_mqtt_conn_open( app_info.mqtt_object, mqtt_connection_event_cb );
  connection_retries++ ;
  host_rtos_delay_milliseconds( 1000 );
  } while ( ( ret != WICED_SUCCESS ) && ( connection_retries < WICED_MQTT_CONNECTION_NUMBER_OF_RETRIES ) );

Hello,

I have modified snip.uart example like below.  Basically I want to UART receive with timeout and check the number of incoming bytes.  I have 2 questions

1)  UART RECEIVE does not work when I set the timeout anything other than WICED_NEVER_TIMOUT

2)  When timeout is set to WICED_NEVER_TIMEOUT, expected Data Size always return as 0

can you please tell me what I am missing?

void application_start( )

{

    char c[8];

    uint32_t expected_data_size = 2;

    wiced_gpio_init(USER_LED, OUTPUT_PUSH_PULL);

    /* Initialise ring buffer */

    ring_buffer_init(&rx_buffer, rx_data, RX_BUFFER_SIZE );

    /* Initialise UART. A ring buffer is used to hold received characters */

    //wiced_uart_init( STDIO_UART, &uart_config, &rx_buffer );

    wiced_uart_init( STDIO_UART, &uart_config, NULL );

    /* Send a test string to the terminal */

    wiced_uart_transmit_bytes( STDIO_UART, TEST_STR, sizeof( TEST_STR ) - 1 );

    /* Wait for user input. If received, echo it back to the terminal */

    //while ( wiced_uart_receive_bytes( STDIO_UART, &c, &expected_data_size, WICED_NEVER_TIMEOUT ) == WICED_SUCCESS )

    while ( wiced_uart_receive_bytes( STDIO_UART, c, &expected_data_size, 10) == WICED_SUCCESS )

    {

        snprintf(c,3,"%x\n",expected_data_size);

        wiced_uart_transmit_bytes( STDIO_UART, c, 8 );

        expected_data_size = 2;

        memset(c, 0, 8);

    }

}