PSoC™ Creator & Designer Forum Discussions
Everytime I launch PSOC Designer I get "Adobe SVG Viewer" error and it indicates I need to install/reinstall. When I look for SVG viewer I find a 15 year old app for WIN98/XP. I would very much like to resolve this error so I can access pinout view and other.
Show LessI'm having trouble using the port interfaces in the PP_COM_Wrapper dll that PSOC Programmer provides. I am using a CY8CKIT-0529 PSOC 5LP prototyping kit. I am able to successfully open the port to the board and have verified that I can write to it using the USB-I2C bridge. However, when I go to close the port or check if the port is open the commands returns that the port is closed. For the closeport() command it returns -1 and "Port is not opened!" For the IsPortOpen() command, it returns a 0, which means the port is closed, and no error message. I can still write to the board via I2C after running both commands. Any feedback on why I am unable to close the port and why the program thinks the port is closed would be appreciated. Am I missing a use of the command?
Show LessWorking with Creator 4.3 has been going well until Windows 10 was upgraded over-night. Now the message "Can't Open CMSIS-DAP port" comes up whenever trying to compile. I've run the PSoC 4.3 repair and also the PSoC Programmer repair. But, no luck so far.
Any ideas as to how to get over this?
Show LessHi all,
I have a circuit that uses a battery type NCR18650PF with the relative charger mounted on breakout 03962A which uses the 4056E regulator.
I have to supply a CYBLE-012011-00 type module. I was thinking of two solutions.
The first: put the 03962A output, between out + and out-, a low consumption linear regulator, let's say 1.8V output. In this case I would have a current consumption as well as additional components to add.
Second solution: supply the CYBLE module directly between out + and out-, since the charging voltages are within the tolerance limits of the module. So I would have the advantage of not having added current consumption and components.
Can anyone give me some opinion?
Thank you!
Show LessHello.
I am introducing myself into the automotive field and I am working with PSoC4 + CY8CKIT-026. I am working with the LIN protocol and I have done some developments. I would like to know if is there any tool to use in PSoC Creator which allows me to test the MISRA-C Compliance.
Show LessHi, I can't seem to find the file referenced in Designing PSoC Creator Components with UDB Datapaths, Project #3 - Simple UART. Page 39 of the pdf. Can someone please point me in the right direction?
Thanks,
Mike
Show LessHi,
I'm following the example in "PSoC 4100S and PSoC 4100S Plus - PSoC 4 Architecture Technical Reference Manual (TRM)" (par.27.7), to write flash avoiding the blocking; infact the erase/write operation in flash required about 12-20ms, and during this time the CPU is stopped there.
The example shows the mode to avoid this blocking, in particular it is necessary to run code in sram (at least the routines used for the scope) also the interrupt service routine for SPC has to be in sram.
In my project (here attached), I was able to move the routine in sram, I define also the SPC interrupt and redirect its vector address, but this interrupt never happens, I try to read the register CPUSS SYSARG to check the error code, but with Miniprog3 debugger this register seems to be not readable (I see #######... instead of value), but I can access to CPUSS SYSREQ , there I read the last command sent (0x00000007) really with bit31 =0, the command had bit31=1, seems that it becomes 0 due to interrupt management, the question is who, where?.
In the original example is required to have Clock to 48MHz, but the device I'm using CY8C4125AXI-S433 has 24MHz as max value, could be it the problem?
Someone has had similar problems?
Thanks in advance
Renato
Show LessI am working with the CapSense demo kit and have found an error in the datasheet Document Number: 002-02479 Rev. *B
https://www.cypress.com/file/217516/download
I noticed the EEPROM was not working correctly and returned zero on reset. The datasheet points this out and proposes a fix. The problem, however, is the fix makes no sense:
sensorEmptyOffset = ((volotile int16 *))eepromEmptyOffset);
1. volotile should be volatile?
2. Parenthesis are a mess. Should it be sensorEmptyOffset = (volotile int16 *)(eepromEmptyOffset); ?
3. This throws an error "Incompatible pointer to integer conversion assigning to 'int16' (aka 'short') from 'volatile int16 *' (aka 'volatile short *')
Even if this line gets fixed, I'm not convinced this will allow reading from EEPROM. In the sample code, it was necessary to call Em_EEPROM_Read(~) which this code doesn't do. What is the correct fix to allow EEPROM to work? Thanks.
Show LessHi,
I would like to create .a. and folder is named CYPD3171-24LQXQ_pb.cydsn\src\mylib\libtest.c libtest.h
How to do create libtest.a by using PSoC Creater?
Thanks
Edward
Show LessAnd attempt to create Archive -
Search of forum indicates a path name with a single quote in it will produce build error. My
path has no such character in it.
Regards, Dana.
Show Less