Studio Bluetooth Forum Discussions

  Currently, I use something like this: WPRINT_APP_INFO( ( "wiced_bt_ble_set_advertisement_data %d\n", result ) );

that would output the following to the terminal: "wiced_bt_ble_set_advertisement_data 0"

Then I have to figure out what the value 0 represents in the enum where it's declared.

Is there a function that could convert the numerical value back to the string its equal to?

I would like to see something like this: "wiced_bt_ble_set_advertisement_data WICED_SUCCESS"

Hi,

We are looking for vendor specific command to set min and max encryption key size for CYW20704A2. Can some one help

Regards

Santhosh AJ

I am working on an Android product and I'm porting some test code from using the Android hal layer to using just Linux. I have the bcmbtusb driver and BlueZ built, but I can't see any USB controllers in hcitool or the Bluetooth daemon.

I saw that in Android there is some hal code which contains functions to initialize the Bluetooth device (a BCM20704), including uploading the firmware, and I can see it being called during the Android boot.

I'm looking for some help in doing the same thing but under raw Linux rather than Android.

Hello Cypress IoT team.

[Environment]

- WICED Studio version: 6.4

- Compiler:                      MinGW-w64

- Target OS:                    Windows 10

[Background]

To optimize MBT tool for our environment, we would like to build mbt.cpp in the following directory.

  WICED-Studio-6.4\wiced_tools\mbt\mbt.cpp

However, I encountered some errors when building.

== Error Log ==

$g++ -o mbt.exe mbt_com.cpp mbt_usb.cpp mbt.cpp

mbt_com.cpp:17:46: warning: ISO C++ forbids converting a string constant to 'char*' [-Wwrite-strings]

static char* _stopBits[] = { "1", "1.5", "2" };

                                              ^

mbt_com.cpp:17:46: warning: ISO C++ forbids converting a string constant to 'char*' [-Wwrite-strings]

mbt_com.cpp:17:46: warning: ISO C++ forbids converting a string constant to 'char*' [-Wwrite-strings]

mbt_com.cpp: In destructor 'virtual ComHelper::~ComHelper()':

mbt_com.cpp:80:39: error: no matching function for call to 'ComHelper::~ComHelper()'

     TransportHelper::~TransportHelper();

                                       ^

In file included from mbt_com.h:13,

                 from mbt_com.cpp:14:

mbt.h:17:13: note: candidate: 'virtual TransportHelper::~TransportHelper()'

     virtual ~TransportHelper() {};

             ^

mbt.h:17:13: note:   candidate expects 1 argument, 0 provided

mbt_com.cpp: In member function 'virtual BOOL ComHelper::OpenPort(char*)':

mbt_com.cpp:126:84: error: cast from 'HANDLE' {aka 'void*'} to 'DWORD' {aka 'long unsigned int'} loses precision [-fpermissive]

         Logger.DebugOut("OpenPort Overlap Event Handle=%x\n", (DWORD)m_OverlapRead.hEvent);

                                                                                    ^~~~~~

mbt_com.cpp:128:85: error: cast from 'HANDLE' {aka 'void*'} to 'DWORD' {aka 'long unsigned int'} loses precision [-fpermissive]

         Logger.DebugOut("OpenPort Overlap Event Handle=%x\n", (DWORD)m_OverlapWrite.hEvent);

                                                                                     ^~~~~~

mbt.cpp: In function 'int execute_connectionless_dut_loopback_mode(char*)':

mbt.cpp:832:9: error: 'scanf_s' was not declared in this scope

         scanf_s("%x",&bd);

         ^~~~~~~

mbt.cpp:832:9: note: suggested alternative: 'sscanf_s'

         scanf_s("%x",&bd);

         ^~~~~~~

         sscanf_s

mbt.cpp:840:5: error: 'scanf_s' was not declared in this scope

     scanf_s("%x", &lt_addr);

     ^~~~~~~

mbt.cpp:840:5: note: suggested alternative: 'sscanf_s'

     scanf_s("%x", &lt_addr);

     ^~~~~~~

     sscanf_s

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

[Need Help]

Could you tell us the cypress reference way to build MBT?

Thanks,

Yoshinori

Hello,

CYBT-333047-02 has obtained FCC / ISED / MIC / CE regulatory certification.

RF Regulatory Certifications for CYBT-333032-02/CYBT-333047-02 EZ-BT™ XR Module - KBA225653

And the qualified Antenna for CYBT-3330xx-02 are:

Q1.

Do I need to get regulatory certification again if I use something other than this antenna?

Please tell me in each of the following cases.

* I also refer to the following, but I would like to confirm each regulation.

FAQ for BLE and Regulatory Certifications with EZ-BLE modules - KBA213976

  Case-1) Dipole antenna of 2.2 dBi or less or the same value

                - FCC : yes or no ?

                - ISED : yes or no ?

                - MIC : yes or no ?

                - CE : yes or no ?

  Case-2) 2.2dBi or more dipole antenna

                - FCC : yes or no ?

                - ISED : yes or no ?

                - MIC : yes or no ?

                - CE : yes or no ?

  Case-3) Antenna of a different type from dipole

                - FCC : yes or no ?

                - ISED : yes or no ?

                - MIC : yes or no ?

                - CE : yes or no ?

Q2.

If you need to obtain regulatory certification again, you will need the following data.

Can you provide it?

The information contained in the data sheet is insufficient and the image is not clear.

- Block Diagram

- Schematic

- BOM list

Best reagrds,

Takahashi

Hi,

I used wiced_bt_create_pool() to create a pool in

static wiced_bt_buffer_pool_t *pbuffer_pool;

void hello_sensor_application_init( void )

{

...

    pbuffer_pool = wiced_bt_create_pool(512, 1);

    if(pbuffer_pool==NULL)

    {

        WICED_BT_TRACE( "wiced_bt_create_pool failed!\r\n" );

    }

    else

    {

        WICED_BT_TRACE( "wiced_bt_create_pool success!\r\n" );

    }

...

}

Output

wiced_bt_create_pool failed!

What's wrong with wiced_bt_create_pool()?

Best regards!

I was looking for any requirements or recommendations about the proper power-up sequencing for the CYW20179 (QFN Package).

In the Device Data Sheet I see a requirement that VDDO should be up and stable for a minimum of 35ms before releasing Reset, but is there any recommendation or requirement with regard to sequencing of SR_VDDBAT3V and VDDO?

Cannot bring CYBT-413034-02 dual-BT device up:

Command:

hciconfig

Output:

hci1:   Type: Primary  Bus: UART
        BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
        DOWN
        RX bytes:0 acl:0 sco:0 events:0 errors:0
        TX bytes:12 acl:0 sco:0 commands:3 errors:0

Trying to bring device up:

hciconfig hci1 up

Output:

Can't init device hci1: Connection timed out (110)

Devices where attached:

ls -l /dev/ttyA*
crw-rw----    1 root     dialout   166,   0 Dec  8 20:28 /dev/ttyACM0
crw-rw----    1 root     dialout   166,   1 Dec  8 20:28 /dev/ttyACM1

With btattach:

btattach -B /dev/ttyACM0 -S 115200 -P h4 &

btattach -B /dev/ttyACM1 -S 115200 -P h4 &

Any help will be appreciated, Thanks.

Failed to add link_keys database in wiced_bt_dev_add_device_to_address_resolution_db.

The return value is "8042: ILLEGAL_ACTION".

[QA]

1. Please tell me the contents of the error value of "8042: ILLEGAL_ACTION".

2. Please let me know if you know how to handle "8042: ILLEGAL_ACTION" error.

【procedure】

1. Perform pairing with BLE peripheral. (Save link_keys data in DCT_APP_SECTION)

2. Exit program

3. Start the program (Read link_keys data in DCT_APP_SECTION)

4. Database registration by wiced_bt_dev_add_device_to_address_resolution_db at the timing of "BTM_ENABLED_EVT" of Management Callback

5. “8042: ILLEGAL_ACTION” is returned.

[Related QA]

About saving bonding information

https://community.cypress.com/thread/51417?start=0&tstart=0

>> Pairing processing is implemented by QA.

regards.

<Japanese>

"wiced_bt_dev_add_device_to_address_resolution_db" APIのデータベース追加に失敗する

wiced_bt_dev_add_device_to_address_resolution_dbのlink_keysのデータベース追加に失敗します。

リターン値は、「8042：ILLEGAL_ACTION」になります。

【QA】

１．「8042：ILLEGAL_ACTION」のエラー値の内容を教えてください。

２．「8042：ILLEGAL_ACTION」のエラーの対象方法がわかりましたら、教えてください。

【手順】

１．BLE ペリフェラルによるペアリングを実行。（DCT_APP_SECTIONに、link_keysのデータを保存）

２．プログラムを終了

３．プログラムを開始（DCT_APP_SECTIONに、link_keysのデータを読み込み）

４．Management Callbackの「BTM_ENABLED_EVT」のタイミングで、wiced_bt_dev_add_device_to_address_resolution_dbによるデータベース登録

５．「8042：ILLEGAL_ACTION」がリターンされる。

【関連するQA】

About saving bonding information

https://community.cypress.com/thread/51417?start=0&tstart=0

＞＞ペアリング処理は、QAによる実装を行っている。

よろしくお願いいたします。