Smart Bluetooth Forum Discussions
text.format{('custom.tabs.no.results')}
Per the dialog here: Re: Characteristic of variable-length write
I changed the 5th parameter as " LEGATTDB_PERM_WRITE_CMD | LEGATTDB_PERM_VARIABLE_LENGTH" then I could get the actual length information of the data.
But there is another problem.
When I send 15 bytes data, it's OK. But when I sent the 16bytes data or more, nothing happened. The write call-back doesn't fire at all.
BLE pdu packet can send 22byte or someting, but the BCM90737 hardware buffer is 16. So I think the maximum data length is up to 16 bytes. Not 15bytes.
And some sample program set 20byte as the write characteristic size. What is the correct size of the data length for one packet?
Show LessHi,
after compile the hello_sensor example in eclipse, I get the following erros:
Field 'adrType' could not be resolved hello_sensor.c /WICED-Smart-SDK/Apps/hello_sensor line 588 Semantic Error
Symbol 'lesmp_pinfo' could not be resolved hello_sensor.c /WICED-Smart-SDK/Apps/hello_sensor line 588 Semantic Error
Field 'lesmpkeys_bondedInfo' could not be resolved hello_sensor.c /WICED-Smart-SDK/Apps/hello_sensor line 588 Semantic Error
Field 'pairingParam' could not be resolved hello_sensor.c /WICED-Smart-SDK/Apps/hello_sensor line 499 Semantic Error
Field 'AuthReq' could not be resolved hello_sensor.c /WICED-Smart-SDK/Apps/hello_sensor line 499 Semantic Error
Symbol 'lesmp_pinfo' could not be resolved hello_sensor.c /WICED-Smart-SDK/Apps/hello_sensor line 499 Semantic Error
But the fashing to the board is possible. But how can I resolve the errors?
Best regards and thanks for you help.
Christoph
Show LessGood afternoon
I need to have a two scenario usage with the BCM2073xS module regarding I2C behavior:
- i2C master to discuss with I2C devices
- disconnected i2c port because an another device will be the master.
As BCM2073xS doesn't support I2C multimaster, do you know if it is possible to desactivate I2C master port after booting (for example at the beginning of the application) ? (if no access to E2PROM are required after the boot process).
thank you
best regards
Show LessHi,
Would someone please explain in which condition that we shall include this library?
i.e. this patch library is included in example 'puart_control' but not in 'hello_client'.
Show LessHi Sir,
The puart_rxCb is an event function and may I ask when is the trigger point to call this callback function?
I do a test to block in the timer and fine timer function, during the block period, the puart_rxCb won't be called.
Show LessI am attempting to run the PUART example with a WICED Sense.
Code compiles fine and builds to device OK. My device enumerates two COM ports: COM5, and COM6.
According to the PUART documentation, I should be connecting to the second COM port (COM6).
Using the PUART windows application, I select COM6 and click Start Device Discovery. But nothing happens...
I've tried using Realterm to see if I can get any data coming through, but nothing.
Does the WICED Sense support the PUART_Control example application?
Thanks,
Justin
Show LessI'm trying to compile libopus (https://www.opus-codec.org/) with the tool chain that is included in the SDK, but I've ran into several road blocks.
Initially I was getting an error due to a missing system call:
"... newlib-1.20.0/newlib/libc/stdlib/exit.c:65: undefined reference ... "
After reading through the newlib documentation I discovered that I have to provide stub methods for the system calls that aren't implemented. After providing the stubs I encountered the error that is currently holding me back:
"configure:7364: checking for stdlib.h
configure:7364: /Users/jcorrea/WICED-Smart-SDK-2.2.0/Tools/ARM_GNU/bin/OSX/arm-none-eabi-gcc -c -g -O2 conftest.c >&5
conftest.c:9:19: fatal error: stdio.h: No such file or directory"
Is there anything special that I need to do to compile this library with the WICED tool chain? Any help is appreciated.
Show LessHello,
SDK:2.1.1
Hardware:Tag board + iPhone
I want to send variable data from client(iPhone) to the tag-board.
I have checked some samples and documents, and I found a description of setting "LEGATTDB_PERM_VARIABLE_LENGTH" in MMP920732SW-AN103-R application note, P12, table2.
Does any body know how to set this setting?
The samples just have the setting function CHARACTERISTIC_UUID128_WRITABLE () for write characteristic, and it need the length information like this.
CHARACTERISTIC_UUID128_WRITABLE (HDLC_VSP_VSP_TX,
HDLC_VSP_VSP_TX_VALUE,
__UUID_VSP_VSP_TX,
LEGATTDB_CHAR_PROP_WRITE_NO_RESPONSE,
LEGATTDB_PERM_WRITE_CMD,
16), ect...
It sets the data length, so the length is always 16 or something even iPhone sent other length data.
I want to like this,
When I sent data
0x00 0x00
then I want to get two byte of 0x00.
When I sent
0x00 0x00 0x00
then I want to get three byte of 0x00.
I changed the setting LEGATTDB_PERM_WRITE_CMD to LEGATTDB_PERM_VARIABLE_LENGTH.
I want to get 16byte data paket, so I can not add a length data in the data.
Show LessHi All,
I was unable to find an exaustive documentation about API function in WICED. Maybe I'm wrong, but is there someone who can tell me where to find it? In the SDK I have a folder with the html documentation that's not covering all the function used in the SDK examples. Thanks.
Raffaello
Show LessHi,
I have found that communication between two 20737S is really limited to roughly 10-20m and I would hope to attach an antenna to it to
extend the range a little bit. Do you have plans to offer an 20737E in the future or are you offering one already?
I hope you can help,
Kilian
Show Less