Smart Bluetooth Forum Discussions
How do I make the chip connectable but not discoverable ?
Hi,
Is there any guideline for enabling scaternet using 20737S & SDK 2.0?
More specifically, I'd like to know how a tag can support multiple phone connect into to access service.
Thank you in advance,
Brian
Show LessMark your calendars as Broadcom is confirmed for a Broadcom WICED developer and media event taking place on Tuesday 8/26 at the SPUR Urban Center in San Francisco, CA.
During the event, we will unveil the new WICED Sense kit and hand out roughly 50 tags to attending developers and media.
- WHO: Broadcom Corporation, Wireless Internet Connectivity for Embedded Devices (WICED) Group
- WHAT: Developer and Media Networking Event
- WHERE:SPUR Urban Center, 654 Mission Street (at 3rd Street), San Francisco
- WHEN: Tuesday, August 26 from 6:00 – 8:00 p.m. PT
- WHY: Sneak peek and hands-on demo of Broadcom’s latest edition to its WICED portfolio, candid discussion on IoT trends and networking opportunity with key IoT influencers and developers
We'll keep you posted as we continue to make progress.
Show LessHello
With Wiced smart 2.01 and BCM92073X_LE_KIT I face an issue with the debug feature :
when I click on Debug/Wiced Debug": i have the following error message.
And when I click on Debug / debug WICED-Smart-SDK Release I have the following error message :
With this configuration HW and SW I can programm heart rate monitor example and display the result in my android phone.
Something is missing in my configuration?
By the way what kind of probe can I use tho debug via SWD (J10) ?
Thanks for your help
Best regards
Michel
Show Lessconst BLE_PROFILE_CFG dwBaseStation_cfg = {
/*.fine_timer_interval =*/10,// ms -- NOTE: this is bogus, fine timer always ticks off ~78 times per second
/*.default_adv =*/NO_DISCOVERABLE,
/*.button_adv_toggle =*/0, // pairing button make adv toggle (if 1) or always on (if 0)
/*.high_undirect_adv_interval =*/32, // slots
/*.low_undirect_adv_interval =*/2048, // slots
/*.high_undirect_adv_duration =*/300, // seconds
/*.low_undirect_adv_duration =*/300, // seconds
/*.high_direct_adv_interval =*/32, // seconds
/*.low_direct_adv_interval =*/2048, // seconds
/*.high_direct_adv_duration =*/300, // seconds
/*.low_direct_adv_duration =*/300, // seconds
/*.local_name =*/"TRANSMITTER", // char, maximum length is LOCAL_NAME_LEN_MAX
/*.cod =*/"\x00\x00\x00", // char, Class of Device string, max len is COD_LEN, used mostly by Windows for device icon
/*.ver =*/"0.20", // char, version string, max length is VERSION_LEN.
/*.encr_required =*/0, // (SECURITY_ENABLED | SECURITY_REQUEST),
/*.disc_required =*/0, // actions on disconnection
/*.test_enable =*/0, // TEST MODE is enabled when 1
/*.tx_power_level =*/0x04, // dbm
/*.con_idle_timeout =*/120, // second 0-> no timeout
/*.powersave_timeout =*/0, // second 0-> no timeout
/*.hdl =*/{ 0x00, 0x00, 0x00, 0x00, 0x00 }, // [HANDLE_NUM_MAX];
/*.serv =*/{ 0x00, 0x00, 0x00, 0x00, 0x00 },
/*.cha =*/{ 0x00, 0x00, 0x00, 0x00, 0x00 },
/*.findme_locator_enable =*/0, // if 1 Find me locator is enable
/*.findme_alert_level =*/0, // alert level of find me
/*.client_grouptype_enable =*/1, // if 1 grouptype read can be used
/*.linkloss_button_enable =*/0, // if 1 linkloss button is enable
/*.pathloss_check_interval =*/0, // second
/*.alert_interval =*/0, // interval of alert
/*.high_alert_num =*/0, // number of alert for each interval
/*.mild_alert_num =*/0, // number of alert for each interval
/*.status_led_enable =*/0, // if 1 status LED is enable
/*.status_led_interval =*/0, // second
/*.status_led_con_blink =*/0, // blink num of connection
/*.status_led_dir_adv_blink =*/0, // blink num of dir adv
/*.status_led_un_adv_blink =*/0, // blink num of undir adv
/*.led_on_ms =*/0, // led blink on duration in ms
/*.led_off_ms =*/0, // led blink off duration in ms
/*.buz_on_ms =*/0, // buzzer on duration in ms
/*.button_power_timeout =*/0, // seconds
/*.button_client_timeout =*/1, // seconds
/*.button_discover_timeout =*/3, // seconds
/*.button_filter_timeout =*/10, // seconds
};
//We want to store the ASCII representation of our transmitter's bluetooth address into the advertisement's .local_name
Show LessThis question is for the BT stack developer(s) at Broadcom.
I have noticed the following in bleapp.h SDK2.x
extern void ble_trace0 (const char *p_str);
extern void ble_trace1 (const char *fmt_str, UINT32 p1);
extern void ble_trace2 (const char *fmt_str, UINT32 p1, UINT32 p2);
extern void ble_trace3 (const char *fmt_str, UINT32 p1, UINT32 p2, UINT32 p3);
extern void ble_trace4 (const char *fmt_str, UINT32 p1, UINT32 p2, UINT32 p3, UINT32 p4);
extern void ble_trace5 (const char *fmt_str, UINT32 p1, UINT32 p2, UINT32 p3, UINT32 p4, UINT32 p5);
extern void ble_trace6 (const char *fmt_str, UINT32 p1, UINT32 p2, UINT32 p3, UINT32 p4, UINT32 p5, UINT32 p6);
extern void ble_tracen (char *p_str, UINT16 len);
// extern void ble_traceprintf(const char* fmt_str, ...);
I am not clear why the ble_traceprintf has been commented out moving to SDK2.x. This is braking the backward compatibility between the two versions of the APIs. This requires rework of the code being ported from SDK1.x to SDK2.x
Comments on this are welcome,
Thanks
Show LessI'm trying to calculate the period between falling edge and rising edge interrupt in interrupt callback routine.
The period is short as several usec.
Do someone know how to get the CPU tick timer? or tick timer API that has resolution of micro second?
Thank you,
Show LessIs there a provision where the unit at the factory can be loaded with a crude program that would come up as a BLE device searching for a host but without full capability. On first connection, the host quickly determines whether it has current firmware in non-volatile storage. If it doesn’t, the host downloads it. This minimizes what has to be hard-programmed and maximizes operating convenience.
In SDK 2.0.1, the i2c_temperature_sensor sample using cfa_bsc_OpExtended within its temperature_sensor_write_16_bit_register function.
1. if I right-click the function call cfa_bsc_OpExtended and select "Declarations", I don't find any. By searching these forums I found that this is declared in cfa/cfa.h.
2. in the API documentation, "cfa" isn't mentioned, but I2C is. And there's a i2cm_comboWrite function which would appear to do thse same thing as cfa_bsc_OpExtended.
Is cfa_bsc_OpExtended older API, and the sample hasn't been updated?
Is i2cm_comboWrite to be preferred?
Are there situations where one has to use cfa_bsc_whatever?
Why doesn't a search for "Declarations" on cfa_bsc_OpExtended turn up any results?
thanks.
Show Less