Smart Bluetooth Forum Discussions
hi.
i use 20736S custom board and just met a problem.
please tell me something wrong or missed.
after boot, my code enter deep sleep by button event or timeout.
button event wakeup is ok.
after then, i hope to enter deep sleep again.
at this time, button event is success, but next log message show repeatedly.
11:53:35 bleprofile_queryPowersave(POWEROFF): 00000000
11:53:35 bleprofile_queryPowersave(POWEROFF): 00000001
11:53:35 bleprofile_queryPowersave(POWEROFF): 00000001
11:53:35 bleprofile_queryPowersave(POWEROFF): 00000000
11:53:35 bleprofile_queryPowersave(POWEROFF): 00000001
11:53:35 bleprofile_queryPowersave(POWEROFF): 00000001
11:53:35 bleprofile_queryPowersave(POWEROFF): 00000000
11:53:35 bleprofile_queryPowersave(POWEROFF): 00000001
11:53:35 bleprofile_queryPowersave(POWEROFF): 00000001
...
next is my code
ds_create()
{
...
bleprofile_regAppEvtHandler(BLECM_APP_EVT_ENTERING_HIDOFF, (BLECM_NO_PARAM_FUNC)app_enter_hidoff);
bleprofile_regAppEvtHandler(BLECM_APP_EVT_ABORTING_HIDOFF, (BLECM_NO_PARAM_FUNC)app_abort_hidoff);
...
devlpm_init();
devlpm_enableWakeFrom(DEV_LPM_WAKE_SOURCE_GPIO);
interrupt_handler_mask[GPIO_PUSH_BTN / 16] |= (1 << (GPIO_PUSH_BTN % 16));
gpio_registerForInterrupt(interrupt_handler_mask, gpio_intr_handler, NULL);
gpio_configurePin(GPIO_PUSH_BTN / 16, GPIO_PUSH_BTN % 16, GPIO_EN_INT_RISING_EDGE, GPIO_PIN_OUTPUT_HIGH);
...
}
app_enter_hidoff() {}
app_abort_hidoff() {}
ds_timeout()
{
bleapputils_delayUs(500);
bleprofile_Discoverable(NO_DISCOVERABLE, NULL);
bleprofile_PrepareHidOff();
}
Why 1st time ok, but every 2nd time make infinite loop?
thanks.
Show LessI have two sets of parameters defined in the master node as follow:
// Used for low connection mode
blecen_cen_cfg.low_conn_min_interval = 200; // frames; 1.25ms
blecen_cen_cfg.low_conn_max_interval = 220; // frames
blecen_cen_cfg.low_conn_latency = 0; // number of connection event
blecen_cen_cfg.low_supervision_timeout = 500; // N * 10ms
// Used for high connection mode
blecen_cen_cfg.high_conn_min_interval = 6; // frames; 1.25ms
blecen_cen_cfg.high_conn_max_interval = 6; // frames
blecen_cen_cfg.high_conn_latency = 0; // number of connection event
blecen_cen_cfg.high_supervision_timeout = 10; // N * 10ms
The master node will first connect to a slave using high connection mode command blecen_Conn(HIGH_CONN, evt->wd_addr, evt->addressType) and then disconnect.
The master node then connects to another node using low connection mode command blecen_Conn(LOW_CONN, evt->wd_addr, evt->addressType)
However, when I used emconninfo_getConnInterval() to check the parameters, it show that the master still uses the high connection mode parameters for the 2nd node.
I even program the 2nd slaves node to update the parameters via lel2cap_sendConnParamUpdateReq, but the master node still uses the high connection mode parameters.
So, why does the master node use high connection mode parameters even when I use the command blecen_Conn(LOW_CONN, evt->wd_addr, evt->addressType) ?
Any idea how to fix it?
Show LessI want to know if the SDK has a OS, like free RTOS or UCOS or other?
And I want to create two or three custom threads, what should I do?
Thanks.
Show LessCould you send me the datasheet of the antenna?
I also want to know how can I do to test its RF performance, as Certification Lab need to test our modem but can't find a RF switch.
Show LessWe are testing out the SPI2 slave communications of the BCM20736E with the following pin configuration:
SPI_2_CS: P32
SPI_2_CLK: P24
SPI_2_MISO: P25
SPI_2_MOSI: P27
Prior to our code being loaded and executed, the ROM code is driving the output of the chip select line.
We monitored the chip select line, and there is UART ascii data being put out on that pin prior to our reconfiguration for SPI.
See Terminal_Broadcom.jpg
Because it takes the Broadcom module three seconds to load, the master device is already up and running by the time the module is configured.
This is causing a collision when the master device attempts to communicate to the slave when it's driving the port with UART data.
Both devices end up driving the line at the same time.
How do I stop the Broadcom UART debug output on that GPIO port?
Show LessHi guys,
Short version : WriteNVRAM gives me 0x00 for one call, on a line of my software, all other call works. The page ID is 0x12, I try to change it no improvment.
I delayed the write process by 7s (I was wondering is another process could interfer with the EEPROM, no improvement)
Ok, I have a program running on the BLE 20737S, everything works properly beside write/read EEPROM of one function. I'll explain.
My software used 3 page of EEPROM. Each Page is computed regarding of data from BLE.
T = 0s - "BLE transfer" (different UUID ....)
T = 0s - Write to page 0x13, length 50, OK
T = 0,1 (right after the Write, I read the same ID); OK
T = 3s - Write to page 0x11, length 0xFF, OK
T = 5s - Write to page 0x12, length 200, fail (return 0x00 instead of 0xC8 wanted)
I did try lost of possibility
PageID and Length are #define
In Page 0x13 and 0x11, buffer are local memory,
Page 0x12 is a array inside a struct, (I try to use a local buffer, no changes...)
I try to chang the ID 0x12 by 0x13, no changes
I try to reduce the length, no changes
Ready for any comment.
I'm pretty sure it's nothing, but I can't figure it out.
Thanks
Show LessI see the following while trying to build the hello_sensor on MAC using the 2.1.1 IDE.
**** Build of configuration Release for project WICED-Smart-SDK ****
"/Users/user/Documents/Electronics Software/WICED Broadcom/WICED-Smart-SDK/make" hello_sensor-BCM920736TAG_Q32 download
Unknown host
Linux32 uname: ""
Linux64 uname: ""
OSX uname: ""
Win32 uname: ""
Build Finished (took 223ms)
Show Lessas i know, the return value 0x08 of emconinfo_getDiscReason() is connection timeout (link loss).
is that BLE spec ?
I wonder other disconnect reason value.
in my android phone log, below disconnect reason is reported..
SENT Command to HCI. Name: HCI_Disconnect (Hex Code: 0x0406 Param Len: 3) Ctrl(0) Parameters Connection Handle : 64 (0x0040) Reason : 19 (0x13) |
---|
help me...
Do you have the IBIS model for the Bluetooth module BCM2073xS?