Smart Bluetooth Forum Discussions
hi,
I'm using BCm920737TAG
i'have successfully created an application with vendor specific services and characteristics.
i can read wirte using BLE scanner and android.
But anytime after i enable the notify in Android ( with a notify able characteristic) i cannot read or write any other characteristic...
Can someone Help me ?
Do i have to do something else after
bleprofile_sendNotification(HDLC_IR_TEMPERATURE_SERVICE_IR_TEMPERATURE_DATA_VALUE, (UINT8 *)db_pdu.pdu, db_pdu.len); | |
Thank you
Show LessHi,
I would like to add some assembly file (like test.s) into the hello_sensor app in WICED Smart SDK 2.x.
I also modified the makefile.mk to :
APP_SRC = hello_sensor.c test.s
But failed to build with below error message:
make.exe[1]: *** No rule to make target '../../build/hello_sensor-BCM920736TAG_Q32-rom-ram-Wiced-release/test.s', needed by '../../build/hello_sensor-BCM920736TAG_Q32-rom-ram-Wiced-release/A_20736A1-hello_sensor-rom-ram-spar.elf'. Stop.
Any idea to fix it?
thanks.
Show LessWhat's the recommended approach to increase the speed of data collection and transmission from the sensors on the WICED Sense project? Can this be adjusted by modifying the parameters in bleprofile_SendCOnnParamUpdateReq()? Also, is the function blecm_ConnectionEventNOtificationEnable() documented?
Is there any robustness or sustainability difference between DS and VS in NVRAM?
I found sometimes VS data is cleared when power corruption happens, but DS is not.
Show Less===
SDK: 2.1.1
Tag: 920737.
app: hello-client. (1 slave sensor <-> 4 handsets)
===
Problem:
From attached log, current Hello-Client can support in code up to 4 master handset.
So I try to connect with Hello-Client device by trying handset 1, handset 2, and handset 3
but handset 3 is always disconnected right after it attempts to connect.
It seems some timeout action or code modification error. Any help?
Besides I got 2 disconnection cause,
Disc_Reason: 08
Disc_Reason: 13
Dont know what they mean. May I know the disconnection cause? TKS.
Does not having P0 pulled high have any impact on the ability of the module to enter sleep mode? I have been told that it impacts deep sleep mode, but I can't determine if it that is the only impact. I have seen some mention of this on this site: Re: Questions sleep and deep sleep modes on BCM20737 but only in reference to deep sleep mode.
The reason I'm asking is that I'm not seeing the device enter sleep mode when looking at the current draw. I don't seem to get below 100 micro amps. The device is normally always connected or advertising so I need to make sure I can sleep whenever possible to conserve battery life. I'm trying to rule P0 out as a potential issue.
Also, is there any correlation to the fine timer interval and battery life (e.g. shorter intervals leading to more power consumption)?
Thanks!
Show LessHi Sir,
I found a very weird situation about the PUART rx.
I do the experiment to send a continuous packets from Host SoC to BCM20736.
The packet length is 3 bytes only. Once the BCM20736 received the data, it echo the data back to BCM20736.
The following photo are the waveform that the scope with UART module.
The configuration is 115200/8n1. Do you have any idea what's going on?
Show Less
can anybody explain the definition of Absolute Voltage measurement error in ADC?
Hardware spec displays absolute voltage measurement error is typically 2%.
Is that mean add value has 2% error?
If 16bit adc value is measured as 512 (0x200), then can the measured value have error value of adc 10?
I'd like to know the formula of absolute voltage measurement error.
Thank you.
Show LessI need to use all 4 PWM channels and because the way they are connected I had to move the buzzer from P28 to P13 (same hardware pin). The output sound that I am getting now is very distorted. Why ?
Similar issue was already reported with BCM20732 and SDK 1.1 here:
PWN not working on P13/P14 on BCM20732S - SDK 1.1
Also here I don't have any problems with P26, P27, and P28.
This issue is very easy to reproduce, in:
include/Platforms/BCM920737TAG_Q32/platform.h
one can change:
#define GPIO_PIN_BUZZER 28
to:
#define GPIO_PIN_BUZZER 13
and then any sample app (that uses the buzzer) can be used e.g. hello-sensor
Show LessI'm using the BCM920732TAG board with the 1.1.0 WICED Smart SDK. I'm trying to get SPI slave mode working, but I'm having pretty major issues since many of the API functions are either not documented, or have their documentation limited to just the bare function prototype itself. (Was the Doxygen generated API documentation ever actually finished?)
Specific question:
The spi_comm_slave app example uses the following code to enable interrupt on the flow control pin:
interrupt_handler_mask[SPIFFY2_INPUT_FLOW_CTRL_PORT] |= (1 << SPIFFY2_INPUT_FLOW_CTRL_PIN);
// Now register the interrupt handler.
gpio_registerForInterrupt(interrupt_handler_mask, application_gpio_interrupt_handler, NULL);
In my code, I would like to clear the Rx FIFO at the beginning of chip select, then read stuff out at the end of chip select. I think I'm only getting the interrupts at the beginning of chip select at the moment. How can I enable interrupts for both edges on chip select? The gpio_registerForInterrupt() function is completely undocumented, and it seems like a rather critical API function.
Show Less