Smart Bluetooth Forum Discussions
How can I get the BCM920736 to work as a master? I see that there is a hello_client example code, but it seems that this is specific to the hello_sensor example. But what if I want to do a discovery for multiple peripherals? How can I connect to more than one peripheral.
Do BCM 20732 and also the SDK 1.1.0 support multiple slave connections simultaneously?
If yes, what's the maximum connection.Show Less
I am having trouble getting port 0 pin 32 to operate in an input with pull-down enabled mode.
It seems to work for other ports such as P2.
Are these modes supported on all GPIO ports?
I am using a custom board based on the 20732S.Show Less
Where did all of the glucose profile code go?
In SDK 1.1.0 there was code that setup services / characteristics etc ...
Seems like there is skeletal code in there now ?Show Less
In the datasheet, it says pin 25 is "tied to the WP pin of the embedded EEPROM", but it doesn't say if it's active high or low.
Most EEPROMs I've used are active high to enable Write Protect; just want to confirm this is the same for the BCM20732S? If WP is enabled, will this prevent uploading firmware to it via the HCI UART?
I am looking for some sample applications that uses Wiced Smart Module. Doesn't need to be detailed designs, but some high level architectures would be good. Thanks.Show Less
I am having some difficulty with using the ADC on the 20732 chip. I checked the Hardware Interface Guide and it seems the only code you have to use to read from the ADC is the following:
is that correct? Does there need to be any type of configuring to make sure the pin is configured to be used as an ADC input?
I ask because I get the same adc reading whether I choose 2.4V or 3.6V as a reference voltage, which I'm pretty sure is not right.
Your help is greatly appreciated,
In my application I am trying to use P2 and P32 as GPIO pins. I am using the GPIO configuration call to configure them in the usual way. However they appear to still be operating as a serial port; P2 seems permanently operating as an input, and P32 can be controlled as an output but trace data is still output to it. (This despite setting the trace UART to HCI in spar_init.c)
I think I am turning off the peripheral port this way (following example of hello sensor):
// Following structure defines UART configuration
const BLE_PROFILE_PUART_CFG vehicle_tag_puart_cfg =
/*.baudrate =*/ 115200,
/*.txpin =*/ PUARTDISABLE | GPIO_PIN_UART_TX,
/*.rxpin =*/ PUARTDISABLE | GPIO_PIN_UART_RX,
Is there anything else I need to do to make sure the PUART is off so I can use these GPIO?
BTW my application is running on a custom board based on the 20732S.Show Less
Does the API possess a "wait for object" or "wait for event" type of fucntion in lieu of using a flag in a while loop?
For example if we are waiting for all data to transfer over a peripheral uart communication with attached sensor but do not want to proceed until all data is received/parsed AND we are using a uart callback versus polling is there some type of system event/wait object we can use besides using a flag in a while loop .. also does this wait mechanism provide a bailout timeout if too much time has passed?