PSoC™ Creator & Designer Forum Discussions
I'd like to register PSOC creator and I typed my e-mail and password, but there is message "invalid username or password. What's the matter? I entered everything correctly
TIA
Vladimir Naumenkov
www.agat.by
Show LessLink errors for all Cy components on my project. This project was built with creator 2.2 a long time ago and was good. Copied code to new laptop 2 years later, installed 2.2, opened Ok, did not need to update components. All building steps complete up to linker, where the symbols (every cy component I referenced) are not found. See section below from output. I made sure the embedded keil is registered and expire date is confirmed in June 2020. At first, I thought Keil would mangle the libraries. The libraries referenced on the linker command link show below are verified to exist and do not seem corrupt. I found under 'lib' a keil lib called CyCompLib.LIB, and added that to the linker external lib and verified it shows up on the linker line in the output. Still not luck.
What could this be? What should I do to debug this? I do not see the keil LIBx51.exe anywhere, or I would dump the symbols in the libraries to verify they exist in the library. This is the embedded distribution of keil DP8051_Keil_903 for this particular PSOC chip.
Thanks for any hints on how to debug this build issue.
OUTPUT SNIPPIT:
API Generation ...
Dependency Generation ...
Clean Temporary Files ...
c51.exe .\cr_lib.c NOIV LARGE MODDP2 OMF2 VB(1) PR(.\DP8051_Keil_903\Debug\cr_lib.lst) CD DB NOIP "OT(2, Size)" INCDIR(Generated_Source\PSoC3) OJ(.\DP8051_Keil_903\Debug\cr_lib.obj)
c51.exe .\lcd_lib.c NOIV LARGE MODDP2 OMF2 VB(1) PR(.\DP8051_Keil_903\Debug\lcd_lib.lst) CD DB NOIP "OT(2, Size)" INCDIR(Generated_Source\PSoC3) OJ(.\DP8051_Keil_903\Debug\lcd_lib.obj)
WARNING: .\lcd_lib.c:165: 'name': unreferenced local variable
WARNING: .\lcd_lib.c:80: not every exit path returns a value
WARNING: .\lcd_lib.c:93: not every exit path returns a value
c51.exe .\main.c NOIV LARGE MODDP2 OMF2 VB(1) PR(.\DP8051_Keil_903\Debug\main.lst) CD DB NOIP "OT(2, Size)" INCDIR(Generated_Source\PSoC3) OJ(.\DP8051_Keil_903\Debug\main.obj)
WARNING: .\main.c:630: 'i': unreferenced local variable
Ax51.exe .\Generated_Source\PSoC3\CyBootAsmKeil.a51 NOCO MACRO DB PR(.\DP8051_Keil_903\Debug/CyBootAsmKeil.lst) CASE EP INCDIR(Generated_Source\PSoC3) OJ(.\DP8051_Keil_903\Debug\CyBootAsmKeil.obj)
Ax51.exe .\Generated_Source\PSoC3\cymem.a51 NOCO MACRO DB PR(.\DP8051_Keil_903\Debug/cymem.lst) CASE EP INCDIR(Generated_Source\PSoC3) OJ(.\DP8051_Keil_903\Debug\cymem.obj)
Ax51.exe .\Generated_Source\PSoC3\KeilStart.a51 NOCO MACRO DB PR(.\DP8051_Keil_903\Debug/KeilStart.lst) CASE EP INCDIR(Generated_Source\PSoC3) OJ(.\DP8051_Keil_903\Debug\KeilStart.obj)
c51.exe .\Generated_Source\PSoC3\I2C_1_SLAVE.c NOIV LARGE MODDP2 OMF2 VB(1) PR(.\DP8051_Keil_903\Debug\I2C_1_SLAVE.lst) CD DB NOIP "OT(2, Size)" INCDIR(Generated_Source\PSoC3) OJ(.\DP8051_Keil_903\Debug\I2C_1_SLAVE.obj)
c51.exe .\Generated_Source\PSoC3\I2C_1_MASTER.c NOIV LARGE MODDP2 OMF2 VB(1) PR(.\DP8051_Keil_903\Debug\I2C_1_MASTER.lst) CD DB NOIP "OT(2, Size)" INCDIR(Generated_Source\PSoC3) OJ(.\DP8051_Keil_903\Debug\I2C_1_MASTER.obj)
c51.exe .\Generated_Source\PSoC3\adc_AMux.c NOIV LARGE MODDP2 OMF2 VB(1) PR(.\DP8051_Keil_903\Debug\adc_AMux.lst) CD DB NOIP "OT(2, Size)" INCDIR(Generated_Source\PSoC3) OJ(.\DP8051_Keil_903\Debug\adc_AMux.obj)
LIBX51.exe TRANSFER '.\DP8051_Keil_903\Debug\CyBootAsmKeil.obj', '.\DP8051_Keil_903\Debug\cymem.obj', '.\DP8051_Keil_903\Debug\KeilStart.obj', '.\DP8051_Keil_903\Debug\I2C_1_SLAVE.obj', '.\DP8051_Keil_903\Debug\I2C_1_MASTER.obj', '.\DP8051_Keil_903\Debug\adc_AMux.obj' TO '.\DP8051_Keil_903\Debug\MCM_00300_Rev1.lib'
LX51.exe '.\DP8051_Keil_903\Debug\cr_lib.obj', '.\DP8051_Keil_903\Debug\lcd_lib.obj', '.\DP8051_Keil_903\Debug\main.obj', '.\DP8051_Keil_903\Debug\MCM_00300_Rev1.lib', 'C:\Program Files (x86)\Cypress\PSoC Creator\2.2\PSoC Creator\psoc\content\cycomponentlibrary\CyComponentLibrary.cylib\DP8051\DP8051_Keil_903\Debug\CyComponentLibrary.lib' , "C:\Program Files (x86)\Cypress\PSoC Creator\2.2\PSoC Creator\lib\DP8051\DP8051_Keil_903\Debug\CyCompLib.LIB" TO '.\DP8051_Keil_903\Debug\MCM_00300_Rev1.omf' PR(.\DP8051_Keil_903\Debug\MCM_00300_Rev1.map) IX CODE DW(16) RU CL(XDATA(X:0x0000-X:0x1FFF)) CL(CODE(C:0x0000-C:0xFFFF)) CL(CONST(C:0x0000-C:0xFFFF))
*** ERROR L127: UNRESOLVED EXTERNAL SYMBOL
SYMBOL: cr_Read
MODULE: .\DP8051_Keil_903\Debug\cr_lib.obj (CR_LIB)
*** ERROR L127: UNRESOLVED EXTERNAL SYMBOL
SYMBOL: _cr_Write
MODULE: .\DP8051_Keil_903\Debug\cr_lib.obj (CR_LIB)
*** ERROR L128: REFERENCE MADE TO UNRESOLVED EXTERNAL
SYMBOL: cr_Read
MODULE: .\DP8051_Keil_903\Debug\cr_lib.obj (CR_LIB)
ADDRESS: 10017ECH
*** ERROR L128: REFERENCE MADE TO UNRESOLVED EXTERNAL
SYMBOL: _cr_Write
MODULE: .\DP8051_Keil_903\Debug\cr_lib.obj (CR_LIB)
ADDRESS: 10017F7H
*** ERROR L128: REFERENCE MADE TO UNRESOLVED EXTERNAL
SYMBOL: cr_Read
MODULE: .\DP8051_Keil_903\Debug\cr_lib.obj (CR_LIB)
ADDRESS: 10017AAH
*** ERROR L128: REFERENCE MADE TO UNRESOLVED EXTERNAL
SYMBOL: _cr_Write
MODULE: .\DP8051_Keil_903\Debug\cr_lib.obj (CR_LIB)
ADDRESS: 10017B9H
Show LessIn a PSoC 6 project, I have some shared header files which have sections for the two different cores, enabled or disabled by checking the CY_CPU_CORTEX_M0P and CY_CPU_CORTEX_M4 macros.
It seems that in the development environment, this always resolves to the M0+, even when the file being edited is for the M4. This causes the IDE to incorrectly display error flags even though the code builds without errors.
How does one get around this?
Thanks.
Show LessI have a problem launching/using PSoC Creator. The installation processes succeeds and I am able to update all the components (Peripheral Driver Library and PSoC Programmer). When I try to launch PSoC Creator the programs just hangs loading the CyPPDeviceIOPlugin. Eventually (approximately 30 min later), the program will load and work normally, expect when using any kind of USB feature. If a USB feature is used, the program will hang again. I have tried uninstalling and reinstalling, full OS wipe all without any success. The only workaround I found was to run PSoC Creator in a VirtualBox VM and connect the USB device to the guest by using the VirtualBox OHCI controller. For whatever reason that seems to workaround the issue. I am starting to suspect the graphics driver but I am not sure why that would cause any sort of conflict. Has anybody experienced this problem? Does anybody have any suggestions?
--- System Information ---
OS: Windows 10 (10.0.16663 Build 17763)
Motherboard: ASUS Hero X (BIOS 1801 11/5/2018)
Processor: Intel i7-8700k
Graphics: NVIDIA GTX 1080 Ti (GeForce Game Ready Driver 425.31)
Show Less
Apologies if there is a solution posted, unable to find via forums or searching online.
Cannot open PSOC Creator due to “cyprjmgr has stopped working” error.
Trying to open a project or PSOC creator executable results in nothing, no start-up window, no stalled EXE in task manager. Uninstalled, restarted, and reinstalled PSOC Creator 3.3 SP2, nearing the end of installation the follow error popped up.
Opening C:\Program Files (x86)\Cypress\PSoC Creator\4.2\PSoC Creator\bin\cyprjmgr.exe results following cmd prompt text:
Unhandled Exception: System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.BadImageFormatException: Could not load file or assembly 'System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The module was expected to contain an assembly manifest.
at System.Configuration.ExceptionUtil.WrapAsConfigException(String outerMessage, Exception e, String filename, Int32 line)
at System.Configuration.BaseConfigurationRecord.Init(IInternalConfigRoot configRoot, BaseConfigurationRecord parent, String configPath, String locationSubPath)
at System.Configuration.RuntimeConfigurationRecord.Create(InternalConfigRoot configRoot, IInternalConfigRecord parent, String configPath)
at System.Configuration.Internal.InternalConfigRoot.GetConfigRecord(String configPath)
at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem()
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.PrivilegedConfigurationManager.GetSection(String sectionName)
at System.Diagnostics.DiagnosticsConfiguration.GetConfigSection()
at System.Diagnostics.DiagnosticsConfiguration.Initialize()
at System.Diagnostics.DiagnosticsConfiguration.get_IndentSize()
at System.Diagnostics.TraceInternal.InitializeSettings()
at System.Diagnostics.TraceInternal.get_UseGlobalLock()
at System.Diagnostics.TraceInternal.Fail(String message)
at CyDesigner.Common.Base.CyTypeMapper.PvtDoInit(Object initObj)
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)
Deleted APPDATA for PSoC Creator and did not resolve.
Unaware of any local changes to computer that could have caused this, no OS update in recent days.
Updated to the latest PSOC Creator 4.2 and did not resolve.
Any help or direction would be appreciated.
Thank you,
-Neil
Show LessHello,
I have trouble with PDL 3.1 and BLE example, the CE217639 "Heart Rate Server".
I was able to compile and run the example without any issue under PSoC Creator 4.2 (4.2.0.641) and PDL 3.0.4, on a CY8CKIT-062-BLE Rev *B.
When I switched to PDL 3.1, the example did compile, but not run. I noticed some changes in the shared files (e.g. IPC configuration has moved) etc.
However, since there is no compile error, and I did not succeed in running a debug session (I guess during startup the program does not even run up to main() on any of the two cores), it is impossible for me to pinpoint the error.
Can anyone suggest what to do?
Of course, I could go back to PDL 3.0.4, however, I thought that in view of switching to Modus Toolbox at some point, it would be a good idea to give PDL 3.1 a try.
Regards,
SLE
Show LessHello!
I had a couple questions about PSoC Creator features regarding configurations.
As I'm sure we're all familiar with, a workspace in Creator gives you two configurations to play with. Release and Debug. I was hoping it may be possible to add more configurations to the list to enable/disable features for specific builds.
For example I have two firmwares written for PSoC 5 that are extremely similar, but not identical and have slightly differing code depending on the target board.
I've run into this in say, MPLAB X and I can add preprocessors to a custom build configuration, and simply #ifdef the preprocessor to disable/enable different blocks of code. I can't seem to find anything similar in Creator.
Related to this, it would also like to be able to enable/disable hardware components via the same method. The current project I'm working on has a single target board, but depending on what's plugged in will require differing PSoC hardware components. What I'd like to do is place the different configurations of the hardware in their own pages and Disable/Enable them programmatically. Ideally I'd like to toggle which pages are enabled/disabled via a preprocessor define, which I could change depending on in each build configuration.
It looks like item #7 in this thread gets me close: Are these rubbishy ideas? but not quite all the way there. The only missing piece is being able to add custom build configurations.
Is there anything currently in the Creator feature set (or upcoming) that would let me add a custom configuration? These two hardware configs are so similar I'd like to avoid to have to maintain two different repositories. I'd much rather be able to select what I'm building for via custom configuration and keep it all in one project.
Thanks in advance for any tips!
Show LessHello @ll,
with PSoC Creator 4.2 I managed the MagSense example for 4700S controllers to run on the EVA board CY8KIT-148.
But when I try to get our own sensors at the IO Header working, there are problems during pin reconfiguration.
Original example
Pin configuration for IO Header
All port 2 pins seems to be fixed to a pin via directives or controlfiles. But in the project are neither direcitves nor any control file.
With the 2 errors I'm not able to use our external sensors via IO header.
Can anybody give a hint, please, where those constraints are specified and how to remove them.
I would appreciate any help.
TIA
Regards,
Olaf
Show Less