I am working on the CYW920721B2EVK-02 where I have set up a Bluetooth connection, where I can bond with up to 8 devices. I now want to make an automatic connection with the first bonded device available, but I can't get it to work.
Can anyone tell me if there is a way to make this possible, and if so, how?
I am using Capsens module V4.0.
I am using Widget Buttons for my application In this, I found that sometimes it detects the false senses means it sens when I do not even touch the button..
In my application I use Enable all 13 buttons using CapSense_SetParam(CapSense_WDGT_ENABLE0_PARAM_ID, 8191); and after complete the process I disable only 12 buttons CapSense_SetParam(CapSense_WDGT_ENABLE0_PARAM_ID, 4096); because I use the 13th button for touch detection only this performs at every operation.
Why this false detection is happening? is it because of the calling CapSense_SetParam(CapSense_WDGT_ENABLE0_PARAM_ID, 8191) ?
Dear WiFi Experts,
I have the problem with the 64-bit version of wl tool with the lack of libnl version information. I have tried several wl binaries published within this board but most of them are 32-bit and behave erratically or simply does not run at all.
My platform is Raspberry Pi 4B with BCM43455 module, running 64-bit Ubuntu 20.04.2 LTS.
One of the 'wl' variants published here is 64-bit and it appears to run but it complains about the unknown libnl version:
root@rpi:/usr/local/bin# ./wl ver
./wl: /lib/aarch64-linux-gnu/libnl-3.so.200: no version information available (required by ./wl)
./wl: /lib/aarch64-linux-gnu/libnl-genl-3.so.200: no version information available (required by ./wl)
wl0: Mar 12 2018 16:18:54 version 7.45.222 (RPI-PRKE) (r683458 CY WLTEST) FWID 01-35ee9694
Some 32-bit versions of wl also want to run and even do not complain about the libnl version, but after several cycles of tests (usually 'pkteng_start tx' sequence of commands) the wl tool refuses to work. Usually it reports that "wl driver adapter not found", regardless of the wl arguments. Even the simplest wl commands (like out or down) produce the same message, despite it worked many times before. It rather looks like the cross-compiled binaries or libraries mismatch with my platform, than a real radio problem.
Maybe my mfg firmware is too old? I only have its 32-bit version for Raspberry Pi 4:
root@rpi:/usr/local/bin# ls -l /usr/lib/firmware/brcm/brcmfmac43455-sdio.bin
-rw-r--r-- 1 root root 566600 Dec 10 19:52 /usr/lib/firmware/brcm/brcmfmac43455-sdio.bin
Would you be so kind and help me obtain a proper wl version for my platform?
The platform details follow:
root@rpi:/usr/local/bin# uname -a
Linux rpi 5.4.0-1030-raspi #33-Ubuntu SMP PREEMPT Wed Feb 24 11:20:11 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
root@rpi:/usr/local/bin# cat /proc/version
Linux version 5.4.0-1030-raspi (buildd@bos02-arm64-015) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #33-Ubuntu SMP PREEMPT Wed Feb 24 11:20:11 UTC 2021
root@rpi:/usr/local/bin# cat /etc/os-release
VERSION="20.04.2 LTS (Focal Fossa)"
PRETTY_NAME="Ubuntu 20.04.2 LTS"
I will highly appreciate your help 🙂
Now, I can't reset CYW920719Q40EVB-01 by CyBluetool software. What's the problem will be?
I can Build & Download Applications via WICED Studio. Is it causing the board can't be connected with cybluetool after downloading a program by WICED Studio?
What should I do?
In case of PSoC6, we can create a custom BSP in two ways.
It's a CLI and Build Target method.
Both were able to build without error.
In case of PSoC4000S, in either method, if TARGET = CustomName of Makefile is set, a build error will occur.
Is PSoC 4000S still unable to create a custom BSP?
I have an application where, if I am in Bootloader mode and nothing has happened for about 60sec, I want to go into Hibernate mode (my device is battery powered, and I want to ensure that it doesn't sit in Bootloader mode indefinitely if something goes wrong and then drains my battery).
I can use a Timer to force the Bootloader into Hibernate mode, but I can't seem to get it to come back out of Hibernate using an interrupt on an external GPIO.
I am using a similar arrangement, using a signal on a GPIO, in the Application code to boot the device out of Hibernate mode, and this works perfectly. But it doesn't seem to work when in Bootloader mode.
Has anyone tried this? Is there something about being in Bootloader mode and then going into Hibernate that would prevent the 'exit from Hibernate via GPIO trigger' functionality from working?
I have used the latest Firmware 1.2.27 (for CYBT-343026-01) below to verify the operation of BLE GAP Central.
I refer to [3.5 GAP Central Examples] in the User Guide.
I have confirmed the operation of [Example 2: Start 5-second active scan with duplicate filtering enabled], but the scan response packet reports the same data as advertise.
For the environment we are checking, we have prepared two CYBT-343026-01. (One is Central, the other is Peripheral)
Since Factory reset (/ RFAC) is performed, the settings are in the initial state.
Are there any other settings you need?
UVC based application for FX3 is created based on the framework of AN75779. 24bit GPIF is used(D23:D0) . image is 800*600. Pixel depth is 24bit/pixel, i.e. 3Byte/pixel. Since it is 24bits/pixel raw image, GUID for RGB888 is used for media type and RGB888 will be debayered in host. DMA buffer keeps the same: 16kB, 4 counts, 2 sockets. Only change the GPIF bus to 24bits, LD_DATA_COUNT, LD_ADDR_COUNT to 5455. However, it can't stream.
But according to KBA226722,
S= 800*600*3= 1,440,000 byte,
F= int(S/(16384-16))= 1440000/16368 = 87
P= fraction of S/(16384-16) * 16368 = 0.976594*16368 = 15984
It should be working.
I noticed that in KBA226722 , it mentioned in item 5 "If exact line data (i.e nothing is appended at the end of the line data) is intended to be sent to the Host, then make sure that line size in bytes is divisible by GPIF bus width (in bytes)." I don't quite get this point.
Help is needed on the proper setting of DMA configuration and GPIF state machine data and address count value.
Thanks in advance
Dear Cyprerss/Infineon Support,
Wrong configuration for TX-Enable pin (RS-485 Support) is generated using the Device Configurator 3.0.
I had a problem using the configuration generated with that tool. If I select a TX-Enable pin it generates a configuration like this:
#define ioss_0_port_3_pin_3_HSIOM HSIOM_SEL_GPIO
But it must be like this to have a signal coming from CTS pin:
#define ioss_0_port_3_pin_3_HSIOM HSIOM_SEL_ACT_6