Smart Bluetooth Forum Discussions

I am writing firmware for the BCM20736 using the WICED tools on Windows 8.1 and I need help in understanding how to receive bytes on the "test UART" AKA HCI_UART.  The ble_trace0() function can send bytes, but how do I receive them?

I see the following functions that might be related, but can't find adequate documentation on how to use them:

A. bleprofile_regHandleUARTCb( BLEPROFILE_DOUBLE_PARAM_CB cb)

   1. Does the callback return data, the number of bytes, or only inform the application that data is ready?

B. bleprofile_ReadUART(char *data)

   1. Does this function block?

   2. Is there a way to tell how many bytes were returned?

C. Is there a lower level function than ble_trace0() for sending bytes out the test/HCI UART port?

D. Are there other functions to support this UART?

Thanks in advance,

    Aaron

Hello,

I had made some chances to an example which i wanted to reverse. The easiest thing i taught would be to reinstall the SDK and everything be back to new.

Since reinstalling, when i opened the SDK everything is empty. I have no drivers, header files, makefiles, examples etc, The application is empty.

I am guessing there is a problem with paths possibly. I deleted everything to do with wiced off my PC and un-installing the application. Re-downloaded the apllication but its still empty when i open it.

Could someone help me please?

Regards,

Luke.

mwf_mmfaej.tgangi@

Hi maxsong,

Our customer is considering to use serial flash to store user data. Could you confirm if customer is possible to use part number like attached files?

Thanks,

Sung-Mok

Hi,

I'm able to exchange raw data over L2CAP between Linux host and Beaglebone using Broadcom BCM20702 Bluetooth USB adapter.

But it stops after about 150 transactions!

I did experiment on both Linux host using L@PING from BlueZ and found out it stoped after only 44 pings!!!

So, I'm wondering if it is the limitation of Bluetooth where it expects a disconnection/reconnection for every, say 40 transactions

Thanks,

I'd like to know what does blecen_GetConn() mean, and correct disconnection sequence.

With using hello_client and hello_sensor projects, I executed below experiment.

1. Environment: WICED Smart 2.2.0 (mac). Hardware: BCM20737S
2. Preparation: download hello_client application for 1 device, and download hello_sensor application to another device.
3. Connect hello_sensor and hello_client. hello_client_connection_up() is called. In this timing, blecen_GetConn() in hello_client returns 2.
4. Power off hello_sensor device. hello_client_connection_down() is called in hello_client device. Event though connection has been lost, blecen_GetConn()  returns 2.
5. When I call blecen_GetConn() in hello_client_timeout(), it returns always 2 (even though wait around 180sec).

Does connection becomes something wrong?

If I call

    blecen_Conn(NO_CONN, NULL, 0);

in hello_client_connection_down(), blecen_getConn() returns 0 correctly.

- Should I call blecen_Conn(NO_CONN, NULL, 0) in connection_down callback?

- Should I avoid to use blecen_GetConn()  to check connection status?

Thank you for your support in advance.

Hi,

I am developing an Wiced SMART application with BCM20737S which use 23.8kiB RAM (*1). During running application, I found some strange behavior ( bonding is sometimes failed / sometimes cannot write to characteristic etc / wiced return GATT_ERROR(0x83) to android application as write result). They are not always occur, but if they occur once, it cannot recover after reboot.

Then I guess memory on SS area or other configuration area are broken. As supporting evidence, reproducibility becomes larger when I increase application size. When I reduce application size, this issue doesn't reproduce.

I'd like to calculate how many Total RAM footprint is available. Do you have any idea?

(*1)

--------------------------------------------------------------------------------

Patches start at                  0x00204568 (RAM address)

Patches end at                    0x0020537C (RAM address)

Application starts at             0x00204FD0 (RAM address)

Application ends at               0x0020A49E (RAM address)

Patch size (including reused RAM)       3604 bytes

Patch size                              2664 bytes

Application size                       21710 bytes

                                      ------

Total RAM footprint                    24374 bytes (23.8kiB)

--------------------------------------------------------------------------------

Hello everybody, i want to retrieve the ack of th indicate sent to smartphone by the wiced sense; so is there a function or a callback that recuperate the ack ?