Wi-Fi Combo Forum Discussions

Broadcom WICED Software Development Kit 3.1.0 BETA1

This is the non-HomeKit version.

Those with MFI Account numbers on file will get a separate invite to the HomeKit Version.

The documentation in rtos.h defined for ThreadX says the Networking worker thread  has a lower priority than that of the Hardware IO thread. However, when I look at wiced_defaults.h the priorities are flipped. Is there is a reason there is an inconsistency ? The documentation talks about allowing IO to preempt network activity on the network thread which may take longer or block.

I have created a new application folder with a make file in the Apps folder. This is what my make file looks like

NAME := App_Ly05

$(NAME)_SOURCES := ly05.c \

    Tests/SimpleTestClient.c \

    nanopb/pb_encode.c \

    nanopb/pb_decode.c \

    nanopb/Messages.pb.c

$(NAME)_COMPONENTS := inputs/gpio_keypad

WIFI_CONFIG_DCT_H := wifi_config_dct.h

I want to add folders to the include search folders? How can I do this. I tried doing

CFLAG += -I<Path>

but that didn't really work. Any help will be appreciated.

Thanks

Kartik    

ACKme joins AT&T at the Cosmopolitan Hotel in Las Vegas during Super Mobility Week September 6-7 in Las Vegas.

Hackathon enthusiasts are back at it again in Las Vegas and this time at the upscale Cosmopolitan of Las Vegas' Chelsea Theater!

The focus for this hackathon is on connected car and home with numerous prizes for subcategories as well.  We are bringing together the best companies, tools, and services for developers to innovate in the connected car and automated home marketplace.

AT&T Hackathon Fast Facts

What:

• 24-hour Hackathon & developer prize packages
• Developers meet and consult with high profile mentors
• Finalists judged by well-known industry leaders at  VIP party
• On-site entertainment, networking & fun

When:

• September 6-7: (Hackathon, App Presentations, Judging)
• Sept. 8: Finalist Judging,  Awards & VIP Party

Where:

• Chelsea Theater - Cosmopolitan Hotel  - Las Vegas

Why:

• Promote  innovative thinking around apps and services to mobilize life at home and in the car

Fast Links

http://ack.me/

WiConnect by ACKme | WiConnect Reference Guide

ACKme | mbed

WiConnect - a mercurial repository | mbed

I am trying to have my module disconnect from an AP, but the system hangs whenever I try.  The line that actually causes the system to hang is: wwd_management_set_event_handler(link_events, NULL, 0, WICED_STA_INTERFACE);

I have not been able to reproduce the problem outside of my project (which is large and uses several thread).

Any ideas? Or are there other ways to bring down wifi?

Test on 3.0.1 sdk with FreeRTOS+LwIP build.

I hit some issues about wiced_rtos_create_thread:

I thought if a thread is terminated, I can create a new one.

A simple test shows wiced_rtos_create_thread() will fail after a few iteration.

static wiced_thread_t       my_thread[20];

static void test_thread_main(uint32_t arg)

{

        WPRINT_APP_INFO(( "Thread #%d begin\n", arg ));

        wiced_rtos_delay_milliseconds(1000);

        WPRINT_APP_INFO(( "Thread #%d end\n", arg ));

        WICED_END_OF_CURRENT_THREAD();

}

void application_start(void)

{

  // do basic init ....

        for (i =0;i< 20; i++) {

                wiced_result_t status = wiced_rtos_create_thread(&my_thread, WICED_DEFAULT_LIBRARY_PRIORITY, "test thread",

                                                                 test_thread_main, 5000, i);

                if (status != WICED_SUCCESS)

                        WPRINT_APP_INFO(( "create thread fail, status=%u\n", status ));

                wiced_rtos_delay_milliseconds(1000);

        }

}

Then I got below result:

Thread #0 begin

Thread #0 end

Thread #1 begin

Thread #1 end

Thread #2 begin

Thread #2 end

Thread #3 begin

Thread #3 end

Thread #4 begin

Thread #4 end

Thread #5 begin

Thread #5 end

Thread #6 begin

Thread #6 end

Thread #7 begin

Thread #7 end

Thread #8 begin

Thread #8 end

Thread #9 begin

Thread #9 end

Thread #10 begin

Thread #10 end

Thread #11 begin

Thread #11 end

Thread #12 begin

Thread #12 end

create thread fail, status=1031

create thread fail, status=1031

create thread fail, status=1031

create thread fail, status=1031

create thread fail, status=1031

create thread fail, status=1031

create thread fail, status=1031

...

So, why wiced_rtos_create_thread() fails after 12 iterations?

I thought each thread is terminated then it should be ok to create a new one.

If I remove WICED_END_OF_CURRENT_THREAD(), system hangs after thread #1 end.

What is the proper way to terminate a thread?

Any limitation about the number of thread can be created? Is this limitation configurable?

Thanks.

Farnell & Element14 sponsored an online webinar specifically to introduce goHACK.me, the free online IoT cloud solution for developers using ACKme modules.

Watch the event replay below:

What is goHACK.me?