PSoC 6 MCU

I have an Psoc63 as BLE 5 central and three PSoC 4200 as BLE 4.2 peripheral. After a successful discovery from central using whitelist I try to connect to one of the three peripheral using his address.  Unexpectedly the central was connected with a peripheral with different address!!!!! Also I try an unexisting address and again it was connected with a random peripheral with different address. Maybe the issue arise from the BLE 4.2 peripherals.

I will appreciate your help to this

Hi

I am using PSoC-6 as SPI slave to send data to master (PC).

Description of Cy_SCB_SPI_WriteArrayBlocking() says: When in the slave mode, writing data into the TX FIFO does not start an SPI transfer. The data is loaded in the TX FIFO and will be sent to the master on its request.

Does the PSoC slave SPI sends data once it receives the clock from the bus master ? or does it respond when the master asserts the slave_select ?

thanks

We are using CY_BLE_EVT_GAP_DEVICE_DISCONNECTED to know if the peripheral got disconnected. On CY_BLE_EVT_GAP_DEVICE_DISCONNECTED we perform connection cleanup, but we noticed on one time the peripheral disconnected but it seems like we missed or didn't get CY_BLE_EVT_GAP_DEVICE_DISCONNECTED.

Is it expected not to get CY_BLE_EVT_GAP_DEVICE_DISCONNECTED event when device disconnect? Is there way to manually check if BLE stack properly disconnected?

I'm looking to interface external memory with one of the PSoC 6 chips. Our application has large storage requirements (to the tune of around 2-4 gigabytes), so SPI NAND is off the table. Since our use case needs bluetooth and possibly USB, we were looking at the PSoC 63 line, but these chips don't seem to support e.MMC memory, which has raised a few questions?

Is there a (relatively) easy way to interface with raw unmanaged NAND using the PSOC 6 line, or to use e.MMC with PSoC 63? Alternatively, is anyone familiar with any chips that could serve as an intermediary SPI Controller to go between a raw NAND chip and the PSoC MCU, or any other way to work around this? 

The PSoC 62 chips seem to have support for SDHC communication, but to use bluetooth and USB I believe we would need one of the CY8C624A/8 chips with two SDHC interfaces. 

Would appreciate any insight on this, as we'll otherwise need to move away from the PSoC chips and start looking at alternatives.

Hello: I have build a downloadable application to be downloaded by a bootloader application over BLE.

Using the CySmart running on PC with dongle I am able to see my bootloader and select it.  Next click firmware update and select my .cyacd2 file to be downloaded.  All steps show OK in the dialog box until Transfer firmware image, then I get this error. see attached. Can anyone tell me how to fix this issue.  Note: both the bootloader and downloadable app were built on the same PSoC creator with the same settings for both projects.

Thanks Brian  

I am following "Snippet 2: PDM/PCM Asynchronous Receive" from the link below:

https://cypresssemiconductorco.github.io/psoc6hal/html/group__group__hal__pdmpcm.html

The pdm_pcm_event_handler never gets called but when I comment out the line below it starts working.

Hi，

    将USB CDC code example工程修改，将工程下载到自定义的使用CY8C624AAZI-S2D44芯片的板子中，将usb连接到电脑端，可以识别到一个设备：CDC Code Example，但是显示没有安装驱动，从例程文件目录下的win_drv安装驱动，提示安装驱动时出现错误，请问这种情况应如何处理？需要如何才能获得正确的驱动文件？工程请参考附件。

I used PSOC Creator and the examples provided PSOC6 DFU app0 and app1, then change the device to CYBLE416045-2. I get the following error when using the Bootloader Host program trying to upload app1

The bootloader reported error 'The flash row is not valid for the selected array