Wi-Fi Combo Forum Discussions

I'm guessing I need a udev rule to get the serial port to show up.  Anyone able to do this?  I've tried on both Ubuntu 15.1 and Linux Mint 17.  Not USB ports show up in /dev

Here is the output from lsusb.  This is from Linux Mint 17.  The output from Ubuntu only include the first Broadcom device, not the second secure processor.

Bus 002 Device 005: ID 0a5c:43fa Broadcom Corp.

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 003 Device 101: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card

Bus 003 Device 093: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick

Bus 003 Device 092: ID 413c:8157 Dell Computer Corp. Integrated Keyboard

Bus 003 Device 091: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Hi,

I'm trying to add BLE functionality to the the demo/aws_iot/shadow app.  The issue I'm seeing is once I enable the BT stack, the Wi-Fi side of things stops working.  In fact, the BT side doesn't work either outside of successfully broadcasting ADVs.  I'm targeting the BCM4343W_AVN platform.

Note that I'm able to work with the BLE-standalone snips that don't use Wi-Fi such as ble_proximity_reporter.  They behave as expected.

Question:  When enabling both BT and Wi-FI, what's the appropriate procedure for doing this?  What order do I need to call the enabling APIs (ie, wiced_bt_stack_init(), wiced_network_up(), etc) and when do I call them?  Are there any rules I need to follow in terms of allowing time for the stacks to initialize?

Hello,

I have a problem with the source code bellow in SDK 3.4.0. When UART 2 receives a data of 1 byte, the thread calling never stops. I do not if the problem comes from the RTOS or UART lib. However, this source code is working fine in SDK 3.1.2.

Thank you for your help

void application_start(void)
{
    wiced_init( );
    ring_buffer_init(&rx_buffer, rx_data, RX_BUFFER_SIZE );
    wiced_uart_init( WICED_UART_2, &uart_config, &rx_buffer );


    wiced_rtos_create_thread( &uart_thread, WICED_DEFAULT_WORKER_PRIORITY, "UART_RX", uart_thread_main, UART_THREAD_STACKSIZE, NULL );


}


void uart_thread_main()
{


  char read_data;
  uint32_t expected_data_size = 1;


  while ( wiced_uart_receive_bytes( WICED_UART_2, &read_data, &expected_data_size, WICED_NEVER_TIMEOUT ) == WICED_SUCCESS )
  {
  WPRINT_APP_INFO( ( "Thread called. Data : %c", read_data ) );
  }


    WICED_END_OF_CURRENT_THREAD( );
}

Hi,

I am currently using WICED over SN8205.

How to perform OTA without external flash?

Consider that if we can rearrange the Internal Flash to have Bootloader/DCT/OTA-App/APP0.

On OTA trigger, the APP0 will reboot and boot to OTA-App.

The OTA-App can then reflash the APP0.

This implementation would not require the use of External Flash and as the Bootloader/DCT/OTA-App together is small, there should not be any size concern for APP0.

Can this be implemented?

Regards,

Karthik

Hello,

I am using SDK 3.3.1, my application size is 770kb. my flash size is 1MB. so only way i can do OTA upgrades is through external flash, can anybody please tell me how can achieve OTA using SPI serial flash?

Thanks,

Raghu