PSoC™ 4 Forum Discussions
Hello,
With reference from bluetooth datasheet given in the PSOC Creator. Scan response data packet is sent from the peripheral device on receiving scan request from the central.
So i want to locate the scan request structure in Central Ble module code or can anyone help with some technical documents on how to send scan request to peripheral.
Show LessI'm using the PSoC CY8CKIT-145-40XX Prototyping Kit. It has a PSoC 4 CY8C4045AZI-S413 IC.
I have been trying all week just to use the tuner application. I have used the example code that was already available through the PSoC creator. I have followed all the steps correctly, even double checked (more than double) that the configuration parameters are the same for both the Tuner and EZI2C.
I have attached the MINIMAL workspace bundle. Any Advice would help. WHAT AM I DOING WRONG?
Show LessHello colleagues,
I would like to use one of your PRoC modules for designing one product and I am wondering how it behaves in case of Relay Attack? Is there any countermeasure which I can implement?
Thanks in advance and regards,
Peter
Show LessFor my current project am using CYBLE-00120011-00 module
I have to transfer 512 Bytes of data from windows application to my custom design board.
For same purpose i am using BLE-UART example project.
but from windows application only receiving 20 bytes of data.
and from my board can send up to 176 bytes of data.
can anyone please help,
Regards,
sagar
Show LessHi All,
I am working on a Cypress BLE device for implementing below requirement:
1. We have same devices "CYBLE-012011-00 31-SMT" on all BLR node.
2. Each of these nodes will have same board schematics and same firmware.
3. Each devices will send custom beacons on certain intervals.
4. Each devices will scan custom beacons.
5. Based on events generated/timer interval one BLE node has to switch to central mode and should be ready to accept connection from other BLE node.
6. Other BLE node can connect to central/server BLE node and request custom data which could be 100 bytes in length.
I have few questions after going through Cypress BLE example and code.
Questions:
1. What type of GAP profile is suited for above requirement?
2. Can we send 90 bytes data at once?
3. Is Dynamic switching between Central and Peripheral role supported? In between we want be in Observer and broadcast mode also to see eligible node for data transfer.
4. Is Day049_BLE_Mesh_Flood is verified for Psoc 4.0 and device "CYBLE-012011-00 31-SMT".
5. I can see in code RESTART_BLE_STACK is done whenever role are switched between Central to Peripheral role. Is this recommended for "CYBLE-012011-00".
Thanks,
Mritunjay
Show LessI am implementing "WDT_P4_Example01" sample program on PROC BLE and the program generates reset after 5 seconds and after power ON red LED turns ON for 200ms since reset is caused by the watchdog timer.
But when I make only one change to program i.e instead of "uint32 interruptCnt = 1u;" if I define it as "uint16 interruptCnt = 1u;" the reset is cause is not due to WDT and red LED doesn't turns ON for 200 ms.
I am using "CY8CKIT-042-BLE" kit with PROC BLE board. I had attached project with single modification as mentioned above please reply.
Show LessHey i'm on the CYBLE-224110-00 with SPI pins set to
MISO = P2.1
MOSI = P3.1
SCLK = P3.4
SS_BLK = P3.5
And I attach a pic of my pin cofiguration of SS_BLK and SCLK.
So what happens is that I put the device to deepsleep and I see a ~180 uSec glitch (starts at Vdd, down to Vss, back to Vdd) whenever I wake up from a timer wake up interrupt. I see this glitch on P3.4 and P3.5 but not P2.1 or P3.1. I don't know if the glitch is occurring on other pins, I have not sampled the other pins yet. ( I tried to manually write(1) to the SS_BLK and SCLK pins right before I sleep but it didn't help solve the glitch.
Anyone have an idea what the hell I'm seeing?
I have a work around right now by putting the device to sleep instead of deepsleep. This seems to solve the glitch I'm seeing.
Sleep code:
SPI_ACCX_Sleep();
UART_DEB_Sleep();
CySysPmDeepSleep();
SPI_ACCX_Wakeup();
UART_DEB_Wakeup();
Hi All,
I am currently working to capture data from a sensor and use a PSoC 4 to transfer the bytes to my computer using SPI and the PSoC SCB UART-- I have attached my current project. Currently, when I upload and run the program, I receive constant hex values of 72 on the CoolTerm serial monitor I am using, regardless of the sensor status. All of the wiring has been configured correctly and the SPI is operating at the correct parameters, so I believe there is a fundamental problem with my coding. I am not sure, but I think I have a basic misunderstanding of transferring bytes over UART.
Any help or nudge in the right direction would be most welcome! Please let me know if more info is needed.
Thanks in Advance!
Show Less