PSoC™ Creator & Designer Forum Discussions
Hi All
As a result of not always working in the Creator IDE, say Droidedit while on the road, the CYDEV_CHIP_JTAG_ID is not always accessible in cyfitter.h
Is there a reference or include file with all PSoC parts and corresponding CYDEV_CHIP_JTAG_ID's?
Many Thanks
Greg
Hi,
i have some files with .cfg extension. In this file their are some defines. Now the problem is, that Creator does not index these files, and for large areas of my code, i have no syntax highlighting.
Is there a possibility to add file-extensions which should be indexed?
Thanks!
Oliver
Show LessI want to use CY8CMBR2110 but cannot determine from the datasheet if there is pwm support. There is a LED dimming option though. Please tell me if it can be connected to LCD pwm input.
Show LessThe recent post of http://www.cypress.com/blog/psoc-creator-news-and-information/psoc-creator-40-easy-access-kits-and-bluetooth-modules reminded me of a psoc creator feature request I thought of. Why not have psoc creator be able to change your project target device based off of the one you plugged in; either via mini-prog or kitprog? I often take a screenshot of the select debug target dialog box just to be able to go back to the device selector and pick that part.
Sometimes I change devices to try a different code sample on different hardware, or for early POC switch between dev kits and development boards. While it is possible to write down and remember the different chips, since the debugger knows what they are, it is way easier for the debugger to help you switch. Sometimes it can be hard to find the full part number in the dev-kit documentation. This would make it easier to get started with a dev-kit too.
Of course this shouldn't be automatic or anything, it just would be nice to be able to select your device by whatever you have attached at the time.
Show LessHi All
Our safety-critical product that comprises several PSoC 5LP devices as well as a Stellaris Luminary micro (LM3S9B96) communicates with each other via CAN transceivers. This product is in use in many locations and is not in prototype stage.
Until upgrading to PSoC Creator 4.0, including 2.x, 3.x versions, we have had zero issues with the CAN operation. Performing a seamless upgrade from 3.3 CP3 to 4.0, the CAN modules no longer operate as expected. I have attempted multiple 'do-that-upgrade-again' scenarios, making sure I've exited the Creator and restarted the application, and more, I continue to see total disruption of CAN traffic. I have deleted the component, and re-inserted it into the schematic, re-configured it to match the prior configuration. All my efforts have been in vain.
Because of this, I am forced to forego upgrading to PSoC Creator 4.0, and will remain behind at 3.3 CP3. I have not spent the time to dig into what the effects PSoC Creator 4.0 has on the CAN traffic itself, nor should I have to if PSoC Creator 4.0 is billed to be a straightforward, recommended-by-Cypress upgrade.
Has anyone else experienced this?
Show LessHi All
I am using PSOC creator 4, CY8CKIT-049-42xx with the Mark Hastings Strip Light Controller example and having success getting it to work with my 8x8 serial led array, but I have to make changes to some of the "Generated Source" files, StripLights.c, and StripLights_fonts.c and I save the changes and files. Then for unknown reasons, the files revert back to their original form discarding the changes I made to them. How do I prevent this from happening?
I can force it to revert the files using the Build_ Clean and build. It will always revert the files back to original state, breaking my fixes.
How do I change this behavior, or save the files in my new state?
Show LessHi,
I get some unnecessary and random file generated...i have attached the sreen shot of it..
and i also get error whenever i try to open project. the error is:
Error: prj.M0052: Unable to open the project ".\Experiment.cydsn\Experiment.cyprj": Could not find a part of the path 'C:\Users\astro\Dropbox\Amaresh IIA\Code\17_Filters\Experiment.cydsn\Experiment.cyprj'.
Error: prj.M0052: Unable to open the project "": Could not find a part of the path 'C:\Users\astro\Dropbox\Amaresh IIA\Code\17_Filters\Experiment.cydsn\Experiment.cyprj'.
Please suggest me some solution for it..
Thank you.
Show LessHi Everyone
I wondered why PSoC Creator 3 and now with Creator 4, the workspace freezes very frequently, it loses the cursor and this is repeated a few seconds again.
This is very annoying because sometimes occurs for 5 seconds long
This is more intense when I'm online. The first time it happened, it was a couple of weeks and it looked like someone was accessing remotely PSoC Creator because that the cursor was moving alone.
I was suspecting from my laptop but it work OK, I have have 16 GB of memory and 348 GB free on Hard disk.
Thank for any help about it.
Show LessHello,
I'm working my way through some tutorials and I found a project I want to open and build. I was sucessful in opening it once; however, ever since I closed it, it will no longer open. Every time I try it crashes the program. I deleted the entire directory and re-downloaded the files, but it still crashes.
Here is the git hub page of the project in question. https://github.com/LagunaMatada/GlowTime
When I did have it open it wouldn't build, but that's another story I guess. Maybe I can figure that out too?
When PSOC Creator crashes it gives me the option to copy to clipboard. Here is the result (using latest and fully updated creator sp2):
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.RuntimeModule.GetTypes()
at System.Reflection.Assembly.GetTypes()
at CyDesigner.Common.ProjMgmt.Customizer.CyCustomizerLoader.GetDllBasedCustomizerTypes(CyCompName compName, Assembly assembly, Type attributeType)
at CyDesigner.Common.ProjMgmt.Customizer.CyCustomizerLoader.GetDllBasedCustomizer(CyComponentMaster mst, Type attributeType)
at CyDesigner.Common.Db.CyS3Db.CyInst.GetCustomizerProviderImpl(CyCompName compName, CyInstBindContext ctx, String schName)
at CyDesigner.Common.Db.CyS3Db.CyInst.GetCustomizerProvider(CyCompName compName, CyInstBindContext ctx, CyInstCustomizerProvider& custProvider)
at CyDesigner.Common.Db.CyS3Db.CyInstCustomizerProvider.GetDesignWideComponent_v1(CyCompName compName, CyInstBindContext context)
at CyDesigner.PSoC.P3Fit.Common.DesignWideResources.CyComponentsModel.GetIsDesignWideComponent(CyComponentMaster master, CyCompName compName, CyPrjMgmtProjectPSoCExe proj, CyElabInstBindContext context)
at CyDesigner.PSoC.P3Fit.Common.DesignWideResources.CyComponentsModel.GetSelectedSupportedComponentsBySource()
at CyDesigner.PSoC.P3Fit.Common.DesignWideResources.CyComponentsModel.GetSelectedSupportedComponents()
at CyDesigner.Common.ProjMgmt.DWR.CyDWRMgr.<get_DwInsts>d__a.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at CyDesigner.Gde.ComponentUpdateTool.CyCutDocument..ctor(CyPrjMgmtProjectPSoCExe owningPrj)
at CyDesigner.Gde.ComponentUpdateTool.CyCutInputData..ctor(CyDesignerFramework fwk, IEnumerable`1 mgrs)
at CyDesigner.Gde.Common.CyGdePlugin.UpdateCutStatusBarIcon(Boolean writeOutputMsg)
at CyDesigner.Gde.Common.CyGdePlugin.mgr_CurrentWorkspaceChanged(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at CyDesigner.Common.Base.CyBasic.RaiseEvent(EventHandler eventToRaise, Object sender, EventArgs eventArgs)
at CyDesigner.Common.ProjMgmt.CyPrjMgr.OnCurrentWorkspaceChanged(EventArgs e)
at CyDesigner.Common.ProjMgmt.CyPrjMgr.set_CurrentWrkspc(CyPrjMgmtWrkspc value)
at CyDesigner.Common.ProjMgmt.CyPrjMgr.OpenWorkspace(CyPrjMgmtWrkspc workspace)
at CyDesigner.Common.ProjMgmt.CyPrjMgr.CheckandOpenWorkspace(String item)
at CyDesigner.Common.ProjMgmt.CyPrjMgr.OpenItem(String item)
at CyDesigner.Common.ProjMgmt.CyPrjMgr.LoadItemDeferred()
at CyDesigner.Common.ProjMgmt.CyPrjMgr.m_framework_Idled(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at CyDesigner.Common.Base.CyBasic.RaiseEvent(EventHandler eventToRaise, Object sender, EventArgs eventArgs)
at CyDesigner.Framework.CyDesignerFramework.ApplicationIdled(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at CyDesigner.Framework.Run.Main(String[] args)
We are currently experimenting with the CY8CKIT-022 CapSense Liquid Level Sensing Shield. So far we have been using the demo software as is, with CSD mode (self capacitance mode).
One problem we would like to overcome is the possibility of droplets of water or liquid accumulating on the sensors which are not submerged. This would result in measurement errors. The simplest step appears to be to use the CSX mode (mutual capacitance mode). This appears to reduce the impact of the water drops.
Looking at the API, to determine the liquid level, we would use the number of active sensors. The sensors are essentially buttons activated by the water level.
However to reduce the number of sensors we would like to use longer sensors and do some interpolation of the raw sensor data to determine the liquid level. For experimental purposes, we would like to use the CSX mode, but also use the raw sensor data? In the case of CSD there is access to the raw sensor data, but there doesn't appear to be in the case of CSX. I may be wrong, so I will keep looking.
The aim would be to determine if the effect of the water drops could be reduced using CSX combined with longer sensors and data interpolation.
Show Less