Smart Bluetooth Forum Discussions
Hello,
I'm struggling with the memory allocation using the PolarSSL functions to perform a modular exponentiation with a 3072 bits modulus.
The pool allocator doesn't look to be optimized to such cases (Allocating 384 and 768 bytes).
What is the maximum key size supported for RSA like operations and what would be the way to have them working properly ?
Thank you.
Show LessIn WICED SDK 2.0.1, I use hello_client as application.
I believe that connection event is done by hello_client_interrupt_handler().
Without triggering connection through button or interrupt, I'd like to make it connected.
I put following 2 lines at the end of hello_client_create() .
bleprofile_Discoverablew(NO_DISCOVERABLES, NULL);
blecen_Scan(HIGH_SCAN);
but the connection has not done when hello_client_create() ends.
After 2min 30sec about, conn up happened.
How can I put the board into connected status without button or interrupt event?
Show LessI am using wiced smart v1.1.0.
I want to use cgs.exe to convert cgs file to hex file, the hex file with different BT address, I follow this topic: Two dev boards have same MAC address, and use cgs.exe like this:
cgs.exe -I <output_file_name.hex> -O DLConfigBD_ADDRBase:207321234567 –A 0xFF000000 –B <btp_file.btp> -D <file.hdf> <input_file.cgs>
Before executing cgs.exe, I copy cgs.exe, 20732_EEPROM.btp, ConfigDef20732_aa.hdf to \build\hello_sensor-BCM920732TAG_Q32-rom-ram-Wiced-release , and execute cgs.exe like this:
cgs.exe -I hello_sensor-BCM920732TAG_Q32-rom-ram-Wiced-release.hex -O DLConfigBD_ADDRBase:207321234567 -A 0xFF000000 -B 20732_EEPROM.btp -D ConfigDef20732_aa.hdf A_20732A0-hello_sensor-rom-ram-spar.cgs
Below is console response:
C:\Disk_Driver\Firmware\WirelessModem\BLE\truck\WICED-Smart-SDK-1.1.0\build\hello_sensor-BCM920732TAG_Q32-rom-ram-Wiced-release>cgs.exe -I hello_sensor-BCM920732TAG_Q32-rom-ram-Wiced-release.hex -O DLConfigBD_ADDRBase:207321234567 -A 0xFF000000 -B 20732_EEPROM.btp -D ConfigDef20732_aa.hdf A_20732A0-hello_sensor-rom-ram-spar.cgs
cgs v1.3.0.0094 20131210
Copyright (c) 2012-2013 Broadcom Corp.
Processing cgs files:
A_20732A0-hello_sensor-rom-ram-spar.cgs
...
Error: Duplicate field: command: Adc Driver Configuration, field: Reserved_1
Creating Intel Hex file: hello_sensor-BCM920732TAG_Q32-rom-ram-Wiced-release.hex... failed.
Reason:
ConfigDef20732_aa.hdf(0:0): Error: Duplicate field: command: Adc Driver Configuration, field: Reserved_1
What did that mean?
Show Lesshi,
now, i try to use bcm20737 to connect a humidity sensor.
the humidity sensor format is as following.
could any i2c API access the data?
or is there any more underlying function to access it?
Show Less
We just released WICED Smart SDK 2.1.0 to the Community Website.
SDK 2.1.0 Windows Installer: WICED-Smart-SDK-2.1.0-IDE-Installer
Please refer to changelog.txt for all fixes, additions and improvements included within this release.
The following documents were also just released to support the new SDK:
Manufacturing Bluetooth Test Tool Application Note
Manufacturing Bluetooth Test Tool Application Note (SDK 2.1 and TAG3 Board)
WICED Smart Quick Start Guide (SDK 2.1 and TAG3 Board)
WICED Smart Quick Start Guide (SDK 2.1 and TAG3 Board)
WICED Secure Over-the-Air Firmware Upgrade Application Note (SDK 2.1 and TAG3 Board)
WICED Secure Over-the-Air Firmware Upgrade Application Note (SDK 2.1 and TAG3 Board)
Hi Sirs,
I'm new for WICED Smart developer and want to ask a stupid question.
I check the datasheet of 20732, 736 and 737.
The block diagram, pin definitions and I could not tell what's the difference in the hardware point of view?
Fran
Show LessI have two bcm20732 board, one is BCM920732_TAG, the other is bcm20732s module.
When I use mbt tool to do RF character testing such as "mbt set_tx_freqnecy_arm COM39 1 2402 3", the tag board can return as normal like below:
C:\Disk_Driver\Firmware\WirelessModem\BLE\truck\WICED-Smart-SDK-2.1.0\Tools\mbt\Win32>mbt set_tx_frequency_arm COM39 1 2402 3
Sending HCI Command:
0000 < 01 14 FC 07 00 02 00 00 08 03 00 >
Received HCI Event:
0000 < 04 0E 04 01 14 FC 00 >
Success
But the bcm20732s module is without the "Received HCI Event" like this:
C:\Disk_Driver\Firmware\WirelessModem\BLE\truck\WICED-Smart-SDK-2.1.0\Tools\mbt\Win32>mbt set_tx_frequency_arm COM31 1 2402 3
Sending HCI Command:
0000 < 01 14 FC 07 00 02 00 00 08 03 00 >
What is the reason?
Show LessWhile building the target, I get the following error:
12:08:40 **** Build of configuration Release for project WICED-Smart-SDK ****
"\\\\psf\\Home\\Documents\\WICED\\WICED-Smart-SDK-2.0.1\\WICED-Smart-SDK\\make.exe" hello_sensor-BCM920736TAG_Q32 download
'\\psf\Home\Documents\WICED\WICED-Smart-SDK-2.0.1\WICED-Smart-SDK'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
make: *** No rule to make target 'hello_sensor-BCM920736TAG_Q32'. Stop.
12:08:40 Build Finished (took 313ms)
Any info on what could be the issue and how can it be resolved?
Show LessIf I want to ship my product with BCM2073X chip or module, in order to compliant with BT SIG MAC address regulation, I want to know that whether need to purchase BT mac address which is assigned from BT SIG or any other orgnization?
Show Less