Smart Bluetooth Forum Discussions
Hi,
I'm trying to find documentation for which GPIOs are bonded together inside of the BCM20737S. So far I've only been able to find the following note that is specific to the BCM20732TAG board, but it says to see the documentation for the module being used I've looked through the BCM20736S and BCM20732S documentation without any luck. I'm actually planning to use the BCM20737S, but there isn't much specific documentation to that part available yet.
Note: All GPIOs may not be available in the package. Some of the GPIOs may be bonded
together inside the package when not all 40 GPIOs are brought out. See the documentation
accompanying the module you are using for more information. On BCM20732TAG boards, the
following pairs of GPIOs are bonded together: P8 and P33, P11 and P27, P12 and P26, P13
andP28, P14 and P38. Only one of the bonded GPIOs from each pair may be used.
Thanks,
Briana
Hi,
I started developing a BLE application with mmp20732 and WICED-Smart-SDK-1.1.0.
I see now that there are more recent versions, up to 2.2.0.
Are newer wiced releases compatible with mmp20732?
Thank you
Franco
Show LessHi,
According to the Bluetooth specification, limiting controller to advertise via specific channel, i.e. channel #37 only, means to disable 2 (#38, #39) out of 3 in one advertising event. This won't change the count of event in a period of time.
So, I expect to have following evidence from my experiment:
1. Advertising interval 83 ms (a.k.a 12 adv. event / per seconds)
2. Advertising channel with all (#37, #38, #39) and only #37.
3. To expect the same count of discovery from scanning of central role.
But, weird thing that I faced is that I can't get same count of discovery from central device, now I'm using 20737 EVB.
I only got ~ 4 event when the advertising channel is only at #37 with 100% scanning window.
I've confirmed that total count of advertising event is the same at all channels which is enabled for advertising.
Does anyone know the reason for this phenomenon?
Show LessUsing 20737 + SDK2.1.0, we're facing a very weird issue that will cause 20737 stop advertising at all even calling function 'blecm_startAdv'.
The case is that one device (20737) was connected by one central device (i.e. PC) and also being a central role which connect 2 or more peripherals at the same time.
While all connections (including to central and peripheral) are made and running normally (indication is passing between them), the connDown call back was called from all connection (without any reason), after that the call of 'blecm_startAdv' is not working anymore for next discovery.
Any idea about this weird case?
Show LessI have a similar problem to this:
Re: Information: Programming your BCM20732S-based board from an onboard UART header
I am starting a new thread because it is for the BCM20736S. Here it goes:
I built a board for the BCM20736S and the board seems functional. I built it up, it powers on, and I can see a factory pre-programmed 'Hello' application running from my iPhone using LightBlue. I can interact with the services and characteristic and read the manufacture string.
I am trying to program this board with other apps using both the WICED SDK 2.0 virtualized in Windows XP and natively on Mac OS X. Neither seem to be able to program the board. I know my TX/RX lines connected correctly because I can see debug information over my FTDI breakout board from factory-programmed sample app.
I have not taken any scope captures yet of RX/TX or SCL/SDA.
1. P1 is pulled high with a 10k Pull-up.
2. UART_RX (pin 18) is pulled high during power-up. (I can still see the hello application on my iPhone even when I do this)
3. UART_TX is on pin 19.
After power-up, I let UART_RX float or pull it low. I then press the reset button and double-click a sample app and to program/upload code. It always fails to detect the BCM20736S. Obviously it is working so I am not sure why I can't program. What am I doing wrong?
I have test pads/break outs on all I/O's so I can probe anything needed.
Show LessSerialization queue from the LE stack to application is 16 entries deep by default.
I have confirmed it by reading bleappevt_srzn_q_depth.
Our use case use CPU almost full, so I am concerned of serialization queue full case.
1) Is there any way for the application to check if serialization queue full has happened,
so that to determine whether to increase bleappevt_srzn_q_depth?
2) What is the behavior of LE stack if queue is full at the time of queueing a callback?
Watchdog reset has been observed sometimes, by any chance, does it trip watchdog?
3) What is the behavior of queueing AdvReportCb by LE stack?
For example, if Master receives a burst of advertisements (let's say from 30~40 slaves in the room),
the LE stack tries to queue up all advertisement packet received?
Or is there any throttling mechanism to avoid queue full?
Thanks!!
Show LessHi,
I have been trying to get the passkey operation to work, and have had a look at the various discussions and have a very simple question.
As the passkey operation is not working correctly, will connect to anything even if the passkeys do not match, when will this be fixed so that it will operate correctly ?
Thanks
Show LessWe've got a batch of boards that are nearly identical except some use the 2S and others use the 6S. We noticed that the newer boards with the 6S do not have the same range as the older 2S boards. The difference isn't huge, about 10% at most. More concerning is that the connections on the 2S boards seem to be more reliable (they don't spontaneously disconnect like the 6S ones do sometimes).
Has anyone else noticed this and if so, did you determine a root cause?
I'm trying to determine if this is an issue with the boards, the SDK or the modules. Since the modules are identical except for firmware I would guess that this is the least likely case. Leaving the boards or the SDK as potential differences, but I'm not sure how to detect/resolve any problems related the the SDK.
Show LessI have following questions to clarify the NFC offerings;
1. Does WICED Sense (BCM20737S) has a NFC Tag (or NFC Antenna?) inside? So I can trigger the BLE link when the Sense is inside the NFC Reader field. I can't find any other app notes on this, any guidence on how to implement this?
2. iPhones do not operate as NFC Readers, so this will not trigger the BCM20737S. I believe triggering a NFC Reader with a passive NFC chip and then triggering the BLE link on the NFC Reader side is also interesting. But I belive Broadcom chips operate on Passive NFC tag side? Is this correct?
3. What is the difference between the BCM43341 and BCM20737S regarding NFC?
Show Less