PSoC™ 6 Forum Discussions
text.format{('custom.tabs.no.results')}
Hi,
Me and my company are trying to develop a contactless payment wallet the size of a thick credit card.
What would be the microchip to use for such, considering all it would need to do is interface to unlock the device and with the nfc chip to conduct payment transactions.
Show LessHi, I am using CYBLE-416045-02.
Currently having an issues providing OTA functionality to iOS app, because, after bonding to application, when it jumps to stack and tries to connect, it complains about "Peer removed pairing information".
It happens that iOS tries to pair, but since the Stack and Application has its own checksum exclude areas, they have its own bonding information, so the pairing with stack fails, because bonding information stayed with application, moreover both of them have the same MAC address, and this is what smartphone does not like.
Question - is there an easy way to share bonding keys between the two?
Show LessCan Psoc6 be transplanted to embedded Linux?
Has anyone ported Linux to PSoC6?
Thank you
hi Cypress:
can you help to provide the CY8CKIT-062S2-43012 with CY8CKIT-028-TFT Demo with emwin? i use emWin_OLED_FreeRTOS demo but it can't work to show the emwin ? tks;
Show LessI'm running the PSoC 63 and I'm attempting to blow eFuse protections for my application to enable to full secure boot flow and it seems to NOT boot into my first app (classic). I'm running the same code before blowing the eFuse bits to ensure the signature verification flow works (from flashboot perspective) and everything seems fine. But after I run our script to blow eFuse it doesn't boot up. I set the protection as "Secure with debug" so if I attach to the M0+ core to attempt to gather clues, it looks like the PC is somewhere within the ROM code address space (I'm assuming). So I'm curious what debugging steps I have available to diagnose what the error is or if you could provide some guidance on what could possibly be going wrong? See screeshot of CPU registers.
Show Less
Hello
I am compiling a project that incorporates DFU via Bluetooth. The Project compiles successfully with no problems at all. Now, I am merging this project with the original project I am working on, however I am getting this error while merging those files
dfu_mdk_common.h and dfu_mdk_symbols.c
arm-none-eabi-gcc.exe -mcpu=cortex-m0plus -mthumb -I. -IGenerated_Source\PSoC6 -IGenerated_Source\PSoC6\pdl\cmsis/include/ -IGenerated_Source\PSoC6\pdl\devices/psoc6/include/ -IGenerated_Source\PSoC6\pdl\devices/psoc6/include/ip/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/device/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/efuse/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/flash/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/gpio/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/ipc/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/lvd/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/profile/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/prot/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/scb/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/sysanalog/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/sysclk/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/sysint/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/syslib/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/syspm/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/systick/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/tcpwm/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/trigmux/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/wdt/ -IGenerated_Source\PSoC6\pdl\middleware/ -IGenerated_Source\PSoC6\pdl\middleware/em_eeprom/ -IGenerated_Source\PSoC6\pdl\utilities/ -Wa,-alh=.\CortexM0p\ARM_GCC_541\Debug/dfu_mdk_symbols.lst -g -D DEBUG -D CY_CORE_ID=0 -D CY_PSOC_CREATOR_USED=1 -D CYBLE_416045_02 -Wall -ffunction-sections -ffat-lto-objects -Og -c dfu_mdk_symbols.c -o .\CortexM0p\ARM_GCC_541\Debug\dfu_mdk_symbols.o
dfu_mdk_symbols.c:29:7: error: expected '(' before 'void'
__asm void cy_DFU_mdkAsmDummy(void)
How to solve this problem?
Thank you
EDIT: I am having an overlapping problem now
.\CortexM4\ARM_GCC_541\Debug\App1_merged.elf.tmp: Merge error: section at 0x100FFA00 from .\CortexM4\ARM_GCC_541\Debug\App0.elf overlaps section at 100FFA78 from .\CortexM4\ARM_GCC_541\Debug\App1.elf
The command 'post_build_core1.bat' failed with exit code '1'.
dfu_cm0p.Id for Both App0 and App1
flash_app0_core0 (rx) : ORIGIN = 0x10000000, LENGTH = 0x40000
flash_app0_core1 (rx) : ORIGIN = 0x10040000, LENGTH = 0x40000
flash_app1_core0 (rx) : ORIGIN = 0x10090000, LENGTH = 0x40000
flash_app1_core1 (rx) : ORIGIN = 0x100D0000, LENGTH = 0x40000
em_eeprom (rx) : ORIGIN = 0x14000000, LENGTH = 0x4000
flash_storage (rw) : ORIGIN = 0x100C0000, LENGTH = 0x1000
flash_boot_meta (rw) : ORIGIN = 0x100FFA00, LENGTH = 0x400
dfu_cm4.Id for Both App0 and App1
flash_app0_core0 (rx) : ORIGIN = 0x10000000, LENGTH = 0x40000
flash_app0_core1 (rx) : ORIGIN = 0x10040000, LENGTH = 0x40000
flash_app1_core0 (rx) : ORIGIN = 0x10090000, LENGTH = 0x40000
flash_app1_core1 (rx) : ORIGIN = 0x100D0000, LENGTH = 0x40000
em_eeprom (rx) : ORIGIN = 0x14004000, LENGTH = 0x4000
flash_storage (rw) : ORIGIN = 0x100C0000, LENGTH = 0x1000
flash_boot_meta (rw) : ORIGIN = 0x100FFA00, LENGTH = 0x400
The project includes BLE and EEPROM too. It was already working, but with different LENGTHs
Show LessTo work around my issues with Cy_SCB_SPI_Transfer() not working for large blocks of data at 4x oversampling, I am going to implement a DMA route for those exchanges.
I understand the overall DMA scheme of things: you set up a DMA transfer from a source buffer to the SPI's Tx fifo. But... Let's say I'm sending a block of 1000 data bytes, but the SPI Tx fifo is only 128 bytes long. What keeps the DMA transfer from overrunning the Tx fifo?
Thanks,
Ed H.
Show LessHello.
I know that the PSoC6 BLE support the Bluetooth 5.0.
The Bluetooth 5.0 support long range(+ 20 dBm)
Does the lineup of the PSoC6 BLE have long range product?
Thanks and Best regards.
Glenn.
Show LessRecently I was working on a project to display multiple bitmaps on the TFT screen of CY8CKIT-062-WiFi-BT. But soon I realized that the converted images do take a lot of space on the flash memory. Hence wanted to write the images on the FRAM and then retrieve it and the application note CE225248 fits perfectly in this use-case. I tried a lot but the example is not working on the WiFi-BT kit. The TFT display is just plain blank displaying nothing and also debugging works well without any hard faults. I'm using PSoC creator 4.3
Please Help.
Show LessI have implemented an encrypted bootloader using PSoC63 and referring to the sample source project in CE222802.
In addition to this, I would like to support OTA.
Is there a sample BLE Upgradable Stack Bootloader project that supports encryption?
Show Less