PSoC™ Creator & Designer Forum Discussions
Maybe it's a new bug or maybe this is how it's been all the time. I did a search in the forum but nothing showed up.
So I have a project and I do a "Select Device", when the window pops up, I apply filters to narrow down my choices of chips.
Once I'm happy with my filter I click the "Auto Select" button so it will check what devices will support my project.
I wa expecting that it will only check for the devices in the list after the filters are applied, but it checks all of them regardless of the filter. Meaning that It can take a long time until it checks all of them so I can figure out the ones from my list.
After 30 minutes it's just done with the PSoC 3 devices and I had them filtered out. It might take another hour or more to do them all.
Is this the intended way to operate or is it a bug?
Thanks.
Show LessI have a CY8C3866 project using the standard 2x16 parallel char LCD (on port6) & a number of other components working fine on TQFP-100 part 030 board. I've copied that project and am trying to remove the LCD, replace with an I2C panel that I have all drivers for & is working fine in other projects, and change to the 64-QFN. Both projects are in the same workspace (Creator 3 comp pack 7/Win7 Pro/ i7). I copy the project, rename, select the 64-QFN device, delete the parallel LCD from the code and TopDesign, add I2C fixed master to the TopDesign. The old LCD will not leave the pins view, the new I2C master will not show up in the pins view. A clean build does not correct. I know if I start a new project from scratch this will all work fine.
I have never run into this before on a copied project within the same workspace. What am I missing?
Thanks - Steve
Show LessWe share the same source code over several different PSoC devices (PSoC 3 and PSoC 5) and use a varying amount of features. For some debug functions, I would like to test (precompiler - #ifdef) if in the current project a given resource is available. For instance, whether Port3 or Port 5 exists (on the package of course, I understand that the registers and hardware might be even there, just not externally connected), would be useful to a debugging tool that displays the status of each port.
cydevice.h and cypins.h define all the registers, I have checked also in designs that use a package where those pins don't exist.
I think the fitter must have a knowledge base for each device/package?
There is CYDEV_SRAM_SIZE and CYDEV_EE_SIZE, so for some resources the software can find the sizes.
But for instance,
CYDEV_IO_PC_PRT5_SIZE 0x00000008u
for a CY8C3866LTI-067, the 48 pin QFP package, that does not have port 5.
Andreas
Show LessHi,
In my program I write and read to and from PSoC5 EEPROM.
But during read I found unexpected values. The problem is now that I don't know if the Write or the Read is going wrong. For that reason I want to inspect EEPROM to see what was written.
I search everywhere but could not find how to inspect EEPROM memory during debug.
Please help!
Thanks!
Rob
Show LessI have a custom board with PSoC5 using USBUART. In the past, I got this board version working and enumerating just fine. Today, I pulled out a second board made at the same time as the first one. I programmed the PSoC5. I inserted the USB plug into my PC, and things aren't behaving.
Specifically, in Device Manager I see the board identified as "Unknown Device". I tried to update the driver, providing my ...Generated_Source\PSoC5 folder name. Windows told me the driver was up-to-date. Nevertheless, it's not installed properly. The driver is from Microsoft, date 6/21/2006, version 6.1.7601.18328.
Meanwhile, I still have the original board that works. I plug its USB cable into my PC and it comes up just fine as COM9 in the Device Manager. It says it's using a driver from Cypress, date 3/5/2007, version 2.0.0.0.
What step did I forget? How do I force windows to use the Cypress driver?
I'm using Win7 SP1, 64-bit, 32GB ram, Intel I7-2600 3.4GHz
Show LessHi,
I`m wondering if there is GUIDRV_FlexColor for emWin library in psoc. I couldn`t find .C and .H file in that folder.
based on segger documentation, this driver can support RA8875 and that makes the life so easy for Psoc users. because most of chinese LCDs in the market which are cheap ofcourse, are using this controller. (http://www.segger.com/emwin-guidrv-flexcolor.html)
I found this driver for Emwin Pack from ST for their arm products. :
http://www.st.com/web/catalog/tools/FM147/CL1794/SC961/SS1743/PF259225?sc=stemwin#
here is two question:
1: does Emwin library from psoc support this driver? if so how can I have this driver files?
2: if not, is it possible to make the driver offered by ST work for Psoc? I think it will be fast job for your technical professionals who know deep about EmWin library and graphical interface.
Thanks
I find many had these CMSIS related issues raised in these forums but unfortunately I don't see any solution yet.
I need to use ARM CMSIS DSP Libs on pSoC5LP.
ARM provides these libs for all Cortex-M3 devices which one can get from :
It also provides a uvproject file to get all these Lib sources compiled on their MDK as well GCC software toolchains.
I have compiled these as a Lib file for GCC to be used for linking on pSoc Creator using the ARM's uVision IDE set to compile for GCC. The compilation and library creation were succesful.
Since Cypress supports mainly GCC Toolchain on pSoC Creator, I am trying to create an empty project on my pSoC5LP kit, using the Cypress provided GCC 4.7.3 Tools for software using a simple example provided for CMSIS DSP Lib 'arm_class_marks_example'
The linking of this CMSIS DSP Lib does not work on pSoC Creator and it gives undefined reference errors. It does not link these lib functions eventhough I have setup all the paths etc correctly.
I have included an archive of this project.
Appreciate any help in resolving these issues related to use of CMSIS DSP Lib on pSoC Creator.
Thanks in advance!
Show LessI have a problem on communication by SPI.
I observe the following behavoir: the transmission is OK when I send 2 bytes together, but when I send them one by one the last bit of the first byte is corrupted. There is a source code:
uint8_t reg1 = 0x25;
uint8_t Value = 0;
SS_1_Write(0);
// Write reg (reg1, value = 0x10)
SPIM_1_WriteTxData(reg1 & 0x7F);
SPIM_1_WriteTxData(0x10);
while ((SPIM_1_ReadRxStatus() & SPIM_1_STS_RX_FIFO_NOT_EMPTY) == 0)
;
Value = SPIM_1_ReadRxData(); // dummy read to remove byte from buffer
while ((SPIM_1_ReadRxStatus() & SPIM_1_STS_RX_FIFO_NOT_EMPTY) == 0)
;
Value = SPIM_1_ReadRxData(); // dummy read to remove byte from buffer
SS_1_Write(1);
SS_1_Write(0);
// Read reg back
SPIM_1_WriteTxData(reg1 | 0x80);
SPIM_1_WriteTxData(0xFF); // dummy write to synchronize
while ((SPIM_1_ReadRxStatus() & SPIM_1_STS_RX_FIFO_NOT_EMPTY) == 0)
;
Value = SPIM_1_ReadRxData(); // dummy read to remove byte from buffer
while ((SPIM_1_ReadRxStatus() & SPIM_1_STS_RX_FIFO_NOT_EMPTY) == 0)
;
Value = SPIM_1_ReadRxData(); // readen reg value
SS_1_Write(1);
This code works fine. But when I move SPIM_1_WriteTxData(0xFF) in register value reading to place after reading dummy byte I receive wrong value:
// Read reg back
SPIM_1_WriteTxData(reg1 | 0x80);
while ((SPIM_1_ReadRxStatus() & SPIM_1_STS_RX_FIFO_NOT_EMPTY) == 0)
;
Value = SPIM_1_ReadRxData(); // dummy read to remove byte from buffer
SPIM_1_WriteTxData(0xFF); // dummy write to synchronize
while ((SPIM_1_ReadRxStatus() & SPIM_1_STS_RX_FIFO_NOT_EMPTY) == 0)
;
Value = SPIM_1_ReadRxData(); // readen reg value is WRONG
Then after some actions I found that the readen value is equal to value from register with address (reg1 - 1). This behavoir repeats for other register pairs.
Why does this happen?
I have configured SPIM component for mode (CPHA = 1, CPOL = 1), 8 Data Bits, MSB First. The external clock frequency is 2MHz. SS-pin is controlled by software.
Show Less