Studio Bluetooth Forum Discussions

Hi.

I used WICED-Studio-6.2.0 in our products.

I'd like to know about a solution of the following problem.

Bluetooth Expedited Errata Correction 11838: Encryption Key Size Updates

Thank you & Best regard.

yuji,

Hi

Customer confirmed BT profiles(QDID: 99198) for this module.

Launch Studio - Listing Details

Qusetion:

Is this module not compatible with audio profiles such as A2DP, AVRCP and HFP?

Thanks

JY

I am using random addressing (RPA) in my BLE application on a CYW20719. In a situation where there are two or more of my devices within range of a central (e.g. CySmart v1.3 with CY5677), I have no way of determining which advertised address belongs to which device. The advertised data only includes a device name which is the same for all devices.

Is there an API call that will let me get the local random address (RPA) that is/will be advertised by my application so I can display this to the user and identify the device? The wiced_bt_dev_read_local_addr() only provides the local identity address which is not what is presented in the scan results. I could append a unique identifier like a serial number to the advertised device name but it seems that this would defeat the purpose of using random addressing.

Hi:

   when I use the floating point calculation in the wiced studio,and there are some compile errors as below.

Unknown symbol  __aeabi_ui2d (err 0)

Unknown symbol  __aeabi_dcmplt (err 0)

Unknown symbol  __aeabi_ddiv (err 0)

Unknown symbol  __aeabi_dmul (err 0)

Unknown symbol  __aeabi_dadd (err 0)

Unknown symbol  __aeabi_dcmpgt (err 0)

Unknown symbol  __aeabi_dsub (err 0)

Unknown symbol __aeabi_i2d (err 0)

Unknown symbol  __aeabi_d2uiz (err 0)

Unknown symbol  __aeabi_d2iz (err 0)

I guess the reason is that the current  the configuration of the  wiced studio  can't  support the floating point calculation.

who can tell me how to configue the  wiced studio to support the floating point calculation.

thanks!

mandy

Hello Guys

I am using Ubuntu 18.04 and Wiced Studio.

I am getting this message

Detecting device...

********* Detection Failure *************

+------------------------------------------------------------------------------------------+

| The CYW20706 was not detected. Verify that the device is connected, power-cycle if       |

| necessary, and retry.                                                                    |

| Please see Appendix sections in the Kit Guide for common com port problems.              |

+------------------------------------------------------------------------------------------+

I have seen an old post which says you have to perform some steps for device detection in Linux mentioned in Appendix C.

In the users guide there is no appendix C.

Any help will be appreciated

Br

Anuj

Hi :

  I can't find any API about  short delay in the wiced studio, for example 1 us delay, 1 ms delay.

I want to know if the wiced studio sdk has provided the short delay API, how can I create some short delay functions if there is no short delay API in the SDK!

thanks!

mandy

1. Can I get the schematics of CYBT-413034-EVAL.

2. By default WICED Studio uses which level of optimization for compilation of project code. How can I change the level of optimization and include -Wall compiler flag.

3. If I develop my own board using CYBT-413034, how to program it in the hardware, in the sense I have bare HCI UART pins coming out. Please explain the procedure in the sense which file to program (hex/bin/elf).

4. I have a requirement for least range between two BLE devices. What is the least range BLE device available with your company.

5. I have a difficulty in understanding /20719-B1_Bluetooth/apps/demo/watch. Can I get a technical support help to understand the code.

Regards,

Ameet Kumar Haware

Dear Sir,

How to get the result whether the wiced_hal_puart_synchronous_write(UINT8* buffer,UINT32 length) finished or not ? Is there any method ?

How to get 20706 PUART TX FIFO in new SDK ? There is no API for PUART TX FIFO in the new SDK.

Best Regards,

Cloud Chen.

WICED 6.2.1 stalls after certain errors and the only way found so far to pass by is to restart it

At the bottom right corner shows Building Targets: (0%) and the green indicator rolls forever

...

Compiling btn12w.c

../apps/w191/bsc01/bcsc_main.c:31:1: error: unknown type name 'modes_t'; use 'enum' keyword to refer to the type

modes_t mode = MODE_NOTINIT;  // global var

^~~~~~~

enum

make.exe[1]: *** [../build/bsc01-CYBT_413034_EVAL-rom-ram-Wiced-release/bcsc_main.o] Error 1

makefile:432: recipe for target '../build/bsc01-CYBT_413034_EVAL-rom-ram-Wiced-release/bcsc_main.o' failed

make.exe[1]: *** Waiting for unfinished jobs....