Smart Bluetooth Forum Discussions

Hi,

I am following WICED SMART SDK 2.x: Smart Designer Overview video; Kindly let me know which Mobile or PC application/software to use for custom GATT database developed in the video. I will really appreciate if you let me know simple example for getting started on this.

Looking forward for your kind help. Thanks in advance.

Have a nice day!

Kind Regards,

Ghalib

Hello,

I am using the BCM20737S in a custom design.

I want to set up a push button trigger an action.

Currently I have my push button set up on P27. When the button is not pressed, it is open and is pulled to ground. When the button is pressed it is closed and pull to 2.8v.

What do I need to do to set this up in software to trigger an event? Is there an example I can mess around with? I am currently using hello_sensor example.

Regards,

Luke.

Hi BCMs,

     We have one trouble as below.

Condition:

1. 20736 work in central mode.

2. Try to connect to one peripheral whose UUID is 128-bits.

Issue: Fail to get 128-bit UUID from peripheral when 20736 works in Central mode

Debug:

     we find out that, when 20736 call the function of blecli_ClientRsp(int len, int attr_len, UINT8 *data) in blecli.c (..\WICED-Smart-SDK-2.2.1\WICED-Smart-SDK\Wiced-Smart\bleapp\app)

     The process in this blecli_ClientRsp()

     ...

     ......

                for(i=0; i<len; i+=attr_len)

                {

                    uuid = data[i+4] + (data[i+5]<<8);

                    //ble_trace1("uuid=%04x", uuid);

                    if(uuid == cliAppState->blecli_svc_uuid)

                    {

                        found = i; //start position of uuid

           break;

                    }

                }

     Here, we see that, the UUID would be analyzed in 16-bit directly but not 128-bits.

     We try to modify this function to solve this issue, but WICED would not compile & link the file of blecli.c.

     Question: blecli.c is already burned into the internal ROM ? or could be modified by some way to solve this issue ?

     tks

Hello,

I am using the BCM20737s to send some data.

I know you can send 20 bytes in one packet over Bluetooth. Is this the maximum?

I have 16bit data, so I will be able to send 10 16bits of data in one packet?

I have 2500 (16 bits) samples I need to send 250 packets. What's the fastest way to do this?

Regards,

Luke.

Hi,

i'm planning on adding a second MCU (stm32) to a pcb, in addition to the BCM20737s, probably connected via PUART or alternatively, SPI.

I really like the OTA feature of the Broadcom modules, and would like to extend the feature to be able to update the STM32's firmware as well as the BCM's. I'm sure I'm not the only one with this in mind, and I was wondering if anyone has already extended the OTA feature for this purpose, or if someone would like to offer some thoughts on this?

Would there be enough space on the internal eeprom of the BCM20737S to copy a complete firmware image before sending it to the STM32? or would it make more sense to pass it through directly?

I was thinking of just joining the two hex files but adding a large offset to the addresses of the STM32's firmware, so that when the BCM receives it, it will be easy to differentiate that from the firmware that's meant for the BCM, (and pass it on to the STM after subtracting the offset on the fly). Is this how you would go about it?

Thanks for any advice (or sample code for that matter 😉

On Mouser, I find these two part-number...

Different package? reel or tube? or different module? different certifications?

Thanks in advance.

I am trying to see if I can get peripheral UART running using P32 for TX and P2 for RX on the 20736. I noticed in Application Note BCM920732HW (Wiced Smart Hardware Interfaces) it says "When both SPIFFY2 and peripheral UART interfaces are used by the application, the SPIFFY2 signals and peripheral UART RX signal must be on the lower pad bank (P0 through P7) or on the upper pad bank (P24 through P39). Thus, SPIFFY2 and the peripheral UART RX cannot be on two different pad banks."

We are using SPIFFY2 in our application, and we have SCLK P24, MOSI P4, MISO P25. So we do not have all of our SPIFFY2 pins on the same pad bank. Does this mean we cannot do peripheral UART on the desired pins if we do not want to change the pins we are using for SPIFFY2?

Hello,

We have a system with the BCM20737S module. The module is connected to the host CPU via the PUART and HCI uart. The host cpu is running some custom embedded SW - no windows and no linux.

We were hoping we could do a firmware upgrade via HCI port, but I'm reading the HCI protocol specs are not available for public use. This is a real drawback as it requires a extra step in production to program the device via tools provided by the SDK. We were hoping is to ship our host cpu firmware that includes the firmware for the BLE module and program it in filed via the HCI port. This is also needed as we are doing remote firmware upgrades as the host cpu is connecting via WIFI to a remote server.

I'm kindly asking you to provide a strategy to minimize production steps (to none if possible) and have a functional remote FW upgrade possibility via the host CPU. We can sign a NDA if necessary.

Thanks, Marko