Smart Bluetooth Forum Discussions
Hello,
I have recently been debugging some hardware for a BCM20732S in which the App is the simple hello_sensor App. The 20732S board has P0 connected to a PB just as the TAG2 board has. The app runs fine on the TAG2 board and P0 updates/increments Hello x indication/notification.
On the BCM20732S the device connects/pairs fine and I can 'Write' to the HANDLE_HELLO_SENSOR_CONFIGURATION to blink the LED different amounts but as soon as I allow indications/notifications and Press P0 it updates Hello 0 to Hello 1 but then the device stops responding completely. I notice a difference in the Debug Output in that the module prints out "Stop Powersave!!!" that prints out when I use the BCM20732S but does not get printed out with the TAG2 board/SOC. After the first P0 button press the device no longer responds to button presses or if I try to update the HANDLE_HELLO_SENSOR_CONFIGURATION and it certainly appears the device has gone into a DEEP_SLEEP mode as P14/P38 which is attached to the LED drops to GND.
Any ideas on why the same firmware behaves differently on the SOC than the Module?
I have already implemented the XTAL Warmup addition to the project.
Regards,
Frank
Show LessIn hello_sensor.c, there is this test_enable field set to 1:
const BLE_PROFILE_CFG hello_sensor_cfg =
{
...
/*.test_enable =*/ 1, // TEST MODE is enabled when 1
...
}
What does this field do, and should I set it to 0 for production?
Show LessHello,
now i'm working with the BCM92073X board.
So Pin 32/33 (TX/RX) have as standard 1.8V. But i need 3.3V.
If i read the schematic right i musst change the RFB1,RFB2 and C22 to get 3.3V on Pin 32/33!?!?
Regards
Asper
Show LessI want to use the new wireless charging feature as soon as possible. Is there any reference or information regarding designing the coils and using the features in BCM2030737S?
Thanks,
JImmy
Show LessI am testing the BCM20732S and I am wondering how can I identify if the firmware running is a A1 or A0 just by looking at the documentation.
I am not able to program an application with SDK2.x on the BCM20732S, so this means to me that I have a A0 firmware. I am not able to get any other confirmation looking at the documentation. The part number on the datasheet of the BCM20732S does not reflect the information.
Last point, if I dig into the SDK2.0.1 I do see in the changelog.txt file a branch that is created for BCM20732A1, BCM20736A1 and BCM20737A1 SoCs. This means we can have a BCM20732A1 SoC as well.
The question is: how can I identify if the BCM20732S (SIP) is burnt with the A0 or A1 ROM? How can we order a BCM20732S personalized with A1 instead of A0?
Thanks for clarification!
Show LessHi,
I have been asked whether there are any constraints on data transfers when the BCM20736 would work in a mesh network.
So far I could envision that it has to switch between two roles, server and client. Now I'm wondering how fast that could happen with the BCM20736/7 + Stack.
If you have other ideas please let me know.
Regards,
Kilian
Show LessI'd like to add services into hello_client.
When I did it, I could get message but "conn up" message does not display.
I added log file, could anybody explain which status the client is?
Thank you.
Show LessIn order to continuously improve our standard offering and speed up the design review process, we would love to know which EDA tool (PCB/Schematic) vendor you prefer to use within your own designs.
The survey can be found here: http://community.broadcom.com/polls/1012
Show LessHello,
I'm getting strange output when I try to display the trace of a BLE application over the serial USB cable.
I'm using the right settings (115200n8) and I tried with different tools (miniterm.py, screen, gtkterm) under Mac, Windows and Linux.
I get some output that makes sense and some that is completely hazardous (non ASCII characters)
Here is the output of hello_sensor:
Broadcom Debug Port: BLEAPP CFA d�hello_senso����02 16 00 00 2a �48 65 6c 6c 6f 00 00 00 00 00 00 00 00 00 00 00 �02 18 00 01 2a ����23 20 56 7c 05 cf 6e b4 c3 41 77 28 51 82 7e 1b �32 2f2 9b 5e ���0a 18 �02 4f 00 29 2a �42 72 6f 61 64 63 6f 6d �02 51 00 24 2a �31 32 33 34 00 00 00 00 �02 53 00 23 2a �93 b8 63 80 5f 9f 91 71 �0f 18 �02 63 00 19 2a �64 02 01 06 03 19 00 permission check retCode = 00 23 20 56 7c 05 cf 6e b4 c3 41 77 28 51 82 7e 1b �02 01 05 11 0blecm evt handl01 0a 20 00 @$*#04FFF6F70092011E0300C1E804640000008003BA1A002800008003BE1A000000008003AE1A620000008003B21A020000008003B61A050005008003BA1A032800008003BE1A000000008003AE1A630000008003B21A020000008003B61A010001008003BA1A192A00008003BE1A000000008003DA1A0000000000074A05177A732000074E0531690000000782061100010000078206040100000007820603100E000007820620000F000007820601201C000007A207000001000007A607000000000007D2070000000000071A080100000000078A08010000000007EE07000000000007A2080000000000E5490B000000000007362A0100@$*#04FF1EF7009201030000073A2A500000000007522A500001000007021F0100hello_sensor_timeout:hello_sensor_timeout:1
hello_sensor_timeout:2
hello_sensor_timeout:hello_sensor_timeout:4
hello_sensor_timeout:5
hello_sensor_timeout:6
hello_sensor_timeout:hello_sensor_timeouthello_sensor_timeout:9
hello_sensor_timeout:10
hello_sensor_timeout:11
hello_sensor_timeout:1hello_sensor_timeout:13
hello_sensor_timeout:1hello_sensor_timeout:15
hello_sensor_timeout:16hello_sensor_timeout:17
hello_sensor_timeout:18hello_sensor_timeout:hello_sensor_timeout:20hello_sensor_timeout:21
hello_sensor_timeout:hello_sensor_timeout:23
hello_sensor_timeout:24
Does anybody has an idea of what could be wrong ?
Show Less