Studio Bluetooth Forum Discussions

wiced_hal_puart_set_baudrate() is the only one api as am aware is available to config the PUART communication interface. Is there a way to configure the PUART to support customized baud rate and also even parity with stop bits.

We have a requirement where we need to store a specific set of data in a controller NVM, And more importantly this data should not be get erased while reloading/reprogramming CYW20719 controller.

Looked into wiced_hal_write_nvram()  and wiced_hal_read_nvram() methods but data written using these api's gets erased when we reprogram/reload the firmware into CYW20719 controller. 

IS there any other approach to store data in the CYW20719.

Hi,

I am using cypress ble dongle on Windows with C# API.

I want to use this dongle on Ubuntu, Will it support on Ubuntu? if yes can you please provide api documents to integrate this in our application.

I directly compile the WICED6.2 "MeshAPP" source code.There was an error when "build APK" was prompted. The attachment is the LOG information. Please help to check it

After I program my application, I want to disable HCI UART because I don't have any debug traces to print.  What should be the line state for CTS?  If it is low, the app cannot run after reset because I assume it will be in recovery mode.  If I leave it high, the app will run for maybe 10s then stop.  Is the app trying to access the HCI UART?  What code changes should I make in the app to disable HCI UART?  I tried not calling wiced_transport_init() but it doesn't work.  I am using the 20719 Q40EVB but the HCI UART is connected to my own test circuit and not the FTDI output.

Hi All,

I'm trying to make an RTOS application run, with a single thread. Here is snippet of my code

#include "wiced_rtos.h"

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

*                                Constants

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

#define THREAD_PRIORITY 10

#define THREAD_STACK_SIZE 1024

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

*                          Function Definitions

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

void ledThread(uint32_t arg)

{

   while(1)

    {

        WICED_BT_TRACE("**** welcome aboard buddy **** \n\r");

        wiced_rtos_delay_microseconds(5 * 1000);

    }

}

*

*  Entry point to the application. Set device configuration and start BT

*  stack initialization.  The actual application initialization will happen

*  when stack reports that BT device is ready.

*/

APPLICATION_START()

{

    wiced_result_t err;

    wiced_set_debug_uart(WICED_ROUTE_DEBUG_TO_PUART);

    wiced_thread_t* p_thread;

    p_thread = wiced_rtos_create_thread();

    err = wiced_rtos_init_thread(p_thread,THREAD_PRIORITY,NULL,ledThread,THREAD_STACK_SIZE, NULL);

    WICED_BT_TRACE("**** Thread has been created %d **** \n\r",err);

}

Function wiced_rtos_init_thread() returns err = 15, which indicates some kinda Thread error. I'm not being able to figure it out, what's wrong.

I am starting BLE scan by calling wiced_bt_ble_scan(BTM_BLE_SCAN_TYPE_HIGH_DUTY, TRUE, newAdvCallback) to enable duplicate filtering.  I am seeing wrong advertisement data being reported.  This is the trace of advertisement callbacks logging device address:

19:48:27.230 1 adv=b8 78 2e 39 fb a1

19:48:27.233 1 adv=b8 78 2e 39 fb a1

19:48:27.267 1 adv=6e 66 87 a5 77 e3

19:48:27.270 1 adv=6e 66 87 a5 77 e3

19:48:27.515 1 adv=50 99 e4 84 62 bb

19:48:27.517 1 adv=50 99 e4 84 62 bb

19:48:27.520 1 adv=7e 70 76 4c 41 a1

19:48:27.523 1 adv=7e 70 76 4c 41 a1

19:48:27.825 1 adv=58 3c df 89 c2 a0

19:48:27.826 1 adv=58 3c df 89 c2 a0

19:48:29.308 1 adv=c2 35 dd 81 0b a9

19:48:29.310 1 adv=c2 35 dd 81 0b a9

19:48:32.189 1 adv=5b 2b a2 b2 ae 75 //advertisement

19:48:33.088 1 adv=cb 97 74 54 b6 89

19:48:33.097 1 adv=cb 97 74 54 b6 89

19:48:33.273 1 adv=5b 2b a2 b2 ae 75 //scan response - error in data

In normal situations, I get 2 callbacks back-to-back from the same device, the first for the advertisement and the second for the scan response.  In cases where the advertisement is received but the immediate scan response is lost, I see wrong data reported in the callback when the scan response is received later.  This case happens for the device 5b 2b a2 b2 ae 75.  When I receive the scan response callback for 5b 2b a2 b2 ae 75, the data is from the previous scan response callback corresponding to the device cb 97 74 54 b6 89.  Can someone confirm this problem and how to work around it?  Thanks.

How can I configure the BLE transmit power for connection?  I only see wiced_bt_dev_set_tx_power() for 20706.  If I can't configure the power, what is it set to?  Also, what is the default advertisement transmit power?  I tried calling wiced_bt_ble_read_adv_tx_power() but the returned value is always the same even after I called wiced_bt_ble_set_adv_tx_power() with different values.  What is the data format for the wiced_bt_ble_read_adv_tx_power() callback?  The only documentation is:

/**

* Asynchronous operation complete callback.

*

* @param p_data            : Operation dependent data

*

* @return Nothing

*/

typedef void (wiced_bt_dev_cmpl_cback_t) (void *p_data);

Is p_data INT8 or INT8 * or something else?

Hello,

I am working on a software design which requires a BLE + BT module to communicate with the host controller. I have narrowed down a few modules and one of them is CYW20706 meets our requirements.

But I have few questions,

1) Does the chip support Host interface over Standard HCI Protocol?

2) If yes, which transport layer it uses, UART or SPI?

3) If I use SPI for Host interface, Do I have to write my own proprietary protocol on both MCU and BLE Module side?

I am aware that the SDK provides WICED HCI support over UART. But I guess it's not the standard HCI, correct me I am wrong.

I am hoping to get these answers as soon as possible because I have to finalize the design soon.