PSoC™ 6 Forum Discussions
Hi
What is the data source name for channel0 in the ADC to use in configuring the DMA ?
I found several options in the ADC.h file , but not sure which register or macro to use!
thanks
Show Less
I used PSoC Creator4.4 to build a project named Chip Whisperer, and a build error occurred. not able to resolve it. attached is the image of the error am i am getting and project file.
How to solve this problem? Thank you!
Show LessHi
I am trying to configure pin-2 on GPIO port-10 to have an interrupt at both rising and falling edges.
I learnt that the regular method using the pin and interrupt PDL can respond to either of the edges as described in:
https://community.infineon.com/t5/PSoC-4/GPIO-interrupt-on-any-edge/m-p/100797
I am attempting to use the Global Signal method described in the previous link. However, I failed to setup the ISR steps properly.
Usually, we link the ISR to the interrupt source. The callback function is named "SD_CD_ISR()" , but I could not find the name of the calling block, in my case, it is the "GlobalSignal_1"
Cy_SysInt_Init( &-------_cfg, --------);
NVIC_EnableIRQ(--------_cfg.intrSrc);
my questions:
1. How can I link the ISR callback function to the interrupt source ?
2. also, what command shall I use to detect the pin for the interrupt source ?
3. and what command to use to clear the interrupt ?
thanks
Show Less
I'm using PSoC Creator to program a PSoC6 BLE Module dev kit (Cy8CPROTO-0630BLE). Part of my application involves writing a setting via a writeable characteristic which is then used to generate internal settings to be stored in NVM. BLE is configured in Dual Core mode and my application is running on the M4, the M0+ is not doing anything other than BLE stuff.
I've tried using emEeprom API and Cy_BLE_StoreAppData() but both appear to have the same issue, causing the program to enter the FaultHandler. In both cases the fault appears to happen when setting the IPC flag, callstack:
Cy_SysLib_ProcessingFault() Generated_Source\PSoC6\pdl\drivers\peripheral\syslib\cy_syslib.c 472 0x10085900 (All)
Cy_SysLib_FaultHandler(const uint32_t * faultStackAddr = 0x80474d0) Generated_Source\PSoC6\pdl\drivers\peripheral\syslib\cy_syslib.c 444 0x100858EC (All)
UsageFault_Handler() gcc/startup_psoc6_01_cm4.S 455 0x1008036A (All)
<signal handler called>() ?????? ?????? 0xFFFFFFF9 (All)
Cy_IPC_Sema_Clear(uint32_t semaNumber = 4294967289, _Bool preemptable = 16) Generated_Source\PSoC6\pdl\drivers\peripheral\ipc\cy_ipc_sema.c 307 0x10082C4C (All)
Cy_Flash_SendCmd(uint32_t mode = 0, uint32_t microseconds = 2580) Generated_Source\PSoC6\pdl\drivers\peripheral\flash\cy_flash.c 443 0x08024D88 (All)
Cy_Flash_StartErase(uint32_t rowAddr = 269005312) Generated_Source\PSoC6\pdl\drivers\peripheral\flash\cy_flash.c 915 0x10082546 (All)
Cy_Flash_StartWrite(uint32_t rowAddr = 269005312, const uint32_t * data = 0x80475a4) Generated_Source\PSoC6\pdl\drivers\peripheral\flash\cy_flash.c 829 0x1008246A (All)
WriteRow(uint32_t rowAddr = 269005312, uint32_t * rowData = 0x80475a4, cy_stc_eeprom_context_t * context = 0x8028650 <ANIM_EEPROM_context>) Generated_Source\PSoC6\pdl\middleware\em_eeprom\cy_em_eeprom.c 985 0x1008A900 (All)
Cy_Em_EEPROM_Write(uint32_t addr = 0, void * eepromData = 0x8027c54, uint32_t size = 160, cy_stc_eeprom_context_t * context = 0x8028650 <ANIM_EEPROM_context>) Generated_Source\PSoC6\pdl\middleware\em_eeprom\cy_em_eeprom.c 549 0x1008A5DC (All)
nvm_update() haptics.c 221 0x10081424 (All)
HostMain() host_main.c 456 0x10081B56 (All)
main() main_cm4.c 73 0x10080386 (All)
I've found some similar issues by searching the forums but nothing that appeared to be the exact same, mostly it was a DeepSleep issue or possibly a clock change issue when writing flash? I tried the native Cy_BLE_StoreAppData() API function too, hoping that would play better with the BLE Stack but I had the exact same issue. I did try (unsuccessfully) to protect the flash write using:
if(cy_ble_pendingFlashWrite != 0u) return;
<Flash Write>
return
and
while (CY_IPC_SEMA_SUCCESS != Cy_IPC_Sema_Set(CY_BLE_SEMA, false)){}
<Flash Write>
while (CY_IPC_SEMA_SUCCESS != Cy_IPC_Sema_Clear(CY_BLE_SEMA, false)){}
Show Less
I bought a CY8CKIT-062S4 kit , found the controller is CY8C6244. But on the website product search , the closest I can find is CY8C6245. Are they same? or where I can find the CYC6244 Datasheet?
Show Less
I used PSoC Creator4.4 to build a project named Chip Whisperer, and a compiler error occurred. The error is as follows collect2.exe: error: ld returned 1 exit status
The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.
below is the project file
How to solve this problem? Thank you!
Show LessCan CY8CKIT-002 be used to Flash Code onto CW308T-PSOC62 ( Chip Whisperer Target Board).
Kindly let me know if this is possible.
Thanks and Regards ,
Niharika
Show LessHi
I have a pin defined as "SD_CD" (sd-card CD signal), and at one point, it is connected to (P10_2_PORT, P10_2_NUM).
I am writing a library function that would be passed the signal name (SD_CD) and I need to fetch the port and pin name (P10_2_PORT, P10_2_NUM) and perform action on that pin, for example: CY_GPIO_Read(P10_2_PORT, P10_2_NUM)
How would I do this ?
thanks
Show Less
we are working on the Smart Lock project using the Matter protocol or CHIP
I am trying to connect the PSOC 6 with matter protocol/ CHIP software loaded and the Raspberry pi wifi/zigbee interface
not connecting
Matter protocol buildwithmatter.com
i followed the docs provided in the /connectedhomeip/examples/lock-app/P6/Readme.md
I executed the : zcl OnOff On 1234 1 0 ---- command
not connecting , below is the error message
Please reply me the possible solution.
----------------------------------------------------------------------------------------------------------------------------------------------------------
chip-device-ctrl > zcl OnOff On 1234 1 0
[1637573653.279080][9954:9960] CHIP:DL: Avahi resolve failed
[1637573653.279196][9954:9960] CHIP:DIS: Node ID resolved failed with ../../src/platform/Linux/DnssdImpl.cpp:692: CHIP Error 0x000000AC: Internal error
[1637573653.279257][9954:9960] CHIP:CTL: Error resolving node id: ../../src/platform/Linux/DnssdImpl.cpp:692: CHIP Error 0x000000AC: Internal error
Failed to update node address: 172
^Z[1637574457.431856][9954:9954] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-zQ6w1Q)
[1637574457.433052][9954:9954] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1637574457.433175][9954:9954] CHIP:DL: NVS set: chip-counters/boot-reason = 5 (0x5)
[1637574457.433553][9954:9954] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-mnlqAQ)
[1637574457.434501][9954:9954] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1637574457.434610][9954:9954] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1637574457.434666][9954:9954] CHIP:DL: Inet Layer shutdown
[1637574457.434892][9954:9954] CHIP:DL: BLE shutdown
[1637574457.434957][9954:9954] CHIP:DL: System Layer shutdown
pure virtual method called
terminate called without an active exception
Aborted (core dumped)
(python_env) ubuntu@ubun
Show Less
Hi,
Due to lack of stock CY8C6247BZI-D34, new boards came out with CY8C6247BZI-D54 and am figuring out firmware compatibility, as by default JTAG ID is different, and cyacd2 also fails.
From the data-sheet it looks like the -D54 brings the crypto block in addition to what -D34 has, however hex file is different all over when recompiled for D54.
So I wonder do you think the same firmware can run on both CPU (and not using crypto at all) or there are more "fine details" making this impossible?
Kind regards,
Uros