Smart Bluetooth Forum Discussions
I've found that the defined values for Control register 5 doesn't match with the datasheet. This bug directly affects Full-Scale setting (sensitivity) of the sensor.
In "lis3dsh_driver.h" from line 250 to 255 should be fixed this way.
//CONTROL REGISTER 5
#define CNTL5 0x24
#define BW BIT(6) //from BIT(7)
#define FSCALE BIT(3) //from BIT(5)
#define ST BIT(1) //from BIT(2)
#define SIM BIT(0)
Moreover, be careful when you have to call GetAccAxesRaw(AxesRaw_t* buff) because it will divide the raw value by 16.
They cost me a few hours finding what's wrong with my code.
Show LessHello everybody,
I'm stuck with getting P_UART to work with a custom PCB containing the BCM20736S BLE-module and a Cortex-M4-MCU. Both UARTs are connected to the Cortex-M4, I'm perfectly able to get the BLE-module to reset, run and enter programming or recover mode via the M4. I am also able to send data via the M4's UART to the BLE-module.
Connections are as follows:
HCI_UART_RX and _TX are connected to high impedance ports of the M4 and a FTDI-USB-Serialbridge. Programming and tracing is working.
GPIOs P0 (P_UART_TX) and P2 (P_UART_RX) are connected to a UART's RX and TX pin of the M4 respectively. But the BLE-module won't send a byte (or receive one for that matter) via P_UART.
I changed platform.h defines to accomodate the different hardware:
#define GPIO_PIN_UART_TX | 0 |
#define GPIO_PIN_UART_RX | 2 |
For easy testing I used the code of puart_control but no luck. I need a connection with a baudrate of 115200, 8N1, no flow control (these pins are used for internal EEPROM on the BCM20736S module).
I removed the GPIO_PIN_BUTTON and even GPIO_PIN_WP and set them to -1 in the gpio_cfg - still no joy.
I then issued a puart_enableTx() in the init function to no avail.
Best regards
Hannes Baumgart
Show LessI tried to implement a long characteristic more than 20 (+3) with BCM20737.
But the callback function regsitered by legattdb_regWriteHandleCb was called twice if I written 30bytes from iPhone.
First call with 18bytes, and second call with 30bytes.
I tried test the sample App long_characteristic.
The callback function 'long_characteristic_write_handler' was called only once with 30bytes.
I copied long_characteristics.c, long_characteristics.h and makefile.mk into my original app.
But the callback was called twice.
How to implement to let the callback be called once for one characteristic?
I am using WICED Smart SDK 2.1.1 on OS X Yosemite.
Thank you in advance.
Show LessThis is a follow on discussion to the one started here in this thread: Connection Event Callback API (follow-on)
Based on the behavior of my application, it appears that the connection event callback handler can be called asynchronously to the other callbacks in the system.
That is, my code might be executing in a write handler or a timer, and while doing an IO operation, my connection event handler might get called.
This was shocking to me because I have designed my application on the assumption that all application handlers are synchronous, that is, they are all serialized into a single "application" thread.
Is this true in general, except for connection events? Are any other handlers asynchronous? Is there any support for a mutex to properly deal with asynchronous access?
Here is why I believe this to be happening: (Note this is compiled with SDK 2.1).
I have a buffer which is modified from within my connection event handler, as well as elsewhere in the program.
I have some code that writes this buffer to NVRAM, after first computing a checksum.
I found that the buffer changed while my code was executing the call to write the buffer to NVRAM, resulting in the checksum being wrong. The part of the buffer that changed is only written from within the connection event handler.
Is this really possible or should I be looking for another culprit?
Show LessHi,
I'm trying the secure ota and encounter this issue:
Following this post, WICED Smart BCM92073X OTA Firmware Upgrade (1)
After download ota_secure_firmware_upgrade, the device can be discovered and seems working.
But after reboot, it's not broadcasting and get no trace (from timer) also.
I check the OTA image footprint in NV, it is larger than 10k bytes. If I comment the following code in hello_sensor_write_handler(), then the OTA footprint will be below 10k and able to work:
else if ((len >= 1) && (handle == HANDLE_WS_UPGRADE_CONTROL_POINT))
{
return (ws_upgrade_ota_handle_command (attrPtr, len));
}
I also experience when OTA footprint 10k bytes, it will stop working before. Is there any reason and any way to solve it?
Appreciate for help!
I'm using BCM20737S
Best regards,
Sam
Show LessHI...
I am having some problem while downloading.I could not able to download most of the SDKs successfully.But I have downloaded WICED-Smart-SDK-2.2.1-IDE-Installer.exe, while running the exe it shows "please select another location to extract the installer to" and even if i select other locations the same message shows.
Please help me to solve this issue. This all new to me
Show LessHello,
I'm newbie to wiced-smart platform.
Now I'm trying to make my device having a static random BD_ADDRESS, and read
Re: Static random device address
and already understood the mechanisms of wiced's static random address creation process.
But, when I insert following two lines in my _create() function
UINT8 bd_addr[6];
blecm_set_static_random_bd_addr(bd_addr);
with inserting following one line in top of my source code
#include "blecm_set_static_bd_addr.h"
and build, make says:
undefined reference to `blecm_set_static_random_bd_addr'
Is this function already deprecated?
If so, what is the name of the new alternative function?
Best,
Takashi
====
An update.
Adding one line into my makefile.mk in the last line resolved build issue.
APP_PATCHES_AND_LIBS += bd_addr_control.a
But again, the device just becomes FF:FF:FF:FF:FF:FF (because I appended BT_DEVICE_ADDRESS=ffffffffffff), and the Address Type bit is still set as Public (by looking at a sniffer provided by nordic).
Any one have a suggestion?
Best,
Takashi
I can't power my dev-kit on, I guess that the board is broken.
How could I contact a FAE?
Boardcom Beijing office told me to ask help from distributor, and the distributor(Mouser) told me that just ask Boardcom.
I tried to make an feedback on Boardcom website, but the system of website told me
- The reCAPTCHA wasn't entered correctly. Please try again.
Where is the %$%$# reCAPTCHA?
&
Where could I get help
Show LessBased on you response here: BCM20737S flashing process (leveraging extra space in EEPROM)
I am assuming that unused space of the 512Kb eeprom on the 2073xS module cannot be used at all by the customer application as extra resource, for eg logging data?
Show LessI've downloaded a program with a patch "additional_advertisement_control.a" to use "bleprofile_notifyAdvPacketTransmissions". I've found a bug that I cannot solved. Therefore, I removed that patch.
After that download, I've tried to download original sample programs (such as hello_sensor") to the WICED Sense, but it always malfunctions when it advertises (Advertisement start for a few milliseconds and stop. PC cannot pair with it). Seems like the patch in the previous download affects consequent downloads.
I have another WICED Sense that is not affected by that patch. Testing of hello_sensor on that device has no problem at all.
I have followed WICED Sense recovery procedure, but it didn't help me.
How can I solved this problem?
Show Less