Wi-Fi Combo Forum Discussions
I want to load iBeacon app in Wiced Sense Tag but i get a problem when i builded as below. Can anybody help me?
make.exe[1]: *** No rule to make target '../tier2/brcm/libraries/lib/20736/ibeacon.a', needed by '../../build/ibeacon_device-BCM920736TAG_Q32-rom-ram-Wiced-release/lib_installer.c'. Stop.
Makefile:350: recipe for target 'ibeacon_device-BCM920736TAG_Q32' failed
make: *** [ibeacon_device-BCM920736TAG_Q32] Error 2
Show LessHi Everyone!
I Really want to debug my program.
I Push the green bug Icon. I can see the Next message
I use WICED-SDK 3.5.4
I Also Update all program (Check for update at help menu)
and Setting is below like create debugg process
Show Less
Hi,
I am using the Inventek's variant of BCM43341 wifi/ble/nfc module.
I wanted to know, how should I go about allocating space on the 4KB SRAM that is backed up using VBAT, even the module is powered down (VDD).
I wish to save some application context during sleep in this 4KB space and when powered on, I should be able to recover whatever was saved.
Is there any API for allocating data to this specific portion of SRAM?
thanks!
Regards,
Manish
Show LessHi everyone.
I want to know what functions which is in demo or application is.
for example
there is wiced_bt_smartbridge_enable_attribute_cache function.
I don't know what is happen at using this function.
I want to know function and using method of functions in demo and application.
where can I find the this functions description?
Thank you!.
Sincerely!
-Dennis-
Show LessHi, can anyone help me finding Avnet BCM4343W SoC Module datasheet and pcb footprint?, Hi, can anyone help me finding Avnet BCM4343W SoC Module datasheet and pcb footprint?
Show LessPlatform BCM943341WCD1, use ble_proximity project as sample.
defined characteristic in gatt_db[] as :
CHARACTERISTIC_UUID128_WRITABLE(HDLC_XXX_CLIENT_ID,
HDLC_XXX_CLIENT_ID_VALUE,
UUID_XXX_CLIENT_ID,
LEGATTDB_CHAR_PROP_READ | LEGATTDB_CHAR_PROP_WRITE,
LEGATTDB_PERM_READABLE | LEGATTDB_PERM_WRITE_CMD | LEGATTDB_PERM_WRITE_REQ),
CHARACTERISTIC_UUID128_WRITABLE(HDLC_XXX_AUTH_CODE,
HDLC_XXX_AUTH_CODE_VALUE,
UUID_XXX_AUTH_CODE,
LEGATTDB_CHAR_PROP_READ | LEGATTDB_CHAR_PROP_WRITE,
LEGATTDB_PERM_READABLE | LEGATTDB_PERM_WRITE_CMD | LEGATTDB_PERM_WRITE_REQ),
I have an Android program that is writing the characteristics in the exact same way.
a) mBleService.getBleDevice().writeXxxAuthCode(loginAsyncTask.getAccessToken().getBytes());
on BCM943341WCD1 console:
in ble_proximity_gatt_cback, I get event=GATT_ATTRIBUTE_REQUEST_EVT
AND p_event_data->attribute_request.request_type = GATTS_REQ_TYPE_WRITE
b) mBleService.getBleDevice().writeXxxClientId(loginAsyncTask.getClientId().getBytes());
on BCM943341WCD1 console:
in ble_proximity_gatt_cback, I get event=GATT_ATTRIBUTE_REQUEST_EVT
AND p_event_data->attribute_request.request_type = GATTS_REQ_TYPE_WRITE_EXEC
Why does one show up as GATTS_REQ_TYPE_WRITE and the other as GATTS_REQ_TYPE_WRITE_EXEC ?
Show LessI'm using WICED-SDK-3.5.2 and trying to compile the demo apps for AWS IoT.
Where can i find the header file "resources.h" that is referenced in /apps/aws_iot/pub_sub/publisher/publisher.c and other files?
Kind regards,
Adam
Show LessHello Team,
We are using (BCM43236B) USB based dual band Wi-Fi IC in one of our project.
As per the datasheet recommendations we have powered up the device in our PCB and IC is powered ON, with this we are able to achieve voltage levels at all the points and we are getting output voltages as mentioned in the datasheet at few pins(LDO outputs from IC) and also we are able to get XTAL out clock from the IC clock pin.
We are facing a problem in booting up the IC, as we wanted to connect the IC to HOST PC in USB mode we have driven USB signals(USBDM, USBDP) to USB mini connector, when it is plugged to HOST PC (in windows as well as linux) we are not able to recognize the IC or the device with any VID and PID(vendor ID, Product ID) even in Device manager(windows) and listing USB devices(linux)
I would request the Broadcom Team to support us on board bring up and driver support for at least linux OS.
Please reply to this email for more info to be provided.
email - jkranjan@pecsolglobal.com
contact - +918747946777
Show Lesswiced_network_up_default(...) starts with the following lines:
/* Read config */
wiced_dct_read_lock( (void**) &dct_network_config, WICED_TRUE, DCT_NETWORK_CONFIG_SECTION, 0, sizeof(platform_dct_network_config_t) );
*interface = dct_network_config->interface;
wiced_dct_read_unlock( dct_network_config, WICED_FALSE );
The doc for wiced_dct_read_lock and wiced_dct_read_unlock states that the value of ptr_is_writable should match across these two calls. And they don't. Unlock thus does not free the memory allocated by lock.
(When EXTERNAL_DCT is set, the ptr_is_writable is ignored. But this is not always the case)
Show Less