I'm working on a BLE project which has one output data service with three characteristics in it (that correspond to the three data channels I need to send). I'm sending all this data using notifications.

For some reason when I use any of the iOS BLE apps (For example in the screenshot below I have the nRF Connect App for iOS) I cannot see all the characteristics. I can see one of them but I still can't enable the notifications even for that one characteristic. (this happens with the Cysmart app, LightBlue iOS apps as well).

The weird thing about this is that when I use the Android counterparts of the same apps, I don't have this problem. I can see all the characteristics and I can even enable the notifications for them.

Is there anything I can do here to fix this issue with the iOS 

This is how my characteristic definitions look like (I can share the code text itself just let me know)

Hello, first off thanks to all team for all the detailed documentation and support.

I have setup a CYBT-353027 module as an audio sink, sending I2S signals to a codec. All code from your repos and using Modus Tool Box. The codec is setup as the I2S master with a sample rate of 48KHz.  BT modue set as I2S slave by setting the is_master flag to false as per KBA228409. Probing the BCLK, LRCLK and DATA with a scope reveals all signals to be seemingly in order, with the codec driving the BT Module at the right BCLK and LRCLK, and DATA being returned by the Module. However upon hearing the audio playback I can notice the amplitude oscillating quite vigorously, at about a rate of 1Hz. To isolate the issue from the codec I proceeded to stream a pure sine wave of 175Hz from my android phone and decoded the i2s packets. The resulting playback is the same, so my attention turned back to the BT module. (data capture attached). My hypotheses and associated questions so far are the following:

1-Could this be aliasing due to mismatch in sample rate? I noticed the A2DP only negotiates a sample rate of 44.1KHz with my android phone and I haven't found a way to force it to 48Khz from the phone. How does the module deal with this scenario in this case, given that its an I2S slave driven at 48KHz, but the BT is fixed at 44.1KHz?

2-Could this have anything to do with the BT Codec used?

Thanks in advance for your insight.

Hi,

I have a simple console service that works when paired, but I can't for the life of me figure out how to get it to function while unpaired. I saw this thread about refusing pairing:

https://broadcomwiced-v8.hosted.jivesoftware.com/thread/3826

The solution works in that the master no longer attempts to pair, or at least no longer prompts the user to pair, but it doesn't work in that I get various errors and cannot maintain a connection. Disabling the callback added via the solution makes the code work again, but the user is prompted to pair. 

The service is a simple console service, basically like the Nordic UART Service. For now I'm even using the NUS UUIDs to test with generic console apps. I have it working when paired (no bonding), but it will not work when using the linked solution to disable pairing. I've set the various flags - pairing_params has LESMP_AUTH_FLAG_NO_BONDING, encr_required is set to 0, and I am not sending any security requests because as mentioned in this thread sending a security request should result in bonding.

I've verified that it's not the console phone app that I'm using that's trying to pair. When using a similar service set up on a Raspberry Pi no pairing is requested. 

This is for WICED Smart Bluetooth using the BCM920737

Hello.  We are trying to get Bluetooth A2DP functionality up and running on a 20721 design.  Starting with the EVK (CYW920721B2EVK-02) the code is up and running and we are able to establish a connection with a mobile phone to stream audio.  However when this connection starts, the audio stream does not get started.

When the streaming begins from the phone we see this in the WICED_TRACE output, and it looks like the jitter buffer never enters into the

JITTER_NORMAL_STATE

state, so the audio stream never opens.

jitter_buffer_event_handler (status : 0x07)
jitter_buffer_event_handler: ignore states

What could be going wrong here and how do we get the stream open, and data flowing?

In our design, we will need to capture the decoded PCM data which we are hoping to do with either the audio_record APIs or the I2S_inject APIs so that we can route this data over to our playback device (which does not have a PCM or I2S interface).

Thanks in advance for your help!

-larson

HI,

        I bought a CYBLE-013025-EVAL , and it includes CYW20737 silicon device .  I saw the datasheet of CYW20737  mentioned it supports "Bluetooth Smart Audio", and details can  available in application notes on this topic. However, I can't find related application notes  introduce how to implement this function by SDK(WICED SMART). Does there has application notes about how to implement Bluetooth Smart Audio?

Thanks

Best regards

Hi,

I was trying to find some of the documentation on WICED Smart that I was previously looking at but I can't seem to find it. I went to the download page ( https://www.cypress.com/products/wiced-software ) and all of the WICED studio links lead to "page not found". Are the documents and other downloads still available?

Dear all,

Would you please provide us ETSI EN 300 328 V2.1.1 test report of CYW20737S?

Best,

Shun Furusawa

I was following along with the "find me" tutorial on the "Getting Started with EZ-BLE WICED Modules" document and noticed the "bleprofile_LEDOn();" function did not work. What  function do you recommend using to turn on the evaluation board LEDs and pins instead (and how can I implement the function)? Also is there anywhere that I could find a description of common functions and how to use them for this specific board (CYBLE-013025)? Any help would be great!

Thank you very much,

Tim

Does anyone know how to set the TAG4 board switches so i can use the MBT.exe tool to test the Bluetooth regulatory part.   Basically how to set the TAG4 board switch to enable HCI command and then i can use the Manufacturer Bluetooth Test Tool (mbt.exe).

Thanks

G