PSoC™ 4 Forum Discussions
I have a trackpad design requirement. Does PSoC® 4100 supports trackpad design. Since we need to implement X and Y layer.
Why i selected GPIO is since it contains some GPIO.
Please let me know if PSoC® 4100 is the best choise.
Show LessThere is PROJECT #007: BLE PERIPHERAL AND BROADCASTER - CHANGING GAP ROLES sample, it looks like the device can advertise only one role, I wonder if it's possible to do two roles in advertising mode at the same time
- Ble Peripheral: advertising using mac address M1
- Ble Broadcaster: acting as an iBeacon with mac address M2.
Using an app (on the phone) can scan both BLEs (M1, M2) in the same time. if M1 is connected then M2 still broadcasting.
Thanks!
Just out of curiosity...
Disassembled the UART_Bootlader.elf file with arm-none-eabi-objdump -s:
UART_Bootloader.elf: file format elf32-littlearm
Disassembly of section .text:
00000000 <RomVectors>:
0: 00 10 00 20 11 00 00 00 6d 03 00 00 6d 03 00 00 ... ....m...m...
00000010 <Reset>:
10: b508 push {r3, lr}
12: f000 fd9b bl b4c <CyBtldr_CheckLaunch>
16: f000 f9ab bl 370 <Start_c>
Why is the reset vector set to address 0x0000011 instead of 0x00000010?
Also 0x0000036D is not on a 4-byte address boundary...
Show LessHello,
I am now working on a project in which there is a client and up to eight servers from which the client has to read information.
What concerns me is the security aspect of this project. Given that there is no support for more than four devices for the client to bond with we have to use pairing instead of bonding which means that there will be an exchange of keys with every connection, so someone could be reading that sensitive data. Connections will happen constantly.
Another thing is that the servers have no input/output capabilities so the short term keys are always going to be zeroes.
How can I securely exchange information with these two constraints (Bonding limit and no input/output capabilities)? I know it is a long stretch but is there a way to do so?
Both servers and client are BLE 4.1.
Thanks!
Show LessI'm using a CY8C4246AZI-L423 for a project with RS-485 communication (PSoC <-> SN65HVD22D). Realised with UART component V2.5. In normal operation mode everything works fine.
Yesterday I tried to get the firmware update function over RS-485 running.
Step1: This picture shows the normal RS-485 communication includung tx-enable handshake.
Step2: This picture shows the initial bootloader communication between PC an PSoC. PSoc don't handle the tx-enable handshake any more. A firmware update isn't possible.
Now I added some glue logic between the PSoC an the RS-485 transceiver to emulate the tx-enable handshake. I just wanna test if the firmware download runs basically with the UART component V2.5. After I tried to download some firmware - see step3.
Step3: This picture shows the communiacion between PC an PSoC with emulated tx-enable handshake (glue logic). Updating the PSoC fimware is no problem.
Is is possible that the UART component is buggy or do I something wrong? It's curious that in normal operation the tx-enable is served and in bootloader mode not.
Can anybody help me?
Show LessI need a missing pulse detector on a PSOC 4. My Signal is 500ms low and 500ms high. If the Signal is low or high for more than 500ms, the output goes to low.
Is this possible (only with digital blocks / no software) ?
Thanks Andreas.
Show Less