AIROC™ Bluetooth Forum Discussions
Hi,
We are using a CYBT-343026-01 (with CYW20706) for a customer project and use ModusToolbox V2.4.0 with BTSDK Release V3.2.0 to develop our own module software.
One of the customer requirements requests to enable adjustment of the TX Output Power setting of the Link and/or Advertisment. We use the functions as described on page "Configuring Transmit (Tx) Power on CYW20706 Chip -... - Infineon Developer Community" to do that. However, the functions are only executed after the value used for TX output power value was previously set by a custom command and sequentially stored in the NVRAM. After this one time procedure, the value in the NVRAM will be read out and used after each boot up sequence of the module.
Due to a mistake, we did not particularly set the "max_pwr_db_val" in "wiced_bt_cfg_settings_t". We also didn't get any errors or warnings so it would pop in the eye during the build process. So for us it is not defined, what the value of "max_pwr_db_val" is.
As the customer already did some measurements and he wants to evaluate the impact on the measurements, we would like to know what is the default setting of the CYW20706 if no "max_pwr_db_val" was set. If there is no "default" value in the SDK , maybe due to configuration dependency (cgs or hdf-file), where can i identify the correct setting in the files to read out the default setting of the TX power settings.
Thanks in advance!
Bernd
Show LessHello Infineon Support team
We have developed an application for CYW920721M2EVK-02(Chip:CYW20721B2KWB9G) using ModusToolBox.
However our actual adoption chip is CYW20721B2KUMLG. In this case, we should do porting our application from CYW20721B2KWB9G to CYW20721B2KUMLG.
Please tell us the way to the porting using ModusToolBox? (I guess Makefile needs any modification.)
Thanks,
Tayo
The "Basic device firmware upgrade (dfu)" example ( https://github.com/Infineon/mtb-example-psoc6-dfu-basic ) does not work when compiled in Release mode.
Steps to repro:
- use ModusToolbox 2.4 (does not appear on 3.0)
- Create "New Application" -> "CY8CPROTO-062-4343W" -> "Basic device firmware..."
- Modify Makefile: "CONFIG=Release"
- Modify Makefile: "TRANSPORT_OPT=USB_CDC"
- make erase
- make -j program
Expected behavior:
- After programming the device, the device should enter into Bootloader mode.
Actual behavior:
- Device does not leave "reset" state... not sure what's happening TBH.
- But if I press the "reset" button, then the device will boot, and this time it will enter into Bootloader mode.
Observations:
- When compiled in Debug mode it works Ok.
And you'll notice that the
Show LessHi,
I am working with PSoC6 (CYBLE-416045), I want to use the Bluetooth functionality. I have a running code, which I want to test with the CySmart app - I tried the Cypress BLE Beacon which is available on google play– but I can’t connect to the PSoC6. The PSoC6 bluetooth is visible on my smartphone, but not on the app.
Is the app out of function, if so, is there any alternative?
Show LessHW: just get CYW920820M2EVB-01
SW: install ModusToolbox-2.4
lightblue on phone can find this device.--- the board works properly.
Download and build HAL_PUART with no problem.
issue met when try to download the HAL_PUART image:
Started by GNU MCU Eclipse
Open On-Chip Debugger 0.11.0+dev-4.3.0.1746 (2021-09-16-07:59)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 10000 kHz
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
cortex_m reset_config sysresetreq
force hard breakpoints
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : Using CMSIS-DAPv2 interface with VID:PID=0x04b4:0xf155, serial=091E0F1D03201400
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : KitProg3: FW version: 2.30.1155
Info : KitProg3: Pipelined transfers enabled
Info : VTarget = 3.000 V
Info : clock speed 10000 kHz
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: DAP 'CYW20820A1.cpu' initialization failed (check connection, power, transport, DAP is enabled etc.)
Info : CYW20820A1.dap: powering down debug domain...
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Warn : Failed to power down Debug Domains
"
question:
Do i have to set mode to "kp3-daplink"?
I fail to set mode to "kp3-daplink" and can set to other mode with no problem.
"Info: Start API initialization
Info: Connected - KitProg3 CMSIS-DAP BULK-091E0F1D03201400
Info: Hardware initialization complete 534 ms
Info: Disconnected - KitProg3 CMSIS-DAP BULK-091E0F1D03201400
Info: Connected - KitProg3 CMSIS-DAP BULK-091E0F1D03201400
Info: Disconnected - KitProg3 CMSIS-DAP BULK-091E0F1D03201400
Info: Connected - KitProg3 CMSIS-DAP BULK-091E0F1D03201400
Error: Wait for device DAPLink connect is timed out
Mode switch on 'KitProg3 CMSIS-DAP BULK-091E0F1D03201400' device failed.
"
"
$ ./fw-loader --mode kp3-bulk
Cypress Firmware Updater, Version: 3.3.0.1370
(C) Copyright 2018-2021 by Cypress Semiconductor Corporation (an Infineon company)
All Rights Reserved
Info: Start API initialization
Info: Connected - KitProg3 CMSIS-DAP BULK-091E0F1D03201400
Info: Hardware initialization complete 573 ms
Mode switch completed successfully
"
Show Less
My device is a Central that connects to a peer.
I am using CySmart to enable notifications.
It writes all relevant characteristic descriptors to enable notification with value 0x01. And indeed all notification work fine.
But when I look at CySamrt logs, I see that the read of some of the descriptors is 0x00.
Again, I do get notifications from the ones I read zero. But why do they read zeo?
What am I missing?
Show LessHello,
Can someone please explain how wiced_memory_allocate() allocates the memory?
I tried wiced_bt_create_pool() to create some pools and then checked using wiced_bt_get_buffer_usage(), but the pools stats don't change no matter how much I allocate or free using wiced_memory_allocate().. Where does the memory come from and where can I check how much memory I have left? Can I modify the size of the "dynamic memory"? And/or how I am supposed to use the wiced_memory_allocate()?
Thanks,
Jakub.
Show LessHi all,
I use function "wiced_bt_gatt_send_discover" to discovery characteristic_declaration of a service, but no event "GATT_DISCOVERY_RESULT_EVT" hanppened,No matter how the parameters change;
Please help.
type = GATT_DISCOVER_CHARACTERISTICS;
memset(¶m, 0, sizeof(param));
if (uuid != 0)
{
param.uuid.len = LEN_UUID_16;
param.uuid.uu.uuid16 = uuid;
}
param.s_handle = 0;
param.e_handle = 0xffff;
status = wiced_bt_gatt_send_discover(conn_id, type, ¶m);
return status;
Please guide me how to use it correctly ,thanks!
Show LessHi,
We are using the cybt-353027-02 module to build a headset. When listening to music from some phones there is a regular crackling sound. It is about once every four seconds.
Most phones work ok and if I use another headset the "bad" phones sound ok too.
This post seems to have a similar problem, https://community.infineon.com/t5/Studio-Bluetooth/a2dp-periodic-audio-click-with-ios/td-p/332342
The suggested solution there is to call a function called BTM_SetAfhChannelAssessment, but that function is not available for me.
Hello,
I cannot find any project files nor dev tools for Cypress CYW20730.
There is also written in the datasheet, that it "CYW20730 is a Bluetooth 5.1-compliant".
Was that an update in the series of the previous, Bluetooth 3.0 version?
Kind regards
Show Less