Wi-Fi Combo Forum Discussions

Hi

I tried starting the bt_dualmode_server from WICED SDK 3.5.2 on a BCM943341WCD1 eval board. Then I tried connecting to it using the "Wiced SMART Find Me" app from Google Play. I can discover the "WICED DUAL MODE" device but it doesn't connect correctly. The GATT connection reports my phone having bd_addr 00:00:00:00:00:00. Also, the bd_addr shown in the app is different every time I restart the board and is not at all similar to the address reported by the log. The log is below.

Then I tried the ble_proximity_reporter example and that is working better, but the address of my phone reported by the GATT connction is also different every time. And if I connect and set the app to alarm when I lose connection, it simply doesn't. This log is also below.

I guess there could be more problems lurking here, the one I'm most interested in is to get BLE working in dualmode and to see the correct bd_addr reported.

Thanks!

Magnus

bt_dualmode_server

================

WICED DCT BT NAME: WICED DUAL MODE

WICED DCT BT DEVICE CLASS : 20 04 1c

00000007 GKI_create_task func=0x801dd91  id=1  name=BTU  stack=0x0  stackSize=6144

00000014 GKI_create_task func=0x8024451  id=0  name=HCISU  stack=0x0  stackSize=4096

Bluetooth Management Event: 0x15

Bluetooth Management Event: 0x0

Bluetooth enabled (success)

Local Bluetooth Address: [43:34:1B:00:1F:AC]

WICED DCT BT ADDR 0x11:0x22:0x33:0xaa:0xbb:0xcc

Bluetooth Management Event: 0x17

---->>> New ADV state: 3

Waiting for proximity monitor to connect...

Waiting for RFCOMM connection (scn=1)...

Bluetooth Management Event: 0x14

Bluetooth Management Event: 0x14

GATT connection to [00:00:00:00:00:00] established.

Bluetooth Management Event: 0x17

---->>> New ADV state: 0

Local TX power: 4

GATT connection to [00:00:00:00:00:00] released.

Bluetooth Management Event: 0x17

---->>> New ADV state: 3

Waiting for proximity monitor to connect...

Bluetooth Management Event: 0x17

---->>> New ADV state: 4

Bluetooth Management Event: 0x17

---->>> New ADV state: 0

ble_proximity_reporter

=================

Starting WICED v3.5.2

Platform BCM943341WCD1 initialised

Started ThreadX v5.6

Initialising NetX_Duo v5.7_sp2

Creating Packet pools

WWD SDIO interface initialised

WLAN MAC Address : 6C:AD:F8:F0:E9:37

WLAN Firmware    : wl0: Nov 25 2015 14:01:39 version 6.49.2 (r602357) FWID 01-1302682f

00000360 GKI_create_task func=0x8022115  id=1  name=BTU  stack=0x0  stackSize=6144

00000367 GKI_create_task func=0x80235b5  id=0  name=HCISU  stack=0x0  stackSize=4096

Unhandled Bluetooth Management Event: 0x15

Bluetooth enabled (success)

Local Bluetooth Address: [43:34:1B:00:1F:AC]

---->>> New ADV state: 3

Waiting for proximity monitor to connect...

Unhandled Bluetooth Management Event: 0x14

Unhandled Bluetooth Management Event: 0x14

GATT connection to [56:B0:CB:05:B7:27] established.

---->>> New ADV state: 0

Local TX power: 4

---->>> New ADV state: 0

GATT connection to [56:B0:CB:05:B7:27] released.

---->>> New ADV state: 3

Waiting for proximity monitor to connect...

---->>> New ADV state: 4

---->>> New ADV state: 0

I am working with Murata ZX module and looking for a Linux driver that will work with the bcm43362

any one?

I just wanted to know if these APIs are guaranteed thread safe by the ThreadX RTOS?

/** @} */

/*****************************************************************************/

/** @addtogroup queues       Queues

*  @ingroup rtos

*

* Queue management functionss

*

*

*  @{

*/

/*****************************************************************************/

/** Initialises a queue

*

* Initialises a FIFO queue

*

* @param queue : a pointer to the queue handle to be initialised

* @param name  : a text string name for the queue (NULL is allowed)

* @param message_size : size in bytes of objects that will be held in the queue

* @param number_of_messages : depth of the queue - i.e. max number of objects in the queue

*

* @return    WICED_SUCCESS : on success.

* @return    WICED_ERROR   : if an error occurred

*/

wiced_result_t wiced_rtos_init_queue( wiced_queue_t* queue, const char* name, uint32_t message_size, uint32_t number_of_messages );

/** Pushes an object onto a queue

*

* Pushes an object onto a queue

*

* @param queue : a pointer to the queue handle

* @param message : the object to be added to the queue. Size is assumed to be

*                  the size specified in @ref wiced_rtos_init_queue

* @param timeout_ms: the number of milliseconds to wait before returning

*

* @return    WICED_SUCCESS : on success.

* @return    WICED_ERROR   : if an error or timeout occurred

*/

wiced_result_t wiced_rtos_push_to_queue( wiced_queue_t* queue, void* message, uint32_t timeout_ms );

/** Pops an object off a queue

*

* Pops an object off a queue

*

* @param queue : a pointer to the queue handle

* @param message : pointer to a buffer that will receive the object being

*                  popped off the queue. Size is assumed to be

*                  the size specified in @ref wiced_rtos_init_queue , hence

*                  you must ensure the buffer is long enough or memory

*                  corruption will result

* @param timeout_ms: the number of milliseconds to wait before returning

*

* @return    WICED_SUCCESS : on success.

* @return    WICED_ERROR   : if an error or timeout occurred

*/

wiced_result_t wiced_rtos_pop_from_queue( wiced_queue_t* queue, void* message, uint32_t timeout_ms );

/** De-initialise a queue

*

* Deletes a queue created with @ref wiced_rtos_init_queue

*

* @param queue : a pointer to the queue handle

*

* @return    WICED_SUCCESS : on success.

* @return    WICED_ERROR   : if an error occurred

*/

wiced_result_t wiced_rtos_deinit_queue( wiced_queue_t* queue );

/** Check if a queue is empty

*

* @param queue : a pointer to the queue handle

*

* @return    WICED_SUCCESS : queue is empty.

* @return    WICED_ERROR   : queue is not empty.

*/

wiced_result_t wiced_rtos_is_queue_empty( wiced_queue_t* queue );

/** Check if a queue is full

*

* @param queue : a pointer to the queue handle

*

* @return    WICED_SUCCESS : queue is full.

* @return    WICED_ERROR   : queue is not full.

*/

wiced_result_t wiced_rtos_is_queue_full( wiced_queue_t* queue );

/** Get the queue occupancy

*

* @param queue : a pointer to the queue handle

* @param count : pointer to integer for storing occupancy count

*

* @return    WICED_SUCCESS : on success.

* @return    WICED_ERROR   : if an error occurred

*/

wiced_result_t wiced_rtos_get_queue_occupancy( wiced_queue_t* queue, uint32_t *count );

I using STM32F4 to transmit camera capture jpep

form device to server via wifi udp

I do frame transmit, and packet size is 1460, speed 400 packet / second

it's often stuck on wiced_udp_send

it's my code

while(pp->length >0){

if(pp->length>1460){

if(cam_send_data((uint8_t *)pbuff, (uint16_t)1460 )!= WICED_SUCCESS){

WPRINT_MACRO(("socket send data : send data failed\r\n"));

return WICED_ERROR;

}

pbuff=(uint8_t *)(pbuff+1460);

pp->length=(uint32_t)(pp->length-1460);

} else {

if(cam_send_data((uint8_t *)pbuff, (uint16_t)pp->length )!= WICED_SUCCESS){

WPRINT_MACRO(("socket send data : send final data failed\r\n"));

return WICED_ERROR;

}

pp->length=0;

break;

}

}

and cam_send_data is do

const wiced_ip_address_t INITIALISER_IPV4_ADDRESS( peer_ip_addr, MAKE_IPV4_ADDRESS(192, 168, 1, 35) );

memcpy(tx_data, pp, data_length);

wiced_packet_set_data_end(packet, (uint8_t*)tx_data + data_length);

if (wiced_udp_send(&udp_socket, &peer_ip_addr, peer_port, packet) != WICED_SUCCESS)

{

WPRINT_APP_INFO(("UDP packet send failed\n"));

wiced_packet_delete(packet);

return WICED_ERROR;

}

Any solution can fix this problem?

Hi,

I am using Murata Type 1Dx module, which uses Broadcom BCM4343W chipset.

I am  trying to bring-up the Bluetooth module & using WICED SDK 3.5.2

My host MCU platform is ARM Cortex M4. I am using WICED-SDK-3.5.2\apps\snip\bluetooth\ble_hello_sensor application.

I could see read/write operations happening through UART port.

On Console I see below messages

00000000 GKI_create_task func=0xfa1d  id=1  name=BTU  stack=0x0  stackSize=6144

00000000 GKI_create_task func=0x10e91  id=0  name=HCISU  stack=0x0  stackSize=4096

00096110 GKI_exception(): Task State Table

00096110 GKI_exception 65524 getbuf: out of buffers

00100110 GKI_exception(): Task State Table

00100110 GKI_exception 65524 getbuf: out of buffers

00104110 GKI_exception(): Task State Table

00104110 GKI_exception 65524 getbuf: out of buffers

00108110 GKI_exception(): Task State Table

00108110 GKI_exception 65524 getbuf: out of buffers

00112110 GKI_exception(): Task State Table

00112110 GKI_exception 65524 getbuf: out of buffers

00116110 GKI_exception(): Task State Table

00116110 GKI_exception 65524 getbuf: out of buffers

00120110 GKI_exception(): Task State Table

00120110 GKI_exception 65524 getbuf: out of buffers

00124110 GKI_exception(): Task State Table

00124110 GKI_exception 65524 getbuf: out of buffers

Program control never reaches in  bt/ble link management callback function. Whereas the "Out of buffers" message keeps on coming. I also tried increasing  buffer count in wiced_bt_cfg_buf_pools (defined in file WICED-SDK-3.5.2\apps\snip\bluetooth\ble_hello_sensor\wiced_bt_cfg.c). But this did not help.

How can I solve this "getbuf: out of buffers" issue?

It will be very helpful if someone can provide pointers on this.

Thanks & Regards,

Pratik.

I am working with an inventek ISM43362_M3G.  We have a board that keeps a supercap charged and attached to the VBAT line.

In 3.3.1, time was preserved through power cycling for a period of time (at least 20 minutes).  I updated to 3.5.2 and enabled WICED_ENBALE_MCU_RTC.

I set the RTC with  platform_rtc_set_time and read with platform_rtc_get_time in app, and it works fine, but on a momentary power cycle, it reset to 0 (Jan 2000).

Has something changed in 3.5.2 with the RTC, or am I missing something?