PSoC™ Creator & Designer Forum Discussions
Will I need to have a special terminal to show the data I have in SPIS?
Hi,
We use PSoC Creator version 4.2 now.
We needed "Enable wakeup form Sleep Mode" feature.
So, I tried to assign pins using I2C(fixed),
Both P12[0:1] and P12[4:5] are listed as I2C[0].
I confirm for the PSoC 5LP data sheet,
P12[0:1] is I2C1
P12[4:5] is I2C0
I reported it because I think it is misdescription in PSoC Creator.
Regards,
Show LessI am working on a PSoC 5LP realted project, for a specific reason i need to use Miniprog3 to program/ debug the 5LP device. It was working fine before i replaced the device driver with libusb, now i am unable to use it because PSoC creator is not recognizing this device even after changing it.
I have attached few images of device manager how its visible in the system when its working and how its listed in the system when its not working, can any body please help me in resolving this issue.
One thing i observed from the below image is,
---> when its working its listed at Universal Serial Bus Controllers.
---> when its not working its listed at Universal Serial Bus Devices.
1. Device manager image when its working fine.
2.Device manager image when its Not working.
3. PSoC creator port recognition issue.
Show Less
The practice is: on same chip. I will send data from SPIM and read data back from SPIS.
I know SS line is controlled by SPIM, only when SPIM Tx FIFO NOT EMPTY, SS line will go low and allow transmission from SPIM to SPIS.
By default, it will force the SPIS "Interrupt on RX FIFO Not empty" to be on. After one byte is send from SPIM into SPIS RX FIFO , interrupt will be triggered, SPIS Rx will read data in Rx FIFO and move it into SPIS Rx Buffer, then SPIS Rx FIFO is empty now. All other processes are blocked during this interrupt.
My question is:
Now I am sending 10 bytes using SPIM_writeData(), I want slave to send back data starting from the 6th charater it receives in Rx Bxffer.
in the SPIS_Rx_Not_empty ISR, in /* User code required at end of ISR (Optional) */ section, if I add SPIS_Write_data ('a' ) in it, why I cannot send data back to master?
Simon
Show LessHello,
I am using PSOC creator for PSOC 5LP and I need to connect analog inputs to two components but I am getting errors from the compiler.
How do I overcome this?
Show Less我在 PSOC4.2 中编译时,遇到如下错误
arm-none-eabi-gcc.exe -mcpu=cortex-m0plus -mthumb -I.\include -I.\rt-thread\include -I.\rt-thread\components\finsh -I.\rt-thread\libcpu\arm\cortex-m4 -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/crypto/ -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/trigmux/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/wdt/ -IGenerated_Source\PSoC6\pdl\utilities/ -Wa,-alh=.\CortexM0p\ARM_GCC_541\Debug/cy_device.lst -g -D DEBUG -D CY_CORE_ID=0 -D CY_PSOC_CREATOR_USED=1 -D CY8C6247BZI_D54 -Wall -ffunction-sections -ffat-lto-objects -Og -c Generated_Source\PSoC6\pdl\drivers\peripheral\device\cy_device.c -o .\CortexM0p\ARM_GCC_541\Debug\cy_device.o
arm-none-eabi-gcc.exe -mcpu=cortex-m0plus -mthumb -I.\include -I.\rt-thread\include -I.\rt-thread\components\finsh -I.\rt-thread\libcpu\arm\cortex-m4 -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/crypto/ -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/trigmux/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/wdt/ -IGenerated_Source\PSoC6\pdl\utilities/ -Wa,-alh=.\CortexM0p\ARM_GCC_541\Debug/retarget.lst -g -D DEBUG -D CY_CORE_ID=0 -D CY_PSOC_CREATOR_USED=1 -D CY8C6247BZI_D54 -Wall -ffunction-sections -ffat-lto-objects -Og -c Generated_Source\PSoC6\pdl\utilities\retarget_io\retarget.c -o .\CortexM0p\ARM_GCC_541\Debug\retarget.o
arm-none-eabi-as.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/crypto/ -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/trigmux/ -IGenerated_Source\PSoC6\pdl\drivers/peripheral/wdt/ -IGenerated_Source\PSoC6\pdl\utilities/ -alh=.\CortexM0p\ARM_GCC_541\Debug/context_gcc.lst -g -W -o .\CortexM0p\ARM_GCC_541\Debug\context_gcc.o rt-thread\libcpu\arm\cortex-m4\context_gcc.S
rt-thread\libcpu\arm\cortex-m4\context_gcc.S: Assembler messages:
rt-thread\libcpu\arm\cortex-m4\context_gcc.S:110: Error: selected processor does not support `vstmdbeq r1!,{d8-d15}' in Thumb mode
rt-thread\libcpu\arm\cortex-m4\context_gcc.S:119: Error: thumb conditional instruction should be in IT block -- `moveq r4,#0x01'
rt-thread\libcpu\arm\cortex-m4\context_gcc.S:140: Error: selected processor does not support `vldmiane r1!,{d8-d15}' in Thumb mode
rt-thread\libcpu\arm\cortex-m4\context_gcc.S:148: Error: thumb conditional instruction should be in IT block -- `bicne lr,lr,#0x10'
The command 'arm-none-eabi-as.exe' failed with exit code '1'.
--------------- Build Failed: 06/17/2019 17:27:55 ---------------
请问如何解决?
Show LessOften when I save a project, sections of the .cysem file get re-arranged, even though they're identical content, which makes the revision control difficult to read:
Can PSoC Creator be improved to not do this? maybe sort these lines alphabetically?
(Also it would be best if there were no .cysch binary files at all, and everything were just stored as plain text, so changes from different branches could be merged.)
Show LessI am currently just trying to write a simple SPI to transmit string from master to slave.
I would like to use SPIM_PutArray() to transmit data.
I know this PutArray function will put contents in the string into transmit buffer. I guess after PutArray, I can use SPIM_GetTxBufferSize() to read the tx buffer size. However, in debug mode, this buffer size is shown as 1 which should supposed to be 10. Are there any thing I miss here?
uint8 Tx_data[20] = {'a','b','c','d','e','f','g','h','i','j'};
SPIM_PutArray(Tx_data,10); //send data[] from master to slave
Tx_buffersize = SPIM_GetTxBufferSize();
Regards,
Simon
Show LessI have one question about spi master Read access
I try to read 256 bytes of data from flash
all data come out of flash correctly
but spi madule does not read all the data
here is my code
SPIM_Flash_Write(0x06); //Write Enable
CyDelay(1000);
SPIM_Flash_Write(0x03); //Read data byte
SPIM_Flash_Write(0x05); //add 00 Add_Rd_Hi
SPIM_Flash_Write(0x01); //sectR Add_Rd_Lo
SPIM_Flash_Write(0x00);
for(j=0; j<240; j++){ //240
SPIM_Flash_Write(0x00); //to generat read clk
// SPIM_Flash_ReadArraybl(dbg_array_flashdata,240); did not work
dbg_array_flashdata
For me, PSoC Creator 4.2 frequently crashes silently while doing mundane things like scrolling a source window.
There is no error message, it just disappears.
However, the Windows event log has some information (pasted below) that might be useful for the Cypress developers but I can't find a bug database or issue tracker.
Does anyone know where to log this?
--
Faulting application name: psoc_creator.exe, version: 0.0.0.0, time stamp: 0x5a85e2fd
Faulting module name: ucrtbase.dll, version: 10.0.17763.404, time stamp: 0x93e4fbe5
Exception code: 0xc0000409
Fault offset: 0x000a51eb
Faulting process ID: 0x31d0
Faulting application start time: 0x01d524ee02909094
Faulting application path: C:\Program Files (x86)\Cypress\PSoC Creator\4.2\PSoC Creator\bin\psoc_creator.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 92d0a492-2f66-464f-8bf8-fc3017c73c40
Faulting package full name:
Faulting package-relative application ID:
Environment:
PSoC Creator 4.2 (4.2.0.641)
Culture: English (United Kingdom)
OS Version: Microsoft Windows NT 10.0.17763.0
CLR Version: 4.0.30319.42000
--
Show Less