Smart Bluetooth Forum Discussions
Hi:
I use the light dimmable project to develop the bluetooth mesh, I find the wiced_bt_mesh_light_lightness_nvram_id_start in the mesh_setup_nvram_ids(),
I want to know which prameters the nv id have saved .
so I use the wiced_hal_read_nvram API to read the value from the nv id. it seems irregular value。
I want to know if there are some documents to introduce which parameters of the model have been saved into the nvram
thanks
Show LessHello! When using the BLE Proximity Profile, is real (versus predicted) RSSI data used?
The key requirement is being able to read real RSSI data (not predicted data).
Some prelim feedback I have been given is...most, if not all, BLE solutions support reading a RSSI of the local radio and have an api available in the SDK. PSoC Creator or WICED based modules are suggested as they support the Proximity Profile/Service which reads local and remote RSSI data.Link Quality and IQ is subjective and specific per solution. RSSI with Proximity Service is one that would be less subjective as all solutions that support Proximity services would have to has similar RSSI ranges/values for different manufacturers to support.
Show Less
What are exact power consumption of 20732 while:
- pairing
- connecting
- disconnecting
- transmiting at full power
- receiveing at full power
Sincerely,
M.
Show LessHello community,
I'm just wondering here how to do the RADIO RX TEST described in document https://www.cypress.com/file/298091/download without the usage of tools like "mbt".
I'm only able to send RAW HCI hex commands and receive their answers. This already works for the RADIO TX TEST described in the same document.
For RADIO RX TEST there is described, that there should be another event (or something similar) reported which starts with in BT-CoreSpec undefined HCI packet indicator 0x07. The Doc describes it as:
0000 < 07 01 00 00 00 00 00 00 00 1D 03 00 00 1D 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >
With my chip I only get this:
Sending HCI Command:
0000 < 01 52 FC 0E 45 23 01 3A 70 20 E8 03 00 03 01 03 11 00
Received HCI Event:
0000 < 04 0E 04 01 52 FC 00 >
And I do not receive anything more.
Does the tool mbt somehow activate the 0x07 message in background?
Thank you in advance!
Best Regards
Rainer
Show LessIs there a WICED® Wi-Fi™ 101 Video Tutorial manual as described in Chapter. We purchased CY94343WWCD1_EVB kit and going through the demo. Lke to have the manual for reference.
Thanks
_AAO
Show Less
Hello,
I downloaded all possible documentation and tooling i could find related to the CYW20736 chip, but i wasn't able to find the register/memory map for memory mapped I/O and memory. I've been able to find a blog post discussing very high level memory layout, but not the per register level memory map. Could someone point me to the right documentation?
Thank you
Show LessHello,
maybe someone has a hint for me. I try to get the LED to blink on my CYBLE-013025-EVAL.
I downloaded the Wice Smart SDK 2.2.3 and the Platform files for CYBLE_013025_EVAL.
I got my module running with Advertising, but I cannot get the LED to blink.
What I did:
Created the GPIO Config
const BLE_PROFILE_GPIO_CFG myapp_gpio_cfg =
{
/*.gpio_pin =*/
{
GPIO_PIN_LED, // LED GPIO, optional to provide visual effects
-1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1 // other GPIOs are not used
},
/*.gpio_flag =*/
{
GPIO_SETTINGS_LED,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
}
};
Called the bleapp_set_cfg with my gpio function (myapp_cfg was also set to NULL to see if the led_enable flag makes a difference -> It didn't).
bleapp_set_cfg(NULL, 0, (void*)&myapp_cfg, NULL, (void*)&myapp_gpio_cfg, myapp_create);
I called gpio_configurePin(GPIO_PIN_LED / 16, GPIO_PIN_LED % 16, GPIO_OUTPUT_ENABLE, 1); in myapp_create.
I tried bleprofile_LEDOn(); -> LED is off
I tried bleprofile_LEDBlink(250, 250, 100); -> LED is off
Has someone an idea what I can do to get the LED blinking? The PDF I found only mentioned configuring the gpio pin and calling the LED functions.
Best regards,
Tim
Show LessHello,
is there some way to program the CYBLE-013025 without the Wice SDK in production?
I could call the make command via command line, but with this the make is also executed completely.
I only need to flash my previously made hex file together with the BT_DEVICE_ADDRESS to the chip. Does anyone know a better way instead of calling make?
Best regards,
Tim
Show LessHi,
I am working with BCM20737S and I am using an external 32K crystal.
I am able to set the device to deep sleep and keep the clock running. My code follows the rtc_sample code and it is working fine for the basic case.
The workflow of the system regarding the clock creates an issue which I am not sure if I understand correctly.
- So, when the device boots it has a reference time of 2010. Going in and out of deep sleep everything works fine and the time remains correct.
- The system is designed so that the actual time is provided by an external device via the time characteristic. When that happens the time changes
to the current time. The time is set using the rtc_setRTCTime function. So, the correct time is provided to the system after N seconds.
The given time is stored in the NVRAM and will be used as reference time for the next time the system gets out of deep sleep.
- After that when the device goes out of deep sleep and calls the rtc_setReferenceTime the new time is off by N seconds, which is the time the clock was running before
it get the new time. I have to subtract the same N seconds every time a new time is set by the host, after that.
To solve this issue, I store the difference in seconds N and correct the reference time every time a new time is set. This is working but
I am wondering if there is a more straightforward way to reset the rtc_clock so I won't have to go to all this trouble. Maybe, I am missing something obvious here.
Let me know what you think,
Kostas
Show Less